Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The article remains western- (and especially UK-) centric in outlook, a more international business will probably find plenty others. For instance japans disprove:

* The address format is uniform across the country (Sapporo has its own, and Kyoto uses an alternative system on top of the standard one)

* Addresses go from the most specific to least (e.g. flat number to postal code), japan is the exact opposite

* Addressing systems don't change (Japan's was reformed in 1998)

* Building numbers are street-based (Japan's are block-based)

It also expands on things like "addresses will have a street": standard japanese addressing is subdivision-based so addresses provide the prefecture, the ward (~county), the district and the city block.

Except for Sapporo and Kyoto (see 1): Kyoto allows an denoting blocks as the intersection of two streets and the position relative to the intersection (north, south, east or west). One reason is that some wards have multiple districts with the same name... Sapporo uses a system where blocks are addressed by their distance (in blocks) + direction from city center, so you might be told the address is "the 4th building, 3 blocks north and 5 blocks east".



US addresses exhibit neither increasing nor decreasing specificity. Apartment numbers are usually written in the middle, like "30 Tristan Way, Apt. 107, Gwyneth VA 27384". This never seemed strange to me until I saw it being done more sensibly elsewhere.

Singapore is another good one: its postcode scheme changed twice in less than a century, and being a city-state, there is nothing useful to put in a "city" field (mail is often sent to "Singapore Singapore", or even "Singapore Singapore Singapore").


This really bothered me when I had mail shipped to me in Shanghai from amazon (US). Amazon forces you to provide a state. Shanghai is its own administrative unit, at a level with Chinese provinces. So my address ended up being "<street>, Shanghai, Shanghai China".

I've seen natives handle that problem by filling in their district in the "city" field, so e.g. in my case "<street>, Minhang district, Shanghai China", analogous to e.g. "<street>, Nob Hill, San Francisco, USA".


>US addresses exhibit neither increasing nor decreasing specificity. Apartment numbers are usually written in the middle, like "30 Tristan Way, Apt. 107, Gwyneth VA 27384". This never seemed strange to me until I saw it being done more sensibly elsewhere.

Best to think of it as an onion. On the outer layers (beginning and end) automated and semi-automated sorting can be applied most easily (the ZIP code was designed for automated sorting and routing). Apartment and suite numbers in the middle are handled (usually) manually by carriers already at or near the service address.


> Singapore [...] being a city-state, there is nothing useful to put in a "city" field

Good point, which should apply to most city-states (e.g. Monaco, or the Vatican)


...not to mention the substantial number of rural addresses that don't include city names in most countries.


That's a very verbose way of writing an apartment... In Australia, we'd write the first part of that address as 107/30 Tristan Way.


And in Sri Lanka it would be written the other way around - 30/107 Tristan Way.


Or for Singapore, I've seen people put in "China" for the country field. But that was just someone from the US trying to ship to us..


...worse, Japan's addresses are chronologically assigned! You're essentially limited to a big lookup table by the structure of the system.

This is both a comical inconvenience for travelers (try finding an address without speaking the language), and a huge problem for porting any sort of local-data application to Japan.


I think the UK examples are quite good though. They show that you don't even have to change language to run into massive problems with addresses. More than being anglo-centric, the issue of addresses is often even more specific, i.e. US specific.

Japan et. al. add another layer of complexity, other text encodings etc. etc., but even in the seemingly simple case of English being used, it's not quite as simple as many forms make it out to be.


For those that want an example:

100-0001 (ZIP Code) 東京都 (Tokyo-to, Prefecture) 千代田区 (Chiyoda-ku, City) 千代田1−1 (Chiyoda 1-1, Area Block-Subblock)


I'd really like people to turn these into specialized wikis or Github repos or something.

A format of:

  Statement of Falsehood
  Explanation / Description
  Counterexamples
  Suggested mitigations
would be fine. It'd make it possible for us to submit ones that aren't apparent to the originator.


No mention of unicode, either. It might not be a huge problem in Japanese (unless the system silently ignores unicode, and gets all the way to shipping with a blank address field), but romanizing Chinese characters can result in very unreadable text (for a pathological example, see http://en.wikipedia.org/wiki/Lion-Eating_Poet_in_the_Stone_D...)




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: