[Top] [All Lists]

Re: The transition to UTF-8 header fields

1999-02-11 10:09:01
In <199902101331(_dot_)IAA20315(_at_)spot(_dot_)cs(_dot_)utk(_dot_)edu> Keith 
Moore <moore(_at_)cs(_dot_)utk(_dot_)edu> writes:

OK, so what would that look like? Presumably it would have to include
downgrading of some sort.

one thing at a time.  first, you need a good spec for the format,

Well I recently posted here a summary of what USEFOR is proposing -
essentially all protocol words must be ASCII, stuff for humans may be
non-ASCII (phrases, unstructureds, values of some parameters, etc). There
will be a new USEFOR draft out shortly with detailed syntax (though still
needing some details fixing). That could be a good starting point.

probably along with some strong discouragement to ship
UAs that generate raw UTF-8 by default 
(but support for reading it might not be such a bad idea)

the downgrading document can follow  - actually it should specify
translation in both directions.

Yes, something like that.

Charles H. Lindsey ---------At Home, doing my own thing------------------------
Email:     chl(_at_)clw(_dot_)cs(_dot_)man(_dot_)ac(_dot_)uk  Web:
Voice/Fax: +44 161 437 4506      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9     Fingerprint: 73 6D C2 51 93 A0 01 E7  65 E8 64 7E 14 A4 AB A5