Re: Why do webforms often refuse non-ASCII characters?

Henri Sivonen via Unicode <[email protected]>
Newsgroups gmane.text.unicode.general
Message-ID <CAJHk+8QnNzkTFbLS7x-d0cJ__0f4mpPVUYCdEC5V-NOy5pxY5Q@mail.gmail.com>
On Wed, Jan 29, 2025 at 5:58 PM Jens Maurer via Unicode <
[email protected]> wrote:

> For the airline industry, names seem to be all-caps ASCII, and
> I wouldn't be surprised if there are some IATA or ICAO rules that
> require exactly that.


See https://www.icao.int/publications/documents/9303_p3_cons_en.pdf from
PDF page 32 / in-document page number 24 onwards.

FWIW, it's worse than what the spec says: Even though the spec allows A for
Ä and O for Ö, Finnish passports do the German-style AE and OE even though
it doesn't really match the preferences of either Finnish-language or
Swedish-language name holders. I imagine that changing what Finland does
for passports could be messy as people's ICAO names would change.

-- 
Henri Sivonen
[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.