Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Thorsten, Tor, Fridrich, please read the question at the end of the
mail.

Christian Lohmaier píše v Po 14. 03. 2011 v 23:06 +0100:
Hi Andras,

On Mon, Mar 14, 2011 at 6:28 PM, Andras Timar <timar74@gmail.com> wrote:

The proposed l10n workflow is the following. I provide en-US.sdf and
pot files regularly (let say bi-weekly). en-US.sdf and pot files can
be generated with the makefile.mk of the 'translations' module. I also
update Pootle. Before release, I get translations from Pootle (or from
external sources) and commit them to git.

OK, so pootle is the tool used, you don't actually commit the po(t)
files to the repository after each change. If pootle is mediator
anyway, I don't see the reason why the english string should be part
of every po file in the sourcetree.

I am not sure if pootle is the mediator for every localization. I think
that some translation teams prefers they own framework and just provide
updated .po files.

BTW: .po files would help us to get rid of the non-standard .sdf
and .res files. It would be nice to use a pure gettext solution.

Kendy has got an idea that a GSoC student would implement the switch
from .res files to .mo files.

Thorsten, Tor, Fridrich, do you know if .mo files (pure gettext
solution) would work on Windows and MAC?


Best Regards,
Petr


Context


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.