Bugzilla – Bug 4136
CLI input parameter charset management
Last modified: 2014-08-13 09:48:51 UTC
Currently, the CLI performs encoding of the incoming data ONLY if the charset parameter is present in the command. This enables extended commands/queries to accept parameters in a given charset (f.e. search parameters) and "legacy" commands/queries to work as before, mainly for paths. Internally, SlimServer does not encode paths in UTF8, they remain in the native charset, so encoding paths in UTF8 does not work "down the chain". There is however no easy way to determine what a given parameter is for legacy commands. For example, playlist play xxx accepts about anything as xxx... This is logged as an enhancement request but the current logic for $request->fixEncoding() might well lead to bugs on UTF8 native systems.
fred, do you intend to fix this?
Yes, if needed and time allows. This is more a reminder than a strongly needed feature.
Fred - is this still on the todo list?
Strictly speaking yes. For non tagged commands, we have no way of knowing what the charset of the parameters are. This makes managing paths with international chars complicated. You may want to remove this "generic" bug and work on fixing its manifestations when they occur.
Closing following Fred's advice. It's been a while :-)