3 ms·
The problem was that Emine's cell phone was not localized properly for Turkish and did not have the letter <ı>; when it displayed Ramazan's message, it replaced
by orphea 1y ago
The problem was that Emine's cell phone was not localized properly for Turkish and did not have the letter <ı>; when it displayed Ramazan's message, it replaced the <ı>s with <i>s.
Does it make sense? Could the phone arbitrarily replace characters? Or could it more likely that the guy typed dotted i's?
- eknkc 1y agoI think the article is somewhat fabrication. There might be some truth to it but it does not make much sense. Technically, ı would probably show up as □ instead of i if the phone had a hard time displaying it. There is also the suffix not matching that change: sıkışınca vs sikişince. A becomes E in that suffix when you switch from ı to i. Even if the phone fucked up, "sikişinca" would look weird.
- GoblinSlayer 1y agoI noticed that countries with latin script use latin-1 encoding for sms, because they never really needed unicode. Then when software converts text to latin-1 or acsii, there's an option to find the best match character in ascii repertoire, I think in that case ı will be converted to i.
- seba_dos1 1y agoIt's not latin-1, and it's not ASCII either. It's 7-bit GSM 03.38 charset, with optional shift tables. You can use either that or UCS-2 (though these days phones use UTF-16 instead), and UCS-2/UTF-16 significantly limits the number of characters that fit into the message (160 vs. 70).