What? No! UTF-8 takes, at most, 4 bytes per code point.
"But UTF-8 isn't very efficient at storing Asian symbols, taking a whole three bytes. The eastern masses revolted at the prospect of having to buy bigger hard drives and made their own encodings."
Many asian users object to UTF-8/Unicode because of the Han Unification, and because many characters supported in other character sets are not present in Unicode. Size of the binary encoding has nothing to do with it -- in fact, most east-asian characters take 4 bytes in UTF-16.
"American programmers: In your day to day grind, it's superfluous to put a 'u' in front of every single string."
American programmers who aren't morons: Use 'u' or the first time somebody tries to run an accent through your code, it'll come out looking like line noise.
>What? No! UTF-8 takes, at most, 4 bytes per code point.
I thought each half of a UTF-16 surrogate pair used 3 bytes in UTF-8, but it turns out that this is an incompatible modification of UTF-8 called CESU-8. http://en.wikipedia.org/wiki/CESU-8
Lobstertech wrote:
> American programmers: In your day to day grind,
> it's superfluous to put a 'u' in front of every single
> string."*
Good idea, who cares about internationalization? You can
always just pay someone in India to go over all of your
code the day you notice the rest of the world
Regards,
European developer
(... who doesn't want more competition)don't forget to add:
# -*- coding: utf-8 -*-
set encoding=utf-8
set fileencoding=utf-8this will cause problems on windows.