From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48432) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1BcN-0007Oq-AN for qemu-devel@nongnu.org; Tue, 24 Nov 2015 06:18:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a1BcA-0002YU-7h for qemu-devel@nongnu.org; Tue, 24 Nov 2015 06:18:39 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56682) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1Bc9-0002YH-WF for qemu-devel@nongnu.org; Tue, 24 Nov 2015 06:18:26 -0500 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id 87B95E706B for ; Tue, 24 Nov 2015 11:18:25 +0000 (UTC) References: <1448300659-23559-1-git-send-email-pbonzini@redhat.com> <1448300659-23559-3-git-send-email-pbonzini@redhat.com> <565353ED.1090502@redhat.com> <1448352204.27648.19.camel@redhat.com> <5654410E.4000805@redhat.com> From: Paolo Bonzini Message-ID: <5654477E.2060807@redhat.com> Date: Tue, 24 Nov 2015 12:18:22 +0100 MIME-Version: 1.0 In-Reply-To: <5654410E.4000805@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v2 2/4] qjson: do not save/restore contexts List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek , Gerd Hoffmann Cc: Fam Zheng , qemu-devel@nongnu.org, armbru@redhat.com On 24/11/2015 11:50, Laszlo Ersek wrote: > You > (the generic you) can't expect me (the generic me) to read Kanji, > Sanskrit, Thai script, Cyrillic script, and so on, even if your name is > written in that language natively. You come up with an approximation in > Latin script, and use that. >=20 > Is your purpose to feel pleased about the faithful representation of > your name in the commit message (that the international community is > unable to read, not even approximately), or is your goal to allow the > community to read your (approximate) name? >=20 > Specifically about the commit you mention, the email of the reporter is= : >=20 > zuozhi.fzz@alibaba-inc.com >=20 > I'm absolutely sure that "zuozhi" is the official Pinyin transliteratio= n > of the reporter's name (or a part of it). Now, while Pinyin has its own > separate pronunciation rules, I *can* (and occasionally do) look up > those rules. So Pinyin allows me to *work* with the name with relative > safety, and it even gives me a fleeting chance at getting the > pronunciation right, should we meet. I think this is getting into dangerous territory. :) Chinese language and names are very different from ours and it's possible that a person for some reason is very attached to the particular hanzi (kanji is Japanese :)) that are used for their name. (Fam, correct me if I'm wrong). I've also seen people who have adopted an alternative English name and still want to include the Chinese name somewhere, at which point it's understandable that they write the latter with hanzi. Certainly it's better if you get something like these: Signed-off-by: Gong Li (=E5=B7=A9=E4=BF=90) Signed-off-by: =E5=B7=A9=E4=BF=90 (Gong Li) but if the email is understandable I have no problem with Signed-off-by: =E5=B7=A9=E4=BF=90 or in the case of an English name any of Signed-off-by: Jane Li (=E5=B7=A9=E4=BF=90) Signed-off-by: =E5=B7=A9=E4=BF=90 (Jane Li) Signed-off-by: =E5=B7=A9=E4=BF=90 (Jane Li) where in the last case the email doesn't give the full Chinese name, but there is an alternative for people who cannot read Chinese characters. For some reason this almost never happens with Japanese developers, but https://en.wikipedia.org/wiki/Japanese_name#Difficulty_of_reading_names suggests that they may also appreciate using kanji for their names in commit messages. Thanks, Paolo