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

On 11/30/2014 11:52 PM, Rimas Kudelis wrote:
I don't really think this would be viable solution in the long run.
Somebody would have to maintain that "translation" for years just
because in 2014 localizers made a fuss out of a one-time problem that
could (and should) have been automated not to bother them in the first

Not condescending, surely? Just browsing a thousand strings is a hit on translator's time and eyes. Proofing costs more.

Translators are on a receiving end of one-way work creation pipeline, and should have no say in the matter?

Let's not forget that massive changes like these don't happen every
month. Yes, we had migration to different accesskey characters, and

Massive changes like that would and will happen in an open source world, when complex software package is involved; specifically, they'll happen in LibO. For two good reasons: because they cost practically nothing to initiator, and because in Open Source nobody can or wants put a veto on such changes.

And why is not anyone (besides me) discussing automation, of that same problem, too?


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.