public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Check sorting of MAINTAINERS
Date: Tue, 11 Jan 2022 11:05:21 +0100	[thread overview]
Message-ID: <9233f5e9-7072-0ae3-f3d7-a0d5f52e66dc@suse.cz> (raw)
In-Reply-To: <20220111093855.GQ2646553@tucnak>

On 1/11/22 10:38, Jakub Jelinek wrote:
> On Tue, Jan 11, 2022 at 10:27:19AM +0100, Martin Liška wrote:
>> On 1/10/22 17:14, Martin Liška wrote:
>>> Are you fine with the suggested changes?
>>
>> Hello.
>>
>> Jakub had comments so I'm sending v2 where I added few parsing
>> exceptions. Now it reports:
> 
> I'm still surprised by what the sort is doing,
> ( echo Chene; echo Chêne; echo Chfne ) | LC_ALL=en_US.UTF-8 sort
> Chene
> Chêne
> Chfne
> That is on glibc 2.32.  On glibc 2.34.9000 I get a different order though,
> Chêne last.
> That partly ruins the idea of the checking script when the sorting isn't
> the same for many people, either the script will be failing for many people
> or various people will be changing the order there and back all the time.
> 
> 	Jakub
> 

Or we can utilize https://pypi.org/project/Unidecode python package that provides:

In [7]: unidecode.unidecode('Jääskeläinen')
Out[7]: 'Jaaskelainen'

and sort it by that.

Martin

  parent reply	other threads:[~2022-01-11 10:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 16:14 Martin Liška
2022-01-11  9:27 ` Martin Liška
2022-01-11  9:38   ` Jakub Jelinek
2022-01-11  9:55     ` Martin Liška
2022-01-11 10:05     ` Martin Liška [this message]
2022-01-11 13:12       ` Martin Liška
2022-01-11  9:45 ` Tobias Burnus
2022-01-11  9:54   ` Martin Liška
2022-01-18  7:59 ` Thomas Schwinge
2022-01-18  8:18   ` Martin Liška

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=9233f5e9-7072-0ae3-f3d7-a0d5f52e66dc@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@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).