Bad Internationalization Can Get You Killed

This story, of a divorcing couple who both ended up dead due to their cellphone system not supporting ‘ı’ (a Turkish letter called ‘dotless’ or ‘closed’ i), shows why proper i18n in software systems is very important. (Warning: story contains very strong language.)

8 thoughts on “Bad Internationalization Can Get You Killed

  1. I’m really tired of this political correctness: “Warning: story contains very strong language”

    When it comes to murder and death in a story hen strong language is the less important issue.

  2. The fact that there is death in the story was flagged up by my write-up, but the language was not – hence the extra note. Political correctness is changing language so as not to offend people. I think sometimes that is appropriate, but in any case that’s not what I did here. I did precisely the opposite – I didn’t change the language (I just warned people about it).


  3. > Political correctness is changing language so as not to offend people

    Well, warning about strong language is also political correctness:

    The whole thing goes into the same direction as brutal movies which are ok for the audience as long as no one is using strong language. Ridiculous.

    But anyway: your blog, your rules.

  4. Good internationalization is still important, of course, but it seems to me that a culture of stupid violence got the two killed in this case.

  5. Ironically, your RSS feed also mishandles the ‘ı’ and shows it as ‘ı’.
    I hope you won’t get killed over that… ;-)

  6. Oh no. Thank you so much for warning me that the article had a swear word in it. If I had seen the word I would go raving mad and kill innocent people. Thank you for watching out for me. I don’t know what I would’ve done without the warning.

  7. mscha: I see the dotless i correctly in Gerv’s post; but sometimes, in other posts, I’ve had to use “View => Reload” before the text was shown correctly, and at other times, even reloading the mail wasn’t enough, but replying to it showed the correct characters in the quoted text above my reply. I would report it as a bug if I could describe it in a not-too-vague manner.

Leave a Reply

Your email address will not be published. Required fields are marked *