There was an iPhone user who got locked out of his device because the pin pad Unicode changed and one of the characters he used was no longer available. I forget what language he used, I want to say Serbian but am likely misremembering that.
I’m going to hazard a guess that it might be Romanian. Romanian has the letter ș, which is an “s” with a comma beneath. Wikipedia. It wasn’t part of the Unicode standard until 3.0, so people used ş, which is an “s” with a cedilla.
I have the modern Romanian keyboard on my phone, so I can easily type ș, but not ş. I can see how that would have broken during the changeover to Unicode 3.0.
I once encrypted my disk with a passphrase that contained a mere ‘j’. I generated it on bitwarden, then pasted it. The problem was the j key wasn’t working on my keyboard and I had no way to enter the passphrase on boot. Luckily the disk was empty since this was a fresh install, so I just reinstalled it with a different passphrase. But this could have been catastrophic since I didn’t have a spare keyboard.
yeah but I panicked and it didn’t occur to me you can still plug an external keyboard on a laptop. And to be honest, I don’t think I ever thought of that before. So if there was data, I would have lost it.
As an IT guy who have sat through start up wizards on iOS thousands of times on every iPhone since the 5S, you are absolutely right, the last few iPhone models have really made the setup wizard a terrible and bloated experience.
To whoever at Apple decided that the eSIM setup should come after the Apple ID screen, go take a barefoot walk on LEGO and think about what you did!
There was an iPhone user who got locked out of his device because the pin pad Unicode changed and one of the characters he used was no longer available. I forget what language he used, I want to say Serbian but am likely misremembering that.
I’m going to hazard a guess that it might be Romanian. Romanian has the letter ș, which is an “s” with a comma beneath. Wikipedia. It wasn’t part of the Unicode standard until 3.0, so people used ş, which is an “s” with a cedilla.
I have the modern Romanian keyboard on my phone, so I can easily type ș, but not ş. I can see how that would have broken during the changeover to Unicode 3.0.
I think you are correct about it being Romanian, because I think it was an s character. I tried looking for the article so I was not going off memory.
I once encrypted my disk with a passphrase that contained a mere ‘j’. I generated it on bitwarden, then pasted it. The problem was the j key wasn’t working on my keyboard and I had no way to enter the passphrase on boot. Luckily the disk was empty since this was a fresh install, so I just reinstalled it with a different passphrase. But this could have been catastrophic since I didn’t have a spare keyboard.
Would it have been so catastrophic? lol
Could have gone to just about any big store and gotten a cheap keyboard.
yeah but I panicked and it didn’t occur to me you can still plug an external keyboard on a laptop. And to be honest, I don’t think I ever thought of that before. So if there was data, I would have lost it.
I have to assume it’s the cyrillic alphabet, surely apple isnt so stupid they manage to mess up the unicode of latin characters?
I’m just gonna stop you right there…
It’s a marketing and design company with delusions of competence with regards to most other things it does.
As an IT guy who have sat through start up wizards on iOS thousands of times on every iPhone since the 5S, you are absolutely right, the last few iPhone models have really made the setup wizard a terrible and bloated experience.
To whoever at Apple decided that the eSIM setup should come after the Apple ID screen, go take a barefoot walk on LEGO and think about what you did!