4 ms·

> for example Farsi in Egypt (Egyptians primarily speak an Egyptian Dialect of Arabic) Nit picking here maybe, but neither Farsi (Persian) is a dialect of Arab

> for example Farsi in Egypt (Egyptians primarily speak an Egyptian Dialect of Arabic) Nit picking here maybe, but neither Farsi (Persian) is a dialect of Arabic (not even in the same family of languages) nor Egyptians speak it typically. Although, they speak a dialect of Arabic. Update: My mistake, as pointed out here, I misunderstood the point initially.

sunir 4y ago
I believe that was the exact point the article was making.
frogulis 4y ago
Yup, that's the exact point they're making. Non-Arabic-speaker sees Arabic script and assumes it's the Arabic language, so presents it to users that don't understand it, such as presenting Farsi text to Egyptian Arabic speakers. Or, to take the Latin script example, presenting French text to English speakers.
- throwntoday 4y ago
  Well as the Persian and Arabic alphabet are nearly identical, unicode doesn't appear to store two distinct copies, instead just storing one plus the additional characters for Persian. Oddly though, it stores several copies of identical chinese characters. Traditional, simplified, and the Japanese loaned characters kanji.
  - jcranmer 4y ago
    > Oddly though, it stores several copies of identical chinese characters. Traditional, simplified, and the Japanese loaned characters kanji. Actually, all of those characters are usually unified into one code point. This is controversial enough on its own that there's a Wikipedia page on it: https://en.wikipedia.org/wiki/Han_unification https://en.wikipedia.org/wiki/Han_unification
  - throwaway290 4y ago
    > Traditional, simplified, and the Japanese loaned characters kanji. Traditional, simplified, Japanese, Korean. Some are identical, some different. I wonder why these rendering details were not left to fonts and you can type 雨 and ⾬ for example. Maybe stronger presence of those countries in whatever SDOs and tech integration has to do with it.

sunir 4y ago

I believe that was the exact point the article was making.

frogulis 4y ago

Yup, that's the exact point they're making. Non-Arabic-speaker sees Arabic script and assumes it's the Arabic language, so presents it to users that don't understand it, such as presenting Farsi text to Egyptian Arabic speakers. Or, to take the Latin script example, presenting French text to English speakers.

throwntoday 4y ago
Well as the Persian and Arabic alphabet are nearly identical, unicode doesn't appear to store two distinct copies, instead just storing one plus the additional characters for Persian. Oddly though, it stores several copies of identical chinese characters. Traditional, simplified, and the Japanese loaned characters kanji.
- jcranmer 4y ago
  > Oddly though, it stores several copies of identical chinese characters. Traditional, simplified, and the Japanese loaned characters kanji. Actually, all of those characters are usually unified into one code point. This is controversial enough on its own that there's a Wikipedia page on it: https://en.wikipedia.org/wiki/Han_unification https://en.wikipedia.org/wiki/Han_unification
- throwaway290 4y ago
  > Traditional, simplified, and the Japanese loaned characters kanji. Traditional, simplified, Japanese, Korean. Some are identical, some different. I wonder why these rendering details were not left to fonts and you can type 雨 and ⾬ for example. Maybe stronger presence of those countries in whatever SDOs and tech integration has to do with it.