On 30/11/2014 18:52, Rimas Kudelis wrote:
2014.11.30 19:13, Olivier Hallot wrote:
Lets invent a new language in the world named Liboish - LibreOffice
language - that in fact is often confused with en_US, but it is not the
I suggest to create a new entry in Pootle, named en-US so that we get a
translation from Liboish to English. Other languages translates directly
from Liboish and we are all happy not to redo our work.
(Apologizes for the inapropriate sense of humour, but I saw this extra
work comming months ago. 99% of my 4.4 UI was rework)
I can't understand whether or not you're joking, but others are already
voicing their support to this idea, so I'll voice my 'unsupport' as well.
I am joking and also provocative. Sorry for that. Of course there is no
such thing like "Liboish" nor it make any sense.
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
place. Furthermore, in my opinion, there would be constant risk of
either doing too much or not doing enough in this front.
Let's not forget that massive changes like these don't happen every
month. Yes, we had migration to different accesskey characters, and
manually updating all locales to reflect that must have been painful to
localizers. Yes, this current situation is somewhat similar because
again no real translation would is involved in this massive change. But:
I still believe this migration can be automated and made painless (at
least for the most part), so why not aim for making that automation a
prerequisite of the change that is threatening our well-being? LibO
developers don't live in another planet, and they can be reasoned and
negotiated with, right?
painless migration was my hope when I raised the issue, but saddly it
didn't show up in time. Such Changes In Capital Letters And Semicolons
Are Suitebale in EN But Does Not Affect Other Languages Where This Rule
Does Not Apply.
Nevertheless, it may be time to create a T/LSC Translation/Linguistic
Steering Commitee to address the issues raised here. LiBO does not have
a linguistic revision of terms used in the UI.
To unsubscribe e-mail to: firstname.lastname@example.org
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
[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't · Martin Srebotnjak
- [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't (continued)
Impressum (Legal Info)
: 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