W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2010

Re: I18N-ISSUE-6: Localization mechanism too restricted [WOFF]

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 15 Dec 2010 11:16:58 -0800
Message-ID: <AANLkTimqFffmCAr9W5Rza6Zv3WOKrbBD+mK47JDtJOAk@mail.gmail.com>
To: public-i18n-core@w3.org
Cc: www-font@w3.org
On Wed, Dec 15, 2010 at 11:03 AM, Internationalization Core Working
Group Issue Tracker <sysbot+tracker@w3.org> wrote:
>
> I18N-ISSUE-6: Localization mechanism too restricted [WOFF]
>
> http://www.w3.org/International/track/issues/6
>
> Raised by: Richard Ishida
> On product: WOFF
>
> 6.2.1 Extended Metadata Block
> http://www.w3.org/TR/WOFF/#Metadata
>
> WG Reviewed: Yes
>
> A Japanese font vendor would probably want a Japanese audience to see its name in kanji, but present a Latin transcription to non-Japanese viewers.  To enable this, the localised version access mechanism (ie. use of the text element) should also apply to the content of the vendor element.
>
> Likewise, a Tamil font designer would probably want their name in the credit element to be available in either Tamil or Latin scripts.
>
> I'm therefore proposing that you extend the localization selection mechanism to vendor, credit and licensee elements (which would also reinforce the comment that proposes that the content of these elements be element content rather than attribute values).
>
> I am assuming that this would not apply to the uniqueid element, by definition (even though it would be possible for markup authors to use non-ASCII text in the id itself).

Is the only expected issue the name of vendors?  Can this be addressed
simply through normal use of a parenthesized aside to indicate an
alternate representation of the name?  Like "株式会社日立製作所 (Hitachi)"?

~TJ
Received on Wednesday, 15 December 2010 19:18:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 15 December 2010 19:20:29 GMT