Initial work on address formats #622
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for i18n-drafts ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
r12a
approved these changes
Nov 29, 2024
|
|
||
| Address formats vary widely across the globe, with differences in structure, content, and the level of granularity. For authors and developers designing forms, databases, or systems that handle addresses, understanding these variations is crucial to avoid frustrating users from other countries. This article will introduce some of the key differences in address formats around the world and provide guidance on how to design systems that can handle them effectively. | ||
|
|
||
| This is not an exhaustive guide but aims to sensitize you to the complexities of international address formats and the challenges they pose for web design. As with [personal names](https://www.w3.org/International/questions/qa-personal-names.en.html), there is rarely a "perfect" solution, but awareness of these differences is the first step toward building more inclusive systems. |
There was a problem hiding this comment.
Don't use the .en.html in the link, since we have translations of that article.
|
|
||
| In Germany, if there are suburbs, their names should be placed above the street name and house number. | ||
|
|
||
| In China, addresses are written starting with the postal code, followed by the largest administrative area (e.g., province), and down to the smallest unit (e.g., room number). For example: |
|
|
||
| #### **Locality-specific elements** | ||
|
|
||
| For example, the UK includes elements like "dependent locality" and "double dependent locality" for more granular location information. Royal Mail requires the "post town" to be included whenever possible. |
There was a problem hiding this comment.
Even though i live in the UK i don't understand what this dependency stuff means ;-). Perhaps reword, explain, or give an example of what this is about.
|
|
||
| Address formats vary widely across the globe, with differences in structure, content, and the level of granularity. For authors and developers designing forms, databases, or systems that handle addresses, understanding these variations is crucial to avoid frustrating users from other countries. This article will introduce some of the key differences in address formats around the world and provide guidance on how to design systems that can handle them effectively. | ||
|
|
||
| This is not an exhaustive guide but aims to sensitize you to the complexities of international address formats and the challenges they pose for web design. As with [personal names](https://www.w3.org/International/questions/qa-personal-names.en.html), there is rarely a "perfect" solution, but awareness of these differences is the first step toward building more inclusive systems. |
There was a problem hiding this comment.
A difference that i think is worth mentioning is the order of street name and house number. In Germany & Switzerland the house number follows the street name, which has implications for form design.
Also, some people may not have house numbers, or may need to add a house name, or a flat number. This leads to the more general issue, too, that the number of lines needed for an address can vary.
There are also things like where the address should be printed on an envelope - in Switzerland i used to get in trouble for putting the 'to' address in the middle.
| - [International Address Format: Structure and Normalization](https://www.geopostcodes.com/blog/international-address-data/) | ||
| - [Address](https://en.wikipedia.org/wiki/Address) on Wikipedia | ||
| - [Proposal for extending the autocomplete attribute](https://github.com/battre/autocomplete-attribute-explainer/) | ||
| - [Personal names around the world](https://www.w3.org/International/questions/qa-personal-names.en.html) |
|
|
||
| ### How do address formats differ around the world, and what are the implications of those differences on the design of forms, databases, ontologies, etc. for the Web? | ||
|
|
||
| Address formats vary widely across the globe, with differences in structure, content, and the level of granularity. For authors and developers designing forms, databases, or systems that handle addresses, understanding these variations is crucial to avoid frustrating users from other countries. This article will introduce some of the key differences in address formats around the world and provide guidance on how to design systems that can handle them effectively. |
There was a problem hiding this comment.
I think it would be good to include lots of visual example, pretty much for each point you make, rather than just the few you have.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Started to write some stuff about address formats. Comments are welcome.
If this is merged, we might want to consider updating specdev and the techniques page.