Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Cc: gko@gko.net
Subject: Re: Replying with the same charset as the original article
Date: 28 Dec 2000 13:35:12 -0500	[thread overview]
Message-ID: <2nae9gz95r.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <m3ae9lwscr.fsf@symbiose.dnsalias.net>

Georges KO <gko@gko.net> writes:

> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 
> > >     I would like to reply with the same charset as the original
> > > article. Currently, there's gnus-default-posting-charset, 
> > 
> > The variable is bogus.
> 
>     You mean, it is not used ?

Not used.

> > > but it is seems not possible to say "same as the answered
> > > article". Actually, I would like to use it in mail groups, where I
> > > have groups with more than one charset. gnus-default-posting-charset
> > > could be something like 'current.
> > 
> > What are those charsets?  Do they share some characters except ASCII
> > ones?
> 
>     When I do a follow-up or reply, if there are Chinese characters
> like in Big5 in the header (From:), then the To: in the composing
> buffer is displayed as 8-bit characters... Also, the "XXX writes",
> where XXX is extracted from the From:, have 8-bit characters too...

It is because you did not setup the group charset right. By default,
the group charset is iso8859-1, so what you see is not 8-bit
characters, but iso-8859-1 characters.  To setup the default group
charset, you can configure the charset parameter (maybe also
ignored-charsets) in the group parameters.  Once you set it to big5,
you can always see Chinese in the From header, also To: field when you
reply.  To override the default charset temporarily, you could type `0
G cn-big5 RET' on the message.

ShengHuo



      reply	other threads:[~2000-12-28 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-23 17:52 Georges KO
2000-12-24  6:16 ` ShengHuo ZHU
2000-12-24 19:07   ` Georges KO
2000-12-28 18:35     ` ShengHuo ZHU [this message]

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=2nae9gz95r.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    --cc=gko@gko.net \
    /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).