From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: For lack of content...
Date: 31 Aug 1998 23:27:09 +0200 [thread overview]
Message-ID: <m3emtwx2oi.fsf@sparky.gnus.org> (raw)
In-Reply-To: Michael Welsh Duggan's message of "Mon, 31 Aug 1998 18:18:21 GMT"
Michael Welsh Duggan <md5i@cs.cmu.edu> writes:
> There are some posts which I read which contain characters in
> non-default coding-systems, which don't include a proper Content-Type
> header. As a result, these messages end up in my buffer as the raw
> bytes of the coding method. There are a couple of possible solutions
> that I can think of:
>
> 1) A decoding alist of some sort, such as an alist of regexps
> (matching a newsgroup name) to a list of coding-systems. If the
> visited newsgroup matches that regexp, then it should try to decode
> the body using the mehods in the associated list,m in order.
Or group/topic params. I've now added this.
> 2) A washing method, for which the user can supply a coding-system
> with which to decode the article.
And this.
> I actually wrote a prototype of such myself, but ran into the
> problem that decode-coding-region trashes text-properties.
Hm. It does seem that that function trashes text props. Why?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-08-31 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-31 18:18 Michael Welsh Duggan
1998-08-31 21:27 ` Lars Magne Ingebrigtsen [this message]
1998-08-31 22:02 ` Michael Welsh Duggan
1998-09-01 1:47 ` Justin Sheehy
1998-09-01 14:30 ` Michael Welsh Duggan
1998-09-01 22:33 ` Lars Magne Ingebrigtsen
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=m3emtwx2oi.fsf@sparky.gnus.org \
--to=larsi@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).