I used to work in property law here in Ireland and some of the addresses were absolute nightmares - particularly when you included the full description as given on all the deeds going back a couple hundred years. “A formerly known as B situate in the Townland of C, Barony of D and County E now known as 10 F Street, G.”
And usually E (and possibly G) are the only ones you can spell without assistance.
Actually, TLD, NZ Post states in most of their literature that the postcodes are only necessary in NZ for bulk mailout purposes, not really for standard mail. I use mine anyway, because I grew up in an era where every letter in Auckland had a code, just a single or two digit number. Now it’s 4. Progress, eh?
Oh, that’s nothing. You should see the property law in New Mexico. And here’s why:
In the 16th and 17th century, mostly, the Spanish government issued royal land grants. Eventually, when Mexico got independence, that government promised to uphold the original land grants. When the US got the area including New Mexico after the Mexican War, the US government promised to uphold the original land grants.
So, if you really need to track the ownership of a property, sometimes you have to go all the way back several centuries into another language.
I’m sure this is probably true in at least California, Arizona, and Texas, as well.
This rant comes at a good time. I was just now trying to fill out a form at Priceline and I get this. I have reviewed everything several times but I keep getting the same thing. The least they could do is tell you what field does not parse. Screw them. I’m going somewhere else.
I’m not going to mention the website, but it really should have known better. It had 35 available counties to pick from in Ireland (we’d be happy with 32, but thats another issue :)) including “Shannon”.
Oh, and if you want to look at a map of Dublin on the Yahoo! map site, you have to choose “UK”. Furthermore, Yahoo! issues Irish people with @yahoo.co.uk addresses instead of @yahoo.ie ones.
There is, of course, the insular nature of American business that tends to interfere with knowledge of the rest of the world, but most of it is simply the decision by corporations to jump into new software with both feet, then run out and hire lots of young, cheap labor to maintain it. These kids can all do wonderful things normalizing data and sending streams around the world, but most of them do not know how to find their own home town on a map of the U.S.
In a little bit of their defense, I will point out that I was trying to help a couple of them set up a customer DB for a company with a lot of foreign sales and it was a nightmare. We initially tried to actually map the database to the data so that future generations would have reliable information when they went gathering statistics. We wound up with a U.S. model, a Commonwealth model, and a generic model (where every field other than the name and the country were free-form text). The professional mailing companies had 35 separate models, and we knew from experience with actual customers in several of the countries that the professional models were wrong (or, at least, that those countries had multiple acceptable forms and our customers preferred models that differed from the models offered).
The other issue is that many companies are just entering the international market and they have no experience in-house to handle the new stuff. I once had to go through a database changing all the German and Austrian addresses from Strabe to Strasse. The clerk taking the hand-written addresses sent her was simply unaware of what she was reading.
I feel your pain. Immigration forms are even more fun, not to mention the various government and private databases that track the bureaucratic progress of those forms. When you figure out the postal code thing, wanna come over here and design a U.S. immigration forms package, with Lotus Notes interface, that can deal with all the wacky international address and personal name formats and isn’t also a pile of crap? My firm would be eternally grateful.
Eva Luna, Immigration Paralegal, stuck here trying to fit what seems to be a 20-part Brazilian family name into an 10-character box obviously designed by Anglo-Saxons who have never left the Midwest (and you’d think that Fedex, at least, would be used to dealing with this sort of thing!)
Maybe Yahoo issues users in Northern Ireland with .uk addresses, and those in the Irish Republic with .ie addresses? The U.S. handles things similarly from a diplomatic standpoint; I once tried to schedule a final green card appointment in London for a guy from Belfast, but who had an Irish rather than a U.K. passport. London wouldn’t take jurisdiction on the reasoning that he didn’t consider himself a U.K. citizen, by virtue of the fact that he bore an Irish passport, and the U.S. Embassy in Dublin wouldn’t take him, because in the U.S. government view he’d been born in the U.K. We finally gave up on sorting out matters of international diplomacy by sending him to Sydney; as his last foreign residence had been in Australia, that was the only post that had to accept him, exercise of discretion or no.
Feh. Try having a last name with a hyphen. Can’t count the number of freakin’ times I’ve gotten an error: “The name field may only contain letters of the English language” or something like that. Led to a freakin’ 2-hour phone call trying to get the nice folks at the ETS to correct my SAT registration. Same thing happened with the ACT.
It probably does, although as jjimm and I live in the same neighbourhood (which neither crosses nor indeed sits anywhere near the border ), it wouldn’t explain why I could get a .ie address and he couldn’t.
Having once done your job, I empathise completely.
Of course, all the above is also complicated by the fact that the U.S. views the Six Counties as part of Ireland rather than part of the U.K. for the purposes of the Diversity Visa. I’m sure the nordies have Bruce Morrison to thank for that.