From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Fatih Aydin Newsgroups: gmane.emacs.devel Subject: Re: Letter-case conversions in network protocols Date: Mon, 17 Jan 2022 12:41:18 +0300 Message-ID: References: <83h7jda71o.fsf@gnu.org> <87bl9lovpo.fsf@gnus.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000001fa7205d5c3f54a" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3853"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , emacs-devel@gnu.org, Stefan Monnier , =?UTF-8?Q?Daniel_Mart=C3=ADn?= To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 17 13:24:07 2022 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 1n9R3P-0000lJ-Ch for ged-emacs-devel@m.gmane-mx.org; Mon, 17 Jan 2022 13:24:07 +0100 Original-Received: from localhost ([::1]:46524 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n9R3O-0007hv-08 for ged-emacs-devel@m.gmane-mx.org; Mon, 17 Jan 2022 07:24:06 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48274) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9OW8-0000Ku-Cr for emacs-devel@gnu.org; Mon, 17 Jan 2022 04:41:36 -0500 Original-Received: from [2607:f8b0:4864:20::932] (port=38806 helo=mail-ua1-x932.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n9OW4-00070p-1x; Mon, 17 Jan 2022 04:41:33 -0500 Original-Received: by mail-ua1-x932.google.com with SMTP id h11so29339444uar.5; Mon, 17 Jan 2022 01:41:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6vMpqv6h73DSg6MgqJs8gJrpjWWYNd32itXaoX3zPg4=; b=ZeL9KQQ1E1fYsguFk8ACRojYKNhWtkuDDdTUCj3jV02KRnu0gKzIsh7AJKKtQ+xuL8 MvJTPwzEwopCfjS6tqSpnsSgN0NfUxFkumlHqTW7e03ez09gGyBG5cIiFLclToKaBDvu jaFDozuylSijWBAavUMXfhsQoglcx+R+pDo9FgNbvoenavBsEgiN1minMyEB9AjhkJVS sApXiqnmkrtWfiL2sdvVQVO9+F2MMtla8aZg+KualGVle/4FEh8vctcIC+rcVyxvE05L yLSKFDVzfoVnvq9WmJOLD27AbnNrkBNKmx31wxhTvcm6mEmBBTk6IiQLUIq2OrYi9oLc 1pBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6vMpqv6h73DSg6MgqJs8gJrpjWWYNd32itXaoX3zPg4=; b=pXCP7w6/oLJYwniBpPg6wnXpu+ITUZ98DwLsLwAR8deoxPN6UacTF1PaANoYgqs0dK HUY6OwF01EUt7QbD60izEBaWdvITUyCa1kC9o4gIMLMRU4AfcUk5qnJSV+U5XlusmZEW wSq/dwF+SfOzlEKcMiE27Dzr3ZYFU8VRH8Xu0kfxz/mIJ5OyBVD8hBs0RV6526Rmb+GE C/QmxaBJ/QFPhIl39DMxb6J73PO9rjxKrEKFPVftRpm8/wciCm/ZT7zK/vlDB5Vcp/6M zNCn7mDfl2PRuyNpEfs2HnIrYx0uZ1gjzyBrb6j26ZXDp/YQW1z0j4Q9mPEA7AJ7zAHk oCMQ== X-Gm-Message-State: AOAM530T4+EUvhv5vbuySjgKn0rZCryzOCAPDEOLyaJfg6RAHiPDhNwD MmX0J9mMICUJG9e3RJ/+G7t4mTJs5gszxoblQCw= X-Google-Smtp-Source: ABdhPJzu8JNREpV9G2ZyIrZGmwOFTIB+zz0zNQ3+Gi4AQFAK1Lj2FfyeLU6+bmvLgeulNyZx2XEokg5n7bEMtqMEoLI= X-Received: by 2002:a05:6102:485:: with SMTP id n5mr7493887vsa.57.1642412489438; Mon, 17 Jan 2022 01:41:29 -0800 (PST) In-Reply-To: <87bl9lovpo.fsf@gnus.org> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::932 (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::932; envelope-from=fataydin138@gmail.com; helo=mail-ua1-x932.google.com X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, PDS_HP_HELO_NORDNS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Mon, 17 Jan 2022 07:21:30 -0500 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" Xref: news.gmane.io gmane.emacs.devel:284870 Archived-At: --00000000000001fa7205d5c3f54a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable There is still a weird problem, not with network protocols but still in eww= . Run eww and visit Google and check non-ASCII chars, you will see the chars correctly. No problems. The bug is: 1) Set language environment to Turkish 2) Visit www.google.com.tr 3) Try to search something, or just observe the buttons You will see that some chars are displayed as \345. It's weird because I have tried other websites, it just happens with Google. On Sat, May 8, 2021 at 10:46 PM Lars Ingebrigtsen wrote: > Daniel Mart=C3=ADn writes: > > > Of course, code can still be broken if people explicitly do its own > > thing with `downcase', etc. instead of using the case-folding string > > APIs, but that's sort of an anti-pattern, anyway. > > But code does this sort of thing -- for instance, Message allows headers > to be specified in various ways, but will run the header names trough > `capitalize'. > > So this isn't just about doing comparisons, but separating out text > transformations that are done according to a protocol specification > (i.e., octets that happen to be ASCII) vs. the normal DWIM text > transformations. > > -- > (domestic pets only, the antidote for overdose, milk.) > bloggy blog: http://lars.ingebrigtsen.no > --00000000000001fa7205d5c3f54a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
There is still a weird problem, not with network prot= ocols but still in eww.
Run eww and visit Google and check non-AS= CII chars, you will see the chars correctly. No problems.
The bug= is:
1) Set language environment to Turkish
2) Visit www.google.com.tr
3) Try t= o search something, or just observe the buttons
You will see that= some chars are displayed as \345. It's weird because I have tried othe= r websites, it just happens with Google.

On Sat, May 8, 2021 at 10= :46 PM Lars Ingebrigtsen <larsi@gnus.o= rg> wrote:
mardani29@yahoo.es> writes:

> Of course, code can still be broken if people explicitly do its own > thing with `downcase', etc. instead of using the case-folding stri= ng
> APIs, but that's sort of an anti-pattern, anyway.

But code does this sort of thing -- for instance, Message allows headers to be specified in various ways, but will run the header names trough
`capitalize'.

So this isn't just about doing comparisons, but separating out text
transformations that are done according to a protocol specification
(i.e., octets that happen to be ASCII) vs. the normal DWIM text
transformations.

--
(domestic pets only, the antidote for overdose, milk.)
=C2=A0 =C2=A0bloggy blog: http://lars.ingebrigtsen.no
--00000000000001fa7205d5c3f54a--