Why in file and folder names, some characters are still not accepted?

7

Why do not files and folders still accept a few different characters?

Ibelieveyoumusthavesomeprogrammaticinfluencetomakethatdecision.DidtheOperatingSystemshaveand/orstillhaverestrictionstobeproducedinthisway?

Aswellasdomainnamesthatoncedidnotacceptaccentanddifferentcharacters,andhavebeenworkingwiththemmorerecently.

  

AnInternationalDomainNameisadomainnamethatcancontain  charactersnotdefinedbytheASCIIstandard.Thesecharactersinclude  mostoftheaccentedlettersusedindifferentEuropeanlanguagesand  othercharactersthatarenotfoundintheLatinalphabet.(i.e.  accentués.com)

    

Technically,accentedcharacterscannotbeusedinDNS,whichiswhy  everyIDNisencodedasastringofnon-accentedcharacterwhoseshape  iscalledACE.Inthelatter,thedomainnamesbeginwithXN-to  differentiateunaccenteddomainnames.(i.e.xn--accentus-h1a.com)

(removedfrom from here )

Example:

The domain name Ω Ω Ω Ω Ω Ω Ω Ω Ω Ω Ω Ω Ω Ω Ω Ω Ω Ω ー

In this article of w3 talks about this "internationalization" of domains

  

User's expectations and use of the Internet have moved since then,   and there is now a growing need to enable use of characters from any   language in Web addresses. The Web address in your own language and   alphabet is easier to create, memorize, transcribe, interpret, guess,   and relate to. It is also important for brand recognition. This in   turn, is better for business, better for finding things, and better   for communicating. In short, better for the Web.

I think this question is more about the creation history (so it has a bit to do with programming) of the operating systems.

    
asked by anonymous 14.02.2017 / 15:19

1 answer

11

It's basically an ambiguity problem in parsing . It is a problem similar to what we have in strings in languages where some characters are special, such as the quotes themselves, the backslash and the percentage or keys, etc.

These characters have a meaning in operating system commands, in this case MS-DOS initially and then Windows. Unixes have another set of characters that can not be used.

They could have been smarter and allowed these characters inside quotes, and even it could be used with an escape . But they did not. Also not a big problem. They probably do not change because it's not a major need.

  • / - flag flag of the command
  • \ - folder separator
  • : - volume separator
  • * - wildcard to indicate any name
  • ? - wildcard to indicate any character
  • " - text delimiter (names that have space need it)
  • < - input driver
  • > - output driver
  • | - output pipe

It has nothing to do with accentuation, which is allowed.

    
14.02.2017 / 15:35