From: Ralf Angeli <dev.null@iwi.uni-sb.de>
Subject: Re: mm-fill-flowed and f=f article decoding
Date: Thu, 07 Oct 2004 09:49:26 +0200 [thread overview]
Message-ID: <ck2s98$jd4$1@sea.gmane.org> (raw)
In-Reply-To: <b9y7jq3yoxh.fsf@jpl.org>
* Katsumi Yamaoka (2004-10-07) writes:
>>>>>> In <b9y8yajl8l8.fsf@jpl.org> Katsumi Yamaoka wrote:
>
>> Yup! We have to pass MIME parameters to mm-uu-dissect in some
>> way. I need to grapple with it...
>
> I've done so. This also fixes another bug; a non-ascii article
> like this was not decoded since the `gnus-decoded' charset does
> not always mean the part has been decoded.
>
> Can you read this line?
I can read it.
BTW, the article <news:b9ybrfg5c4c.fsf@jpl.org> in this thread is
still getting flowed.
--
Ralf
next prev parent reply other threads:[~2004-10-07 7:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 8:24 Ralf Angeli
2004-10-05 8:57 ` OT: Japanese names (was Re: mm-fill-flowed and f=f article decoding) Katsumi Yamaoka
2004-10-05 9:33 ` OT: Japanese names Ralf Angeli
2004-10-05 20:07 ` mm-fill-flowed and f=f article decoding Xavier Maillard
2004-10-06 7:49 ` Katsumi Yamaoka
2004-10-06 8:09 ` Ralf Angeli
2004-10-06 8:18 ` Simon Josefsson
2004-10-06 11:17 ` Katsumi Yamaoka
2004-10-06 12:15 ` Simon Josefsson
2004-10-06 15:06 ` Katsumi Yamaoka
2004-10-06 15:16 ` Simon Josefsson
2004-10-06 23:39 ` Katsumi Yamaoka
2004-10-07 7:20 ` Katsumi Yamaoka
2004-10-07 7:49 ` Ralf Angeli [this message]
2004-10-07 7:55 ` Katsumi Yamaoka
2004-10-08 7:25 ` Katsumi Yamaoka
2004-10-07 8:08 ` fetching pubkeys (was Re: mm-fill-flowed and f=f article decoding) Katsumi Yamaoka
2004-10-07 9:19 ` fetching pubkeys Reiner Steib
2004-10-07 11:54 ` Katsumi Yamaoka
[not found] ` <b9yr7obx85n.fsf_-_-NvgVpDro27E@public.gmane.org>
2004-10-07 16:01 ` Jochen Küpper
2004-10-07 21:12 ` Xavier Maillard
2004-10-07 23:08 ` Katsumi Yamaoka
2004-10-08 19:28 ` Xavier Maillard
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='ck2s98$jd4$1@sea.gmane.org' \
--to=dev.null@iwi.uni-sb.de \
--cc=angeli@iwi.uni-sb.de \
/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).