Name: Illegitimate
caterina.net
caterina.net
But I keep getting hit by this in odd ways. Like with the FB+Heroku integration - I couldn't get FB to accept that my Heroku login was valid because it was failing the 'Is this a suspicious alias' test.
If someone from FB is watching, you would save me a great deal of annoyance if you help me get around this.
This is the single most annoying thing about signing up for services. If they disallow this or the +flag chances are I won't sign up for a service.
http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b...
Someone who decides to identify themselves with Klingon (whether their parents gave them that name or not) should expect to have an alias ready...
Even if it wasn't for historical characters that aren't part of Unicode, this will probably stay that way because of the inefficiencies of encoding Asian text in e.g. UTF8.
That's part of the reason the ruby programming language didn't have proper Unicode support for a long time (and now supports arbitrary encodings for its strings, not just Unicode ones)
That's true but doesn't really answer GP's question. Shift-jis is an encoding for one of the JIS X character sets. Unicode includes all the characters defined in JIS.
http://unicode.org/faq/han_cjk.html#8
Though if we enter into details it gets a bit messy due to the complications due to different simplifications occured in (mainland) China and Japan, questions about different glyphs for the "same" character, etc.
There's a lot of code out there that works fine with one-char code points but breaks on two-char code points.
UTF-8 is inherently variable-width, but it's a flat scheme in that one universal mechanism suffices to represent everything you can represent.
UTF-16 appears fixed-width until you realize it isn't, at which point you discover it's segmented and the segmentation scheme is both somewhat complex and likely to be missed entirely in naïve testing.
What does match is the fact that you can use a huge number of combining characters [1] to form a single glyph; each combining character and the base are a code point, so in order to figure out how many glyphs there are you have to iterate with the knowledge of what code points are combining characters.
I think it's more about business process than technology limitations.
So my point is, maybe then it's better not to implicitly promise that your system has no limitations at all, but make these limitations more obvious instead. This'll help to avoid surprise errors and ensure consistent user experience by setting correct expectations.
I admit that most users today expect systems to accept their names in their language though, and that it might be an edge case depending on particular occasion, but then I can see why most payment systems apparently still accept only latin letters (cardholder's name is an example).
Actually I think the image field is a good idea, just have everyone use a typed alias and then draw/render what they want to be called. Maybe an image and/or a sound, to be more inclusive.
http://outsports.com/nfl/2005/0301nflshopnaughtywords.htm
There's actually a few in there that could turn up as names. But a lot of humor in that list. "Flogging the Dolphin" is not allowed on the back of NFL Jersey's if anyone was thinking of that. (and if Pud is viewing this thread, don't try getting your nickname on the back of a jersey)
"Our automated system will not approve this name. If you believe this is an error, please contact us.[0]"
Every product I've seen starts out pure, beautiful, etc... Then the edge cases start getting reported, and pure beautiful code very rapidly gets dragged down to earth.
You unsimplify code as needed, as exceptions crop up.
Michael Bolton: No way! Why should I change? He's the one who sucks.
Please state your name for the record:
"Bob Pi BlahBlah"
However, if you Asked the Warrior what "concordia com veritate" (the university's motto) meant, it told you not to use dirty words.
cum, not com.
I wouldn't bother except the story doesn't work if you change that vowel.
('Cum' is Latin for 'with'; "concordia cum veritate" means "In harmony with truth", which the search program was not.)
"Our automated system will not approve this name. If you believe this is an error, please contact us."
At least they let folks contact them now, I guess.
Don't bother saying "What if I check between their legs?" or anything like that, because gender and sex are two different things that are merely strongly correlated in most people.
I never said that was true in all cases. In fact, I said it was strongly correlated with gender in most cases. However, it isn't an absolute determinant, especially if you equate 'sex' with 'genitalia'.
Web sites that need to know how a person is physically constructed as opposed to socially constructed are going to be rare.
But even then, the physiology is not always always binary: "1 percent of live births exhibit some degree of sexual ambiguity.Between 0.1% and 0.2% of live births are ambiguous enough to become the subject of specialist medical attention" - http://en.wikipedia.org/wiki/Intersex#Prevalence
Look, EVERY website is built based on some assumptions. Sometimes it's that people comprehend a certain language. Sometimes it's that they're using a browser with support for images and they're not using LYNX. The general assumption of most websites is that their user hasn't changed their gender ... and while I'm sure there's some equal-rights group that would disagree with me, I think that's a fair assumption. I'd also bet that for the vast majority of sites that request gender information, that input is unlikely to ever have an impact on the user's experience on that site.
If a user has transformed their identity, then I think they've also taken on the responsibility of figuring out how that new identity will navigate the real-world. That means a woman that identifies as a man can enter "Male" in a gender drop-down if that's how they choose to self-identify, but unless they've had a surgical procedure to change their physiology, then they're still going to need to operate their body like any other woman would. If they're in a pharmacy, that means buying feminine products to maintain their body. If they're on WebMD, that may mean declaring themselves as a woman to get relevant content. If they're on a dating site, maybe it makes sense to declare themselves as a man ... much to the potential future chagrin of their date.
Nearly every complaint about crappy customer service ignores that large companies don't have much incentive to improve at the margins.
Because I can totally imagine how a lawsuit can suddenly incentivise them.
http://stackoverflow.com/questions/6163683/cycles-in-family-...
I used to naively think my name issues were limited to people being unable to spell or pronounce my names. But, no, it gets betterer.
I thought I would escape my name issues by marrying. No dice. I thought I would escape them by going by my more common middle name. It doesn't help as much as I hoped. It's like a curse.
But at least I don't own a cat.
And she can be Jr. III