W3C home > Mailing lists > Public > public-i18n-geo@w3.org > July 2004

RE: Proposed translation policy update

From: Richard Ishida <ishida@w3.org>
Date: Tue, 6 Jul 2004 18:08:12 +0100
To: "'Masayasu Ishikawa'" <mimasa@w3.org>, <public-i18n-geo@w3.org>
Message-Id: <20040706170811.E3ACF4EF15@homer.w3.org>

> -----Original Message-----
> From: public-i18n-geo-request@w3.org
> [mailto:public-i18n-geo-request@w3.org] On Behalf Of Masayasu Ishikawa
> Sent: 06 July 2004 17:04
> To: public-i18n-geo@w3.org
> Subject: Re: Proposed translation policy update
> "Richard Ishida" <ishida@w3.org> wrote:
> > I would like us to add romanised versions of names in parens after
> > non-ASCII ones.  There are two reasons for this: [a] I can remember
> > more easily who did a Japanese, Arabic, etc. translation,
> [b] people
> > can see how the name is written for correspondence in an English
> > environment.  I added this to the page above.
> That's OK, but for Japanese names, using the order like
> "石川 雅康 (Masayasu Ishikawa)" could be a bit confusing -
> especially when someone sees it after "リチャード 石田 (Richard Ishida)".
> If a reader is not familiar with Japanese names, s?he might think
> "石川" corresponds to "Masayasu", which is actually wrong.

There are many more things that could go wrong here. I'm not sure it's ever
wise to try to figure out the elements of a  name in one script from

> When I list my name in Kanji and latin alphabet, I tend to write
> "石川 雅康 (ISHIKAWA Masayasu)" or "石川 雅康 (Masayasu ISHIKAWA)",
> or when appropriate use ruby, e.g.
>     http://www.w3.org/TR/xhtml-media-types/#editor
> In any case, in romanized version it should be made clear
> which is family name and which is given name.

OK. I guess we can do that by capitalization.

> Regards,
> --
> Masayasu Ishikawa / mimasa@w3.org
> W3C - World Wide Web Consortium
Received on Tuesday, 6 July 2004 13:08:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:01 UTC