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
