Re: [libreoffice-l10n] l10n of LibreOffice 3.3.1

2011/2/2 Sophie Gautier <gautier.sophie@gmail.com>:
> Hi Andras,
> On 02/02/2011 00:50, Andras Timar wrote:
> > 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

-- 
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***