From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: =?iso-8859-1?q?Bj=F8rn?= Mork Newsgroups: gmane.emacs.bugs Subject: Re: bad rfc2047 encoding Date: Thu, 22 Aug 2002 15:50:13 +0200 Organization: DoD Sender: bug-gnu-emacs-admin@gnu.org Message-ID: References: NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1030024207 11843 127.0.0.1 (22 Aug 2002 13:50:07 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 22 Aug 2002 13:50:07 +0000 (UTC) Cc: Simon Josefsson , bugs@gnus.org, bug-gnu-emacs@gnu.org Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 17hsLY-00034u-00 for ; Thu, 22 Aug 2002 15:50:01 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17hsMk-0007MW-00; Thu, 22 Aug 2002 09:51:14 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 17hsMS-0007IL-00 for bug-gnu-emacs@gnu.org; Thu, 22 Aug 2002 09:50:56 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 17hsLw-0007Ef-00 for bug-gnu-emacs@gnu.org; Thu, 22 Aug 2002 09:50:55 -0400 Original-Received: from canardo.mork.no ([148.122.252.1]) by monty-python.gnu.org with esmtp (Exim 4.10) id 17hsLv-0007EH-00 for bug-gnu-emacs@gnu.org; Thu, 22 Aug 2002 09:50:24 -0400 Original-Received: from rasputin.ws.nextra.no (bjorn@canardo.mork.no [148.122.252.1]) by canardo.mork.no (8.12.5/8.12.5) with ESMTP id g7MDoELh008879; Thu, 22 Aug 2002 15:50:15 +0200 Original-Received: from bmork by rasputin.ws.nextra.no with local (Exim 3.35 #1 (Debian)) id 17hsLl-0000rw-00; Thu, 22 Aug 2002 15:50:13 +0200 Original-To: Dave Love In-Reply-To: (Dave Love's message of "22 Aug 2002 12:50:41 +0100") Original-Lines: 45 User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-debian-linux-gnu) Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:3277 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:3277 Dave Love writes: > Simon Josefsson writes: > >> Bj=F8rn Mork writes: > > [In something that hasn't reached here...] Sorry about that. I am also reading bugs@gnus.org via the nntp gateway and forgot to add a Cc-header. BTW, your Cc-header did not look good: Cc: =3D?iso-8859-1?q?Bj=3DF8rn_Mork_, __bugs@gnus.org, __bug-gn?=3D.=3D?iso-8859-1?q?u-emacs@gnu.org?=3D I guess this is the same problem you demonstrated in a previous example. Never seen Gnus behave as bad as this before, though... >> > In this example the quoted-string should probably be unquoted and >> > then encoded. Or would that break something? >>=20 >> It could perhaps encode the quotes too. > > The spirit of the RFC and examples seem to suggest unquoting the > string, encoding it, and (perhaps) re-quoting encoded word sequences > on decoding. Is the correct behaviour really not explicitly specified > somewhere? I am no expert on this, but trying to read RFC2822 and RFC2047 makes me think that Simon is right. A 'quoted-string' is a 'word', and may as such be replaced by an 'encoded-word'. The DQUOTE is part of the 'quoted-string' and should therefore be encoded with it. So the proper way to encode From: "Bj=F8rn Mork" would be From: =3D?iso-8859-1?q?=3D22Bj=3DF8rn_Mork=3D22?=3D I guess. An example of proper handling of a 'quoted-string' in RFC2047 would have been nice. But as far as I can see, this is the only way you can do compliant encoding without losing any information. Bj=F8rn