More things I'm begging people to do, this time with no apologies:
If you have any influence or control at all over the people who run a database with people's names, please please please do whatever you can to make sure they accept hyphens and apostrophes. This is 2022! You don't need to be so stingy with what are, in fact, pretty common aspects of a lot of people's names!
My sister should not have spent half this day arguing with the hospital over whether or not the name Anne-Marie properly contains a fucking hyphen.
My sister should not have spent half this day arguing with the hospital over whether or not the name Anne-Marie properly contains a fucking hyphen.
no subject
My partner has a middle name. We recently flew with Delta and her name appeared as Firstnamemiddlename Lastname on her boarding pass. I was a bit stunned... This is not a minor company.
no subject
no subject
no subject
no subject
no subject
The apostrophes can be a hassle, because so many platforms read them as an open-quote, then cough up a hairball when they can’t find a corresponding close-quote.
But there are a lot of O’Brians out there, as well as plenty of other names I’m not so familiar with, that include non-alphabetic characters. So we find workarounds.
no subject
I recommend that anybody in the market for a platform to handle a new database carefully avoid anything that can't handle fucking apostrophes in names without screaming in agony.
no subject
no subject
Obligatory xkcd
https://www.explainxkcd.com/wiki/index.php/327:_Exploits_of_a_Mom
Re: Obligatory xkcd
Re: Obligatory xkcd
no subject
no subject
no subject
Some of those databases were Irish, including businesses and I think some official paperwork/institutions.
no subject
My wife currently has the awkwardness of being named (genericized (-:) P Q R S which her passport clearly says has P Q as first name and R as middle name. No hyphen so everybody in Britain seems to assume it's P first name, Q R middle names, despite efforts to explain otherwise.
In Boston I had the job of working on a webapp that handled hospital patient databases that could handle French and German customers and such, we had all this stuff solved at least a decade ago. There's really no excuse.
no subject
(I did of course seriously consider not changing my name at all, and in retrospect sometimes wish I hadn't, but it has been very convenient to have one family name.)
no subject
unfortunately, ACME's database apparently cannot handle hyphens. and we serve *lots* of people with double-barreled last names. it's a big commercial DB in the field, and I've no idea just what the programming problem is, we were just warned years ago not to include hyphens. so we're supposed to enter last names separately (I do usually include hyphens in first names, and so far things have not blown up). and I include the apostrophes, as we also serve a population which tends to use those lots
no subject
no subject
And because of the issue YOU just noted, not all offices put the double name in properly, and sometimes the first half gets put in as a MIDDLE name.
(I'm pretty fond of 'tell me the date of birth and WHAT DAY it was sent to us' just to get a narrower field when last name is breaking the system because the system is stupid)
no subject
no subject
no subject
no subject
no subject
This is very stupid, and my sister is very unhappy about it, but we generally agreed that my mother had enough issues with perceived rejection without us stranding her body in the morgue over this.
no subject
no subject