Hi,
Am 11.11.2010 22:02, schrieb Paolo Pozzan:
[cut]
I think that a workflow similar to the OOo one would be more efficient: if
we have a deadline we can organize time much better and at the same time
I think a single big export would be much faster to manage than many
small exports.
Not really, as we had to wait for the last team to do the export. And
some teams ar not working with pootle but committing to git directly.
In general, this is a temporary "workflow" anyway. We definately need to
change this for 3.4.
I think we can do something more continous then.
E.g. :
- translation templates will be updated in git regularely (say every week)
- translation templates will be pushed to pootle
- language team can update their pootle repository from templates at any
time (it's possible through the web frontend or this can be automated as
well)
- translations will be pulled from pootle regularely (also every week)
- translations will be pushed to git then (we may need some indicator
for teams directly working on git).
but this needs to be tested.
André
--
E-mail to l10n+help@libreoffice.org for instructions on how to unsubscribe
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
Context
- Re: [libreoffice-l10n] Re: LibreOffice 3.3 string freeze, Pootle update (continued)
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.