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?
Yury -- To unsubscribe e-mail to: email@example.com Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted