Re: [l10n-dev] IMPORTANT: Translation Schedule for 2.4 - 2nd handoff

[Aijin Kim]

Hi Javier,

Javier SOLA wrote:

Dear Aiin,

Thanks, but Khmer is not working through Pootle. The data there is 
very old, and with many errors. We will file our own issue when we 
finish the translation.
I see. So do you mean that Khmer doesn't have to be uploaded to Pootle 
on the current stage?


Thanks,
Aijin



Regards,

Javier

Aijin Kim wrote:

Hi Pootle users,

Six languages in Pootle have just been submitted via IssueTracker and 
the issue numbers are:


Catalan: i83973
Italian: i83116
Spanish: i83095
Khmer: i83976
Kurdish: i83974
Occitan-lengadocian: i83975

For Italian, Spanish and Khmer languages, there are still several 
gsicheck errors.


The leaders of Italian, Spanish and Khmer communities,
Can you please check the gsicheck log file on each issue, fix the 
errors and submit revised file by COB today?


Thanks,
Aijin

Aijin Kim wrote:

Dear Pootle users,

Please note that Pootle will be down from 11/26- 29 for preparing 
the 2nd hand-off.


Regards,
Aijin


Rafaella Braconi wrote:

Dear Translators/Localizers,

here some updates on the translation schedule as well as volume for 
the second and last translation round for the OpenOffice.org 2.4 
Update release.
All details can be found at: 
http://wiki.services.openoffice.org/wiki/Translation_for_2.4


Here below the highlights:

Translation schedule:

- final delivery deadline has been extended one week to December 20th
- sdf files for translation will be available on November 29th
- Pootle content will be updated November 26th to November 29th - 
no work on Pootle during the updating process.


Translation volume for the 2nd handoff for all teams who have 
completed translation by November 26th:


- GUI: approx. 1,200 words
- Help: approx. 13,800 words

Teams who jointly work on localization with Sun/Globalization are:

#  Dutch Community
# French Community
# Germanophone Community
# Italian Community
# Spanish Community
# Brazilian Community
# Swedish Community
# Russian Community
# Chinese Community (for Simplified Chinese)
# Korean Community
# Japanese Community

Please let me know by Friday the volume you can commit to translate 
by December 20th so that I can arrange the translation work 
accordingly.


Kind Regards,

Rafaella
P.S. I still have some giveaways to give you  :-) . Just send an 
email directly to me, subject *OOo Giveaways*, indicating your 
name, address and language you contributed to



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [l10n-dev] IMPORTANT: Translation Schedule for 2.4 - 2nd handoff

[Javier SOLA]

Dear Aiin,

Thanks, but Khmer is not working through Pootle. The data there is very 
old, and with many errors. We will file our own issue when we finish the 
translation.


Regards,

Javier

Aijin Kim wrote:

Hi Pootle users,

Six languages in Pootle have just been submitted via IssueTracker and 
the issue numbers are:


Catalan: i83973
Italian: i83116
Spanish: i83095
Khmer: i83976
Kurdish: i83974
Occitan-lengadocian: i83975

For Italian, Spanish and Khmer languages, there are still several 
gsicheck errors.


The leaders of Italian, Spanish and Khmer communities,
Can you please check the gsicheck log file on each issue, fix the 
errors and submit revised file by COB today?


Thanks,
Aijin

Aijin Kim wrote:

Dear Pootle users,

Please note that Pootle will be down from 11/26- 29 for preparing the 
2nd hand-off.


Regards,
Aijin


Rafaella Braconi wrote:

Dear Translators/Localizers,

here some updates on the translation schedule as well as volume for 
the second and last translation round for the OpenOffice.org 2.4 
Update release.
All details can be found at: 
http://wiki.services.openoffice.org/wiki/Translation_for_2.4


Here below the highlights:

Translation schedule:

- final delivery deadline has been extended one week to December 20th
- sdf files for translation will be available on November 29th
- Pootle content will be updated November 26th to November 29th - no 
work on Pootle during the updating process.


Translation volume for the 2nd handoff for all teams who have 
completed translation by November 26th:


- GUI: approx. 1,200 words
- Help: approx. 13,800 words

Teams who jointly work on localization with Sun/Globalization are:

#  Dutch Community
# French Community
# Germanophone Community
# Italian Community
# Spanish Community
# Brazilian Community
# Swedish Community
# Russian Community
# Chinese Community (for Simplified Chinese)
# Korean Community
# Japanese Community

Please let me know by Friday the volume you can commit to translate 
by December 20th so that I can arrange the translation work 
accordingly.


