News for hackers. Stuff that matters.
Re:EBCDIC Is Incompatible with GDPR by HPsquared on Wednesday October 25, 2023 @05:25AM (#38010910)
The good thing with ASCII is that everyone, everywhere can type it in using a standard keyboard. Everyone can read, write, speak and hear the basic Latin alphabet.

Not even an English/US thing, this is the Latin script from Roman times.

Re:EBCDIC Is Incompatible with GDPR by SiempreViernes on Wednesday October 25, 2023 @05:41AM (#38011017)
Funny! But you should put the /s in there to indicate it is satire :)
Re:EBCDIC Is Incompatible with GDPR by HPsquared on Wednesday October 25, 2023 @05:52AM (#38011076)
It's funny because it's true.

Edit: what do you suggest as a universal alternative for bit-perfect verbal communication... Spelling out Base64 Unicode over the phone?

Re:EBCDIC Is Incompatible with GDPR by epcoa on Wednesday October 25, 2023 @06:18AM (#38011243)
> speak and hear the basic Latin alphabet.

The Latin alphabet does not have a single pronunciation. And the vowels are ambiguous across the most common languages so you can't even make an argument that they are intelligible.

You've really lost the plot on this one.

Re:EBCDIC Is Incompatible with GDPR by HPsquared on Wednesday October 25, 2023 @06:30AM (#38011297)
I'm only assuming the two people speaking on the phone share a common language, I think that's a fair assumption.
Re:EBCDIC Is Incompatible with GDPR by inkyoto on Wednesday October 25, 2023 @06:59AM (#38011473)
I instantly conjure up an image of a Roman citizen, a retired soldier now, speaking Vulgar Latin picking up the phone and dialling Comitia Centuriata to lodge a complaint about a unpaid engagement in Punic Wars.

The clerk answers in and speaks Classical Latin.

Re:EBCDIC Is Incompatible with GDPR by mkup on Wednesday October 25, 2023 @05:43AM (#38011028)
Just nitpicking: Latin script from Roman times lacked W and U, among other things.
Re:EBCDIC Is Incompatible with GDPR by cedilla on Wednesday October 25, 2023 @06:14AM (#38011211)
Also lower case and most typography, including spaces.
Re:EBCDIC Is Incompatible with GDPR by latexr on Wednesday October 25, 2023 @05:48AM (#38011055)
> Everyone can read, write, speak and hear the basic Latin alphabet.

Not everyone in countries which use the Latin alphabet can read or write it (called analphabets or illiterate). And there isn’t a single way to speak it, either, pronunciation depends on the language. So I’m not sure I buy there aren’t people who can read and write only in a non-Latin alphabet.

I have no clue what you mean when you say everyone can hear the Latin alphabet. Listening to sounds has no relation to the language spoken. I can hear Korean just fine, doesn’t mean I understand the meaning of the words or understand their alphabet.

> Not even an English/US thing

Even languages who use the Latin alphabet have diacritics and characters not present in ASCII.

Re:EBCDIC Is Incompatible with GDPR by kps on Wednesday October 25, 2023 @11:08AM (#38013633)
Blame Jean-Maurice-Émile Baudot for not including diacritics in his teleprinter code. Dude couldn't even send his own name.
Re:EBCDIC Is Incompatible with GDPR by cedilla on Wednesday October 25, 2023 @06:12AM (#38011200)
I assure that billions of users can't. Even if they have ASCII letters printed on their key board, which is not a given, they will be unable to find that 'f' anywhere, just like you won't find most lower case Cyrillic letters on a Russian keyboard.

And even if they know how to type in all 52 letters, it's absolutely not a given that they are able to transliterate from their native script to the English alphabet.

"Everyone, everywhere" does not have a "Latin" alphabet as the basis.

Re:EBCDIC Is Incompatible with GDPR by Asooka on Wednesday October 25, 2023 @06:24AM (#38011265)
Where do you find these computers with keyboards that do not have the full set of ASCII letters printed on them? ASCII and Latin script are the lingua franca, they're not hard to learn and it's not unreasonable to ask that everyone who wants to use computers learn them.
Re:EBCDIC Is Incompatible with GDPR by gdprrrr on Wednesday October 25, 2023 @09:44AM (#38012702)
Most Keyboards only have uppercase printed on them
Re:EBCDIC Is Incompatible with GDPR by account42 on Wednesday October 25, 2023 @07:20AM (#38011600)
You really underestimate how widespread use of Latin script is, especially in computers. People cope just fine with domain names (IDN is generally still rare), foreign brands, names of famous people etc. Sure your central chinese rice farmer living in a remote village might only be exposed to chinese script but once to get to someone familiar with a computer they likely will be able to cope with ASCII text just fine even if they don't understand the meaning.
Re:EBCDIC Is Incompatible with GDPR by b3orn on Wednesday October 25, 2023 @07:41AM (#38011734)
Not sure if this is still the case or only some legacy stuff, but at least for a while chinese websites used numbers instead of names, China Railway for example uses 12306.cn as their domain name.
Re:EBCDIC Is Incompatible with GDPR by marcus_holmes on Wednesday October 25, 2023 @06:24AM (#38011269)
You do know that the "standard" keyboard you're referring to is specifically the US keyboard?

It's not even standard for English: there's a UK keyboard that is organised differently and has different characters.

Re:EBCDIC Is Incompatible with GDPR by HPsquared on Wednesday October 25, 2023 @06:33AM (#38011314)
OK, we can do away with the currency symbols and brackets, and limit it to Base64. Little Bobby Tables, and perhaps a few musical artists, may need to find an alternate spelling.
Re:EBCDIC Is Incompatible with GDPR by latexr on Wednesday October 25, 2023 @07:30AM (#38011669)
You seriously underestimate how common it is for European first names to have diacritics.
Re:EBCDIC Is Incompatible with GDPR by msm_ on Wednesday October 25, 2023 @08:40AM (#38012145)
That's the most Ameri-centric thing I've read all day. I assure you that:

- There is no such thing as a "standard keyboard"

- Not everyone can type Latin alphabet

- Almost nobody can read, speak, hear or write latin, and it makes no sense to "hear latin alphabet". How do you pronounce "Bordeaux" using only your knowledge of the Latin alphabet? How do you pronounce "Queue" using only your knowledge of the Latin alphabet? You realise native speakers of various languages will pronounce words (for example "pain") and even letters (for example "w", "j", "y") very differently? Etc.

- Not every country is related to the Roman culture.

Re:EBCDIC Is Incompatible with GDPR by HPsquared on Wednesday October 25, 2023 @09:16AM (#38012452)
Anyone can listen and understand when a person spells "Q U E U E", even if they don't speak English, so long as they share a common (spoken) language. Not so with "列"
Re:EBCDIC Is Incompatible with GDPR by marcus_holmes on Wednesday October 25, 2023 @10:29AM (#38013196)
Wait, so anyone can understand written English even if they don't speak English? So if I type in German you can understand it even if you don't speak German? Wie funktioniert das?
Re:EBCDIC Is Incompatible with GDPR by HPsquared on Wednesday October 25, 2023 @12:30PM (#38014568)
People can spell out words in a language they don't understand, as long as they understand the letters. This is good for names. People can only do this if they understand the letters.
Re:EBCDIC Is Incompatible with GDPR by marcus_holmes on Wednesday October 25, 2023 @08:36PM (#38020201)
How do you pronounce "Mebd"? Can you work out how to pronounce that name from how it's spelled? Or "Siobhan"?

Your statement isn't even remotely true.

Re:EBCDIC Is Incompatible with GDPR by shiroiuma on Thursday October 26, 2023 @02:34AM (#38022413)
They don't have to pronounce those: they can just spell out the letters: M-E-B-D. It's not that hard. But if the customer's name is "坂本", how exactly is the bank employee supposed to say that?