Details
-
Bug
-
Resolution: Unresolved
-
P4: Low
-
None
-
6.6.1
-
None
Description
qprocess_unix.cpp applies QFile::encodeName on every argument.
This can change the encoding of Unicode strings containing precomposed characters (e.g. "ö", "ü", ...).
Depending on the binary invoked that can cause unexpected results.
In my use case ldapsearch or rather the ldap server it queries won't match a filter containing such characters. Invoking ldapsearch via shell works as expected (the shell does not mess around with the arguments).
I can understand why the binary path is handled this way. But why is this done for the arguments as well?