[centur]

This hits so very close to home for me. I'd rather prefer that certain things stays in ASCII, despite my name and surname are not originally written in English.

This problem is too well-known to everyone who have their original docs written in non-English alphabet (read - everyone with diacritics or cyrillic script or hebrew or heaps of other non-Latin-based writing systems).

To add insult to injury - this is not even about some common transliteration tables from non-Latin to Latin script. Sometimes? rules of transliteration are changed based on local govt whims and if you got caught in such bureaucracy - all hell let loose. You can't obtain a document with previous "latin spelling", because it's changed in a system. This way you may have a ticket with one spelling and passport with another. Or, like in my case, my brother and I have different surname transliterations to English. And my first name would be spelled with 4 different letters than it's in all my other documents if I have to issue a document from scratch. Good luck explaining all this nonsense to anyone, who is trying to "character-match" someone's hard-to-pronounce surname from official document. Even worse when they would try to re-type any of UTF-8 characters without knowing a correct character codes or not having corresponding layout installed (most of the time in international airports and customs).

So, I'm personally fine with something is incompatible with GDPR, as long as certain systems would stay ASCII as long as they can. We'll be opening a whole new can of worms if internationally used documents would be in UTF-8, imo.