From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/16923 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: 0.26: Bug in text of button Date: 11 Sep 1998 16:50:22 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035155716 30673 80.91.224.250 (20 Oct 2002 23:15:16 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:15:16 +0000 (UTC) Return-Path: Original-Received: from gizmo.hpc.uh.edu (gizmo.hpc.uh.edu [129.7.102.31]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id KAA14001 for ; Fri, 11 Sep 1998 10:51:40 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (sina.hpc.uh.edu [129.7.3.5]) by gizmo.hpc.uh.edu (8.7.6/8.7.3) with ESMTP id JAF11205; Fri, 11 Sep 1998 09:22:39 -0500 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 11 Sep 1998 09:50:00 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [209.195.19.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id JAA04467 for ; Fri, 11 Sep 1998 09:49:50 -0500 (CDT) Original-Received: from sparky.gnus.org (ppp092.uio.no [129.240.240.97]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id KAA13941 for ; Fri, 11 Sep 1998 10:49:03 -0400 (EDT) Original-Received: (from larsi@localhost) by sparky.gnus.org (8.8.5/8.8.5) id QAA03787; Fri, 11 Sep 1998 16:51:48 +0200 Mail-Copies-To: never X-Now-Reading: Ursula K. Le Guin's _Unlocking the Air and Other Stories_ Original-To: ding@gnus.org In-Reply-To: Jean-Yves Perrier's message of "11 Sep 1998 15:41:35 +0200" User-Agent: Gnus/5.070027 (Pterodactyl Gnus v0.27) XEmacs/21.0 (Finnish Landrace) X-Face: &w!^oO~dS|}-P0~ge{$c!h\ writes: > I've just got the following button: > [application/msword (PV =?iso-8859-1?Q?r=E9union?= 18-8-98.doc)] > > I suppose that the function call to decode =?iso-8859-1?Q?... > is missing Nope. This is malformed. Quoth RFC2047: These are the ONLY locations where an 'encoded-word' may appear. In particular: + An 'encoded-word' MUST NOT appear in any portion of an 'addr-spec'. + An 'encoded-word' MUST NOT appear within a 'quoted-string'. + An 'encoded-word' MUST NOT be used in a Received header field. + An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured field body except within a 'comment' or 'phrase'. So decoding this would be naughty. Although I don't understand how one is supposed to use non-ascii chars in the C-T header, then. -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen