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

Big +1 for what Martin and Mikhel have said about matching existing translations and not losing the ability to translate to different targets depending on the context.

If there is going to be wholesale re-organisation as to how the strings are presented for translation, two other considerations also spring to mind which I didn't see on the list: 1) Plurals? I think LO still doesn't do plurals properly (but I may be confusing projects here, apologies if it does). This would also tie in with the 1 source string » multiple target strings issue. 2) Turning en-US into a to-be-translated locale and making the source strings just en or some fake locale? That way, en-US can change case, correct en-US typos and other such stuff which is English specific to its heart's content without hitting all the other locales at the same time.


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.