News for hackers. Stuff that matters.
Re:A popular but wrong way to convert a string to uppercase ... by sebstefan on Tuesday October 08, 2024 @06:01AM (#41775511)
Yes please, keep making software that mangles my actual last name at every step of the way. 99% of the world loves it when you only care about the USA.
Re:A popular but wrong way to convert a string to uppercase ... by Muromec on Tuesday October 08, 2024 @06:13AM (#41775607)
If it needs to uppercase names it probably interfaces with something forsaken like Sabre/Amadeus that only understands ASCII anyway.

The real problem is accepting non-ASCII input from user where you later assume it's ASCII-only and safe to bitfuck around.

Re:A popular but wrong way to convert a string to uppercase ... by InfamousRece on Tuesday October 08, 2024 @08:13AM (#41776465)
Some systems are still using EBCDIC.
Re:A popular but wrong way to convert a string to uppercase ... by sebstefan on Tuesday October 08, 2024 @07:06AM (#41776002)
From experience anything banking adjacent will usually fuck it up as well

For some reason they have a hard-on for putting last names in capital letters and any other treatment just won't fly.

Re:A popular but wrong way to convert a string to uppercase ... by Muromec on Tuesday October 08, 2024 @09:52AM (#41777384)
If it uses ASCII anyway, what's the problem then? Don't accept non-ASCII user input.
Re:A popular but wrong way to convert a string to uppercase ... by sebstefan on Tuesday October 08, 2024 @10:01AM (#41777484)
First off: And exclude 70% of the world?

Usually they'll accept it, but some parts of the backend are still running code from the 60's.

So you get your name rendered properly on the web interface, and most core features, but one day you're wandering off from the beaten path, by, like, requesting some insurance contract, and you'll see your name at the top with some characters mangled, depending on what your name's like. Mine is just accented latin characters so it usually drops the accents ; not sure how it would work if your name was in an entirely different alphabet

Re:A popular but wrong way to convert a string to uppercase ... by Muromec on Tuesday October 08, 2024 @04:16PM (#41781414)
>First off: And exclude 70% of the world?

Guess what, I'm part of this 70% and I also work in a bank and I know exactly how.

Not a single letter in my name (any of them) can be represented with ASCII. When it is represented in UTF-8, most of the people who have to see it can't read it anyway.

So my identity document issued by the country which doesn't use Latin alphabet includes ASCII-representation of my name in addition to canonical form in Ukrainian Cyrillic. That ASCII-rendering is happily accepted by all kinds of systems that only speak ASCII.

People still can't pronounce it and it got misspelled like yesterday when dictated over the phone.

Now regarding the accents, it's illegal to not support them per GDPR (as per case law, discussed here few years ago).

Re:A popular but wrong way to convert a string to uppercase ... by numpad0 on Tuesday October 08, 2024 @08:19PM (#41783224)
Why can't these people understand that that 70% of the world consider ASCII to be "the computer language", not English, and UTF-8 to be "whatever soup that only works inside files and forms and can't be program manipulated"?

Maybe it needs to be communicated more often, like way more often, until it sticks.

Re:A popular but wrong way to convert a string to uppercase ... by Muromec on Wednesday October 09, 2024 @01:36PM (#41790523)
Well, it's much easier to understand the difference when one and another are using different alphabets.
Re:A popular but wrong way to convert a string to uppercase ... by account42 on Wednesday October 09, 2024 @10:46AM (#41788462)
You are not being excluded just because you need to use a romanized version of your name. Clear example of a first world problem.
Re:A popular but wrong way to convert a string to uppercase ... by sebstefan on Thursday October 10, 2024 @07:04AM (#41797616)
>first world problem

? The more first world you are the more your alphabet is taken into consideration

Hint: You use the word """romanized"""

Re:A popular but wrong way to convert a string to uppercase ... by MajimasEyepatch on Tuesday October 08, 2024 @07:31PM (#41782911)
It’s totally reasonable to assume your users are in the US if your business only sells to people in the US. I work in the health insurance sector; there’s absolutely no chance my company ever sells these products internationally. We can’t even sell them in every state.
Re:A popular but wrong way to convert a string to uppercase ... by davidcbc on Tuesday October 08, 2024 @07:47PM (#41783011)
It's not reasonable to assume that users in the US have names that only use 7-bit ASCII
Re:A popular but wrong way to convert a string to uppercase ... by bigstrat2003 on Tuesday October 08, 2024 @11:13PM (#41784154)
It actually is. That covers the vast, vast majority of people in the US.
Re:A popular but wrong way to convert a string to uppercase ... by saagarjha on Monday October 14, 2024 @04:50AM (#41835557)
That is not very reasonable, is it?
Re:A popular but wrong way to convert a string to uppercase ... by MajimasEyepatch on Tuesday October 15, 2024 @12:04PM (#41849991)
It is if all your customers are in the US.
Re:A popular but wrong way to convert a string to uppercase ... by account42 on Wednesday October 09, 2024 @10:51AM (#41788518)
It's reasonable to assume that all users can deal with having to encode their names in 7-bit ASCII. Otherwise you might as well demand that computer systems need to support arbitrary drawings in the name field at which point you might as well not have a name field at all because even most humans won't be able to deal with what you want to put in there.
Re:A popular but wrong way to convert a string to uppercase ... by davidcbc on Wednesday October 09, 2024 @06:58PM (#41793705)
Nice slippery slope you've got there
Re:A popular but wrong way to convert a string to uppercase ... by account42 on Wednesday October 09, 2024 @10:44AM (#41788450)
Cool, I will.