Update on FR localization and terminology

l10n
#1

Hi all,

I've updated the French localization on Pootle and I'm not sure if I must ask for the file to be committed here, or if it will be done on a more automated way for all Pootle languages before 3.3 final.

I've also extracted the FR glossary file from SunGloss and transformed it in a .po file that is ready to be the terminology file on Pootle. Could one of the Pootle Admin upload it instead of the Gnome one currently uploaded? Both files (last l10n and terminology) are here :
http://sophiegautier.com/l10n/

Also, may be this terminology.po file could serve as a basis for the other languages who has no terminology currently because it contains all the UI strings in English. It should be possible to remove the French strings and update it with a TM, then upload it on Pootle to be completed?

Kind regards
Sophie

#2

Hi all,

I've updated the French localization on Pootle and I'm not sure if I must ask for the file to be committed here, or if it will be done on a more automated way for all Pootle languages before 3.3 final.

I also wonder that since it seems we are commiting the po directly but at the same time we are maintaining the Pootle translation.

I've also extracted the FR glossary file from SunGloss and transformed it in a .po file that is ready to be the terminology file on Pootle. Could one of the Pootle Admin upload it instead of the Gnome one currently uploaded? Both files (last l10n and terminology) are here :
http://sophiegautier.com/l10n/

We got a homebrew app for the glossary more updated than SunGloss but didn't thought about converting it to po. Might be a good idea.

Also, may be this terminology.po file could serve as a basis for the other languages who has no terminology currently because it contains all the UI strings in English. It should be possible to remove the French strings and update it with a TM, then upload it on Pootle to be completed?

+1

#3

Hi Sophie,

2010.11.19 16:06, Sophie Gautier rašė:

I've updated the French localization on Pootle and I'm not sure if I must ask for the file to be committed here, or if it will be done on a more automated way for all Pootle languages before 3.3 final.

I'm not sure what exactly the plan is. In any case, I don't think it hurts the process to ask explicitly for the file to be committed. Lior?

I've also extracted the FR glossary file from SunGloss and transformed it in a .po file that is ready to be the terminology file on Pootle. Could one of the Pootle Admin upload it instead of the Gnome one currently uploaded? Both files (last l10n and terminology) are here :
http://sophiegautier.com/l10n/

I've uploaded as libreoffice/fr.po, and left the gnome file intact. Do you really want me to delete it?

Also, may be this terminology.po file could serve as a basis for the other languages who has no terminology currently because it contains all the UI strings in English. It should be possible to remove the French strings and update it with a TM, then upload it on Pootle to be completed?

