341 reputation
212
bio website malcolm-soft.com
location New York, United States
age 24
visits member for 2 years, 11 months
seen 15 hours ago

Mobile application developer who freaking loves what he does - that's the most apt description for me. I mainly spend time writing something for Android, but I also play a lot with other technologies as well.


Feb
20
comment Should UTF-16 be considered harmful?
Well, if I had to choose between UTF-8 and UTF-16, I would definitely stick to UTF-8 as it has no BOM, ASCII-compliant and has the same encoding scheme for any plane. But I have to admit that UTF-16 is simpler and more efficient for most BMP characters. There's nothing worng with UTF-16 except the psychological aspects (mostly fixed-size isn't fixed size). Sure, one encoding would be better, but since both UTF-8 and UTF-16 are widely used, they have their advantages.
Sep
26
comment Should UTF-16 be considered harmful?
If BMP is that far from having enough capacity to write normally in Chinese, how do they manage to write in such encodings as GBK or GB 2312? It is clear that support of other planes would be useful, but nonetheless.
Aug
12
comment Should UTF-16 be considered harmful?
It does, but characters outside BMP are not for everyday use, they can be used, for example, for old texts or to write names with rare hieroglyphs in them. And all characters that are commonly used fit into BMP.
Jul
2
comment Should UTF-16 be considered harmful?
There is, but it's not really a problem specific for Unicode since standart encodings also don't include this characters. People use homophones and other ways to write such names, and that can be done in any encoding, including Unicode. Probably there are serious difficulties even with inputting rare symbols, so the situation doesn't happen all of a sudden and users won't be surprised to find out the program is refusing to accept them correctly if it does.
Jun
29
comment Should UTF-16 be considered harmful?
And what did I write wrong? All characters of plane 2 contain only rare or historic symbols and all other characters fit into BMP and thus don't need surrogate pairs.
Jun
27
comment Should UTF-16 be considered harmful?
Not true, Asian scripts like Japanese, Chinese or Arabic belong to BMP also. BMP itself is actually very large and certainly large enough to include all the scripts used nowadays, it's not like it includes only European scripts or something. No, if you are really going to encounter non-BMP characters, you'll almost definitely know it.
Jun
26
comment Should UTF-16 be considered harmful?
UTF-16 is simpler for anything inside BMP, that's why it is used so widely. But I'm a fan of UTF-8 too, it also has no problems with byte order, which works to its advantage.
Jun
26
comment Should UTF-16 be considered harmful?
I agree with the last edit. The simplest example: we still use C and C++ though both languages use pointers and thus are not safe.
Jun
26
comment Should UTF-16 be considered harmful?
Actually I'm from Russia and encounter cyrillics all the time (including my own programs), so I don't think that I have Anglo-centric view. :) Mentioning ASCII is not quite appropirate, because it's not Unicode and doesn't support specific characters. UTF-8, UTF-16, UTF-32 support the very same international character sets, they are just intended for use in their specific areas. And this is exactly my point: if you use mostly English, use UTF-8, if you use mostly cyrillics, use UTF-16, if you use ancient languages, use UTF-32. Quite simple.
Jun
26
comment Should UTF-16 be considered harmful?
Certainly. But that doesn't mean that if someone can use something incorrectly, we shouldn't use it at all, right?