Answer the question
In order to leave comments, you need to log in
What's wrong with Cyrillic and spaces?
An educational question.
Situation:
Windows 10. The account name consists of several words.
Adobe acrobat during installation creates a new folder in the Users folder with the first word of the account name and eventually stops the installation with an error.
I had to go into this newly created folder by the acrobat and run the executable there to complete the installation.
How to evaluate it? More than once I have seen IT people panicking at the sight of Cyrillic spaces in the names of files, folders, etc. Is there a reasonable explanation for this? Or is it just that historically, that strange things are connected with the Cyrillic alphabet and spaces, and it’s better to just stupidly refuse them?
Answer the question
In order to leave comments, you need to log in
To some extent, it can be called "historically developed." Once there were 8.3 format names and no Cyrillic and spaces. Now a lot of things are possible. But there are still programs stuck in development somewhere in the middle. Either just old ones, not updated, or minor ones, to which developers pay little attention. As in this case, it is not the acrobat himself that is buggy, but his installer.
The user cannot influence this promptly, but he needs the program here and now! Therefore, it is better to play it safe in advance and avoid such usernames and, accordingly, profile folder names.
You need to understand that arguments for the program are also passed through spaces and everything goes in one line. The search for an executable file is carried out in a very non-trivial way.
C:\Program Files (x86)\My Program\prog arg
results in checks C:\Program.com C:\Program.exe C:\Program.vbs and so on five more extensions. Then do the same for "C:\Program Files", "C:\Program Files(x86)\My". It seems to be not fatal, but there is such a thing as cmd.exe, which breaks already at C:\Program, if the full path to the application is not wrapped in quotes. And all programs that somehow use cmd.exe run into this problem.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question