ISSUE-69: Support for reading/phonetic/pronunciation fields

Support for reading/phonetic/pronunciation fields

Raised by:
Koji Ishii
Opened on:
Section 4.4: 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:
  1. Review of tracker issues for best practices (part II) (from on 2015-03-28)
  2. Re: I18N-ISSUE-69: Support for reading/phonetic/pronunciation fields [Contacts API] (from on 2011-07-05)
  3. I18N-ISSUE-69: Support for reading/phonetic/pronunciation fields [Contacts API] (from on 2011-07-04)

Related notes:

No additional notes.

Display change log ATOM feed

Addison Phillips <>, Chair, Richard Ishida <>, Bert Bos <>, Fuqiao Xue <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $