From: Lars Ingebrigtsen <larsi@gnus.org>
To: Fatih Aydin <fataydin138@gmail.com>
Cc: "Eli Zaretskii" <eliz@gnu.org>,
emacs-devel@gnu.org, "Stefan Monnier" <monnier@iro.umontreal.ca>,
"Daniel Martín" <mardani29@yahoo.es>
Subject: Re: Letter-case conversions in network protocols
Date: Thu, 20 Jan 2022 10:21:58 +0100 [thread overview]
Message-ID: <87czkm69u1.fsf@gnus.org> (raw)
In-Reply-To: <CAHRQZ1zDhsNUVQkWHQpOso+AxzD4Pi7iNYEdwrv2irs92saNhA@mail.gmail.com> (Fatih Aydin's message of "Mon, 17 Jan 2022 12:41:18 +0300")
Fatih Aydin <fataydin138@gmail.com> 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
prev parent reply other threads:[~2022-01-20 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 9:50 Letter-case conversions in network protocols Eli Zaretskii
2021-05-08 10:20 ` Lars Ingebrigtsen
2021-05-08 13:47 ` Stefan Monnier
2021-05-08 15:41 ` Daniel Martín
2021-05-08 19:45 ` Lars Ingebrigtsen
2022-01-17 9:41 ` Fatih Aydin
2022-01-20 9:21 ` Lars Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czkm69u1.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fataydin138@gmail.com \
--cc=mardani29@yahoo.es \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).