valentina 2

[Olivier]

Le 4 janv. 05, à 15:42, Ruslan Zasukhin a écrit :

> With UTF8 work only software products that do not have time or power to
> switch to UTF16.

Strange.

In Matt Neuburg's article in " Realbasic developer " N°2.2, page 24, 
Matt presents us the various Unicode (32,16 and 8).
The UTF8 is clearly presented as being the best:

"UTF-8 is still more complicated, but it’s also very ingeniously 
designed to be compact and easily machine-parsable. In contrast to 
UTF-16, where every string is at least twice as long as its ASCII 
counterpart,
in UTF-8 the 128 ASCII values appear as themselves, a single byte, so 
that they take up no extra space; ASCII strings are completely 
interchangeable with UTF-8 strings consisting of just ASCII values. 
Other characters are represented by two, three, or four bytes, in 
accordance with a clever mathematical formula such that (1) you know 
instantly from the first byte of a UTF-8 character how many bytes it 
consists of, and (2) if you start with a byte in the middle of a UTF-8 
string, you know instantly whether this is the first byte of a 
character and, if not, you can easily find the first byte. The UTF-8 
representation of Spanish enye is C3B1, but note that this is just a 
way of writing bytes; it still represents (by way of the mathematical 
formula) the numeric value F1."


In practice, how does it take place between Valentina and does 
realbasic? If for the moment Valentina uses only utf-16 and realbasic 
utf-8, it is necessary for every writing / reading to make a 
conversion? As before?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1849 bytes
Desc: not available
Url : http://lists.macserve.net/pipermail/valentina-beta/attachments/20050104/cae951b4/attachment.bin