From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43782) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1CxQ-0006It-Pl for qemu-devel@nongnu.org; Tue, 24 Nov 2015 07:44:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a1CxM-0008VJ-FE for qemu-devel@nongnu.org; Tue, 24 Nov 2015 07:44:28 -0500 Received: from mx1.redhat.com ([209.132.183.28]:58924) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1CxM-0008V8-7u for qemu-devel@nongnu.org; Tue, 24 Nov 2015 07:44:24 -0500 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (Postfix) with ESMTPS id D6C67689 for ; Tue, 24 Nov 2015 12:44:23 +0000 (UTC) Date: Tue, 24 Nov 2015 20:44:21 +0800 From: Fam Zheng Message-ID: <20151124124421.GB29832@ad.usersys.redhat.com> 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> <5654477E.2060807@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <5654477E.2060807@redhat.com> 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: Paolo Bonzini Cc: armbru@redhat.com, Laszlo Ersek , Gerd Hoffmann , qemu-devel@nongnu.org On Tue, 11/24 12:18, Paolo Bonzini wrote: >=20 >=20 > 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 transliterat= ion > > of the reporter's name (or a part of it). Now, while Pinyin has its o= wn Yes, it's the Pinyin of =E7=A5=9A=E8=87=B3, his given name. It's a peculi= ar and literary choice of name. :) > > separate pronunciation rules, I *can* (and occasionally do) look up > > those rules. So Pinyin allows me to *work* with the name with relativ= e > > safety, and it even gives me a fleeting chance at getting the > > pronunciation right, should we meet. >=20 > I think this is getting into dangerous territory. :) >=20 > 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). >=20 > 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. >=20 > Certainly it's better if you get something like these: >=20 > Signed-off-by: Gong Li (=E5=B7=A9=E4=BF=90) > Signed-off-by: =E5=B7=A9=E4=BF=90 (Gong Li) >=20 > but if the email is understandable I have no problem with >=20 > Signed-off-by: =E5=B7=A9=E4=BF=90 >=20 > or in the case of an English name any of >=20 > 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) >=20 > where in the last case the email doesn't give the full Chinese name, bu= t > there is an alternative for people who cannot read Chinese characters. >=20 > 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. The problem for using Pinyin is, even I as a Chinese can't tell which is = the last name out of a two-syllable name such as "Gong Li", because of obviou= s reasons. Having hanzi together with Pinyin helps a lot, in that it tells me how to= call it, should we meet. Not just in "which is the family name", but also whic= h tone to use. In Chinese, you're not calling one's name if not using the r= ight tone. For example "zuozhi" can be "=E5=B7=A6=E4=B9=8B" or "=E7=A5=9A=E8=87= =B3" or one of other 100 combinations, which vary in tones. Personally I don't feel very comfortab= le when a Mandarin speaker calls me with a wrong tone. And I know that will = happen from time to time if I stick to Pinyin rather than Fam. Thinking from th= e other way round, that may be a reason why they use hanzi. All in all, in my opinion, only something like Signed-off-by: =E5=B7=A9=E4=BF=90 , from which you can't easily infer the pronunciation, is apparently inconsiderate in an English context. Otherwise I think we should tolerate= the usage of non-latin characters even if it means we have to copy&paste. Fam