On 12.10.2017 10:46, Michael Bauer wrote:
Sometimes 'cosmetic' change could mean a difference. To me is
indicative if string is 1) in all caps, if 2) first letter is
capitalized and if 3) all letters are lowercased.
Not a good reason Kruno. For one, not all scripts even entertain the
idea of caps. CJK, Nagari, Amhara, Arabic-based ... non of them have
caps. Yet somehow they manage to make their UI work.
Secondly, quite a lot of locales have strict lowercasing. Like ours.
So caps in en-US don't make a blind bit of difference to our
translations.
Thirdly, there is largely no rhyme, no reason, and apparently no
season. In en-US, caps follow whatever the flavour of the month is.
Evidence? Sure. Just as Microsoft was abandoning sentence case,
LibreOffice went for it, or the other way round, I can't remember.
Either way, round about the same time, their respective UI went
*exactly* the opposite way.
If LO does not want to start treating en-US as a translatable locale,
it really needs to introduce a new change category into Pootle of "cap
change" which does not void existing translations but introduces a QA
flag like "missing placeholder".
Right now, it feels like every time en-US play with their caps, they
give 100 or so other locales the finger, as if our time didn't matter
two hoots. And it's NOT like this is a novel issue, we've debated this
ad nauseum and STILL you dump these on us volunteers. Do you know how
much I'd charge for this kind of time?
Michael
Translating LibreOffice bought me a house.
Kruno
--
To unsubscribe e-mail to: [email protected]
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
