Re: Why the normative form of IETF Standards is ASCII

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In message <4B9AA7FF.4000400@xxxxxx>, Julian Reschke writes:
> On 12.03.2010 21:41, Masataka Ohta wrote:
> > Doug Ewell wrote:
> >
> >> A space character (which looks like an ordinary U+0020 space to me, in
> >> both the plain-text message I received and in the Web archive) got
> >> erroneously converted to a question mark in Tim's plain-text mail.
> >
> > It is not a question mark character but a some strange non-ASCII
> > character, though it is displayed as a question mark in some
> > environment.
> >
> >> How does this demonstrate anything about PDF?
> >
> > As it occurred with pure ASCII profile of non-ASCII-capable e-mail,
> > the same will occur with pure ASCII profile of non-ASCII-capable PDF.
>  > ...
> 
> What *is* a "pure ASCII profile of non-ASCII-capable PDF"? A PDF viewer 
> that doesn't understand, for example, code point 160?

The problem with email is people use html way too much.  TXT ->
HTML -> TXT does not work reliable.  Too many one way transformations.

> Best regards, Julian
> _______________________________________________
> Ietf mailing list
> Ietf@xxxxxxxx
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@xxxxxxx
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]