Date: prev next · Thread: first prev next last

Not sure what can we add here?

You summed it up nicely in those 3 points.
As far as I'm concerned, en_us can be changed/improved as much as anyone wants... only if they provide script for automatic update for all other affected languages.

New strings - OK
Edited strings with changed meaning, fixed typos - OK
Cosmetic changes (~ to _ or "Status" to "Status:" or ... to … or those different quote styles I don't even have on my keyboard) and anything similliar - NOT OK if you don't script it for all languages Cosmetic changes ("Big brown fox" -> "Big Brown Fox") - NOT OK at all, change just for en_us, don't change my strings and don't even notify me you did it in en_us


26.01.2015 u 09:33, Sophie je napisao/la:

To conclude, what l10n team would like to see is:
- a review process of the strings before they are committed and make
sure they respect the en_US standards (capitals, grammar, punctuation,
typography). Maybe adding the Gnome HIG book to our pages [like 2] if
not already.

- if there is a way to script changes, script them otherwise wait until
there is a script available to commit them

- any time there are heavy changes that pop up in someone's mind (like
changing ... for …) discuss it with the l10n team before committing
those changes.

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.