Henri Sivonen

No replies in one and a half years. @annevk, does the document linked to from the previous sentence look OK to you for submission to the Unicode Technical Committee? (This...

Based on off-issue comments, I [revised](https://hsivonen.fi/unicode-feedback/empty-iso-2022-jp-draft2.pdf) the draft to conclude to go for "End state 1" right away instead of leaving it as non-committal.

Oops. That edit was internally inconsistent. [Tried again.](https://hsivonen.fi/unicode-feedback/empty-iso-2022-jp-draft3.pdf)

If we add API surface that doesn't work in old browsers, I'd like to know if users of the potential API surface care about non-UTF-8 encodings. If not, I'd prefer...

> > since the WebIDL layer is a perf bottle neck > > @hsivonen How so? In Deno we have an optimized path in our WebIDL bindings for this specific...

> High performance applications try to avoid creating temporaries to reduce GC impact. Is there a reason why the JS engines can't do escape analysis and heap-allocate temporary view objects?...

> Thanks for that analysis, I guess that is indeed a novel angle that I'm not sure was fully considered. While novel angle for the Encoding Standard, my understanding is...

The [old Big5 study emails](https://lists.w3.org/Archives/Public/www-archive/2012Apr/0019.html) suggest have evidence of lead bytes in the 0x81 to 0x86 (inclusive) range in pages whose URLs seem no longer to work. How did those...

> The code above produces: Interesting. So it maps to the PUA. _Maybe_ we should map byte pairs with leads in the 0x81 to 0x86 (inclusive) range to the PUA....

https://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WindowsBestFit/bestfit950.txt says "EUDC" for those lead bytes (but also for 0x87 to 0xA0, inclusive). The Unicode.org vendor repo does not appear to have a Microsoft submission for the Hong Kong...