Kind Regards,

Rafaella
P.S. I still have some giveaways to give you  :-) . Just send an 
email directly to me, subject *OOo Giveaways*, indicating your name, 
address and language you contributed to



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [l10n-dev] Guidelines for translating documentation

[Ain Vagula]

Jordi Mas kirjutas:

Hello folks,

Do we have any Guidelines for translating the OpenOffice.org documentation?

For example, what to do with the tags embedded in the translations (what 
has to be translated or not).


Regarding quality control I understand we have to a a gsicheck -c before 
committing translations. Anything else?


Any help or experiences in this area would be appreciated.

Regards,



Found finally:
http://documentation.openoffice.org/online_help/localization/LocalisationguideOOo2.pdf
Was hard to search 'cause of typo in file name...
;)

ain

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [l10n-dev] Guidelines for translating documentation

[Ain Vagula]

Jordi Mas kirjutas:

Hello folks,

Do we have any Guidelines for translating the OpenOffice.org documentation?

For example, what to do with the tags embedded in the translations (what 
has to be translated or not).


Regarding quality control I understand we have to a a gsicheck -c before 
committing translations. Anything else?


Any help or experiences in this area would be appreciated.

Regards,



There was a document written by Frank Peters at
http://documentation.openoffice.org/online_help/LocalisationguideOOo2.pdf

I cannot find it any more... Frank?

ain

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[l10n-dev] Guidelines for translating documentation

[Jordi Mas]

Hello folks,

Do we have any Guidelines for translating the OpenOffice.org documentation?

For example, what to do with the tags embedded in the translations (what 
has to be translated or not).


Regarding quality control I understand we have to a a gsicheck -c before 
committing translations. Anything else?


Any help or experiences in this area would be appreciated.

Regards,

--

Jordi Mas i Hernàndez, HomePage http://www.softcatala.org/~jmas/
Bloc personal http://www.softcatala.org/~jmas/bloc/
Planeta Softcatalà: http://www.softcatala.org/planet/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [l10n-dev] TMX files (List of UI strings/translation)

[Jean-Christophe Helary]

On 28 nov. 07, at 19:21, Reiko Saito wrote:


Hi JC,

I understood your point.
To increase the leverage, we may be able to lower the lowest match- 
rate,

or will use this tmx just for reference and search a certain string
as a file... what do you think ?


It is possible to use the sdf directly and not the PO file as source.
For that it is necessary to do a few things to the sdf file as I  
described sometimes in the summer if I remember well. Simply put, it  
amounts to that:


Basically the sdf comes as pairs of lines:
"string in English+meta data"
"string in target language+meta data"

The format for each line is very close to CSV so the idea is to:

1) convert each pairs to:
"string in English+meta data" "string in target language+meta data"
2) import that into OOo and to select the columns that correspond to  
"string in English".
3) put that into a text file for use as source in OmegaT or anything  
else with the TMX provided by Rafaella as reference.


All this is done with a text editor and a few regex search/replace.

Once the translation is completed, it is pasted into the "string in  
target" part of the CSV file, the file is converted back to a 2 lines  
format and the result is delivered.



Can anyone generate csv file from these tmx ?


It is very easy but now that I am seeing the contents, I wonder it is  
is a good idea. Look at one :




The query already exists. Do you want to delete 
it?


このクエリはすでに存在します。削除します 
か。





Obviously this is a full sentence and not a menu item. So maybe  
Rafaella's idea of using Sun Gloss for glossary reference is better  
after all ?


Anyway, just in case we need the conversion it is not a very complex  
task to do that by hand with a few regex. I'll do it for the Japanese  
group if you want.


Jean-Christophe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [l10n-dev] TMX files (List of UI strings/translation)

[Jean-Christophe Helary]

On 28 nov. 07, at 19:55, Rafaella Braconi wrote:

Can anyone generate csv file from these tmx ?
I need the list of User Interface translation to use as the glossary
for OmegaT.



why don't you use the glossary available in Sun Gloss?


Is there a real equivalence between the UI files and Sun Gloss ? I  
think the point is to get only the UI strings, not the rest of the  
glossary.



Jean-Christophe

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [l10n-dev] TMX files (List of UI strings/translation)

[Rafaella Braconi]

Hi Reiko,

Reiko Saito ha scritto:

Hi JC,

I understood your point.
To increase the leverage, we may be able to lower the lowest match-rate,
or will use this tmx just for reference and search a certain string
as a file... what do you think ?

Can anyone generate csv file from these tmx ?
I need the list of User Interface translation to use as the glossary
for OmegaT.

