Re: For 1.5.9: iconv-hook patch by Moriyama-san
On Sat, Feb 19, 2005 at 12:01:43AM +0100, Alain Bench wrote:
> Hi Tamotsu,
Hi Alain,
Thanks for your information.
> On Friday, February 18, 2005 at 11:05:52 PM +0900, Tamotsu Takahashi wrote:
>
> > buggy MUAs send iso-2022-jp-ms messages as "iso-2022-jp".
>
> You mean an incoming mail contains iso-2022-jp-ms, and is wrongly
> MIME labelled iso-2022-jp? Isn't such lie corrected by:
>
> | charset-hook ^iso-2022-jp$ iso-2022-jp-ms
Thanks! Your suggestion should allow me to read it.
I must have missed the point of this patch.
The problem is that MS thinks ISO-2022-JP means ISO-2022-JP-MS.
And MS does not think there is a charset called ISO-2022-JP-MS.
I have to reply to it with already-included characters in
the (ISO-2022-JP-MS - ISO-2022-JP) range in some cases.
So, I have to tell mutt to convert my eucJP-ms files
to ISO-2022-JP-MS, labelling it with "charset=iso-2022-jp",
to send it to MS-MUA users.
This cannot be corrected by your charset-hook.
Also, the iconv-hook patch is useful for future changes of
charsets definition. If we have no reason to forbid using
of iconv-hook for already-available charsets, this patch
goes the right way, IMHO.
--
tamo