From: amu@MIT.EDU (Aaron M. Ucko)
Subject: Re: How am I seeing *both* \2xx *and* iso-8859 chars?
Date: 28 Aug 1999 18:01:25 -0400 [thread overview]
Message-ID: <udlzozbpnt6.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: Jonas Steverud's message of "28 Aug 1999 03:28:51 -0400"
Jonas Steverud <d4jonas@dtek.chalmers.se> writes:
> Lars: You said when I posted this to gnu.emacs.gnus way back that in a
> future release of Gnus there would be a function doing this - treating
> a character in the article into a string, has this happend?
I'm not Lars, but I'll reply anyway.
W d runs the command gnus-article-treat-dumbquotes
which is an interactive Lisp function.
(gnus-article-treat-dumbquotes &optional INTERACTIVE &rest ARGS)
Translate M******** sm*rtq**t*s into proper text.
Note that this function guesses whether a character is a sm*rtq**t* or
not, so it should only be used interactively.>
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)
prev parent reply other threads:[~1999-08-28 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-27 21:10 Karl Kleinpaste
1999-08-27 21:31 ` Lars Magne Ingebrigtsen
[not found] ` <wtnzozc1i22.fsf@licia.dtek.chalmers.se>
1999-08-28 22:01 ` Aaron M. Ucko [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=udlzozbpnt6.fsf@contents-vnder-pressvre.mit.edu \
--to=amu@mit.edu \
/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).