why don't you use the glossary available in Sun Gloss?

Rafaella


Regards,

-Reiko

Jean-Christophe Helary wrote:


On 28 nov. 07, at 10:24, Jean-Christophe Helary wrote:

I forgot to add the following:

1) The TMXs contain all the XML code escaped with "\" as per the sdf 
file: they are not "proper" TMX level2 files
2) Since they conform to the sdf contents they can be used directly 
to translate it (either in OpenLanguageTools or OmegaT)


The problem is that translators who use such tools (or any TMX 
supporting software) _do not_ work with the sdf file but with a PO 
file created from the sdf.


The PO file adds another layer of escapes, which makes matches from 
the sdf based TMX even harder to find.


For example, the TMX contains the following translation unit:

\Title\: String expression displayed 
in the title bar of the dialog box.


Which corresponds to the following sdf string:

\Title\: String expression displayed in the title bar 
of the dialog box.


(you see how the sdf format escapes the "<" and ">")

A tool that uses the TMX would get a match between this string and a 
sdf file that contains a similar string.


But the PO that will be our sources will come as:

\\Title\\: String expression displayed in the title 
bar of the dialog box.


So the matches between the TMX and the PO files will be of lower 
quality because of the "noise" added by the extra escapes.


I hope what I just wrote means something to somebody here :)

Jean-Christophe Helary

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [l10n-dev] TMX files (List of UI strings/translation)

[Reiko Saito]

Hi JC,

I understood your point.
To increase the leverage, we may be able to lower the lowest match-rate,
or will use this tmx just for reference and search a certain string
as a file... what do you think ?

Can anyone generate csv file from these tmx ?
I need the list of User Interface translation to use as the glossary
for OmegaT.

Regards,

-Reiko

Jean-Christophe Helary wrote:


On 28 nov. 07, at 10:24, Jean-Christophe Helary wrote:

I forgot to add the following:

1) The TMXs contain all the XML code escaped with "\" as per the sdf 
file: they are not "proper" TMX level2 files
2) Since they conform to the sdf contents they can be used directly to 
translate it (either in OpenLanguageTools or OmegaT)


The problem is that translators who use such tools (or any TMX 
supporting software) _do not_ work with the sdf file but with a PO file 
created from the sdf.


The PO file adds another layer of escapes, which makes matches from the 
sdf based TMX even harder to find.


For example, the TMX contains the following translation unit:

\Title\: String expression displayed in 
the title bar of the dialog box.


Which corresponds to the following sdf string:

\Title\: String expression displayed in the title bar of 
the dialog box.


(you see how the sdf format escapes the "<" and ">")

A tool that uses the TMX would get a match between this string and a sdf 
file that contains a similar string.


But the PO that will be our sources will come as:

\\Title\\: String expression displayed in the title bar 
of the dialog box.


So the matches between the TMX and the PO files will be of lower quality 
because of the "noise" added by the extra escapes.


I hope what I just wrote means something to somebody here :)

Jean-Christophe Helary

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--

Reiko Saito
Japanese Language Lead
Translation and Language Information (TLIS)
Globalization Services
Sun Microsystems, Inc.
Email: [EMAIL PROTECTED]
Phone: +81 3 5962 4912
Blog: http://blogs.sun.com/reiko


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [l10n-dev] TMX files (List of UI strings/translation)

[Jean-Christophe Helary]

On 28 nov. 07, at 10:24, Jean-Christophe Helary wrote:

I forgot to add the following:

1) The TMXs contain all the XML code escaped with "\" as per the sdf  
file: they are not "proper" TMX level2 files
2) Since they conform to the sdf contents they can be used directly  
to translate it (either in OpenLanguageTools or OmegaT)


The problem is that translators who use such tools (or any TMX  
supporting software) _do not_ work with the sdf file but with a PO  
file created from the sdf.


The PO file adds another layer of escapes, which makes matches from  
the sdf based TMX even harder to find.


For example, the TMX contains the following translation unit:

\Title\: String expression displayed  
in the title bar of the dialog box.


Which corresponds to the following sdf string:

\Title\: String expression displayed in the title bar  
of the dialog box.


(you see how the sdf format escapes the "<" and ">")

A tool that uses the TMX would get a match between this string and a  
sdf file that contains a similar string.


But the PO that will be our sources will come as:

\\Title\\: String expression displayed in the title  
bar of the dialog box.


So the matches between the TMX and the PO files will be of lower  
quality because of the "noise" added by the extra escapes.


I hope what I just wrote means something to somebody here :)

Jean-Christophe Helary

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]