I had my share of problems, so I didn't use non-latin chars in my name as much as possible, but there was an instance that really surprised me. It was around 2

I had my share of problems, so I didn't use non-latin chars in my name as much as possible, but there was an instance that really surprised me. It was around 2010 and I joined (as a contract) company which used Google's Cloud Platform for their products. It was initial phase, but stuff was ramping up quite quickly. So, since I was contractor, and it was supposed to be short gig, access was given to my Google account, which was one of not that many places that had my full name visible (mostly for visibility and official matters). Week or two later I was to do something with CDN, or Cloud Files, don't remember the product, but it was managed through Python script. As soon as I logged in and tried to do something I got familiar error about unsupported encoding. That was weird, but as that was Python script I quickly figured out that the reason was that Google was pulling my name from their account and their script couldn't handle it. Oh well, happens, I mailed support (what a time to be alive back then!) and went toward my way not really expecting much. I received response shortly after, that in this case it wasn't possible to fix the access script. After few back and forth where I pushed against using latin chars in every Google product possibly support finished with something along the lines "well, you can just change your name in that case". Funnily enough, for company that was hiring me it was the last straw and they took their business elsewhere. I, personally, was annoyed for a long time, but today it only makes for a good anecdote. I never used any GCP products though.