<<< Date Index >>>     <<< Thread Index >>>

Re: "send_charset" and saved record file's charset



 On Tuesday, July 25, 2006 at 10:19:33 +0900, Henry Nelson wrote:

>| set 
>assumed_charset="euc-jp-ms:euc-jp:iso-2022-jp:iso-2022-jp-ms:shift_jis:utf-8"

    Unrelated, but there may be a problem here:

 -1) I believe that "iso-2022-jp" should be first, because any 2022-jp
string (pure Ascii with some escape sequences) is also a valid euc-jp-ms
string, just not saying the same thing.

 -2) It's useless to set a perfect subset together with a more complete
charset: Set only the complete one. So "euc-jp-ms:euc-jp" could be
simplified to "euc-jp-ms" only.

    Now I don't know enough to say where to insert it, and what's the
better compromise knowing that the 1st position in $assumed_charset is
essential for bodies.


    It's unfortunately a grave weakness of $assumed_charset to have
different behaviours between headers and bodies. Setting constraints are
very different, nearing incompatibility. For westerners it prohibits
any usefull multiple $assumed_charset in practice: We have to use only
one well choosen charset there.


> send all Japanese mails in iso-2022-jp, [...] and save the record in
> euc-jp or euc-jp-ms. [or] use utf-8 for sending, but save the record
> in euc-jp or euc-jp-ms

    Impossible. The goal of FCC is to record *verbatim* what you sent.

    Now you can postprocess the sent folder. Perhaps <decode-copy>
("<Esc>C" by default) elsewhere the mails you need: They will be
transcoded to $charset, euc-jp-ms for you.


 On Tuesday, July 25, 2006 at 14:38:18 +0900, Henry Nelson wrote:

> If there is a "$(D"7(B" in the mail, then mutt sends it as: "[text/plain,
> 8bit, utf-8, 0.1K]", which I'd like to avoid

    Would "iso-2022-jp-2" be acceptable? It is IANA approved, and has
the fullwidth tilde (and circled numbers). Theoretically usable, but I
ignore practical aspects. Would all or most your recipients be able to
read it, including mailx/nkf users? If at all, it should be inserted as
$send-charset="...:iso-2022-jp:iso-2022-jp-2:utf-8". This mail is so.


Bye!    Alain.
-- 
Libiconv 1.11 is released.