- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 04 Jan 2010 21:15:45 +0100
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- CC: WebApps WG <public-webapps@w3.org>
Boris Zbarsky wrote: > ... > Mozilla trunk already does byte _inflation_ when converting from header > bytes into a JavaScript string. I assume you meant to convert > JavaScript strings into header bytes via dropping the high byte of each > 16-bit code unit. However that fails the "preserve as much information > as possible" test... In particular, as soon as any Unicode character > outside the U+0000-U+00FF range is used, byte-dropping loses information. > ... But what's the alternative? Decide the encoding in each case? The encoding not being predictable seems to be worse than anything else... BR, Julian
Received on Monday, 4 January 2010 20:16:23 UTC