From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Changing charset for posting news
Date: 18 Jul 2005 10:33:30 -0400 [thread overview]
Message-ID: <4nd5pg18w5.fsf@lifelogs.com> (raw)
In-Reply-To: <17114.21866.109263.589624@parhasard.net> (Aidan Kehoe's message of "Sun, 17 Jul 2005 14:56:10 +0200")
On Sun, 17 Jul 2005, kehoea@parhasard.net wrote:
> Ar an cúigiú lá déag de mí Iúil, scríobh Ted Zlatanov:
> > I think removing features is the wrong way to go, personally. Setting
> > the charset per newsgroup is useful.
>
> Do you use the feature? Since Emacs de-unifies the Han character
> sets, the only people for whom this would be theoretically useful,
> in the presence of a working mm-coding-system-priorities variable
> that chooses the character set based on the message content, would
> be Russian speakers who want to choose between koi8-r and
> windows-1251 for their Russian posts. Are there any such users? (Or
> Bulgarians or Serbs etc. who want to make the same choice, I
> suppose.)
Some groups (Usenet and others) require a certain character set. I
don't think mm-coding-system-priorities will handle that. This is not
just for Cyrillic posts.
> Agreed, it does offer a better out-of-the-box experience for
> Cyrillic users; but changing the default value of
> mm-coding-system-priorities based on language environment would
> achieve the same thing, I think.
Would it work, then, to connect the per-group charset parameter with code
that uses it to set the mm-coding-system-priorities on group entry? I
think that's what you were suggesting as well.
> And it’s horrible, horrible code :-) .
Simplifying or eliminating bad code is definitely a worthy goal. I
just think the feature is valuable.
Ted
prev parent reply other threads:[~2005-07-18 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3y88dc7ub.fsf@ceres.staly.plus.com>
[not found] ` <4nbr57naf1.fsf@lifelogs.com>
[not found] ` <m3eka3wwxa.fsf@ceres.staly.plus.com>
2005-07-12 23:23 ` Aidan Kehoe
2005-07-15 15:40 ` Ted Zlatanov
2005-07-17 12:56 ` Aidan Kehoe
2005-07-18 14:33 ` Ted Zlatanov [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=4nd5pg18w5.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).