Loading…
ebonsi
Resolved comment
It seems that the Glossary and the source strings are sensitive in regards to upper-case and low-case letters, what it shouldn't! It is possible for the programmers to fix that? Thanks!
2 years ago ebonsi
Resolved comment
I am saying that because I can see the word "UPDATE" on the source string and despite of the fact that I have already entered in the Glossary, the word is not showing up there. It would be an extra work to enter the same word twice just because one is uppercase and the other isn't.
2 years ago
eloquence
Resolved comment
Hi @ebonsi, I am not sure that changing the capitalization in the source string would be advisable here. The reason is that converting case in code or via CSS can have unpredictable results in certain languages. As Mozilla advises on https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_content_best_practices :
In general, localizers should make the decision about capitalization. If you want to display WARNING, add a string with that capitalization, and explain it in the localization note.
On that basis I think it may be preferable to keep these strings all-uppercase, but I defer to the experts like @erinm.
7 months ago
gonzalo-bulnes
Resolved comment
I seconding @eloquence's point on this. Capitalization has different meanings in different languages (e.g. nouns in German must start with a capital) and that makes modifying case in code a problematic pattern. (It won't always lead to a bad result, but it is hard enough to get right to justify avoiding it altogether, see Mozilla's guidelines).
7 months ago
jxtsai