Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!novia!nx02.iad01.newshosting.com!newshosting.com!news-out.readnews.com!transit3.readnews.com!panix!panix.com!mrbrklyn From: Ruben Safir Newsgroups: comp.lang.c++ Subject: Re: UTF-8 and strings Date: Sat, 11 Jun 2011 00:29:14 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 20 Message-ID: References: NNTP-Posting-Host: panix2.panix.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: reader1.panix.com 1307752154 3278 166.84.1.2 (11 Jun 2011 00:29:14 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Sat, 11 Jun 2011 00:29:14 +0000 (UTC) User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (NetBSD/5.1 (i386)) Xref: x330-a1.tempe.blueboxinc.net comp.lang.c++:6598 John M. Dlugosz wrote: > On Jun 9, 7:36=A0am, "MikeP" wrote: >> >> But isn't Windows (XP)'s "UTF-16" really UCS-2 and hence not a risk at >> all then? >=20 > Originally, yes. At some point it went to real UTF-16 awareness, at > least for rendering strings using fonts into windows, and converting > between code pages correctly. This was around Windows-2000 or XP, > certainly well before Windows 7. I don't need my text editor to absorb all the complexity of a word processor. >=20 > I think the file system is technically still USC-2 in that it doesn't > care what the code points mean and doesn't reject improper use of > surrogate pairs as errors. >=20