Why not use Unicode's "Private use characters" to display reserved characters in file paths.
Regular fonts would be used, but Windows could replace certain Unicode characters without glyphs and display them with the glyphs of reversed characters, like the question mark (?).
Otherwise, will Windows ever change it's file system to allow these characters?
Seems kind of an outdated limitation. I know why it exists in the first place but won't there EVER be quotes or question marks under Windows?
It's there a better solution, present or future?
Welcome to MSFN ForumRegister now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account
Reserved Characters in File Paths
Posted 19 September 2010 - 05:49 PM
Posted 20 September 2010 - 09:21 AM
Some of them are able to be used if you use the ASCII code. There was one code that did get updated when XP came out, and that was the Delete code is now "ignored" by Windows. In Windows 98, if you put the Delete code in a file or folder name, you couldn't open or delete the file from Explorer, only could do things in the command prompt. I am guessing the reason why they still don't let you use those reserved characters is because Windows is still based on the command interpreter, which isn't smart enough to know anything about fonts.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users