[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XML and mainframes, yet again (was RE: So

• To: Elliotte Rusty Harold <elharo@m...>
• Subject: Re: XML and mainframes, yet again (was RE: So me comments on the 1.1 draft)
• From: John Cowan <cowan@m...>
• Date: Sun, 16 Dec 2001 21:58:13 -0500 (EST)
• Cc: John Cowan <cowan@m...>, xml-dev@l...
• In-reply-to: <p04330105b842fa88d32e@[192.168.254.4]> from Elliotte Rusty Haroldat "Dec 16, 2001 09:35:51 pm"

Elliotte Rusty Harold scripsit:

> >EBCDIC vs. ASCII is perfectly irrelevant to this discussion: mainframes
> >can work with ASCII files as well as EBCDIC files, but in either
> >case the NEL character (encoded as hex 85 in ASCII encoding or
> >hex 15 in EBCDIC encoding) is the native line delimiter.
> 
> Again, that's simply not true. There is no NEL in ASCII. A document 
> that includes NEL (or any other byte above #7F) is not an ASCII 
> document.

Fair enough.  I should have said "ASCII-compatible encoding".

-- 
John Cowan           http://www.ccil.org/~cowan              cowan@c...
Please leave your values        |       Check your assumptions.  In fact,
   at the front desk.           |          check your assumptions at the door.
     --sign in Paris hotel      |            --Miles Vorkosigan

• References:
  • Re: XML and mainframes, yet again (was RE: So me comments on the 1.1 draft)
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: Suggestion for an alternative XML 1.1
• Next by Date: OT: Research Survey on Content-Driven Applications
• Previous by thread: Re: XML and mainframes, yet again (was RE: So me comments on the 1.1 draft)
• Next by thread: Some thoughts about the compatibility between XML 1.0 and XML 1.1
• Index(es):
  • Date
  • Thread