{"id":73,"date":"2014-10-19T23:13:16","date_gmt":"2014-10-20T03:13:16","guid":{"rendered":"http:\/\/expectedly.org\/inclusivetech\/?p=73"},"modified":"2017-10-24T02:27:52","modified_gmt":"2017-10-24T06:27:52","slug":"label-in-own-language","status":"publish","type":"post","link":"https:\/\/expectedly.org\/inclusivetech\/label-in-own-language\/","title":{"rendered":"Write language labels in their own language"},"content":{"rendered":"

(Edit, 24 Oct 2017: included Dropbox as a good example of what to do)<\/em><\/p>\n

When creating language selectors, make sure the language labels are written in that language, not the language the page is currently on if it differs. For example, on an English-language web page, German should be written as Deutsch<\/strong>, not German<\/strong>. This makes it easier for people to find their own language. Someone browsing a website that defaults to Japanese and wants to find German may not know that \u30c9\u30a4\u30c4\u8a9e<\/strong> means Deutsch<\/strong>. But if the link says Deutsch<\/strong> they will be able to recognise it. Wikipedia uses this strategy when labelling languages in the sidebar – if you want to find Czech<\/strong>, you just need to find \u010ce\u0161tina<\/strong>. Also, make sure the languages are alphabetised by their own name, not by their names in English or another language.<\/p>\n

Example of what to do:<\/strong><\/p>\n

\"Screenshot<\/a><\/p>\n

Dropbox writes language labels using their own names, so German is Deutsch<\/em> and Indonesian is Bahasa Indonesia<\/em>. (They also get a few other things right too – they label all dialects for English, Chinese and Spanish and include indicators for Norwegian and Portuguese as well. Flags are not used to represent languages. The languages are alphabetised according to their own names, not their English names. The Ukrainian translation is a beta and is marked as such.)<\/p>\n

Example of what not to do:<\/strong><\/p>\n

\"A<\/a><\/p>\n

This is a screenshot from SquirrelMail, a popular webmail web app that comes installed with many hosting packages. The language chooser has all the languages listed in English <\/strong>(except for Malay and Indonesian, for some reason), regardless of whether the UI language is set to English or not. If I speak Arabic and want to find it in a list, I don’t want to search for the English name.<\/p>\n

Bad<\/strong>:
\nAllemand
\nAnglais
\nChinois
\nEspagnol
\nFran\u00e7ais
\nItalien
\nHongrois
\nJaponais
\nN\u00e9erlandais
\nPolonais
\nPortugais
\nRusse
\nSu\u00e9dois
\nTch\u00e8que<\/p>\n

Good<\/strong>:
\n(language drop-down or unordered list)
\n\u010ce\u0161tina
\nDeutsch
\nEnglish
\nEspa\u00f1ol
\nFran\u00e7ais
\nItaliano
\nMagyar
\nNederlands
\nPolski
\nPortugu\u00eas
\n\u0420\u0443\u0441\u0441\u043a\u0438\u0439
\nSvenska
\n\u65e5\u672c\u8a9e
\n\u4e2d\u6587<\/p>\n","protected":false},"excerpt":{"rendered":"

(Edit, 24 Oct 2017: included Dropbox as a good example of what to do) When creating language selectors, make sure the language labels are written in that language, not the language the page is currently on if it differs. For example, on an English-language web page, German should be written as Deutsch, not German. This… Continue reading Write language labels in their own language<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/posts\/73"}],"collection":[{"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/comments?post=73"}],"version-history":[{"count":6,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/posts\/73\/revisions"}],"predecessor-version":[{"id":211,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/posts\/73\/revisions\/211"}],"wp:attachment":[{"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/media?parent=73"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/categories?post=73"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/tags?post=73"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}