Re:EBCDIC Is Incompatible with GDPR
by deadbeeves on Wednesday October 25, 2023 @08:00AM
(#38011868)
It seems odd to me to arbitrarily restrict the alphabet if the only requirement is that the data has to be readable by a machine through an OCR system. They could have easily used the Latin alphabet to encode arbitrary bit strings.
[ Parent
| on HN ]
Re:EBCDIC Is Incompatible with GDPR
by imtringued on Wednesday October 25, 2023 @11:33AM
(#38013897)
How do you pronounce 64656164626565766573?
Re:EBCDIC Is Incompatible with GDPR
by deadbeeves on Wednesday October 25, 2023 @12:02PM
(#38014189)
You don't? It's machine-readable.
> alphabet if the only requirement is that the data has to be readable by a machine
its the only requirement because
1. it's only meant for OCR
2. it's clear that it won't be used by only OCR but at least also human interacting with the system, potentially phone calls passing this information by voice, and anyone who can't pronounce the original spelling. For fairness if you e.g. didn't sing at all in your life are somewhat tone deaf and now are expected to pronounce a asian you probably have to spend days or more until you can do so (just as a extreme example).