Issue 21655 - Set an official GSI file for translators
Summary: Set an official GSI file for translators
Status: CLOSED WONT_FIX
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: hans_werner67
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-24 12:20 UTC by ohallot
Modified: 2013-08-07 15:34 UTC (History)
3 users (show)

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


Attachments
pt-BR GSI file extracted from OO 1.1 (414.11 KB, application/octet-stream)
2003-10-24 12:27 UTC, ohallot
no flags Details
extracted strings in pt-BR from oo 1.1 (432.02 KB, application/octet-stream)
2003-10-24 12:30 UTC, ohallot
no flags Details
Patch suggested by Sergiy Kudryk (513 bytes, application/x-tar)
2003-12-16 17:07 UTC, ohallot
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description ohallot 2003-10-24 12:20:42 UTC
I have been contributing to OO for pt-BR since jan 2002, and I have developed
skills to build OO from the sources files. From OO 1.0.3 to 1.1, I have
succesively extracted and merged translated strings into the code to catch the
additions and correct translations errors.

I have been struggling with this process because on each new milestone, I have a
different GSI file, and pinpointing the differences is not an easy job. AFAIK,
among the RC's before 1.1, the localize/transex3 broke and was fixed back.

Now on 1.1 release I extracted the strings in en-US and got 25,639 lines while
in the same source the pt-BR has 25,679 lines.

It seems that the difference is in module offcfg, which is not visible to the
outside world. However it is litteraly finding a 40 needles among 25679 straws.
Also I dont understand why pt-BR has more strings than en-US.

For me, the solution is to have an "Official GSI File", "The-Real-One", located
in the CVS repository, and updated at each milestone. This file must contain the
valid strings in en-US. This will take out of my responsibility to extract the
strings at each milestone and risk to get lost if a bug raises in
Localize/transex3. Bear in mind that handling GSI files are not a trivial task
especially for edition. It is a clumsy file.

Olivier Hallot
Comment 1 ohallot 2003-10-24 12:27:10 UTC
Created attachment 10604 [details]
pt-BR GSI file extracted from OO 1.1
Comment 2 ohallot 2003-10-24 12:30:12 UTC
Created attachment 10605 [details]
extracted strings in pt-BR from oo 1.1
Comment 3 ohallot 2003-10-24 12:31:32 UTC
Well,
The correct attachments are en26n = english, br26n= Brazilian portuguese.
Olivier
Comment 4 pavel 2003-10-24 19:13:59 UTC
The problems you met are bugs in localize already filled in IZ. See
bugs where I'm reporter on in CC:.
Comment 5 stefan.baltzer 2003-11-04 11:47:21 UTC
SBA: Reassigned to Nils.
Comment 6 nils.fuhrmann 2003-12-15 09:27:10 UTC
Regarding a official gsi file: We have started working on some additional
infrastructure for OOo to download and upload gsi files into the translation
database which is used to collect strings out of the code and reflect them back
to the code, once they are translated.
Jörg Jahnke works on this, I would suggest to close this task.

Comment 7 ohallot 2003-12-16 17:07:59 UTC
Created attachment 11981 [details]
Patch suggested by Sergiy Kudryk
Comment 8 ohallot 2003-12-16 17:10:45 UTC
OOPs!!! this attchment is not for this bug. Please disregard.
Comment 9 pavel 2004-05-04 11:42:36 UTC
jj: what is the status of the work on GSI for external people?
Comment 10 epost 2004-06-28 15:15:36 UTC
Sorry for the late reply as I lost track of this issue even though I received an
email notification :-(.
As for the status, it's still as Nils described earlier that we have some plans
about such a tool, similar to the Environment Information System which can now
be used outside the Sun network. But currently I could not even give you a due
date when such a solution might be in place.
Comment 11 pavel 2004-06-28 19:07:32 UTC
OK, so please kepp this issue.

No problem if it is not to be available soon.
Comment 12 epost 2004-07-27 09:39:40 UTC
Frank, could you please take over
Comment 13 hans_werner67 2004-08-26 12:45:34 UTC
change component to tools
Comment 14 hans_werner67 2004-08-26 12:46:12 UTC
set target DevTools
Comment 15 ivo.hinkelmann 2005-09-07 12:32:24 UTC
Pavel, can we close this one also ? Is imho also solved by the po / pot variant.
Comment 16 ivo.hinkelmann 2005-09-07 12:37:23 UTC
ihi cc'ed
Comment 17 pavel 2005-09-07 12:47:46 UTC
yes, closing.
Comment 18 pavel 2005-09-07 12:49:03 UTC
.