Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <2148269.SXehZU3gLx@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Sat, 22 Sep 2012 21:12:23 +0200 User-Agent: KNode/4.4.11 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+&. <1621260.MulQa8nmlF@PointedEars.de> <505db945$0$6958$e4fe514c@news2.news.xs4all.nl> <35486874.FMhRtqDPO2@PointedEars.de> <505df60b$0$6917$e4fe514c@news2.news.xs4all.nl> Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 19 NNTP-Posting-Date: 22 Sep 2012 21:12:23 CEST NNTP-Posting-Host: 19dde149.newsspool3.arcor-online.net X-Trace: DXC=g0]KGA5ja>mPKPPVf;4hUjMcF=Q^Z^V3h4Fo<]lROoRa8kF […] it took some experimenting with combinations of the native string > types in my server environment and the encoding in the processing > instruction. I've tried combinations of string types (ANSI, utf8, unicode) > with encoding specs 'utf-8', 'utf-16' and absent. All work in Chrome. In > IE8 all fail if there is a diacritic in the data. What does work is the > combination of unicode string and 'iso-8859-1'. Doesn't make it universal > […] Correct, that makes it wrong. PointedEars -- Sometimes, what you learn is wrong. If those wrong ideas are close to the root of the knowledge tree you build on a particular subject, pruning the bad branches can sometimes cause the whole tree to collapse. -- Mike Duffy in cljs,