Hi Olivier,
On 28/12/2010 13:35, Olivier Hallot wrote:
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.
Is there somebody working on the new Brazilian strings already in OOo?
Or are we sure that the strings have not been touched?
It may be quite hard to make difference between a *new* (m90) translated
string and an old one.
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?
The amount of work is and will not be the same for us and if possible,
it would be great if we have some plans on this to organize/optimize our
time and our work.
Kind regards
Sophie
--
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.