Le 06/10/2015 21:01, Pavel Sanda a écrit :
Guillaume Munch wrote:
Seriously, I think this is just going to annoy our translators.
Seriously :) as described in the rationale of my patch, this cannot be more
transparent for translators. Gettext pre-sets the previous translation;
translators just have to do a global search-replace. And until they do, the
old translation is still displayed. I took the time to check that it's
indeed the case. And you might be underestimating our translators, some of
whom might be lovers of proper typographic usage.
Seriously, who knows how to get an ellipsis on his/her keyboard?
Seriously :) I am sorry, ignorance is not an argument. A lot of bad
typographic usage is only the legacy of past technical limitations that are
long gone. It took me 10 seconds to learn that ??? is AltGr+Shift+, in the
french Linux keyboard and Option+; on Mac. (For proper French usage, you
can also input accented upper-case characters and I am sure that your
question marks are preceded by a space ??? though I would agree that a thin
space would appear as too formal in e-mails.)
I dont think this is a question of ignorance but of comfort.
It took me 5 min to figure out how to enter elipsis directly and no
I will not rember the number 2026 or whatever weird shortcut my
keyboard layout might have for the next time.
I'm afraid more on JMarc side on the points above.
Pavel
I think you might be mixing issues. One thing is allowing to have UTF-8
string literals especially in translations, another one is deciding that
we now use … instead of ... in the interface to be consistent with Qt.
If you do not find typographic consistency important personally, then I
imagine that you would continue typing "..." in UI strings. I would see
it personally as a minor bug, but who will prevent you from doing it?
Guillaume
