Great Circle Associates Majordomo-Users
(September 1999)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: How does Majordomo manages ISO-8859-1 characters?
From: tibbs @ hpc . uh . edu
Date: 04 Sep 1999 12:40:18 -0500
To: Mikko Hänninen <Mikko . Hanninen @ iki . fi>
Cc: Majordomo-Users @ GreatCircle . COM
In-reply-to: Mikko Hänninen's message of "Thu, 2 Sep 1999 20:13:53 +0300"
References: <Pine.GSO.3.96.990831170712.1007A-100000@genesis.dcaa.unam.mx> <ufaaer6f45c.fsf@epithumia.math.uh.edu> <19990902201353.C17576@chamber.dna.fi>
User-agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) Emacs/20.3

>>>>> "MH" == Mikko Hänninen <Mikko.Hanninen@iki.fi> writes:

MH> What about digests?

Same thing; the Majordomo behavior is correct.

MH> I realise that Majordomo just doesn't do any decoding for From: lines
MH> and uses what's there exactly, but having this solved so that the
MH> sender information appears correctly would be nice.

It _isn't allowed do_.  What you see really is the contents of the Subject:
header and it is entirely up to the client to decode it.  Even if it tried,
how do you propose to mix up the various possible encodings into one body?
A body part can have only one encoding, so if you get one message with its
subject in ISO-8859-1 and another using KOI8 then what do you do?  The
solution is not to do anything and let the client do its job.

 - J<


Follow-Ups:
References:
Indexed By Date Previous: Re: Vacation Message Loops
From: "Adam H. Kerman" <ahk@chinet.com>
Next: Re: How does Majordomo manages ISO-8859-1 characters?
From: Mikko Hänninen <Mikko.Hanninen@dna.fi>
Indexed By Thread Previous: Re: How does Majordomo manages ISO-8859-1 characters?
From: Mikko Hänninen <Mikko.Hanninen@iki.fi>
Next: Re: How does Majordomo manages ISO-8859-1 characters?
From: Mikko Hänninen <Mikko.Hanninen@dna.fi>

Google
 
Search Internet Search www.greatcircle.com