From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/83618 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: header encoding problem, multi-lingual text Date: Fri, 02 Aug 2013 17:36:32 +0900 Organization: Emacsen advocacy group Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1375432699 6636 80.91.229.3 (2 Aug 2013 08:38:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 2 Aug 2013 08:38:19 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M31874@lists.math.uh.edu Fri Aug 02 10:38:19 2013 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1V5AsD-0006nk-E6 for ding-account@gmane.org; Fri, 02 Aug 2013 10:38:09 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1V5Aqv-0007ZD-5V; Fri, 02 Aug 2013 03:36:49 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1V5Aqt-0007Yz-Ss for ding@lists.math.uh.edu; Fri, 02 Aug 2013 03:36:47 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1V5Aqr-0006y6-UX for ding@lists.math.uh.edu; Fri, 02 Aug 2013 03:36:47 -0500 Original-Received: from mail-hampton.hostforweb.net ([216.246.15.223] helo=hampton.hostforweb.net) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1V5Aqp-00031t-UH for ding@gnus.org; Fri, 02 Aug 2013 10:36:44 +0200 Original-Received: from localhost.localdomain ([127.0.0.1]:52436 helo=localhost) by hampton.hostforweb.net with smtp (Exim 4.80.1) (envelope-from ) id 1V5Aqg-001O6F-IR for ding@gnus.org; Fri, 02 Aug 2013 03:36:36 -0500 X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.130008 (=?iso-2022-jp?B?GyRCPz8bKEI=?= Gnus v0.8) Emacs/24.3.50 (i686-pc-cygwin) Cancel-Lock: sha1:5BTJCEj60j4OFpm9S4Kuh0ZTLa4= X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - hampton.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Get-Message-Sender-Via: hampton.hostforweb.net: acl_c_authenticated_local_user: root X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -0.0 (/) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:83618 Archived-At: Hi, Say I reply to a Chinese friend, who reads and writes Japanese as well, with a subject like this: Subject: Re: =E7=AD=94=E5=A4=8D: No Gnus T-=E3=82=B7=E3=83=A3=E3=83=84 "=E7=AD=94=E5=A4=8D:" seems to mean "Re:", so I remove the first one: Subject: =E7=AD=94=E5=A4=8D: No Gnus T-=E3=82=B7=E3=83=A3=E3=83=84 I realized today that this subject of a message sent to the recipient is not decoded fully if the recipient uses M$ Outlook; it is shown in that mailer as follows: Subject: =E7=AD=94=E5=A4=8D: No Gnus T-=EF=BD=A5$B%7%c=EF=BD=A5(B=EF=BD=A5$= B%D=EF=BD=A5(B What happens is that Gnus encodes the subject into[1] Subject: =3D?utf-8?B?562U5aSNOg=3D=3D?=3D No Gnus =3D?iso-2022-jp?B?VC0bJEI= lNyVjGyhC?=3D =3D?iso-2022-jp?B?GyRCJUQbKEI=3D?=3D and M$ Outlook decodes it from a charset that is first found in those encoded words, I believe. This must not be Gnus' fault, however it gets to be a real annoyance; that broken subject will never be fixed while repeating of replies each other. Then, I made a change in rfc2047.el's header encoder[2] so that it unifies the charsets into a single one used to encode the whole text in a header as much as possible. As for the subject, containing Chinese and Japanese texts, now `utf-8' will be chosen. [1] In the Japanese locale, `mm-coding-system-priorities' defaults to `(iso-8859-1 iso-2022-jp iso-2022-jp-2 shift_jis utf-8)', so `iso-2022-jp' is applied to Japanese text and `utf-8' is applied to Chinese text. [2] `rfc2047-encode-message-header'. That is an aliasee of `mail-encode-encoded-word-buffer'.