From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Letter-case conversions in network protocols Date: Thu, 20 Jan 2022 10:21:58 +0100 Message-ID: <87czkm69u1.fsf@gnus.org> References: <83h7jda71o.fsf@gnu.org> <87bl9lovpo.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28950"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel@gnu.org, Stefan Monnier , Daniel =?utf-8?Q?Mart=C3=ADn?= To: Fatih Aydin Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 20 11:14:08 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 1nAUSF-0007I5-2U for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Jan 2022 11:14:07 +0100 Original-Received: from localhost ([::1]:54718 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nAUSD-0004q4-PY for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Jan 2022 05:14:05 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:43430) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nATeE-0000dM-Tw for emacs-devel@gnu.org; Thu, 20 Jan 2022 04:22:26 -0500 Original-Received: from [2a01:4f9:2b:f0f::2] (port=36508 helo=quimby.gnus.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nATeC-0000ZQ-Mc; Thu, 20 Jan 2022 04:22:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To: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=rpNtkzyAfELEBPzkaAqD1c/hHg9oN9AZsMqutbcietQ=; b=BrSCpFmrqrr5zvImjfeyayAzL4 lJlPi6D7cNJZgeoGv+D9AotQS93GZXrEOp0QhqQEDrPUV3TEEuPi0WqqKgRWiO31U0JUGiL4xVUXi 6dJ5EXBVfvsMLv9Vo2w4MI0USQt4DUGN2s77mWIJ5pL9vPCfZQn0MdFf5pceiS173ykE=; Original-Received: from [84.212.220.105] (helo=giant) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nATdn-0003lA-1o; Thu, 20 Jan 2022 10:22:01 +0100 X-Now-Playing: DMX Krew's _We Are DMX_: "Release My Love (Instrumental)" In-Reply-To: (Fatih Aydin's message of "Mon, 17 Jan 2022 12:41:18 +0300") X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a01:4f9:2b:f0f::2 (failed) Received-SPF: pass client-ip=2a01:4f9:2b:f0f::2; envelope-from=larsi@gnus.org; helo=quimby.gnus.org X-Spam_score_int: -35 X-Spam_score: -3.6 X-Spam_bar: --- X-Spam_report: (-3.6 / 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, RCVD_IN_DNSWL_MED=-2.3, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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" Xref: news.gmane.io gmane.emacs.devel:285023 Archived-At: Fatih Aydin writes: > 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. As far as I can tell, it's because the Google web site returns invalid data. It's not returning utf-8 but a different charset, but the headers claim that it's utf-8. I've seen this before with various Google web sites -- they return other data when not using Chrome/Firefox, and that data is often invalid. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no