Jason wrote:
> I'll probably do the mangling (by running over the headers and calling
> MIME::Words::encode_mimewords on each) based on some per-list configuration
> variable.
Sounds fair enough. Options could include all of the character sets which
encode_mimewords can handle, as well as the current status quo (i.e. GIGO).
What would be the default? For the reasons which you give in the following
paragraph it seems best to use good old GIGO as the default, with iso-latin-1
explicitely suggested as an alternative in the documentation?
> to rectify in a sane manner. Why? Because 2047-encoding requires that you
> know the character set. You can have multiple character sets in one
> header. The vast majority of sites will do the right thing with respect to
> 8-bit headers, so if we choose to encode them in some random character set
> we run the risk of mangling a header that is perfectly acceptable to most
> sites.
Yes... on some lists (especially those where the discussions are not in
English, but some other language) there will be a clear 'standard' way of
interpreting 8-bit-characters. On other lists this will not be the case.
-- NB.
>
> I'll probably do the mangling (by running over the headers and calling
> MIME::Words::encode_mimewords on each) based on some per-list configuration
> variable.
>
> Note that if 2047-encoded headers come in but 8-bit headers go out, that
> means I screwed up.
>
> - J<
>
>
References:
|
|
