@marczellm said in Big list of software that cannot handle spaces or accents in paths:
XAMPP is a particulary bad offender. First of all it does ask for UAC permission. Then you get this:
Then this:
Then if I install to 'D:\Program Files (x86) - because it did warn about C:\Program Files (x86) not being OK - it starts installing fine, then you get this right before the end:
Quoting the official website:
The XAMPP open source package has been set up to be incredibly easy to install and to use.
Quoting https://community.apachefriends.org/f/viewtopic.php?f=16&t=75766]
It is not planned to support that on XAMPP.
Same thread:
These single components are programmed primarily on and for *nix based systems and because of that are sometimes only able to work on *nix friendly path names.
*nix is far more permissive than Windows. Any valid Windows path is a valid *nix path (at least on the most common variety: linux).
marczellm wrote:
But at least sensible error messages should indicate these problems to the user!
No. Its a question of your personal knowledge that (especially) servers do not accept all characters in file names. It is very well known that specials characters are not supported. Apache is designed to run on different OS and different file systems, its an sophisticated Administrators task to install and configure a webserver. It is not designed for everybody.
See, this kind of shit is why @blakeyrat hates open source projects. It's also why it's hard to disagree with him a lot of the time. This is wrong, wrong-headed, and talking down to the user for making an eminently reasonable request. Good job, Altrea and Nobbie.