Issue 21516 - need weekly incremental gsi's
Summary: need weekly incremental gsi's
Status: CLOSED WONT_FIX
Alias: None
Product: Internationalization
Classification: Code
Component: www (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: hans_werner67
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-21 19:47 UTC by Martin Hollmichel
Modified: 2013-08-07 15:00 UTC (History)
4 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2003-10-21 19:47:39 UTC 
we need periodic informatation about changed strings, more inforomation in our
next brown bag meeting.
Comment 1 Martin Hollmichel 2003-10-21 19:48:43 UTC 
set target milestone.
Comment 2 pezz 2003-10-21 21:09:24 UTC 
Weekly incremental GSIs aren't very useful. People who use GSI-s, 
translators, doesn't do OOo stuff 5 days a week. They just need 
somehow to know what is changed in strings about month or so before 
every new version is released so they could make needed changes to 
translation and test it. Also they need to be sure that strings 
doesn't change for some period before release so they can work on 
translation and know that they will not find any surprises when 
release happens. It means hard string freezes with no exceptions.
Comment 3 nils.fuhrmann 2003-10-22 07:14:11 UTC 
What I like to have in place on the way to 2.0 is a web frontend which
allows downloading and uploading gsi files and having the incremental
files based on the status within the underlaying db.
Yes, lets have a brown back meeting for this ;-)
Comment 4 nils.fuhrmann 2003-12-01 14:21:39 UTC 
Jörg, as we already have started to set up some public available
infrastructure to better allign OOo and Sun workflow, I like t see
this requets within your responibility. Please keep a gsi im/export
mechanism on your list in a reasonable time frame. Thanks!
I have cc't Paval on this to keep him informed about the enhancements
we are driving for the l10n process.
Comment 5 nils.fuhrmann 2003-12-01 14:22:39 UTC 
Reassigned
Comment 6 epost 2004-01-06 08:51:05 UTC 
This is not a defect but a feature request!
Comment 7 epost 2004-07-27 08:59:59 UTC 
Frank, could you please take over.
Comment 8 hans_werner67 2004-08-09 08:36:18 UTC 
set target milestone OOo-later, agreed by JJ
Comment 9 pavel 2005-09-07 09:08:02 UTC 
Ivo: what do you think about this issue?

i think we can close it now, because we have POT files for every milestone.
Comment 10 pezz 2005-09-07 09:46:15 UTC 
yes, the problem is out of question now
Comment 11 ivo.hinkelmann 2005-09-07 12:33:28 UTC 
ok, I agree that this one is solved by pot / po
Comment 12 ivo.hinkelmann 2005-09-07 12:33:51 UTC 
-> closed