• 0 Posts
  • 9 Comments
Joined 2 years ago
cake
Cake day: January 5th, 2024

help-circle
  • 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:

    1. C:\
    2. Users\
    3. Adam\
    4. Documents\
    5. Research\
    6. Paper.pdf

    In Hebrew you’d have: “C:\משתמשים\אדם\מסמכים\מחקר\מאמר.pdf”, which breaks down to:

    1. C:\
    2. משתמשים\
    3. אדם\
    4. מסמכים\
    5. מחקר\
    6. מאמר.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