From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Changing charset for posting news
Date: 15 Jul 2005 11:40:23 -0400 [thread overview]
Message-ID: <4n64vcjcwo.fsf@lifelogs.com> (raw)
In-Reply-To: <17108.20738.57239.905612@parhasard.net> (Aidan Kehoe's message of "Wed, 13 Jul 2005 00:23:46 +0100")
On Wed, 13 Jul 2005, kehoea@parhasard.net wrote:
> Ar an dara lá déag de mí Iúil, scríobh David Sumbler:
>
> > Strange: I have tried this, having commented out in .gnus the lines
> > suggested by Aidan, and it doesn't work! Despite having specified
> > iso-8859-1, as you suggest, messages I send to the fr.test group still
> > are sent as UTF-8 and quoted printable.
>
> 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.
> 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.
Ted
next prev parent reply other threads:[~2005-07-15 15:40 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 [this message]
2005-07-17 12:56 ` Aidan Kehoe
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=4n64vcjcwo.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).