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

My original comment was purely an editorial issue, which I believe has 
been fixed.

Perhaps we should continue this discussion on a new thread, since it is 
not directly related.

RI



On 17/09/2013 08:13, Sylvain Galineau wrote:
>
>
> 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.
>


-- 
Richard Ishida