|
Unicode is not an encoding, though.
|
|
Peteris, what is it then? I always thought it was an encoding standard. And so does the Unicode website:
<< The Unicode Standard is the universal character encoding standard used for representation of text for computer processing. >>
From: unicode.org/standard/principle ...
|
|
I was always under the presumption that UTF was a character encoding and Unicode was just the standard.
|
|
I think both are encodings:
Unicode defines how to encode text into numbers (code points).
UTF-(7,8,16,32) define how to encode a series of Unicode code points into a file (this deals with issues like legacy 7-bit systems, endianess, visual compatibility with ASCII, etc.)
|
|
As I understand Unicode is just a standard that defines all the possible characters in the existence (by assigning them a "code point" number). It does not tell how it will be represented in computer memory, it just defines them.
An encoding actually defines how the code points will be represented in memory.
|
|
And this standard also defines how they can be variously represented officially in computer memory. Obviously you understood wrongly. Read the standard.
|
|
Unicode itself is a standard that defines several of those encodings.
|
|
According to the chart if you combine the entries for ascii and the similar western European encoding they are about twice as frequent as unicode.
en.wikipedia.org/wiki/How_to_L ...
en.wikipedia.org/wiki/Lies,_da ...
|
|
BTW, Blogger with FTP is not really ISO compliant... :-/
|
|
Web servers provide bytes, not Unicode characters. Peteris is 100% correct, and the rest of you should [attack removed]
|
