ISSUE-6: Localization mechanism too restricted

Localization mechanism too restricted

State:

CLOSED

Product:

woff

Raised by:

Richard Ishida

Opened on:

2010-12-15

Description:

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).

Related Actions Items:

No related actions

Related emails:

1. Re: [css-text-decor-3] Updated DoC, open issues (from fantasai.lists@inkedblade.net on 2017-10-18)
2. Re: [css-text-decor-3] Updated DoC, open issues (from florian@rivoal.net on 2017-01-08)
3. Review of tracker issues for best practices (from addison@lab126.com on 2015-03-25)
4. Re: I18N-ISSUE-6: Localization mechanism too restricted [WOFF] (from ishida@w3.org on 2011-07-13)
5. Re: I18N-ISSUE-6: Localization mechanism too restricted [WOFF] (from chris@w3.org on 2011-07-06)
6. Re: I18N-ISSUE-6: Localization mechanism too restricted [WOFF] (from ishida@w3.org on 2011-06-02)
7. Re: I18N-ISSUE-6: Localization mechanism too restricted [WOFF] (from jackalmage@gmail.com on 2010-12-15)
8. I18N-ISSUE-6: Localization mechanism too restricted [WOFF] (from sysbot+tracker@w3.org on 2010-12-15)

Related notes:

Display change log