In <3E1DBF72(_dot_)8050109(_at_)alex(_dot_)blilly(_dot_)com> Bruce Lilly
<blilly(_at_)erols(_dot_)com> writes:
Charles Lindsey wrote:
The occurrence in a Netnews article of a
Return-Path containing non-ASCII within a comment is as unlikely as they
come.
You have completely missed the point. That point is that your
"heuristic" is inherently unworkable. Any scheme that requires
encoding content via standard (e.g RFC 2047, 2231, 2396) methods
for header fields requires that the syntax of the header field
be known.
And you have completely missed the point, which is that these situations,
which are not supposed to happen, WILL happen in the real world.
So you cannot say "this will never happen, so we need do nothing about
it". You have to specify _something_.
So the possibilities are:
1. Use some heuristic that works most of the time
2. Drop it on the floor (i.e. it works none of the time)
and another possibility that occurs to me:
3. Convert it to an X- header (stick and "X-" on the front) and convert
that according to RFC 2047. At least that way no information gets lost.
--
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl
Email: chl(_at_)clw(_dot_)cs(_dot_)man(_dot_)ac(_dot_)uk 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