Joerg Schilling <joerg.schill...@fokus.fraunhofer.de> wrote:
|Steffen Nurpmeso <stef...@sdaoden.eu> wrote:
|>|> have some Unicode support.
|>|
|>|What do you expect:
|>|
|>| strtol("\u4e00\u4e8c\u4e09", &endp, 0);
|>
|> The entire is*() family cannot work with multibyte or stateful
|> encodings, right.
|
|I asked a person who speaks japanese and he told me that
|
| "\u4e00\u4e8c\u4e09"
|
|is similar to
|
| "one two three"
|
|and this is not used for computing.
If i recall correctly this has been discussed already; if not here
then on the Unicode list. Unicode brings quite a lot of
codepoints, like CIRCLED DIGIT ONE, PARENTHESIZED DIGIT ONE, DIGIT
ONE FULL STOP etc. All these are marked "No", and i think the
discussion concluded that they should not be taken into account
when converting strings to numbers. Hans Åberg surely knows
better than I.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
