send_charset doesn't support charset-hook'd charsets

[Marco d'Itri <md@…>]

Package: mutt
Version: 1.3.28-2
Severity: normal

[NOTE: this bug report has been submitted to the debian BTS as Bug#152444.
Please Cc all your replies to 152444@bugs.debian.org .]

From: Ilya Konstantinov <debian-bug-report@future.shiny.co.il>
Subject: send_charset doesn't support charset-hook'd charsets
Date: Wed, 10 Jul 2002 02:06:00 +0300

Its impossible to use a charset alias defined via charset-hook as a
charset in send_charset.

For example:
Charset iso-8859-8-i is totally identical to iso-8859-8
charset-wise (its different logically-wise, but that's not the subject
of this bug), and indeed it works great to alias iso-8859-8-i to
iso-8859-8. BUT I want to use "iso-8859-8-i" for my outgoing mail too
(i.e. I want the mail to be marked as "iso-8859-8-i" rather than
"iso-8859-8") and its impossible to do currently with the
send_charset option.


>How-To-Repeat:
>Fix:

[Alain Bench <veronatif@…>]

Hello Ilya, thanks for the report.

On Wednesday, July 10, 2002 at 2:06:00 AM +0300, Ilya Konstantinov wrote:

> Its impossible to use a charset alias defined via charset-hook as a
> charset in send_charset.

   That's the intended bahaviour: charset-hook deals with incoming
mails only. The contrary would trigger unwanted side-effects, like you
can see examples in archives before Edmund fixed a bug last year.


> For example: Charset iso-8859-8-i is totally identical to iso-8859-8
> charset-wise (its different logically-wise, but that's not the subject
> of this bug), and indeed it works great to alias iso-8859-8-i to
> iso-8859-8. BUT I want to use "iso-8859-8-i" for my outgoing mail too
> (i.e. I want the mail to be marked as "iso-8859-8-i" rather than
> "iso-8859-8") and its impossible to do currently with the send_charset
> option.

   I'm not sure to understand fully iconv-hook feature. But reading the
very old discussions when this was commited, it might have seemed to be
good for you. But it doesn't work, I tried. Probably simply because Mutt
preferes canonical MIME charset name.

   Why do you want to use "iso-8859-8-i" label? The IANA seems to have
registered it as a MIME charset, but _not_ as an alias of ISO-8859-8.
MIBenums differ: 85 for -i and some aliases, 11 for 8859-8 and its own
aliases. And nor libiconv 1.8 neither glibc iconv 2.3.2 know it.


Bye!	Alain.
-- 
Microsoft Outlook Express users concerned about readability: For much
better viewing quotes in your messages, check the little freeware
program OE-QuoteFix by Dominik Jain on <URL:http://flash.to/oblivion/>.
It'll change your life. :-) Now exists also for Outlook.

[Ilya Konstantinov <debian-bug-report@…>]

On Wed, Nov 05, 2003 at 12:04:15PM +0100, Alain Bench wrote:
>     Why do you want to use "iso-8859-8-i" label? The IANA seems to have
> registered it as a MIME charset, but _not_ as an alias of ISO-8859-8.
> MIBenums differ: 85 for -i and some aliases, 11 for 8859-8 and its own
> aliases. And nor libiconv 1.8 neither glibc iconv 2.3.2 know it.

You are right -- they are different. And indeed, iconv doesn't support
"iso-8859-8-i".

iso-8859-8-i is identical to iso-8859-8 charset-wise (ie. the octet value
to Unicode value mapping in both charsets is the same). The difference
is that iso-8859-8-i requires the use of BiDi reordering algorithm
before displaying.

Because iconv doesn't deal with complex layouts and reordering but only
banal charset conversion, we can pretend iso-8859-8-i is iso-8859-8 for
the sake for conversions.

However, in the outgoing mail, I'd wish to specify "iso-8859-8-i",
since the text I write *has* to be interpreted by BiDi reordering
algorithm on the receiver's mailer.

[tamo]

FYI: Some discussion here:

For 1.5.9: iconv-hook patch by Moriyama-san
http://marc.theaimsgroup.com/?l=mutt-dev&m=110873560103951&w=2

[tamo]

- Uploading MORIYAMA-san's patch.
- Adding keyword: patch.

[ab]

upload patch-1.5.12.msyk.iconvhook.1-ab patch with comments
deduppe unformatted.

[brendan]

Applied, thanks.