From: Aidan Kehoe <kehoea@parhasard.net>
Cc: ding@gnus.org
Subject: Re: Changing charset for posting news
Date: Sun, 17 Jul 2005 14:56:10 +0200 [thread overview]
Message-ID: <17114.21866.109263.589624@parhasard.net> (raw)
In-Reply-To: <4n64vcjcwo.fsf@lifelogs.com>
Ar an cúigiú lá déag de mí Iúil, scríobh Ted Zlatanov:
> > That’s a bug that some changes I made tickled, according to this mail:
> >
> > http://list-archive.xemacs.org/xemacs-beta/200505/msg00121.html
> >
> > But I’ve looked into this some more, and, well, the design of that code is
> > hugely broken--loads of programming using and endorsing underdocumented
> > dynamic binding, crazy return values--and I haven’t seen an example where
> > setting mm-coding-system-priorities appropriately is broken. I’ll put
> > together a patch removing support for newsgroup-specific character sets if
> > this sounds reasonable.
>
> 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.)
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.
> > If not, I’ll look into adding support for binding
> > message-posting-charset around calls to mm-find-charset-region, which
> > should re-add support for the charset-per-newsgroup approach.
>
> If you could do that, it would be great. I was going to look into it
> when I had free time, which will not be soon :) I think it's a
> valuable Gnus feature.
And it’s horrible, horrible code :-) .
--
Russian has no phoneme that's close to Germanic /h/. As a result, for a
not-insignificant number of people, the Second World War involved the Soviet
Union defeating Адольф Гитлер, �Adolf Gitler.”
next prev parent reply other threads:[~2005-07-17 12:56 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 [this message]
2005-07-18 14:33 ` Ted Zlatanov
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=17114.21866.109263.589624@parhasard.net \
--to=kehoea@parhasard.net \
--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).