Hi Sophie,
On 2010-12-29 at 19:52 +0300, Sophie Gautier wrote:
This is why I ask: do we merge Libo with the last dev versions or do we
work on the last SDF file only (I think it's OOo330m9) because it is now
two completely separated products?
We are still working towards a plan how to cherry pick or merge from OOo
from now on, so do not expect any huge changes in the next 2 weeks or
so ;-) We have to evaluate the possibilities first, but most probably,
this will be more on case-by-case basis, ie. the amount of strings to
translate will grow at reasonable pace, not a huge drop of stuff to
translate from a day to day.
Our concerns here, with Olivier and the few of us not doing localization
for OOo any more, is that the localization will be done by someone else,
may be a professional agency. Most of the time the quality is very very
low because the agencies know nothing about the product where we work
with it and localize it since years. So, no matter the amount of
strings, if we are sure of the consistency and we do not have to
research in the files to ensure it. Currently there is a little more
than 6000 new/fuzzy words until DEV300m90, it's not so much and even
less if we have a long deadline ;)
Ah, maybe I understand now ;-) So of course, it is up to you to define
if you want to have the translations merged from the OOo tree to the LO
tree for 3.4, or not. I understand it that you'd prefer not to, ie.
l10n repo (containing the localize.sdf's) untouched by the merges from
OOo, right?
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.