Thomas Frauendorfer wrote:
The main reason why we need to mess with encoding strings is that
paths on disk doesn't have a specified encoding. File paths are
>just arrays of bytes (where NUL and / have a special meaning). On
the other hand strings stored in sqlite (and now xmmsv_t) needs to
be UTF-8.
Then why not require that clients send the urls as UTF-8?
How do you send an URL pointing to a filename on disc that isn't valid
UTF-8?
Example:
ln /path/to/some.mp3 $'\xff.mp3' # Not ln -s as xmms2 is too smart
The example may seem theoretic but it happens in practice when mounting
stuff from other compters and stuff using different default encoding.
anders
--
_______________________________________________
Xmms2-devel mailing list
Xmms2-devel@lists.xmms.se
http://lists.xmms.se/cgi-bin/mailman/listinfo/xmms2-devel
