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

Re: [libreoffice-l10n] Git repo for l10n?


Hi Goran,

Am 04.10.2010 20:57, schrieb Goran Rakic:


It should also be a goal to move all locale data into this repository
and modify the build system to look for them in this new separate
module. But this is something we have a power to set up, no need for
someone else to amend this change. Unfortunately, I do not have time to
dive into this now but I would be happy to test and send feedback to
whoever pick this as goal and join the development effort later.

Anything we can do that you have more time for us? :)

I did hope, you could help with the build system and the needed scripting stuff - I know, you do have experience on this.

I curently have a good idea, what needs to be done regardings scripting, but am very new to the build system and have only some basic ideas how translations are handeled there.

regards,

André
--
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.

Follow-Ups:
Re: [libreoffice-l10n] Git repo for l10n?Santiago Bosio <santiago.bosio@gmail.com>
References:
[libreoffice-l10n] Git repo for l10n?Guido Ostkamp <ooo@ostkamp.fastmail.fm>
Re: [libreoffice-l10n] Git repo for l10n?Goran Rakic <grakic@devbase.net>
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.