Yeah, that is pretty much how it works in some GUIs like in the screenshot, where each slash is replaced by >. But if you represent the path in a string, and put that string in some context that doesn't know it's a path and that it should be rendered by some special rules, then it'll just be subject to the usual Unicode Bidirectional Algorithm (UBA).
The UBA is a masterpiece, and I'm not being sarcastic. For everyday text with mixed directionality, such as a WhatsApp chat in Arabic/Hebrew with a bit of English or just some numbers mixed in, the UBA's default output is the ideal way to order the characters.
The problem is, special cases (such as file paths) just can't be covered by a universal algorithm. You can insert special characters into the path, namely FSI and PDI ("First Strong directional Isolate" and "Pop Directional Isolate") to make the text render the way you want under the UBA... But then, when you copy that path, the special characters would still be there so software would consider them part of the path, and then of course, File Not Found.
You complain about ASCII filenames but a few of the examples are obviously Unicode, namely using emoji, well outside of the ASCII character set. But since you've brought up Unicode file names, let me introduce you to bidirectional text!
If you use Hebrew or Arabic, some of your directories or files will have right-to-left text in them. This is a recipe for disaster.
If in English you'd have "C:\Users\Adam\Documents\Research\Paper.pdf", which breaks down to:
C:\
Users\
Adam\
Documents\
Research\
Paper.pdf
In Hebrew you'd have: "C:\משתמשים\אדם\מסמכים\מחקר\מאמר.pdf", which breaks down to:
C:\
משתמשים\
אדם\
מסמכים\
מחקר\
מאמר.pdf
The entire path goes backwards, and the ".pdf" extension is visually attached to the "Users" folder if the text is rendered naively. It's insane. Fortunately many GUI shells nowadays separate each path item so they can't get intermixed like this. Example:
But still, if you copy a path into plaintext, it will still visually look wrong, and there is literally nothing that anyone can do about it. This is the correct way to render this text.
Exact same issues occur in Arabic and the few other RTL languages usedin the world. It's a massive pain.
Edit: oh, and on commandline on Windows, the required characters aren't even available by default so you get this lovely thing
Does this break games? Where in the input pipeline is the long press converted to shift? Being in the firmware implies that it's in the keyboard itself, so even games wouldn't be able to see that you're just holding W to go forwards.
Or perhaps, hear me out here, we could dedicate an entire field of science to understanding human biology, and train many people in this subject as professionals. They will be qualified to, among other things, examine a patient and determine objectively that they are deceased with no chance of revival. They can then verbally communicate this fact, or in other words, "pronounce" that the patient is dead.
I agree with some of this but not so much with these parts:
I suggest it is time for you to grow up some.
No reason to treat OP like a child. This post is more of an "off my chest" than anything else. It sounds to me like that already accept most of what you said, but just need to process it.
if this were happening in the states it would be totally acceptable if she were 365 days older.
Would it? I'm not American. Would it be socially and ethically acceptable for a 40-something man to date an 18 years old girl? I'm skeptical of that. OP started their post pointing out it's not about legality.
Your father is [...] providing you safe place to have the relationships you want but you are not affording him the same.
That's not fair, for many reasons. First, I didn't get the impression that OP actively tried to sabotage the relationship, just probed at how it happened and maybe expressed that it makes them feel uncomfortable, though we don't even know that for sure. That's not the same as "not providing a safe space". For all we know, OP's dad might also be uncomfortable with a queer relationship but swallows it up - same as OP is doing.
Where I do agree with you is that OP's only remaining option is to accept that this relationship is happening. And I think OP already knew that before posting this.
Yeah, that is pretty much how it works in some GUIs like in the screenshot, where each slash is replaced by
>. But if you represent the path in a string, and put that string in some context that doesn't know it's a path and that it should be rendered by some special rules, then it'll just be subject to the usual Unicode Bidirectional Algorithm (UBA).The UBA is a masterpiece, and I'm not being sarcastic. For everyday text with mixed directionality, such as a WhatsApp chat in Arabic/Hebrew with a bit of English or just some numbers mixed in, the UBA's default output is the ideal way to order the characters.
The problem is, special cases (such as file paths) just can't be covered by a universal algorithm. You can insert special characters into the path, namely FSI and PDI ("First Strong directional Isolate" and "Pop Directional Isolate") to make the text render the way you want under the UBA... But then, when you copy that path, the special characters would still be there so software would consider them part of the path, and then of course, File Not Found.