W3C home > Mailing lists > Public > www-style@w3.org > September 2013

Re: [css-fonts-3] i18n-ISSUE-296: Usable characters in unicode-range

From: Sylvain Galineau <galineau@adobe.com>
Date: Tue, 17 Sep 2013 00:13:52 -0700
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Anne van Kesteren <annevk@annevk.nl>
CC: Jonathan Kew <jfkthame@googlemail.com>, John Daggett <jdaggett@mozilla.com>, Addison Phillips <addison@lab126.com>, Richard Ishida <ishida@w3.org>, W3C Style <www-style@w3.org>, www International <www-international@w3.org>
Message-ID: <CE5DCD6C.C5A9%galineau@adobe.com>


On 9/15/13 1:28 PM, ""Martin J. Dürst"" <duerst@it.aoyama.ac.jp> wrote:

>On 2013/09/13 20:22, Anne van Kesteren wrote:
>> On Fri, Sep 13, 2013 at 11:33 AM, Jonathan Kew<jfkthame@googlemail.com>
>> wrote:
>>> This is a tricky issue, IMO. What would it mean for the rendering
>>>subsystem
>>> to "treat lone surrogates as errors", exactly?
>>
>> Basically to treat them as if U+FFFD was passed. That's how we deal
>> with them in the encoding layer and in character references and such.
>
>So that would mean that all lone surrogates render the same, and the
>same as some other stuff? I think it would be better to show what's
>there, because that may help in debugging.

+1. If something is going to be shown, the hexbox option seems the most
helpful.

Received on Tuesday, 17 September 2013 07:14:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:34 UTC