It's impossible to represent that on paper. It could be misrepresented as a specific number of spaces. Depending on the position on the paper, it may also be hard to tell if the carriage return comes with the line feed. Unless you want the document to be in ASCII or EBCDIC hex, it's like writing an ambiguous math problem where the answer is different depending on how you were taught about the order of operations. Don't do this to your kid, Abcde.
Once I was tasked with doing QA testing for an app which was planned to initially go live in the states of Georgia and Tenessee. One of the required fields was the user's legal name. I therefore looked up the laws on baby names in those two states.
Georgia has simple rules where a child's forename must be a sequence of the 26 regular Latin letters.
Tenessee seemed to only require that a child's name was writable under some writing system, which would imply any unicode code point is permissible.
At the time, I logged a bug that a hypothetical user born in Tenessee with a name consisting of a single emoji couldn't enter their legal name. I reckon it would also be legal to call a Tenessee baby 'John
'.
By the time the app was due to go live, we'd only reported bugs with the signup and login flows. This was misinterpreted as there only being issues with the signup and login flows, and the app launched on time. In reality, it was impossible to get past the login screen.
I have an apostrophe and it's super annoying as some companies see it as a SQL injection hack and sanitize it.
So I've received ID with Mc%20dole or they add a space in it. Or I'll get a work email with an apostrophe but I cant use it anywhere because sites have it disabled. And I've missed my flight because I changed my ticket once to add the apostrophe and the system just broke at the gate.
Worse yet many flight companies have "you will not be able to board if your ID doesn't exactly reflect your details" but their form doesn't allow it. Even most forms for card payments don't allow it even though it's the name on my card.
Same shit with American custom forms. On the one hand, they threaten you with Armageddon if you fill out the form incorrectly, on the other hand, they only allow plain letters, numbers, and a handful of special characters. Nobody there has the capacity of the mind that maybe a name cannot be correctly represented with that tiny subset of characters. So it is simply impossible to fill out that form without breaking the law. And it is a customs form, so they should know that people filling it out are most likely foreigners.
I have an apostrophe and it’s super annoying as some companies see it as a SQL injection hack and sanitize it.
My surname contains a character that's only present in the Polish alphabet. Writing my full name as is broke lots of systems, encoding, printed paperwork and even British naturalisation application on Home Office website. My surname was part of my username back at uni, and everytime I tried to login on Windows, it would crash underlying LDAP server, logging everyone in the classroom out and forcing ICT to restart the server.
everytime I tried to login on Windows, it would crash underlying LDAP server, logging everyone in the classroom out and forcing ICT to restart the server.
Now that's the way to do it! Make it everybody's problem, not just yours.
Been there, seen that, had to deal with it. Now add the problem that there are people who don't know their birth date or not even the f-ing year they were born in. And I'm not talking about someone from a lost tribe at the Amazonas.
I had to convince people to let me on board a plane because my name contain a swedish letter (å). Their computer system translated it into "aa", which then didn't match my passport.
some companies see it as a SQL injection hack and sanitize it.
Which kind of apostrophe?
A straight apostrophe, fine - that can and does get used in valid SQL injection attacks. I would be disgusted at any input form that didn’t sanitize that.
But a curly apostrophe? Nothing should be filtering a curly apostrophe, as it has no function or use within SQL. So if you learn how to bring that up in alt codes (Windows, specifically), Key combos (Mac) or dead keys (Linux), as well as direct Unicode codes for most any Win/Mac/*Nix platform, you should be golden.
Unless the developer of that input form was a complete moron and made extra-tight validation.
Plus, knowing the inputs for a lot of extended UTF-8 characters not found on a normal keyboard is also a wee bit of a typing superpower.
... why are you putting an apostrophe in McDole? The O-apostrophe in Irish names is an anglicisation of Ó, eg. Ó Briain becomes O'Brien. Mac Dól would become MacDole/McDole.
Prank or not, Tartaro was playing with fire by going with NULL in the first place. “He had it coming,” says Christopher Null, a journalist who has written previously for WIRED about the challenges his last name presents. “All you ever get is errors and crashes and headaches.”
I just realized that the shitty software on the other side of the divide is casting null to ”null", which absolutely explains that issue. What a cluster
asking questions like this is how i found out that one of the allowed characters in names in my country is ÿ, which is fine in Latin-1 but in 7-bit ASCII is DEL.
Ah, but you see, "John" and "Doe" are two names - first and last - and when you say "My name is", you're really listing out your names, with spaces inbetween!
But then there's hyphenated names, and I have no idea how those are treated.
No, they didn't even use the space to separate words. Take a look at any Roman inscription in Italy, there are no spaces between the words (just like there are no silent pauses between spoken words).
There are a frightening number of systems that don't allow "-", which isn't even an edge case. A lot of people - mostly women - hyphenate their last names on marriage, rather than throw their old name away. My wife did. She legally changed her name when she came of age, and when we met and married years later she said, "I paid for money for my name; I'm not letting it go." (Note: I wasn't pressuring her to take my name.) So she hyphenated it, and has come to regret the decision. She says she should have switched, or not, but the hyphen causes problems everywhere. It's not a legal character in a lot of systems, including some government systems.
There are also fringe externalities from this too. I have my mom's last name for my middle name and my dad's for my last name. But back in the 90s, my state would erroneously handle that scenario as having no middle name and both names hyphenated for a last name. I didn't find this out until I turned 18 and tried to get a retail job and they wouldn't hire me until it got fixed.
First I had to go to the Dept of Health and get a new birth certificate, then I had to do the same at the social security administration for a new social security card. Hours and hours over multiple days just so I could earn minimum wage folding and selling used clothing. Ironically, the name mixup never was a problem when I did taxes previously.
And you'd think a simple solution is just leave out the hyphen when you put you name in, but that can also lead to problems when the system is looking for a 100% perfect match.
And good luck if they need to scan the barcode on your ID.
Then the first part is interpreted (in the US, anyway) as a middle name, not as part of the last name. I did run into a recently married woman who did that: dropped her middle name, moved her last to the middle, and used her spouse's last name.
More commonly, places that don't take hyphens tend to just run the two names together: Axel-Smith becomes AxelSmith.
I have come across a shockingly large amount of people who not only have a hyphenated last name but also have a hypenated first name! Dealing with every new computer system is like a new adventure
Nah, it will end up simply as "John" in the database. You need "John%sDoe" to crash C software with unsafe printf() calls, and even then it's better to use several "%s"
so John\r Doe ? depending on the software, when it gets printed, the carriage return will move the cursor to the start of the line without moving a line down, becoming \x20Doe.
Na, names are about pronunciation (how you call someone). Written letters are an approximation of that. You can't pronounce a newline, so there's that.
But something has to be written on the birth certificate and social security card, and that's what everything else will expect you to use. I think just due to technical limitations (e.g. of the printer/template for those things) it wouldn't be allowed, but I dunno about legally
\n already is an escape sequence, consisting of \, the escape character, and n, the code that is responsible for the new line. Together they form an escape sequence.
A line break is a non-printable character. So it would only work in the scope of electronic storage. The minute it hits other media, the line break character is subject to how that media handles it’s presence, and then it is lost permanently from that step forward.
Plus, many input forms make use of validation that will just trim anything that isn’t a character or number, removing the line break character.
As someone with a very mildly unusual name, I can tell you that it doesn't matter whether a system could or could not meaningfully represent the name. Often the people or systems just refuse to acknowledge any deviation from what's expected. Sometimes databases are written to enforce arbitrary grammatical rules that make my name impossible to write, or the people using the systems will just "correct" the "error" without telling me. I don't mind that much but our normative systems just love to homogenise us.
I really can't even begin to properly explain this because it's just so many layers of intuition. No, you absolutely cannot have a line break in your name. That's not a letter. That said, I'm fully prepared for someone to give me an example of some writing system that uses line breaks for unique purposes apart from spaces.