Le 6 oct. 2017 22:14, "Adolfo Jayme Barrientos" <email@example.com> a
2017-10-06 10:45 GMT-05:00 Serg Bormant <firstname.lastname@example.org>:
What is your point?
What the fucking shit happens again and again release to release?
Watch your mouth. Nobody has put a gun down your throat to oblige you
Russian we get 7_540 items to translate and most of them are tinkering
with English source items, that doesn't change anything in translated
items, but again, again, and AGAIN we need to restore by hands old
translations for new sources.
You realize that Cloph fixes this behind the scenes every six months, right?
Please, please, PLEASE make English-to-English translation and play
with spaces and capital letters there...
You realize that this suggestion makes no sense whatsoever?
Please all, calm down, we will look after what bugs next with Christian.
There has been changes with gettext, others with UX, we will sort out what
should be automated and what can't. As Adolfo said there won't be EN to EN
translation however. But please think that LO needs to evolve and we need
to adapt our process too, meaning that we can make mistakes together with
having to redo some work.
I'm a volunteer like you on this so be sure that I evaluate what commitment
To unsubscribe e-mail to: email@example.com
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
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