On Sat, Oct 7, 2017 at 12:53 AM, Serg Bormant <firstname.lastname@example.org> wrote:
2017-10-06 23:12 GMT+03:00 Adolfo Jayme Barrientos
2017-10-06 10:45 GMT-05:00 Serg Bormant <email@example.com>:
What is your point?
It is very simple.
As I can see, Pootle has 135 languages now and some teams work offline.
If someone makes ONLY ONE cosmetic change in translatable strings,
everyone of 135 language teams should adopt this change.
As someone who translates practically alone for my language (mainly
stealing from my sleep), I agree that this is far from effective use of
volunteers’ often very scarce spare time. Saying ‘You’re volunteers so if
you don’t want to put up with ♥♥♥♥, we’ll wait for someone who does’
doesn’t seem the best stance to take.
On the other hand, I’m also a stickler for correct typography, perfectly
composed layouts and such things and I think that ‘cosmetic’ changes
go a long way to make a product appear much more professional and
to work with.
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?
Why not? Assign any unused language code for source and "en" for
This seems like an attractive option but it has problems of its own
when looking at the source, you will never be sure how the actual UI
like; many teams may actually want to implement some of the changes
the ‘English translation’ but they will not be notified of them and will
have to periodically search for such, etc.).
OTOH, setting that particular solution aside, I’m sure that other things
can be done to somewhat improve the situation. For example, couldn’t some
mechanism be implemented to explicitly mark certain changes as ‘small’ or
‘cosmetic’ so that the translations in Pootle are just marked as ‘Needs
work’ instead of right out deleting them? Or even better, add a new
specifically meaning ‘Cosmetic change’ that allows re-confirming the
existing translations en masse if the changes are irrelevant to them?