Re:The surprisingly subtle ways Microsoft Word has changed h...
by mcpackieh on Sunday November 05, 2023 @10:10AM
(#38151767)
I also know Americans who go by their middle names because everybody in the family has the same first name, with the first name turned into an initial before their middle name. Usually software can handle this by entering "J Bob" in the first name field, but not always. Sometimes software asks for first name and middle name separately, and then you know you're going to have trouble because another system thinks "J Bob" is your first name and the two won't match.
I think a single field for the entire name would be ideal, with an optional second field for "how should we address you?" so that the software doesn't have to play games with asking gender and breaking out the last name to fill out a form letter with "Dear Mr. Smith, ..."
Re:The surprisingly subtle ways Microsoft Word has changed h...
by cratermoon on Sunday November 05, 2023 @11:43AM
(#38152761)
Names are not strings. Until software developers get that through their heads, the situation is going to stay broken.
I consulted on a project for a US-based airline. The horror show that is Sabre infests everything, and Sabre doesn't understand any character that didn't exist in six-bit BCD
Re:The surprisingly subtle ways Microsoft Word has changed h...
by esafak on Sunday November 05, 2023 @12:11PM
(#38153098)
> Names are not strings.
So what are they?
Re:The surprisingly subtle ways Microsoft Word has changed h...
by cratermoon on Sunday November 05, 2023 @12:15PM
(#38153154)
Strings are a primitive type. Names are not strings in the same way Dates are not strings. They can be implemented, represented, and printed as strings, but they have behaviors and meaning that the primitive string type does not.
To use another example, a binary tree is not an array, although it can be implemented using an array.
Money is not a floating point value, and woe to the programmer that tries to use float for money.
Re:The surprisingly subtle ways Microsoft Word has changed h...
by mcpackieh on Sunday November 05, 2023 @01:50PM
(#38154271)
There are international standards for representing dates, but none exist for names. Names do not abide by any scheme or set of rules, therefore the only appropriate data structure for storing names is a unicode string. Anything else will exclude people.
Re:The surprisingly subtle ways Microsoft Word has changed h...
by cratermoon on Sunday November 05, 2023 @04:37PM
(#38155905)
Point me to the international standards for representing money.
Re:The surprisingly subtle ways Microsoft Word has changed h...
by Shadowmist on Monday November 06, 2023 @01:14AM
(#38159442)
ISO 4217
Re:The surprisingly subtle ways Microsoft Word has changed h...
by cratermoon on Monday November 06, 2023 @01:06PM
(#38166212)
TIL
Re:The surprisingly subtle ways Microsoft Word has changed h...
by esafak on Sunday November 05, 2023 @07:31PM
(#38157335)
Without making assumptions about the origin of the name, you can't impute any structure onto that string, can you? In that case, it is still simply a string.
Re:The surprisingly subtle ways Microsoft Word has changed h...
by cratermoon on Thursday November 09, 2023 @05:08PM
(#38212064)
> making assumptions
We have i18n to give context, no assumptions needed.
Re:The surprisingly subtle ways Microsoft Word has changed h...
by TRiG_Ireland on Sunday November 05, 2023 @06:14PM
(#38156740)
The main problem with the single field idea is alphabetisation.
Poor old John Smith Ⅳ (pronounced “John Smith the Fourth”) probably gets turned into the initials “JI” (because let’s be real, he actually wrote “IV” rather than “Ⅳ”).