From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,NO_DNS_FOR_FROM, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from [192.168.1.2] (unknown [101.128.126.198]) by gnuweeb.org (Postfix) with ESMTPSA id 2A5FC804D1; Mon, 7 Nov 2022 01:27:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1667784461; bh=pkyr9gRSETXwoInaffXoI9lTzJAE7BMq3ISE4Ud2nn0=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Bo6jcVx6P0ES+Vo8KvSzOK9ox2msxjLGSWuXsyi1tlMz85rFEd6161ZtBx5yR8gl2 J81zj1phqUA6PjzFIfoZnM/QUDbpPdeoWRdUIKpfJjAGNwDjVWvWO/CPjtZ5O9M1/z xaLcsSPsI2QeI59lTKbDoTfJNXJVNvFNIRRGVzo7jUWbQ7Yvk8KuNHNGu9JXkMnbuO sW1oDlRcZ7YBY5hENpsFOTXGicmLbcZ+365n4gY5d7Mw6i/GKSEryAuCBx8w5Mc14w Kzhm6X7aAuI7KuYWOqZEfmXjKdDRhtx4+pKte8dYBbFZMDmMTaOeFumAO0uz+AqPFq tXdm5xK3BTN/g== Message-ID: <5bda707a-c198-8795-d836-e51c9bedf841@gnuweeb.org> Date: Mon, 7 Nov 2022 08:27:37 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 Subject: Re: [PATCH v1 05/16] utils: Improve fix_utf8_char() Content-Language: en-US To: Ammar Faizi Cc: Alviro Iskandar Setiawan , GNU/Weeb Mailing List References: <20221104180931.3852-1-kiizuha@gnuweeb.org> <20221104180931.3852-6-kiizuha@gnuweeb.org> <73b917bc-6d20-b2d1-f956-11d6e2ff1662@gnuweeb.org> <942fe0b7-9b12-0445-6c75-ad90addb0f21@gnuweeb.org> <99ca9aae-0d1c-3cc1-1f7f-eee09ff99585@gnuweeb.org> From: Muhammad Rizki In-Reply-To: <99ca9aae-0d1c-3cc1-1f7f-eee09ff99585@gnuweeb.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: On 07/11/2022 08.26, Ammar Faizi wrote: > On 11/7/22 8:11 AM, Muhammad Rizki wrote: >> From the past patch, some email doesn't escape correctly, like it >> supposed to escaped "> >" to "> >", but the result keep "> >". >> That problem is from the past, IDK if current patch will fix that escape >> if using html.escape() 1 time. > > Any reproducer to try? > Will try it in the next version.