From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Removing ignore-errors in mm-dissect-buffer
Date: Thu, 16 Feb 2006 08:38:37 +0900 [thread overview]
Message-ID: <b4mwtfwnqf6.fsf@jpl.org> (raw)
In-Reply-To: <v9wtfwo8zf.fsf@marauder.physik.uni-ulm.de>
>>>>> In <v9wtfwo8zf.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:
> Gnus errors out with "forward-sexp: Scan error: "Unbalanced
> parentheses", 21, 32" when displaying the following spam article:
I see. Though the article seems to have been cancelled.
[...]
> The culprit is the string «charset=\"us-ascii\"» in the first MIME
> part which might be invalid:
> ,----
>| --fc55ff24ae7d5dde3b9cddf90cbc0f08
>| Content-Type: text/html; charset=\"us-ascii\"
>| MIME-Version: 1.0
>| Content-Transfer-Encoding: quoted-printable
> `----
> But Gnus should render the article despite of the broken charset
> declaration, I think.
Yes, I think so. The change I made aimed to cope with
Thunderbird 1.5 which generates wrong name and filename
parameters for an attachment of a long non-ASCII file name[1].
In such a case, now at least type/subtype will be extracted.
> To reproduce (even from «emacs -Q»), eval the following code:
> (require 'mail-parse)
> (with-temp-buffer
> (insert "Content-Type: text/html; charset=\\\"us-ascii\\\"
> MIME-Version: 1.0
> Content-Transfer-Encoding: quoted-printable")
> (setq ct (mail-fetch-field "content-type")
> ctl (and ct (mail-header-parse-content-type ct))))
> Reverting mm-decode.el to revision 7.37 fixed the problem:
[...]
> If reverting the following changes is not the right thing, could you
> suggest a better approach, Katsumi?
I think mail-header-parse-content-type should never cause erros
and it should extract at least type/subtype if it is possible.
I will make an effort so that it might do so.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=323318
next prev parent reply other threads:[~2006-02-15 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 16:57 Reiner Steib
2006-02-15 23:38 ` Katsumi Yamaoka [this message]
2006-02-16 8:23 ` Katsumi Yamaoka
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=b4mwtfwnqf6.fsf@jpl.org \
--to=yamaoka@jpl.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).