- From: Ned Freed <Ned.Freed@INNOSOFT.COM>
- Date: Sun, 05 Apr 1998 22:35:45 -0700 (PDT)
- To: (wrong string) ща <alb@sct.gouv.qc.ca>
- Cc: Tom Hastings <hastings@cp10.es.xerox.com>, Chris Newman <Chris.Newman@INNOSOFT.COM>, Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, ietf-charsets@ISI.EDU
> > Strictly speaking, the ISO 8859-n series are only graphic character sets, > > i.e., they are only specifying code positions 0x20 to 0x7e and 0xa0 to 0xff; > > they are silent about code positions 0x00 to 0x1f, 0x7f, and 0x80 to 0x9f > > which is where CR and LF go. > That is correct, the whole series is only dealing with graphic characters, > not even with CR/LF, which are of course an essential part of the text data > realm anyway, but ouside this series of standards. This is dealt with quite explicitly in RFC 2026 section 4.1.2 -- the lower 128 characters of all the ISO-8859-x registrations are forced into alignment with US-ASCII. Ned --Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)
Received on Sunday, 5 April 1998 22:40:09 UTC