[Libreoffice] Localization issues, readme

Sophie Gautier gautier.sophie at gmail.com
Fri Dec 10 03:19:31 PST 2010


Hi Andras,
On 10/12/2010 13:05, Andras Timar wrote:
> Hi,
>
> I found a few issues and I need your advice. If I correct these
> issues, new strings for translation will appear, but I think we need
> to address these issues before the release (not necessaryly before RC2
> because there is not enough time).
>
> Strings for our additional features (difference between OOo 3.3 and
> LibreOffice) are in build/po/lo-build.pot which is generated from
> lo-build.sdf. However, in lo-build.sdf there are duplicated source
> language entries, because bogus strings are coming from
> build/po/sdf-templates/OxygenOffice.sdf. Therefore translators may
> translate OxygenOffice strings instead of LibreOffice string in po
> files, it depend on which string comes first in the alphabetically
> sorted string list. My recommendation: clean duplicated/unused strings
> from OxygenOffice.sdf (will there be any left?).
>
> Other big issue is the readme. The source of the readme is in
> libs-core/readlicense_oo/docs/readme.xrm which contains many
> duplicated paragraph IDs, therefore messup is granted. First thing to
> do is change duplicated IDs to unique IDs. Then strings should be
> extracted and changed+new strings should be added to
> build/po/sdf-templates/SUSE.sdf and build/po/lo-build.sdf, then pot/po
> files should be generated, should be sent to Pootle etc. Readme
> contains many new strings to translate, so it will take time to have
> them translated in all languages. Also, old strings should be removed
> from l10n/source/<lang>/localize.sdf files, because they will come
> back, and make the localized readmes confusing (half-LibreOffice,
> half-OpenOffice.org). Alternatively we can change the corresponding
> paragraph IDs in LibreOffice readme.
>
> Please let me know, if you wish me to work on these issue in the
> week-end. It is unfortunate to have these issues long after the string
> freeze, but it's better to correct them now. Corrections can be pushed
> after RC2 tagging.

Please go on, several of us won't be able to distribute LibreOffice 
otherwise, so even if it's late, it's better anyway.
Thanks a lot.

Kind regards
Sophie


More information about the LibreOffice mailing list