-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide better mapping between PaymentAddress and HTML5 autofill #505
Comments
Does |
sorting code example would also help? |
Also, the |
Sorting codes are used in France and related countries. See the Wikipedia entry. Our French working group members should be able to provide some good examples. CLDR is better than ISO in that it's updated more frequently to reflect the changes in the real world, like the break-up of Yugoslavia. @lararennie: Please double-check my i18n-foo. |
The field labelled "sorting code" is not just used for that, but is country specific: in some countries it manifests as a post office indicator. Comments for this field should be: Note that address-level1 and 2 does NOT map to the levels used for administrative purposes in a country, but in an address. For instance, for the US, level1 would be state, and level2 would be city/post-town NOT county. In Spain, the top-level admins e.g. Catalonia are not in an address, so level1 is the province, which is. |
Good link for CLDR: http://www.unicode.org/cldr/charts/31/supplemental/territory_information.html |
@marcoscaceres why is this a blocker for CR? |
Closing in favor of w3c/contact-picker#71 |
For instance, be more clear that:
This helps with the conversion from auto-filled form fields to payment
PaymentAddress
.The text was updated successfully, but these errors were encountered: