From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Michael Ellerman <mpe@ellerman.id.au>,
Thorsten Blum <thorsten.blum@linux.dev>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Naveen N Rao <naveen@kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Transliterate author name and remove FIXME
Date: Sat, 23 Nov 2024 11:19:28 +0100 [thread overview]
Message-ID: <d9e232bb-5069-4526-b781-f4e316bda95d@csgroup.eu> (raw)
In-Reply-To: <87v7weodqn.fsf@mpe.ellerman.id.au>
Le 23/11/2024 à 04:01, Michael Ellerman a écrit :
> Thorsten Blum <thorsten.blum@linux.dev> writes:
>> On 11. Nov 2024, at 02:11, Michael Ellerman wrote:
>>> Thorsten Blum <thorsten.blum@linux.dev> writes:
>>>> The name is Mimi Phuong-Thao Vo.
>>>
>>> Is that the correct spelling?
>>>
>>> The github commit below suggests it's Mimi Phûông-Thåo Võ.
>>>
>>> And presumably the author preferred that spelling, otherwise they would
>>> have just written it in ASCII in the first place.
>>>
>>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbminor%2Fbinutils-gdb%2Fcommit%2F6603bf38d74409906b3814f6a26c0483a5d32e41&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7Ce09e131ad44342b0be9a08dd0b6b1c9b%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C638679276875561424%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=5F8j2IkQc6sy8tnoBoNVlbxA2YyxptCfh92Gx9mi460%3D&reserved=0
>>
>> Hi Michael,
>>
>> Are you suggesting to keep "Mimi Ph\373\364ng-Th\345o V\365" and a FIXME
>> instead of changing it to "Mimi Phuong-Thao Vo" which is how she spells
>> her name on her LinkedIn profile and other websites?
>
> No I'm not suggesting to leave it as-is.
>
> But I also suspect they spell it that way on LinkedIn etc. because it's
> the path of least resistance, not because it's the correct spelling.
>
> I was hoping someone who's more familiar with Vietnamese (I believe)
> spelling would chime in and tell us which is correct.
>
>> I doubt anyone prefers their name to be spelled with octal escape
>> characters.
>
> Sure, but it wouldn't have been octal escapes in the original character
> encoding, it would have appeared, I believe, as Mimi Phûông-Thåo Võ.
>
Isn't our file just a copy of the one from binutils ? Shouldn't we
adjust it based on commit
https://github.com/bminor/binutils-gdb/commit/2ce18a16268a ?
Christophe
next prev parent reply other threads:[~2024-11-23 10:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 16:21 Thorsten Blum
2024-11-11 1:11 ` Michael Ellerman
2024-11-11 7:16 ` Thorsten Blum
2024-11-22 11:57 ` Thorsten Blum
2024-11-23 3:01 ` Michael Ellerman
2024-11-23 10:19 ` Christophe Leroy [this message]
2025-01-07 12:16 ` Thorsten Blum
2025-02-11 10:09 ` Thorsten Blum
2025-05-13 14:10 ` Thorsten Blum
2025-05-13 17:48 ` Christophe Leroy
2025-05-14 3:35 ` Madhavan Srinivasan
2025-05-18 3:45 ` Madhavan Srinivasan
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=d9e232bb-5069-4526-b781-f4e316bda95d@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=thorsten.blum@linux.dev \
/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
all inboxes | Powered by JetHome®