Date: prev next · Thread: first prev next last

2015-01-27 16:09 GMT+01:00 Michael Bauer <>:

 PS the current setup is not foolproof either as we sometimes get really
bad strings, linguistically bad that is.

If this is such a concern, then why don't we set up a panel of experiences
localizers who are willing to help developers judge if a change is semantic
or cosmetic before we land them on l10n in general?


+1 to both your comments, Michael.

Sgrìobh Jan Holesovsky na leanas 27/01/2015 aig 14:16:

be deciding if a change should be applied in the sources (ie. it is a
change needed for all languages) and what is just making the original
more consistent?  And again - what to do if the person mis-judges?

 And thank you to you, Kendy (aka Jan Holesovsky), for answering my
"why". I do see that it is a complex matter.

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.