Re: Character Data

Daniel W. Connolly (connolly@hal.com)
Thu, 22 Sep 94 13:48:25 EDT

In message <9409221044.aa00721@dali.scocan.sco.COM>, Murray Maloney writes:
><P>
>Because certain special characters are subject to interpretation
>and special processing, information providers and
>browser implementors should follow
><A HREF="#spclchars"> these guidelines </A>

This paragraph is misleading. In HTML 2.0, there are no characters
that are "subject to interpretation and special processing."
There's just ISO8859-1 -- a bunch of character glyphs, two or
three control characters, and the rest are not used.

><P>
>Certain characters may not be accessible from your
>keyboard, or some part of your system (i.e. translation software)
>may not be equipped to deal with 8-bit character codes.

This is correct. And it is the _only_ reason for the ISO Added
Latin 1 entity names in HTML (well... you could also say
that they serve a mnemonic purpose).

><H4> Line Feed (LF - 10 dec) </H4>
><UL>
><LI> Interpreted as a word space in all contexts except &lt;PRE&gt;.
><LI> Within &lt;PRE&gt;, the tab should be interpreted
>as a shift to the start of a new line;
>that is, <CODE> col := 0; row := row+1 </CODE>
></UL>
><H4> Carriage Return (CR - 13 dec) </H4>
><UL>
><LI> Interpreted as a word space in all contexts except &lt;PRE&gt;.
><LI> Within &lt;PRE&gt;, the tab should be interpreted
>as a shift to the start of the line;
>that is, <CODE> col := 0; </CODE>
></UL>
></UL>

What if a line is terminated by CRLF in PRE content? Does
that count as 1 linebreak or 2?

Corprew: could you run some tests?

I think this could be clarified.

Dan