From: Andreas Schwab <schwab@suse.de>
To: Mike FABIAN via Libc-alpha <libc-alpha@sourceware.org>
Cc: Mike FABIAN <mfabian@redhat.com>, Jens Petersen <petersen@redhat.com>
Subject: Re: [PATCH] Change collation rules in localedata/locales/th_TH to use copy "iso14651_t1" and agree as much as possible with CLDR
Date: Wed, 28 Jun 2023 13:30:06 +0200 [thread overview]
Message-ID: <mvmfs6bx1s1.fsf@suse.de> (raw)
In-Reply-To: <s9dtturc0c3.fsf@hathi.site> (Mike FABIAN via Libc-alpha's message of "Wed, 28 Jun 2023 13:06:52 +0200")
I see a lot of undecodable byte sequences which consist of "\340\270?"
and "\340\271?".
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-06-28 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 11:06 Mike FABIAN
2023-06-28 11:30 ` Andreas Schwab [this message]
2023-06-28 14:15 ` Mike FABIAN
2023-06-28 14:29 ` Andreas Schwab
2023-07-05 11:31 ` Mike FABIAN
2023-07-05 12:11 ` Andreas Schwab
2023-07-05 14:39 ` Siddhesh Poyarekar
2023-07-07 17:55 ` Mike Fabian
2023-07-10 7:43 ` Andreas Schwab
2023-07-11 20:11 [PATCH] Change collation rules in localedata/locales/th_TH to use copy iso14651_t1 " Mike FABIAN
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mvmfs6bx1s1.fsf@suse.de \
--to=schwab@suse.de \
--cc=libc-alpha@sourceware.org \
--cc=mfabian@redhat.com \
--cc=petersen@redhat.com \
/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.
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).