From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Kazuhiro Ito Newsgroups: gmane.emacs.devel Subject: Re: Encoding issue in the digest (Re: Emacs-devel Digest, Vol 240, Issue 25) Date: Wed, 28 Feb 2024 22:02:08 +0900 Message-ID: References: <71B4DAF4-0C36-40A5-8FF4-6E4B107E5113@protonmail.com> <867ciou6xp.fsf@gnu.org> <2DD5484A-C4DB-47AA-9690-D8C6ED1F0727@protonmail.com> <8634tcu6f2.fsf@gnu.org> <32EA1DC4-A0E7-47E3-9D17-48867885CC75@traductaire-libre.org> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16118"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/30.0.50 (x86_64-pc-cygwin) MULE/6.0 (HANACHIRUSATO) Cc: Eli Zaretskii , suzume@protonmail.com, Jean-Christophe Helary To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Feb 28 14:04:23 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rfJbi-00040d-WB for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Feb 2024 14:04:22 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rfJbD-0001sV-PG; Wed, 28 Feb 2024 08:03:54 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rfJZt-0001Bk-HW for emacs-devel@gnu.org; Wed, 28 Feb 2024 08:02:31 -0500 Original-Received: from snd00001.auone-net.jp ([111.86.247.1] helo=dmta0009.auone-net.jp) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rfJZo-00026V-HQ; Wed, 28 Feb 2024 08:02:27 -0500 Original-Received: from kzhr.d1.dion.ne.jp by dmta0009.auone-net.jp with ESMTP id <20240228130208325.DRVS.27211.kzhr.d1.dion.ne.jp@dmta0009.auone-net.jp>; Wed, 28 Feb 2024 22:02:08 +0900 In-Reply-To: <32EA1DC4-A0E7-47E3-9D17-48867885CC75@traductaire-libre.org> Received-SPF: pass client-ip=111.86.247.1; envelope-from=kzhr@d1.dion.ne.jp; helo=dmta0009.auone-net.jp X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:316615 Archived-At: > >> I'm using Apple's Mail.app. I don't usually have issues displaying > >> contents in French/Japanese, etc. even mixed with other languages. > > > > Maybe something is wrong here, then. I'm not an expert on this stuff; > > does anyone know whether this Subject encoding is OK or not? Obviously not. I read your original message from newsgroup via Wanderlust. Your message's subject is below. -------- Subject: =?utf-8?Q?Traduction_fran=C3=A7aise_des_manuels_d=E2=80=99Emacs, _=C3=A9tat_des_lieux.?= -------- SPACE and LF within encoded-word are not allowed. RFC 2047 (in section 2) says > IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's > by an RFC 822 parser. As a consequence, unencoded white space > characters (such as SPACE and HTAB) are FORBIDDEN within an > 'encoded-word'. For example, the character sequence > > =?iso-8859-1?q?this is some text?= > > would be parsed as four 'atom's, rather than as a single 'atom' (by > an RFC 822 parser) or 'encoded-word' (by a parser which understands > 'encoded-words'). The correct way to encode the string "this is some > text" is to encode the SPACE characters as well, e.g. > > =?iso-8859-1?q?this=20is=20some=20text?= -- Kazuhiro Ito