From 8632502166372115998 X-Google-Language: ENGLISH,ASCII X-Google-Thread: f78e5,b1fa62568eb1d2a7 X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 2002-02-26 09:40:05 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!logbridge.uoregon.edu!news.maxwell.syr.edu!btnet-peer1!btnet-peer0!btnet!dispose.news.demon.net!news.demon.co.uk!demon!mail2news.demon.co.uk!not-for-mail From: kanze@gabi-soft.de (James Kanze) Newsgroups: comp.std.c++ Subject: Re: Unicode vs. Char Date: Tue, 26 Feb 2002 17:39:31 GMT Organization: http://groups.google.com/ Approved: Fergus Henderson , moderator of comp.std.c++ Message-ID: References: <0hU68.89357$h31.5940930@e420r-atl1.usenetserver.com> <3C6B0579.6FB164C6@acm.org> <3C72E1EC.90E8CFD1@acm.org> X-Trace: mail2news.demon.co.uk 1014745177 mail2news:1156 mail2news mail2news.demon.co.uk X-Complaints-To: abuse@demon.net X-Mail2News-Path: news.demon.net!mulga.cs.mu.oz.au X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit NNTP-Posting-Date: 22 Feb 2002 12:39:35 GMT Lines: 33 Xref: archiver1.google.com comp.std.c++:9759 Pete Becker wrote in message news:<3C72E1EC.90E8CFD1@acm.org>... > James Kanze wrote: > > Unicode is supposed to be more or less compatible with ISO 10646, > > and the standard refers to this code set elsewhere. > Yes, as Hans pointed out, it is part of the description of universal > character names. What threw me was the reference to "Unicode > strings." There is no way to say 'the characters in this string are > Unicode', although you can say 'this character is Unicode'. You can't even say that. All you can say is that you want the code (in whatever code set the implementation feels like giving you) that corresponds to the Unicode character with the following code. There are a number of reasons why the standard shouldn't require a specific code set, even for wchar_t. On the other hand, Unicode/ISO 10646 are universal enough that one might like some sort of indication concerning their support, something like is_iec559 in numeric_limits for IEEE floating pointer. -- James Kanze mailto:kanze@gabi-soft.de Beratung in objektorientierer Datenverarbeitung -- -- Conseils en informatique orient�e objet Ziegelh�ttenweg 17a, 60598 Frankfurt, Germany, T�l.: +49 (0)69 19 86 27 --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.research.att.com/~austern/csc/faq.html ]