l10n of LibreOffice 3.3.1

l10n
#1

Hi Localizers,

Today I cherry-picked some bugfixes to libreoffice-3-3 branch. 14
strings were changed/added. I updated lo-build.pot and po files in git.
Rimas, can you please update Pootle.

The deadline is Sunday, February 6, 21:00 UTC. RC1 is due to February 7,
and only serious blockers can be fixed after that date.

Also, I started to work on leveraging translation fixes from various
sources. The first language was Danish. Source of updated translation
was OOo Pootle. I used translate-toolkit 1.8.1 and I created an msgmerge
script at ~/bin.

#!/bin/bash
/usr/bin/msgmerge --previous $@

With this argument, when merging translations as fuzzy old source
message will be preserved as a message comment. This helps when fixing
fuzzy translations as old and new source message can be easily compared.
Some PO editors provide in-line comparison visualization.

1. I extracted strings from LibreOffice:
$ localize -e -l en-US -f en-US.sdf
$ grep -v ^nlpsolver en-US.sdf > en-US.2
$ mv en-US.2 en-US.sdf

2. I created pot files:
$ oo2po -P -i en-US.sdf pot

3. I extracted Danish po files to da-orig directory.

4. I created lo-build extra po files from lo-build-da.sdf
$ oo2po -i lo-build-da.sdf -l da da-lobuild

5. I copied those po files from da-lobuild to da-orig which did not
exist there.

6. I concatenated da-orig and da-lobuild po files.
$ mkdir da
$ cd da-lobuild
$ for i in `find . -type f`;do msgcat --use-first $i ../da-orig/$i

../da/$i;done

7. Finally I migrated translations.
$ cd ..
$ pomigrate2 -C -F da da-new pot

8. Updated Danish po files are in da-new, upload to Pootle, etc....

Problems:
* fuzzies where one would not expect
* untranslated strings
   - basic/source/app.po (it is not there in OOo Pootle, prolly on
purpose and can be ignored)
   - scp2/accessories.po and extensions.po (their translations are
generated by localize-oo script, can be ignored for the time being)

So, in the limited timeframe until translation deadline all l10n teams
have two options:

1. Have lo-build-xx.po translated in Pootle and do nothing else.

-- OR --

2. Download SDF and/or pot files from here:
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.pot.tar.bz2
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.sdf.bz2
Update your localization as you wish. Ask for tips and tricks here.
Share your tips and tricks. Submit the URL of your localized UI and/or
help. If you send po files to Rimas, I'm sure he'll put them to the
newly created Pootle modules.
http://translations.documentfoundation.org/projects/libo33x_help/
http://translations.documentfoundation.org/projects/libo33x_ui/
I'll take care of integration into 3.3.1.

We can repeat this process for 3.3.2. If you miss the deadline now,
don't worry, 3.3.2 will come in 3 weeks after 3.3.1.

I need your active participation. I realized that I don't have time to
manually update that many languages from various sources. It is not
enough, if you give me a link to a translation that you made for
OpenOffice.org. There are many differences and the number of differences
are growing.

Thanks,
Andras

#2

Andras,

Also, I started to work on leveraging translation fixes from various
sources. The first language was Danish. Source of updated translation
was OOo Pootle. I used translate-toolkit 1.8.1 and I created an msgmerge
script at ~/bin.

I have in the meantime worked on OOoDEV300 translation up to m98 which has
only 2 fuzzy strings. I changed/corrected/updated translations compared do
OOO330. Is there a way to use DEV300m98 Slovenian translation for LO331? I
mean, I could try myself using the LO331 sdf (is that still the same as
OOO330 sdf?) and use the DEV300m98 compendium and po files for updating and
merging. I would get some untranslated strings since from m86 there were
some strings dropped on the DEV300 codeline, I guess, but I could search
from them in the current OOO330 translation.
Can you post a link to the LO33(1) sdf here so I can try?

Thanks, m.

#3

I posted it in my previous mail which was too long, I'm afraid. :wink:
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.pot.tar.bz2
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.sdf.bz2

Cheers,
Andras

#4

Ok,

I posted it in my previous mail which was too long, I'm afraid. :wink:
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.pot.tar.bz2
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.sdf.bz2

thanks, sorry for my negligence. So, would you suggest I update the
translation for 3.3.1 or do I wait for 3.4 or 3.X to use m98?
In a sense new things already translated in m98 will only arrive in LO on
the road to 3.4, so if I do it with 3.3.1, the translations will go to
"waste", as the new English strings are not in this branch.

Lp, m.

#5

2011.02.01. 23:31 keltezéssel, Martin Srebotnjak írta:

I posted it in my previous mail which was too long, I'm afraid. :wink:
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.pot.tar.bz2
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.sdf.bz2

thanks, sorry for my negligence. So, would you suggest I update the
translation for 3.3.1 or do I wait for 3.4 or 3.X to use m98?
In a sense new things already translated in m98 will only arrive in LO on
the road to 3.4, so if I do it with 3.3.1, the translations will go to
"waste", as the new English strings are not in this branch.

