I18N Review

No implementation impact

• Editorial issues
  • Typo in reference, addressed by pull request 941
  • Non-US examples, addressed by pull request 943
  • Currency code / symbol handling - Does this pull request 942 address issue 1044 and issue 1045?

Potential implementation impact

Localization issues

• Checkout content, dir/Lang on labels: Revisit WPWG issue 327 for issue 1359 (PayerErrors dictionary), issue 1357 (PaymentShippingOption dictionary), issue 1046 (PaymentDetailsUpdate dictionary), and issue 1040 (displayItems). See also PaymentItem Dictionary and PaymentShippingOption Dictionary. See comments from r12a. Proposed: Add dir/lang to dictionaries with human-readable labels.
• Browser UX, localization based on language of merchant checkout experience: See pull request 944 for issue 1043 and issue 1041 and issue 650. See also comments from Marcos. See also issue 946

Questions:

• For a given object with multiple text fields (e.g., PaymentErrors), would a single semantic marker suffice?
• From an implementer perspective, is the higher cost (1) parsing data (e.g., structure versus series of values) or (2) doing the localization work?

Data requests for contact information

• Given/Family name: issue 467. See comment from Addison
• Phonetic name: issue 773. See comments from Marcos. Is Phonetic name only used for addresses?

Notes:

• ApplePay supports given, family, phonetic given, and phonetic family for shipping and billing address information.
• GooglePay supports neither

SPC Task Force

• First meeting 19 April