Bugzilla – Bug 1895
Non-ASCII characters mangled and dropped when scanning directories
Last modified: 2008-12-15 11:57:34 UTC
This looks related (at first glance) to 1774 and 1786, but has different symptoms. When I set SlimServer's music folder to a directory containing non-ASCII characters (e.g., without the quotes, "/Volumes/Eve�s Annex/Media/music/iTMS (test)"), the web GUI accepts the value, but scanning fails. When I created symbolic links "/mtest" and "/music test", pointing to the above directory, and pointed SlimServer to those directories instead, scanning worked successfully. I turned on d_files, d_paths, d_scan; d_server was left on. The relevant log section is attached. (This has entries referring to the above symbolic links; it was generated after I changed the music directory *back* to the non-working path from "/music test".) It appears that the "special" character (the "smart apostrophe" in the second component of the path) was mangled twice: the first time was the first entry, where it has only the first character of its misinterpreted UTF-8 value; the second time, starting with the second entry and continuing from that point, it drops even that character, turning the correct "/ Volumes/Eve�s Annex/..." into "/Volumes/Eves%20Annex/...". Using Mac OS 10.4.2, iTunes *with an additional SlimServer music folder*, 6.2 nightly from 7/30/2005 (SlimServer Version: 6.2b1 - trunk - Mac OS X 10.4.2 (8C46) - EN - utf8).
Created attachment 686 [details] Log exhibiting server misbehavior when scanning directories containing non-ASCII characters.
Changing "Component" from Audio (default) to Misc. Given the workaround, this is not a top-priority bug for me.
We need to properly decode UTF8 from these fields in Settings
Ben - I've checked in a fix as subversion change 3936 to the 6.2 tree.
Thanks. I'll test this soon -- hopefully tonight, this weekend at the latest.
The bug is fixed in today's nightly (8/14/2005). I'm marking this bug "verified"; for future reference, is that correct protocol for how you folks use Bugzilla?
Yes. Thanks.
This bug has been fixed in the latest release of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.