{"id":498,"date":"2006-10-04T21:05:32","date_gmt":"2006-10-04T18:05:32","guid":{"rendered":"http:\/\/www.all-things-me.net\/blog\/archives\/2006\/10\/04\/recycling-ui-strings-is-bad"},"modified":"2022-04-22T14:01:38","modified_gmt":"2022-04-22T11:01:38","slug":"recycling-ui-strings-is-bad","status":"publish","type":"post","link":"https:\/\/www.all-things-me.net\/blog\/2006\/10\/04\/recycling-ui-strings-is-bad","title":{"rendered":"Recycling UI strings is bad"},"content":{"rendered":"

I work in localisation among other areas of translation and I know it’s very tempting to re-use texts that one might think are “the same”. (What a money-saver it is, too!)<\/p>\n

If only it was that simple.<\/p>\n

One problem is caused by the grammatical gender<\/a>. Here’s a simple example from a text I was working on today (it won’t give anything away): the word “Saved” — that was the whole UI<\/abbr> string. In English and many other languages it can easily be translated and re-used without a problem. But in for example Spanish (I pick a language I know) you need to know what<\/em> has been saved because the adjective\/past participle is inflected depending on whether the subject is masculine or feminine (salvado<\/em> or salvada<\/em> respectively). You can’t use the same 7-character string in all contexts; I suppose most of the time it would just be annoying, in worst cases it might even be confusing.<\/p>\n

Just now I from the library and looked at the file properties in Adobe Reader 7.0. Here’s what the window looks like:<\/p>\n

\"Adobe<\/p>\n

I’ve circled the word Tulostetaan<\/em> (Finnish). In an English program I’m sure it would say “Printing”, that is “Printing is allowed\/not allowed”. The word can also be used when you print a page and the program lets you know that it’s busy doing something by displaying “Printing” or perhaps “Printing…” with animated fullstops. The words do look the same but they don’t mean the same. The problem in Finnish (and other languages) is that, if translated correctly, the words do not<\/b> look the same. “Tulostetaan” can be used in letting us know that the program is busy but not in this context. Here the word ought to be “Tulostaminen”.<\/p>\n

Usually recycling is encourageable — not in localisation I’m afraid.<\/p>\n

Addition, Thu 5th October<\/strong><\/p>\n

I don’t know what has “gone wrong” with the above localisation, and I don’t know if the two (or more) strings are perceived as the same (i.e. use the same resource) or if they just have been copied to save money\/time\/trouble. They shouldn’t be perceived as the same because they clearly aren’t. Some problems could perhaps be solved if at least words that are of different parts-of-speech would be separated from one another (noun printing vs. gerund printing). Perhaps they are. Do remember that I don’t know a thing about application development or the inner workings of Windows applications (among others) so I have no idea what’s going on under the hood.<\/p>\n

I suppose WordPress functions similarly (“the wrong way”) because it uses GNU Gettext framework<\/a> where texts are translated on message level. At closer look it does look like the context is taken into account, though, so problems like in this example on multiple meanings of “post”<\/a> are avoided. Way to go!<\/p>\n","protected":false},"excerpt":{"rendered":"

I work in localisation among other areas of translation and I know it’s very tempting to re-use texts that one might think are “the same”. (What a money-saver it is, too!) If only it was that simple. One problem is caused by the grammatical gender. Here’s a simple example from a text I was working […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,4,23],"tags":[],"class_list":["post-498","post","type-post","status-publish","format-standard","hentry","category-computer-and-gadgets","category-language","category-work"],"_links":{"self":[{"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/posts\/498","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/comments?post=498"}],"version-history":[{"count":2,"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/posts\/498\/revisions"}],"predecessor-version":[{"id":2565,"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/posts\/498\/revisions\/2565"}],"wp:attachment":[{"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/media?parent=498"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/categories?post=498"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.all-things-me.net\/blog\/wp-json\/wp\/v2\/tags?post=498"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}