Ken Lunde

While I cannot confirm about the *.ttf versions, at least for the *.otf versions, I confirmed through experimentation that Illustrator—and Photoshop, which uses the same layout engine—uses the second element...

@annevk By "escape followed by an escape," you are referring to ISO 2022 escape **sequences**, not individual "escape" (U+001B) characters, right? If so, back in the day when ISO 2022...

The following paragraph is from the bottom of page 583 of [_CJKV Information Processing_, Second Edition](http://shop.oreilly.com/product/9780596514471.do): > Besides simple code conversion, it is also very important to be able to...

@annevk In my opinion, enough time has passed that anything that is Unicode-encoded should have no realistic or real-world need to convert back to legacy encodings, particularly because almost all...

@EarlgreyPicard In other words, you agree with my suggestion to simply nuke the no-op escape sequences.

@EarlgreyPicard Sorry. To clarify, I meant 1) to remove no-op escape sequences; and 2) to not emit U+FFFD in their presence.

@Artoria2e5: The reasons why Source Han Sans (and the Google-branded Noto Sans CJK) does not support the 24 PUA code points of GB 18030 are because 1) PUA code points...

@annevk: I will ping my contact at CESI in China to get the current status of the GB 18030 revision.

@annevk: My contact at CESI told me that a draft of the GB 18030 is expected to be available sometime this year, and is expected to fix known issues, such...

Sufficient time has passed that to implement GB 18030 in any encoding other than Unicode makes no sense. The main benefit of the GB 18030 revision is to simply remove...