No translations will go waste, because you have them locally. You can
update now for LibreOffice 3.3.1, then later on for LibreOffice 3.4 but
don't expect perfect match between LibreOffice 3.4 and OOoDev m98. Try
to build a compendium or translation memory that you can use for both
OOo and LibreOffice.

Best regards,
Andras

#6

OK,

No translations will go waste, because you have them locally. You can
update now for LibreOffice 3.3.1, then later on for LibreOffice 3.4 but
don't expect perfect match between LibreOffice 3.4 and OOoDev m98. Try
to build a compendium or translation memory that you can use for both
OOo and LibreOffice.

yes, I already have compendii and tmx built for every m I finish with...

Will try with 3.3.1 first.

Thanks, m.

#7

Which conclusion did Leif come to?

I don't quite get what you meant in the last part. Update our translations?

..."Submit the URL of your localized UI and/or help."

This was very fuzzy. What am I supposed to do here? It almost sounds like
we have to start from scratch, which would be complete madness.

Regards,

Olav

#8

"No translations will go waste, because you have them locally." Pardon?

#9

Hi,

Which conclusion did Leif come to?

He said that result of migration (as described in my previous mail)
was acceptable.

I don't quite get what you meant in the last part. Update our translations?

..."Submit the URL of your localized UI and/or help."

This was very fuzzy. What am I supposed to do here? It almost sounds like
we have to start from scratch, which would be complete madness.

If you have complete OOo translation + complete lo-build-nb.po and you
are happy with the quality of nb LibreOffice 3.3.0, then you don't
have to do anything. Some teams reported they had translation fixes to
OOo 3.3 or later which did not get into LibreOffice. Now they can
submit updated translations. It's not translation from scratch. The
tools - see my previous mail - will leverage ~99% of existing
translation, the rest can be processed in a few hours.

Cheers,
Andras

#10

Hi,

"No translations will go waste, because you have them locally." Pardon?

Don't you keep a backup of nb translation on your hard drive? If you
do, or you maintain a translation memory, then you can work on
translation of different versions of OOo and LibreOffice with less
effort.

Cheers,
Andras

#11

Hi folks,

2011.02.01 23:50, Andras Timar rašė:

Today I cherry-picked some bugfixes to libreoffice-3-3 branch. 14
strings were changed/added. I updated lo-build.pot and po files in git.
Rimas, can you please update Pootle.

The deadline is Sunday, February 6, 21:00 UTC. RC1 is due to February 7,
and only serious blockers can be fixed after that date.

This is to inform you that the new strings have arrived to Pootle. It looks like the top teams are now lacking 20 new strings/244 words, but the true numbers are probably even smaller. :slight_smile:

Rimas

#12

Hi Andras,

Hi Localizers,

Today I cherry-picked some bugfixes to libreoffice-3-3 branch. 14
strings were changed/added. I updated lo-build.pot and po files in git.
Rimas, can you please update Pootle.

The deadline is Sunday, February 6, 21:00 UTC. RC1 is due to February 7,
and only serious blockers can be fixed after that date.

Also, I started to work on leveraging translation fixes from various
sources. The first language was Danish. Source of updated translation
was OOo Pootle. I used translate-toolkit 1.8.1 and I created an msgmerge
script at ~/bin.

#!/bin/bash
/usr/bin/msgmerge --previous $@

With this argument, when merging translations as fuzzy old source
message will be preserved as a message comment. This helps when fixing
fuzzy translations as old and new source message can be easily compared.
Some PO editors provide in-line comparison visualization.

1. I extracted strings from LibreOffice:
$ localize -e -l en-US -f en-US.sdf
$ grep -v ^nlpsolver en-US.sdf> en-US.2
$ mv en-US.2 en-US.sdf

2. I created pot files:
$ oo2po -P -i en-US.sdf pot

--> this is for all the UI+HC2 strings + the nlpsolver file, right?
[...]

2. Download SDF and/or pot files from here:
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.pot.tar.bz2
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.sdf.bz2
Update your localization as you wish. Ask for tips and tricks here.
Share your tips and tricks. Submit the URL of your localized UI and/or
help. If you send po files to Rimas, I'm sure he'll put them to the
newly created Pootle modules.
http://translations.documentfoundation.org/projects/libo33x_help/
http://translations.documentfoundation.org/projects/libo33x_ui/
I'll take care of integration into 3.3.1.

so we can provide a single .sdf containing all our fixes for UI and HC2 (gsichecked too of course :)?

We can repeat this process for 3.3.2. If you miss the deadline now,
don't worry, 3.3.2 will come in 3 weeks after 3.3.1.

I need your active participation. I realized that I don't have time to
manually update that many languages from various sources. It is not
enough, if you give me a link to a translation that you made for
OpenOffice.org. There are many differences and the number of differences
are growing.

