J
Jukka K. Korpela
Scripsit Ben C:
It's an absurdity, since control characters proper cannot be rendered as
normal characters. By definition, they have control functions, not
visible rendering. Whether spaces are control characters is a matter of
definition.
This isn't the only part in the CSS 2.1 draft that is hopelessly messy
and obscure, especially if taken as an attempt to dictate what happens
in processing HTML documents in general, rather than as relating
(somehow) to the CSS property being discussed there.
Well it says in 16.6.3 that "Control characters other than tab,
line-feed, space and bidi formatting characters are treated as
characters to render in the same way as any normal character".
You can probably explain better what that means, but as far as I can
tell, implementors are meant to leave the non-breaking spaces in.
It's an absurdity, since control characters proper cannot be rendered as
normal characters. By definition, they have control functions, not
visible rendering. Whether spaces are control characters is a matter of
definition.
This isn't the only part in the CSS 2.1 draft that is hopelessly messy
and obscure, especially if taken as an attempt to dictate what happens
in processing HTML documents in general, rather than as relating
(somehow) to the CSS property being discussed there.