Hi Sophie
I have a demand on this subject.
I don't have enough energy to dedicate to the translation of two large
softwares like LibO and OO. I had already made my choice to stick with
LibreOffice.
So someone else will take care of OO. When it come to import the
developments from OO to LibO it will be important to flag *all new OO
strings* (m90) as fuzzy or untranslated, even if they are translated
already, so that I can revise and aprove for LibreOffice. Otherwise
LibreOffice will bear inconsistencies because of an external influence.
It may be quite hard to make difference between a *new* (m90) translated
string and an old one.
Thanks
Olivier
Em 28-12-2010 07:45, Sophie Gautier escreveu:
Hi all,
Now that the 3.3 localization is over for LibO too, could we plan an
update of the localization files and with which version of OOo shall we
update the files to get in sync.
There is already some work to be done (approx 7000 words up to
DEV300m90), so the sooner we know the better for us to organize our time
between the fixes and the new translations.
Thanks in advance
Kind regards
Sophie
--
Olivier Hallot
Founder, Steering Commitee Member - The Document Foundation
Translation Leader for Brazilian Portuguese
--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***
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.