MvdV> I have seen some arguments against using UTF-8 in messages. So far MvdV> however I have seen no arguments against UTF-8 in the nodelist. Other MvdV> than using ANY non ASCII characters that is.
In that way of reasoning, the current nodelist with it 7bit limit, is encoded in all characterset, that are identical to ascii. There is some experience, when 8 bit characters are used, but have you ever tried to process and use a nodelist with e.g. Bjorn's name encoded in 16 bit values.
MvdV> That of course is not practical. The only practical downward compatible MvdV> way is that the whole nodelist is in one and the same character encoding MvdV> scheme. And since there is no single 8 bit character encoding scheme MvdV> that can fulfil the needs of all the users of the nodelist, UTF-8 is the MvdV> only logical choice for encoding the nodelist.
Shure keep the 7 bit check in makenl and claim the nodelist is in UTF-8 ;)
Kees
--- FPD v2.9.040207 GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
