2017-10-13 7:45 GMT-05:00 Yury Tarasievich <yury.tarasievich@gmail.com>:
Seconding this. The project just throws away the l10n people man-hours (but
just you try to get them dev guys to fix something in the code!).
What are you talking about? Developers are committing many patches per
day, even on holidays (see e.g. our GitHub Pulse or our dashboard).
This is a ridiculous accusation.
Also, I translate for Mozilla and cosmetic changes are something that
happens every day. Why is it so controversial here to try to fix the
strings? It’s user experience and perception, which in my book matters
a lot.
Everyone please have this in mind: for better or worse, many of our
developers aren’t native speakers and can’t contribute high-quality
English strings the first time they land a patch, so we inevitably
have to iterate. While I’m conscious that our tooling isn’t the best
and does lead to wasted time over repetitive actions, I would—as a
translator who contributes to Mozilla, Ubuntu, Fedora and many smaller
projects—appreciate a little understanding that any software in
continuous development IS BOUND TO CHANGE.
Adolfo
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
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
Context
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.