Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27) from jungshik on 2017-10-16 (public-webapps-github@w3.org from October 2017)

From: jungshik <notifications@github.com>
Date: Mon, 16 Oct 2017 17:37:42 +0000 (UTC)
To: whatwg/encoding <encoding@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/encoding/issues/27/336964103@github.com>

> Besides, supporting PUA code points in the context of the Noto CJK and Source Han fonts is a total non-starter, mainly because they are Pan-CJK typefaces, and PUA usage is extremely dangerous in such contexts.

There's no doubt about that ! I'm in full agreement with you on that. 

> This means that the chance of encountering them in the wild, in genuine documents, is somewhere between very slim and none.

What I'm saying is that repeating what's done in 2005 is likely to be slightly better in terms of rendering legacy gb18030 documents on Android and other places where no font support for U+Exxx PUAs is available.  (note that newer WIndows Chinese fonts do not cover those PUA code points either). 

However, given what @kenlunde  wrote, it may not matter much whichever way we choose. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/27#issuecomment-336964103

Received on Monday, 16 October 2017 17:38:11 UTC