Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


2013/12/12 Andras Timar <>

It is OK to fix new strings, also it is OK to fix obvious typos
anywhere. But we should refrain from re-phrasing old messages. It
would make a lot of unnecessary work for translators, and loss of
translation for unmaintaned languages. IMHO we have more important
things to do, than unify ("Returns...", "Calculates...", "Value
of...") or ("cannot", "couldn't", "could not") or whatever.

I just meant to use rules for new strings, not to make revolution in
current translations. At least not for now, when we are frustrated by all
the changes due to .ui conversion and when Pootle has no translation
memory. However, the current state is far from what you describe: we
resubmit translations for options pricing (first letter capitalized),
graphics changed to images, change in reset filter...

And I'm sorry, but volunteers can't be forced to do more important things -
they do what they like/are able to do; and it should be clearly said what
is desired and what isn't.

Best regards,

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.