Gnus development mailing list
 help / color / mirror / Atom feed
From: Dmitry Yaitskov <dimas@home.com>
Subject: Re: Message - which charset?
Date: 14 Mar 1999 12:49:22 -0500	[thread overview]
Message-ID: <u90d055ct.fsf@home.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "14 Mar 1999 17:19:41 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:

> Dmitry Yaitskov <dimas@home.com> writes:
> 
> > 1) the charset of a message, if it is a reply or a followup, would be
> > the same as the charset of the original message (somehow I supposed
> > that this would be the default behavior but I don't think it is on my
> > system).
> 
> If you are using a Mule-enabled Emacs, then that should be the case.

Thanks, but no, I am using a non-Mule emacs. I don't want to pay the
performance penalty for the very limited multilingual support that I
really need. Basically, besides English I only *sometimes* need
Russian support in news and email - which would work fine out of the
box if it were not for the 2 different coding sysems used for Russian.
Even with that, most problems are solved by a lisp module enabling to
select the coding system. And with some simple elisp, I can now
determine which of the 2 coding systems is used in a particular
incoming message. My only problem left is - I'd like to be able to
specify the charset "of my choice" for the message that I compose (for
the whole message or for the 1st part of a mime one), based on the
headers/body of the (1st part of the 1st) message being replied
to/followed up. (For new messages, the default Gnus charset works
fine.) Is it possible to set up a hook like that to tell Gnus which
charset to specify?

> > 2) do something in the message buffer depending on the charset of the
> > message. I wanted to use the message-setup-hook for this but don't
> > know how to make sure that I have the charset available in the message
> > headers when the message setup hook is called. Even if I reply to a
> > message with a specified charset, I don't see it in the reply's
> > headers although I have message-generate-headers-first set to t.
> 
> Well, there may be several charsets in an article, so there's no easy
> way to do that.
> 
> (mm-find-mime-charset-region (point-min) (point-max))
> 
> will return a list of charsets in the current buffer.

Thanks, I will try to use it. I am not sure though this would help as
I'd like the list of charsets in the message(s) being replied to, not
the current (new?) one. In other words: while in the original message
buffer, I can determine (using mm-find-mime-charset-region or
otherwise) what the charset in the reply should be. Now, I hit
reply/followup/whatever, and in the new message buffer need to tell
Gnus somehow to change its "default" charset for this message only to
the one that I just found out in step 1. Is there a way to achieve
this? Thanks.

-- 
Cheers,
-Dima.



  reply	other threads:[~1999-03-14 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-14  7:49 Dmitry Yaitskov
1999-03-14 16:19 ` Lars Magne Ingebrigtsen
1999-03-14 17:49   ` Dmitry Yaitskov [this message]
1999-03-16  7:23     ` Hrvoje Niksic
1999-03-16  7:55       ` Dmitry Yaitskov
1999-03-16  8:09         ` Hrvoje Niksic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u90d055ct.fsf@home.com \
    --to=dimas@home.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).