Follow SMF on Twitter.
Started by m4z, September 06, 2019, 12:50:20 PM
Quote from: Arantor on September 11, 2019, 01:12:09 PMDevelopers should care on some level though because with a bit of care, they can make it less hard to translate sensibly.
Quote from: Aleksi "Lex" Kilpinen on September 10, 2019, 11:31:47 PMIn many languages context is key, for example if some one asked me to translate "Set to 0 to disable" in to any other language I know, I would first ask in which context would this be used? Disable is not a word that is easily translated. So, in english; super generic. In other languages, eh - not so much.
Quote from: Gwenwyfar on September 11, 2019, 05:11:25 PMIt is just as confusing in either language.
Quote from: Gwenwyfar on September 11, 2019, 05:11:25 PMIn this particular case disable is very straightforward and there's no other alternative translation for portuguese, but it'd be nice if there were two strings, one for each situation. I was confused about this some times as well, while using the forum in english. It is just as confusing in either language.
Quote from: m4z on November 06, 2019, 04:51:03 PMI stand by my original point, but I guess once you know what is meant, it's obvious.
Quote from: shawnb61 on November 06, 2019, 04:41:47 PMThis is a difficult discussion, since the broader question raised throughout is what needs to be done to 2.1 to bring it more compliant with i18n. Which is a valid question. But I'm not sure we have an actionable answer yet...