Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsreader4.netcologne.de!news.netcologne.de!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <5433557.orKWNd2VbX@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Sat, 20 Apr 2013 01:23:26 +0200 User-Agent: KNode/4.8.5 Content-Transfer-Encoding: 8Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. MIME-Version: 1.0 Lines: 35 NNTP-Posting-Date: 20 Apr 2013 01:23:26 CEST NNTP-Posting-Host: 85247a2d.newsspool4.arcor-online.net X-Trace: DXC=`cQ5OD4o2W[I?44J>Z[:RQ4IUK Jerry Stuckle wrote: >> But be aware just because YOU are working with an ASCII charset, not >> everyone is. ACK. > I'm not looking for worldwide compatibility. On the World Wide Web, most certainly you should. US-ASCII is simply obsolete there, because it hinders more than it helps. The default character encoding for HTTP/1.0 and later is ISO-8859-1 (which AFAIK is PHP's default, too), and using UTF-8 or UTF-16 becomes increasingly common both on the Web and in current operating systems (see e. g. the percent encoding in RFC 3986 how to handle that). Most recently, IDNs have been introduced. PHP is fully equipped to deal with that (through functions), even though it has no native Unicode string support. > My primary concern is with the annoying affectation a few users have of > using a slashed zero in place of a just plain zero. None are using a non > ASCII character set otherwise. One problem with helping you with your problem is that the term “slashed zero” actually is _not_ well-defined. PointedEars -- var bugRiddenCrashPronePieceOfJunk = ( navigator.userAgent.indexOf('MSIE 5') != -1 && navigator.userAgent.indexOf('Mac') != -1 ) // Plone, register_function.js:16