From: Aidan Kehoe <kehoea@parhasard.net>
Subject: Re: Character sets in Usenet messages, rereading messages in Gnus
Date: Mon, 24 Jan 2005 16:44:18 +0000 [thread overview]
Message-ID: <16885.9698.361539.388353@parhasard.net> (raw)
In-Reply-To: <a97psc.36.ln@acm.acm>
Ar an fichiú lá de mí Eanair, scríobh Alan Mackenzie:
> > Iâ~@~Ym not arguing the theory of the thing--if you want to upgrade to
> > a UTF-8 capable newsreader, Iâ~@~Yll do all I can to help you.
>
> Thanks. I run my newsreading software on a 166 MHz Linux Machine set up
> for ISO-8859-1. I'm not prepared to compromise the quality of my Usenet
> setup or degrade the performance of my machine by using X-Windows. I
> suspect there are many Usenetters in the over-exploited parts of the
> world using machines as powerful as mine, who also don't want the
> degradation that GUIs impose. Relevant help files were noticeably absent
> from Markus Kuhn's home page, the one you directed me to a few days ago.
>
> Suggestions on how best to field utf-8 encoded postings in west European
> languages would be welcome.
Excuse me not getting to that earlier; I managed, accidentally, to have Gnus
ignore comp.emacs.xemacs for half a week :-( .
Gnus people, when you’ve subscribed to a group, and have read all the
messages in that group, and the line for that group has disappeared from the
*Groups* buffer, what’s the sanctioned way to go back and reread those
messages? I type “U” in the “*Group*” buffer, subscribe to
comp.emacs.xemacs, read 50 messages, and then I seem to be unsubscribed from
it, which is exactly what I don’t want.
Anyway, Alan, tell us if recode with trn works for you. A few minutes’
googling doesn’t give me anything better as a suggestion, besides using the
UTF-8 branch of Mutt together with a news-mail gateway.
--
“Ah come on now Ted, a Volkswagen with a mind of its own, driving all over
the place and going mad, if that’s not scary I don’t know what is.”
next parent reply other threads:[~2005-01-24 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1105250310.785876.43550@c13g2000cwb.googlegroups.com>
[not found] ` <16865.41690.741411.876095@parhasard.net>
[not found] ` <16865.52540.429705.39431@parhasard.net>
[not found] ` <87ekgrw121.fsf@tleepslib.sk.tsukuba.ac.jp>
[not found] ` <fcmasc.36.ln@acm.acm>
[not found] ` <16873.7306.704923.942041@parhasard.net>
[not found] ` <8thbsc.36.ln@acm.acm>
[not found] ` <jwv7jmb3is4.fsf-monnier+comp.emacs.xemacs@gnu.org>
[not found] ` <16876.20540.318129.669152@parhasard.net>
[not found] ` <bngmsc.66.ln@acm.acm>
[not found] ` <16879.49257.276164.218339@parhasard.net>
[not found] ` <a97psc.36.ln@acm.acm>
2005-01-24 16:44 ` Aidan Kehoe [this message]
2005-01-24 17:52 ` Reiner Steib
2005-01-24 18:34 ` Aidan Kehoe
2005-01-25 19:17 ` John Paul Wallington
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=16885.9698.361539.388353@parhasard.net \
--to=kehoea@parhasard.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).