It is possible, but I'm not really sure if there's a demand for this nor if this is the best approach. Your file has more than 14K strings, of which some are dupes (e.g. "rounded rectangle" and "rounded rectangle\t") or look a bit out of place in terminology (e.g. the very first string: "%PRODUCTNAME %PRODUCTVERSION [doc_type]"). I doubt every team would have enough resources and/or determination to translate them all (note: I don't mean to depreciate your work, treat them as simply observations from a fellow localizer).

By the way, Pootle also has internal means of generating terminology, which could probably work at least for some languages. I just tried this for Lithuanian on the sandbox installation of Pootle, and sadly it left quite a bunch of terms untranslated (I guess Pootle got confused with different grammatical cases of the same term), but we may experiment with it a bit more later. Also, I hope that maybe it would work better when we have all of OOo translation files in Pootle, not just our additional strings.

Best regards,

Rimas

#4

Hi Rimas, all

Hi Sophie,

2010.11.19 16:06, Sophie Gautier rašė:

I've updated the French localization on Pootle and I'm not sure if I
must ask for the file to be committed here, or if it will be done on a
more automated way for all Pootle languages before 3.3 final.

I'm not sure what exactly the plan is. In any case, I don't think it
hurts the process to ask explicitly for the file to be committed. Lior?

Ok.

I've also extracted the FR glossary file from SunGloss and transformed
it in a .po file that is ready to be the terminology file on Pootle.
Could one of the Pootle Admin upload it instead of the Gnome one
currently uploaded? Both files (last l10n and terminology) are here :
http://sophiegautier.com/l10n/

I've uploaded as libreoffice/fr.po, and left the gnome file intact. Do
you really want me to delete it?

Thanks a lot, you can let the Gnome one in place.

Also, may be this terminology.po file could serve as a basis for the
other languages who has no terminology currently because it contains
all the UI strings in English. It should be possible to remove the
French strings and update it with a TM, then upload it on Pootle to be
completed?

It is possible, but I'm not really sure if there's a demand for this nor
if this is the best approach. Your file has more than 14K strings, of
which some are dupes (e.g. "rounded rectangle" and "rounded
rectangle\t") or look a bit out of place in terminology (e.g. the very
first string: "%PRODUCTNAME %PRODUCTVERSION [doc_type]"). I doubt every
team would have enough resources and/or determination to translate them
all (note: I don't mean to depreciate your work, treat them as simply
observations from a fellow localizer).

Yes you're right, the file still needs some work and I need to add comments too. I'm not sure there is a demand also or enough resources, but that's just a proposal :slight_smile:

By the way, Pootle also has internal means of generating terminology,
which could probably work at least for some languages. I just tried this
for Lithuanian on the sandbox installation of Pootle, and sadly it left
quite a bunch of terms untranslated (I guess Pootle got confused with
different grammatical cases of the same term), but we may experiment
with it a bit more later. Also, I hope that maybe it would work better
when we have all of OOo translation files in Pootle, not just our
additional strings.

Yes, I've seen that I didn't try it but it should help when all the localization will be uploaded.
Thanks!

Kind regards
Sophie

#5

2010.11.20. 10:10 keltezéssel, Rimas Kudelis írta:

2010.11.19 16:06, Sophie Gautier rašė:

I've updated the French localization on Pootle and I'm not sure if I
must ask for the file to be committed here, or if it will be done on a
more automated way for all Pootle languages before 3.3 final.

I'm not sure what exactly the plan is. In any case, I don't think it
hurts the process to ask explicitly for the file to be committed. Lior?

I'm not sure if there is anybody who knows the plan or knows which teams
use Pootle. I created a wiki page -
http://wiki.documentfoundation.org/Translation_for_3_3 - everybody
please fill it. This page can be useful when someone has to decide what
to take from Pootle and what not. For example Hungarian file is in
Pootle, but I don't use Pootle. It would not be nice, if my translation
in git was overwritten by a mass commit from Pootle.

Translations can be committed any time to libreoffice-3-3 branch, when
someone asks explicitly.

Andras

#6

2010.11.20. 10:10 keltezéssel, Rimas Kudelis írta:
> 2010.11.19 16:06, Sophie Gautier rašė:
>> I've updated the French localization on Pootle and I'm not sure if I
>> must ask for the file to be committed here, or if it will be done on a
>> more automated way for all Pootle languages before 3.3 final.
>
> I'm not sure what exactly the plan is. In any case, I don't think it
> hurts the process to ask explicitly for the file to be committed. Lior?

I didn't commit French recently.

Translations can be committed any time to libreoffice-3-3 branch, when
someone asks explicitly.

I would prefer to have this done on a deadline we choose for translations,
and not in a sporadic way.

On the deadline we could take all the translations from master branch on git
and the pootle and make
sure they're committed to the 3.3 branch.

I guess it's time to develop the translation process as part of the release
process. I'm not sure who to work with on this ?

Kaplan

#7

Translations can be committed any time to libreoffice-3-3 branch, when
someone asks explicitly.

I would prefer to have this done on a deadline we choose for translations,
and not in a sporadic way.

Why? People might want to build themselves and want their latest
translations included. There are only 10-15 active languages, we can
handle it in the sporadic way, too.

On the deadline we could take all the translations from master branch on git
and the pootle and make
sure they're committed to the 3.3 branch.

The entire "build" repository including lo-build* files will be
removed very soon from master. We should not use master for 3.3
translations.

I guess it's time to develop the translation process as part of the release
process. I'm not sure who to work with on this ?

It's the best if we don't wait for somebody else, but start to find
out how to work. We don't need a complicated process, because it will
be used only once (only for 3.3).

A few teams have already updated their data on
http://wiki.documentfoundation.org/Translation_for_3_3. When we have a
deadline, all po files from the teams who have YES in their Pootle
column should be committed to git (libreoffice-3-3 branch). If the
team has NO or nothing in their Pootle column, then it will be the
responsibility of the language team leader to send their translation
to this list by the deadline. Translations may come from
Novell/openSUSE as well, as the did in the past. Ideally it will not
interfere with our work, i.e. they work on only those languages which
we don't work on. How can we make sure? Petr?

Thanks,
Andras

#8

Sophie Gautier <gautier.sophie <at> gmail.com> writes:

Hi all,

I've updated the French localization on Pootle and I'm not sure if I
must ask for the file to be committed here, or if it will be done on a
more automated way for all Pootle languages before 3.3 final.

I've also extracted the FR glossary file from SunGloss and transformed
it in a .po file that is ready to be the terminology file on Pootle.
Could one of the Pootle Admin upload it instead of the Gnome one
currently uploaded? Both files (last l10n and terminology) are here :
http://sophiegautier.com/l10n/

Also, may be this terminology.po file could serve as a basis for the
other languages who has no terminology currently because it contains all
the UI strings in English. It should be possible to remove the French
strings and update it with a TM, then upload it on Pootle to be completed?

Hello,

I was giving a look at that .po files, but found some problems in the way it was
built:
-- some "msgstr" are not unique, so it can't be handled in a number of apps:
probably it needs some "msgctxt"s for having duplicated "msgstr"s like:

msgid "abstract"
msgstr "synthèse"

msgid "abstract"
msgstr "abstrait"

Also, the translator comments should be placed at the beginning of the unit:
msgid "abort"
msgstr "abandonner"
#quitter ou subst. abandon

-->
#quitter ou subst. abandon
msgid "abort"
msgstr "abandonner"

Hope this helps,
King regards,
Gonçalo

#9

Andras Timar píše v So 20. 11. 2010 v 21:50 +0100:

>
>> Translations can be committed any time to libreoffice-3-3 branch, when
>> someone asks explicitly.
>>
>>
> I would prefer to have this done on a deadline we choose for translations,
> and not in a sporadic way.

Why? People might want to build themselves and want their latest
translations included. There are only 10-15 active languages, we can
handle it in the sporadic way, too.

You might commit the translations at any time, once you are happy with
it.

Also, we should also send a reminder mail before we do an beta/rc
release. It is hard to define an exact date because it always depends on
the state of blocker bugs. Anyway, We could send a reminder 1-2 days
before the release (before we tag the sources).

The entire "build" repository including lo-build* files will be
removed very soon from master. We should not use master for 3.3
translations.

I agree. It is better to commit the stuff to the libreoffice-3-3 branch
directly.

A few teams have already updated their data on
http://wiki.documentfoundation.org/Translation_for_3_3. When we have a
deadline, all po files from the teams who have YES in their Pootle
column should be committed to git (libreoffice-3-3 branch). If the
team has NO or nothing in their Pootle column, then it will be the
responsibility of the language team leader to send their translation
to this list by the deadline. Translations may come from
Novell/openSUSE as well, as the did in the past. Ideally it will not
interfere with our work, i.e. they work on only those languages which
we don't work on. How can we make sure? Petr?

BTW: Who could actually commit the strings from pootle to git?

Best Regards,
Petr

#10

2010.11.22. 11:31 keltezéssel, Petr Mladek írta:

BTW: Who could actually commit the strings from pootle to git?

Did you ask for a volunteer? I can do that. I have access to both pootle
and git.

Andras

#11

Andras Timar píše v Po 22. 11. 2010 v 12:59 +0100:

2010.11.22. 11:31 keltezéssel, Petr Mladek írta:
> BTW: Who could actually commit the strings from pootle to git?
>

Did you ask for a volunteer? I can do that. I have access to both pootle
and git.

Thanks a lot for volunteering! It would be great.

BTW: How is it complicated?
How long before releases should we ping you? I mean before tagging the
repos.

Best Regards,
Petr

#12

2010.11.22. 13:31 keltezéssel, Petr Mladek írta:

Andras Timar píše v Po 22. 11. 2010 v 12:59 +0100:

2010.11.22. 11:31 keltezéssel, Petr Mladek írta:

BTW: Who could actually commit the strings from pootle to git?

Did you ask for a volunteer? I can do that. I have access to both pootle
and git.

Thanks a lot for volunteering! It would be great.

BTW: How is it complicated?
How long before releases should we ping you? I mean before tagging the
repos.

It's not complicated but please allow at least 24 hours, because I
usually work only at night on LibreOffice.

Andras

#13

Hi,

Sophie Gautier<gautier.sophie<at> gmail.com> writes:

Hi all,

I've updated the French localization on Pootle and I'm not sure if I
must ask for the file to be committed here, or if it will be done on a
more automated way for all Pootle languages before 3.3 final.

I've also extracted the FR glossary file from SunGloss and transformed
it in a .po file that is ready to be the terminology file on Pootle.
Could one of the Pootle Admin upload it instead of the Gnome one
currently uploaded? Both files (last l10n and terminology) are here :
http://sophiegautier.com/l10n/

Also, may be this terminology.po file could serve as a basis for the
other languages who has no terminology currently because it contains all
the UI strings in English. It should be possible to remove the French
strings and update it with a TM, then upload it on Pootle to be completed?

Hello,

I was giving a look at that .po files, but found some problems in the way it was
built:
-- some "msgstr" are not unique, so it can't be handled in a number of apps:
probably it needs some "msgctxt"s for having duplicated "msgstr"s like:

msgid "abstract"
msgstr "synthèse"

msgid "abstract"
msgstr "abstrait"

yes, it depends on the context, so both are correct.

Also, the translator comments should be placed at the beginning of the unit:
msgid "abort"
msgstr "abandonner"
#quitter ou subst. abandon

-->
#quitter ou subst. abandon
msgid "abort"
msgstr "abandonner"

Hope this helps,

Yes, thanks for the hint :slight_smile: I've noticed that in the Gnome file, I'll polish the file later on.

Kind regards
Sophie