From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: Re: Encoding issue in the digest (Re: Emacs-devel Digest, Vol 240, Issue 25) Date: Wed, 28 Feb 2024 13:31:22 +0100 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> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="m1HZZCDiAWjWCcRq" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9281"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Feb 28 13:32:49 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 1rfJ7A-0002A4-LS for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Feb 2024 13:32:48 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rfJ6K-0001Yw-Et; Wed, 28 Feb 2024 07:31:56 -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 1rfJ5s-0001US-4N for emacs-devel@gnu.org; Wed, 28 Feb 2024 07:31:36 -0500 Original-Received: from mail.tuxteam.de ([5.199.139.25]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rfJ5o-0007er-UN for emacs-devel@gnu.org; Wed, 28 Feb 2024 07:31:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=tEw9N2ER82R/NWjJ7NgW9zqEyZ3yljhesBPuryBJIfk=; b=bsMlbXhpHGEcbLyDNuiKCC6EvK S+zjI2Gzmz9dsSRmNGy9b5dYnfZZw8/Pudyf5/ruln50Bq8uZRN54zX+aYhB1N9moPpdsGHM1nXPy 9I8lpUU1wOW15jTuTc1Q15I4ge17P5QwWo87Ou8TA3+PmXPK7gukBTcrGs/JoT4wXdglEY9pnQ5oe OoLKfa0yt1ebKQ/lhwndBNygVsWGr668b0SHQJxGcPZ+t0sjBXMU9pwhhpwn9GM3DxWJf9UjqRZHC QjXrcBbtWgno0lq1pj2xaCr/mRN8QR2RmQs+NECk2JvGhkn8rutoiwNGTG5KAH3knqWNdfS9m+BQP d8zePpCw==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.94.2) (envelope-from ) id 1rfJ5m-0007Hj-Cx for emacs-devel@gnu.org; Wed, 28 Feb 2024 13:31:22 +0100 Content-Disposition: inline In-Reply-To: <8634tcu6f2.fsf@gnu.org> Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=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:316610 Archived-At: --m1HZZCDiAWjWCcRq Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 28, 2024 at 02:20:17PM +0200, Eli Zaretskii wrote: > > Date: Wed, 28 Feb 2024 12:14:29 +0000 > > From: "suzume@protonmail.com" > > Cc: emacs-devel@gnu.org > >=20 > > > On Feb 28, 2024, at 21:09, Eli Zaretskii wrote: > > >=20 > > >> Date: Wed, 28 Feb 2024 00:18:59 +0000 > > >> From: "suzume@protonmail.com" > > >>=20 > > >>=20 > > >>> On Feb 26, 2024, at 2:00, emacs-devel-request@gnu.org wrote: > > >>>=20 > > >>> Message: 12 > > >>> Date: Sun, 25 Feb 2024 08:45:33 +0000 > > >>> From: Jean-Christophe Helary > > >>> > > >>=20 > > >>=20 > > >>> Subject: > > >>> =3D?utf-8?Q?Traduction_fran=3DC3=3DA7aise_des_manuels_d=3DE2=3D80= =3D99Emacs, > > >>> _=3DC3=3DA9tat_des_lieux.?=3D > > >>=20 > > >> Is there anything I can do on my side to make sure that the subject = is > > >> properly encoded/decoded on the server side? Or is it a setting that > > >> needs to be modified on the server side? > > >=20 > > > Sorry, I don't understand what you are asking. What is "improper" > > > with the above subject, in your opinion? And in what MUA are you > > > looking at it? > >=20 > > This is how it looks in the digest listing here: >=20 > Which is okay, I think. That's how the author's MUA sent it; the > Subject is encoded using quoted-printable method, I think. >=20 > > I'm using Apple's Mail.app. I don't usually have issues displaying=20 > > contents in French/Japanese, etc. even mixed with other languages. >=20 > 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? I didn't dive into all details ($DAYJOB), but prima vista it looks OK. Mime [1] prescribes "Encoded Word" for Unicode encoding in mail headers, and this very much looks like Q encoding. Now one might rightfully argue that the client is supposed to decode that and show Unicode in its full glory (other MUAs do it). Perhaps this is the OP's point? Cheers [1] https://en.wikipedia.org/wiki/MIME#Encoded-Word --=20 t --m1HZZCDiAWjWCcRq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZd8nkwAKCRAFyCz1etHa Rir4AJ9E/bHb7nm7Zvq3doj28gF7LggMLACfUnRIh9clZ1w/3+KM/d/v+64c6l4= =R6t7 -----END PGP SIGNATURE----- --m1HZZCDiAWjWCcRq--