Translating LibO 3.3

l10n
#21

Done by Petr Mladek.
http://cgit.freedesktop.org/libreoffice/build/commit/?id=74ed9d44838f828f54ce5d3f0f226147803f513a

But it is questionable if these files are actually used in the built
package over libs-core/sysui/desktop/menus :slight_smile:

If you manually updated <lang>.po, you will need to replace
OpenOffice.org with LibreOffice before committing the file.

Goran

#22

In data martedì 5 ottobre 2010 21:13:05, Goran Rakic ha scritto:

> [...] they should probably be updated for LibreOffice, replacing OOo
> with LibO.

Done by Petr Mladek.
http://cgit.freedesktop.org/libreoffice/build/commit/?idted9d44838f82

8f54

ce5d3f0f226147803f513a

But it is questionable if these files are actually used in the built
package over libs-core/sysui/desktop/menus :slight_smile:

If you manually updated <lang>.po, you will need to replace
OpenOffice.org with LibreOffice before committing the file.

You are quite right! Sorry for the mistake.
I attach the corrected file for the commit in

http://cgit.freedesktop.org/libreoffice/build/tree/po

Best regards,

#23

Hi, icelandic OOo-l10n-team here...

Þann þri 5.okt 2010 19:13, skrifaði Goran Rakic:

[...] they should probably be updated for LibreOffice, replacing OOo
with LibO.

Done by Petr Mladek.
http://cgit.freedesktop.org/libreoffice/build/commit/?idted9d44838f

828f54ce5d3f0f226147803f513a

But it is questionable if these files are actually used in the built
package over libs-core/sysui/desktop/menus :slight_smile:

If you manually updated<lang>.po, you will need to replace
OpenOffice.org with LibreOffice before committing the file.

Goran

Would some nice jolly person with adequate permissions commit our PO-files ?

<http://www.nett.is/~sveinki/libreoffice/is.po>
<http://www.nett.is/~sveinki/libreoffice/ooo-build-is.po>

Thanks a lot,

Sveinn í Felli

#24

Hi Sveinn,

Would some nice jolly person with adequate permissions
commit our PO-files ?

I just pushed them now.
http://cgit.freedesktop.org/libreoffice/build/commit/?id=741f935d8d722eb98c88c75392cb32c767ca6c55

Regards,

#25

In data martedì 5 ottobre 2010 21:13:05, Goran Rakic ha scritto:

> [...] they should probably be updated for LibreOffice, replacing OOo
> with LibO.

Done by Petr Mladek.
http://cgit.freedesktop.org/libreoffice/build/commit/?idted9d44838f82

8f54

ce5d3f0f226147803f513a

But it is questionable if these files are actually used in the built
package over libs-core/sysui/desktop/menus :slight_smile:

Hi, the file has been partially updated and not with my file. The error sti
ll
remains

#26

Valter Mura píše v Pá 08. 10. 2010 v 11:22 +0200:

In data martedì 5 ottobre 2010 21:13:05, Goran Rakic ha scritto:

> > [...] they should probably be updated for LibreOffice, replacing OOo
> > with LibO.
>
> Done by Petr Mladek.
> http://cgit.freedesktop.org/libreoffice/build/commit/?idted9d44838f82
8f54
> ce5d3f0f226147803f513a
>
> But it is questionable if these files are actually used in the built
> package over libs-core/sysui/desktop/menus :slight_smile:

No, the libreoffice/build/po/<lang>.po files are used just by some Linux
distributions. They are not used in the official LibreOffice build.

Only the libreoffice/build/po/lo-build-<lang>.po are needed for the
LibreOffice build.

I have added this information at
http://www.freedesktop.org/wiki/Software/LibreOffice/i18n/translating_3.3

Hi, the file has been partially updated and not with my file. The error sti
ll
remains

Ah, you send the fixed file before I subscribed. The attachments are not
in the list archive. Could you please send it once again? I will commit
it.

I am sorry for the inconvenience. I hope that we will have better
processes soon.

Best Regards,
Petr

#27

Let us start this discussion.

As there are no more patches, there is no need to run the build twice to
extract the difference, right? We should stop to separate lo-build and
upstream messages and use the single SDF file.

I would like if we can make it easy for us translators to work by having
both POT and SDF template available in the Git. When it is time for a
string freeze period someone can run the build up to l10ntools, extract
SDF, convert it and push it into Git. This can be either in build/po or
preferably somewhere inside l10n/ and removing build/po from a tree.

The extracted POT file will be large and we should test how our tools
can handle this or we should split it into a directory tree using oo2po.

There is a real issue when splitting POT files into a directory tree
when messages get moved from one file to the other. Our tools
(pomigrate2 from Translate Toolkit) can not understand this and we get
fuzzy match while the same string was not changed, just moved around.
There are also some issues when we have the same filename in different
directories.

If we split the POT into a directory tree we should solve the issues by
having a better pomigrate2.

You can read this message from ooo-l10n-dev list for some background:
http://www.mail-archive.com/dev@l10n.openoffice.org/msg07836.html

The scenario for a developer would be to extract the strings, convert
and commit to Git with something like:

  + ./configure
  + build up to l10ntools
  + cd bin && ./extract-gsi -d en-US GSI-en-US.sdf
  + oo2po -P -i GSI-en-US -o po/pot
  + copy sdf and pot to l10n/

Translator can work on Pootle or whatever we decide to use, or take the
POT files from Git and work on PO in l10n/<lang>.

We should merge existing PO files when the POT is regenerated. I believe
Pootle will do this for us, and translators can do this manually but we
may also want to push the updated files into Git as well.

Our build process should compare if the PO files are updated and
regenerate the SDF automatically during the build. Developer can commit
this updated SDF file back or, if this is fast enough, we can even
decide to regenerate the SDF in the every build (just the languages that
are being built).

Other option would be to require from translators to deliver SDF (like
we do currently in the OpenOffice.org workflow) or the PO files would be
downloaded from Pootle and SDF will be generated and pushed into Git.

Whatever option is selected I would like to have PO files in the version
control, as a backup and for keeping a complete history. It is possible
that Pootle can work using Git repository giving a lot of new
possibilities for continuous translations integration.

Best regards,
Goran