- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Sat, 10 May 2014 15:07:58 -0700
- To: Zack Weinberg <zackw@panix.com>
- CC: "www-style@w3.org" <www-style@w3.org>, Anne van Kesteren <annevk@annevk.nl>
On 03/20/2014 02:11 PM, Zack Weinberg wrote: > On Wed, Mar 19, 2014 at 11:00 PM, James Clark <jjc@jclark.com> wrote: > > I have no opinion on most of this, but ... > >> 1. In addition to 0x9, 0xA and 0xD, Unicode gives characters 0xB (VT), 0xC >> (FF) and 0x85 (NEL) the White_Space property. Characters with the >> White_Space property are supposed to be rendered as a visible but blank >> space. (Of these, HTML includes only 0xC as a space character.) > > For compatibility with legacy content naively converted to UTF-n, > U+0085 (and, indeed, the entire C1 controls block) need to be > interpreted as graphic characters per Windows-1252, instead of as > control characters. Should this be handled at the render layer or at the encoding layer? (The latter is only possible of course if there are Unicode equivalents.) ~fantasai
Received on Saturday, 10 May 2014 22:08:31 UTC