Thanks for your step by step explanations.
May be if we keep this process for 3.3.2 too, we may add it to the wiki? I can do it, but I need to run all the steps first to make sure I understand well.

Thanks again
Kind regards
Sophie

#13

Andras

I was quite happy to have all po files in pootle in the OOo project. That allowed me to inspect e fix a couple of mistakes on-the-fly and get our translation up-to date in all the modules of the software.

I want to help, and do more on the files handling and checks, but I don't want to start from scratch and somehow I need help to extract the existing translation from LibreOffice (pt-BR). OOO files are now outdated for me.

I have the files of OOo 3.3 final. Does it helps?

Thanks,

Olivier

#14

Hi Andras,

Hi Localizers,

Today I cherry-picked some bugfixes to libreoffice-3-3 branch. 14
strings were changed/added. I updated lo-build.pot and po files in git.
Rimas, can you please update Pootle.

The deadline is Sunday, February 6, 21:00 UTC. RC1 is due to February 7,
and only serious blockers can be fixed after that date.

Also, I started to work on leveraging translation fixes from various
sources. The first language was Danish. Source of updated translation
was OOo Pootle. I used translate-toolkit 1.8.1 and I created an msgmerge
script at ~/bin.

#!/bin/bash
/usr/bin/msgmerge --previous $@

With this argument, when merging translations as fuzzy old source
message will be preserved as a message comment. This helps when fixing
fuzzy translations as old and new source message can be easily compared.
Some PO editors provide in-line comparison visualization.

1. I extracted strings from LibreOffice:
$ localize -e -l en-US -f en-US.sdf
$ grep -v ^nlpsolver en-US.sdf>  en-US.2
$ mv en-US.2 en-US.sdf

2. I created pot files:
$ oo2po -P -i en-US.sdf pot

--> this is for all the UI+HC2 strings + the nlpsolver file, right?
[...]

No, nplsolver is grepped out because it is not (yet) part of the l10n
process. The localize program extracts all nlpsolver strings not only
en-US and merge does not work. It's a TODO for the futore to fully
integrate nlpsolver.

2. Download SDF and/or pot files from here:
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.pot.tar.bz2
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.sdf.bz2
Update your localization as you wish. Ask for tips and tricks here.
Share your tips and tricks. Submit the URL of your localized UI and/or
help. If you send po files to Rimas, I'm sure he'll put them to the
newly created Pootle modules.
http://translations.documentfoundation.org/projects/libo33x_help/
http://translations.documentfoundation.org/projects/libo33x_ui/
I'll take care of integration into 3.3.1.

so we can provide a single .sdf containing all our fixes for UI and HC2
(gsichecked too of course :)?

Yes.

We can repeat this process for 3.3.2. If you miss the deadline now,
don't worry, 3.3.2 will come in 3 weeks after 3.3.1.

I need your active participation. I realized that I don't have time to
manually update that many languages from various sources. It is not
enough, if you give me a link to a translation that you made for
OpenOffice.org. There are many differences and the number of differences
are growing.

Thanks for your step by step explanations.
May be if we keep this process for 3.3.2 too, we may add it to the wiki? I
can do it, but I need to run all the steps first to make sure I understand
well.

I also wanted to write the wiki page. No problem, if you do, and
checking alI steps by another person will be definitely good. This
covers one scenario (migrating translations from OOo Pootle). The
other scenario is when we have a bilingual sdf file (not necessarily
up-to-date but fresher than LibO source). The last resort is LibO
source. It should be decided individually for each language. I'll
cover these scenarios, too.

Thanks,
Andras

#15

Thanks for the answer Andras. Just so everything is crystal clear.

-Olav

#16

Yes, I have the recent Norwegian OOo/LibO translations locally, with
complete compendiums for several projects. I was thinking more of
the people that have everything in Pootle and miss this luxury.

-Olav

#17

Please do.

#18

Den 02-02-2011 06:15, Olav Dahlum skrev:

Thanks,
Andras

Which conclusion did Leif come to?

The merge was perfect, but unfortunately we used a two week old dump :frowning:

/Leif

#19

Does all this mean it'll be possible to submit the LO translation in .po format (archive of .po files in subdirs, actually)?

...

Also, I started to work on leveraging translation fixes from various

...

We can repeat this process for 3.3.2. If you miss the deadline now,
don't worry, 3.3.2 will come in 3 weeks after 3.3.1.

-Yury

#20

2011.02.03. 8:03 keltezéssel, Yury Tarasievich írta:

Does all this mean it'll be possible to submit the LO translation in .po
format (archive of .po files in subdirs, actually)?

Well, yes. If you send me archive of .po files in subdirs based on
http://ftp.fsf.hu/LibreOffice/libreoffice-3-3-en-US-2011-02-01.pot.tar.bz2
by February 6, then I see no problem with integrating it to 3.3.1.

Andras