|
|
|
|
|
by kjetijor
897 days ago
|
|
I'll add another airline story. SAS, the Scandinavian flag carrier - which you'd think would have Scandinavian characters down. I've had an account with them since, well, they got a web presence. My last name contains an ø - for which; technically at least Norway accepts both o and oe as valid transliterations. Order a ticket online, they pick the transliteration for ø as o, passports transliterate ø to oe - the less ambiguous choice. This generally isn't a problem until you want to travel to one of the APIS countries - USA or UK, which won't let you check in if the name on your passport doesn't match the name on the ticket. I have tormented many check-in counter staff with this, especially at regional airports that don't see a lot of international travel. |
|
We had to do it because the underlying backend is Spanish and the APIs are insane. Behind our JSON-wrapper is an adapter to translates it into teletype friendly format … spaces, new lines and tabs makes it look like a ticket you’d get from a travel agency in the 1970s.
This format is also the reason why your name is truncated on your ticket (or so I was told). IT in the airline industry is insane and many systems are many decades old at this point.
A bit surprised you have trouble with APIS though.