ISSUE-69: Support for reading/phonetic/pronunciation fields
Support for reading/phonetic/pronunciation fields
- State:
- CLOSED
- Product:
- contacts-api
- Raised by:
- Koji Ishii
- Opened on:
- 2011-07-04
- Description:
- Section 4.4: ContactName
http://dev.w3.org/2009/dap/contacts/#idl-def-ContactName
WG Approved: Yes
The fields defined in the ContactName interface do not include fields for "pronunciation" (also called variously "furigana", "reading", or "phonetic"). These fields are necessary to support East Asian cultures and names, since the pronunciation information is important for both sorting/organizing names (Chinese and Japanese ideographs do not contain this information directly).
Many vendors support this via proprietary X- extension fields. Lack of interchange for these fields represents a significant barrier for global name catalogs.
Please add optional pronunciation fields for at least the family and given name fields. - Related Actions Items:
- No related actions
- Related emails:
- Review of tracker issues for best practices (part II) (from addison@lab126.com on 2015-03-28)
- Re: I18N-ISSUE-69: Support for reading/phonetic/pronunciation fields [Contacts API] (from robin@berjon.com on 2011-07-05)
- I18N-ISSUE-69: Support for reading/phonetic/pronunciation fields [Contacts API] (from sysbot+tracker@w3.org on 2011-07-04)
Related notes:
No additional notes.
Display change log
