[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-l10n] Swedish contribution


Per Eriksson píše v Čt 07. 10. 2010 v 23:34 +0200:
> Hi Goran,
>
> Thank you for your help.
>
> Please find the updated po below.
>
> http://erinet.se/lo-build-sv.rar

Hmm, I do not know how to merge these translations into the existing
lo-build-sv.po. You might find it at
http://cgit.freedesktop.org/libreoffice/build/plain/po/lo-build-sv.po

Note that it is very important to keep the comments above the translated
string. e.g. the
editeng/source/items/svxitems.src#RID_SVXITEMS_HORJUST_LEFT.string.text

--- cut ---
#:
editeng/source/items/svxitems.src#RID_SVXITEMS_HORJUST_LEFT.string.text
msgid "Align left"
msgstr ""
--- cut ---

The OOo build process uses the .sdf format internally. The comments are
important to convert .po into .sdf.

Does anyone know how to add translations without loosing the comments?
Alternatively, is it possible to send .po with the comments instead
of .mo?


Best Regards,
Petr

--
To unsubscribe, send an empty e-mail to l10n+unsubscribe@libreoffice.org
List archives are available at http://www.libreoffice.org/lists/l10n/
All messages you send to this list will be publicly archived and cannot be deleted.

References:
[libreoffice-l10n] Swedish contributionPer Eriksson <pereriksson@openoffice.org>
Re: [libreoffice-l10n] Swedish contributionGoran Rakic <grakic@devbase.net>
Re: [libreoffice-l10n] Swedish contributionPer Eriksson <pereriksson@openoffice.org>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.