I don’t know for sure about the “why” - it’s not a rule anymore if it ever really was. The current rule is
“Parents, sponsors, and the pastor are to take care that a name foreign to Christian sensibility is not given.”
And the way I heard the rule ( again , if it really was a rule) was that baptism required a saint’s name but it was just fine if the kid was named Jessica and baptized using her middle name, Anne and if you can do that , I don’t see why you couldn’t have Maggie on the birth certificate and use Margaret for the baptism. But priests and nuns and mothers like to make up their own rules and I’m sure part of the reason was so the child had a “patron saint” .
Speaking as one of the aforementioned clerks, you’re close to the point without actually hitting it. Databases such as driver’s licensing, vehicle registration, and so forth have to be usable for multiple purposes; they don’t just sit there, holding records forever. Adding things like diacritics and non-Roman characters may be easy to do on a technical level, but it would make the system a nightmare for some users. For example, multiple departments use the same driver’s licensing database, under different circumstances. The clerk at the Department of Health may be calmly sitting at a desk and may have the luxury of considering whether Maria has a diacritic in her name or whether Hagai is spelled with Roman or Hebrew letters. The police dispatcher looking for a suicidal person? Not so much. There just isn’t time to go through different iterations of what is essentially the same name.
Many state databases are also still built on the finest technology 1986 had to offer, at least some of Pennsylvania’s are. The state (any state, including PA) isn’t going to spend money to upgrade a system if it doesn’t have to, and it’s probably not going to just to support cultural norms in languages other than English. If the system ends up supporting that, it’s a bonus.
Yep, I worked for one of those government agencies that had the best technology available in 1986 - and because of that, even newer functions, like electronic case records used 1986 technology . * It was bad enough looking for Obrien vs O’Brien - and that’s assuming the person looking had the correct spelling and it wasn’t actually O’Bryan ( or Obryan). it would be way worse if there were five different “a” s that the person who originally entered the name might have used. Sure only one is correct - but I guarantee there would be mistakes.
* black screen, green text , difficult to correct mistakes- if you accidentally typed “can” instead of “can’t” you had to retype everything afterwards so we left blank spaces at the end of each line.
Thanks to both of you for the report from the trenches.
There’s also
which was an early attempt to bridge the gap between literal database lookup and what we might now call fuzzy search that can automatically find every conceivable variation of e.g. “O’Brien”.
But which of course brings its own long list of biases and blind spots to the party. And still fails when Officer Billy Jim-Bob Thornton tries to pronounce Vivek Ramaswamy or Recep Tayyip Erdoğan.
Which is why, if you want people searchable in a database, you use something like a unique identification number instead. Which we sort of had, until people decided they were security risks, and so everyone has a number that must never be used. Or rather, we decided to prioritize the banks’ ability to quickly and easily find individuals over the police and public services.
I assume you are referring to social security numbers - but they really never took the place of names. I’m old enough that my college grades were posted by my SS number on walls that anyone could see- but I’ve always had a separate number on my driver’s license ( DMV didn’t even have my SS number until Real ID became a thing ) , my health insurance, my car insurance and every other place that needed some sort of ID number. . But you can’t look me up by my driver’s license number unless you already have my license number - if you need to look up my DL number you are pretty much going to have to search the database by some name and birthdate combo.
No, I know that’s how things work now. I’m saying they COULD work by just SSN if we wanted to. If the DMV database were searchable by SSN, you could pull up all the other data with one number.
Cross-checking with another unique identifier is always a good idea, though, because it’s even easier not to notice typos in long numbers than in names.
I suppose, now that phone numbers are individual and portable, we could use those. But I have a unique name which at least I can spell, so I don’t really care how all the Ashley Smiths distinguish themselves.
We never sort of had that with SS numbers , not even when it wasn’t considered a security risk. At the exact same time my SS was my student ID number and posted on the walls of my college , the DMV didn’t even ask for my SSN.
There are some computer tables to disambiguate easily-confusable characters, with or without diacritics. As for Brian vs Bryan or Briam, a fuzzy search may take care of it, but even if everything is typed in exactly correctly, what is the government agency going to do when it is looking for John Doe, not to be confused with John Doe? It is not diacritical marks that are at the root of the problem, it seems to me.
Numbers exist; people have driver’s license numbers, cars have title numbers and license plates. But in an emergency, they’re not helpful because the person reporting the incident may not know the number, or in the case of a missing car, the number is on the registration, which is in the missing car. So search by name is usually the only thing to do.
I’m sure that’s true for your system. I was talking about a hypothetical system. The point made elsewhere about people not knowing their numbers is a good point, though.