Hi,

I submitted a new bug at support@slimdevices.com a few days ago (see below for 
the original bug report), and after a few testing and toubleshooting here is 
what I found when folder and mp3 file names contains special characters 
like "�" (e with a grave accent) for example.

First of all, all (or most of) special characters seems to be concerned. 
Moreover the bug seems to happen randomly. Here's the details :

I have a large collection of mp3 files (more than 20000 files). My collection 
is organized by CD each in its own directory in the following way : <Album 
Artist> - <Album Title>\<Track Number>. <Track Title>

I have about 1600 directory and file names that include at least one special 
character. Example : "U2 - Discoth�que\01. Discoth�que (DM Deep Club Mix).mp3".

It seems the database builing process has problem with filenames or tags when 
a special character is involved. In my case, the consequence is that, when I 
browse by artist, I found an artist called "No Artist" on an album called "No 
album" containing all the 1600 tracks with special characters in the folder or 
file name, or in the mp3 tags.

Strangely enough, the problem occurs randomly. For testing purpose, I created 
a new source directory containing a few files (about 30) with special 
characters directly copied from my collection, and... no problems. Then I 
added a few more files, and rebuild the database (clearing the cache) and the 
problems occured again on certain files.

Hope I'm clear enough. Unfortunately, I cannot send you my entire 105GB 
collection of mp3 files for testing purpose. (By the way, all files are 
perfectly legal. I have more than 2500 CD and started to rip them years ago)


For additional information, here's my original bug report (not entirely exact 
after a few testing as indicated above):
------------------------------------------------------------
I have found a bug with version 6.1.1 and 6.1.2. The bug happens under Windows 
when there is the special character � (e with a grave accent) in the file 
name. Here an example with the U2 "Pop" album. This album contains 12 tracks. 
The title of the first track is "Discoth�que" (note the � character).

Here is what happens with version 6.1.1: The Slim server detects two different 
albums. The first album called "Pop" contains only 11 tracks (the first 
track "Discoth�que" is omitted). The second album is called "U2 - Pop" and 
only contains one track "Discoth�que".

The bug is different and worst in version 6.1.2 (v2005-08-25): it seems the 
special character "�" is converted to the string "\xE8" (or something like 
that), and unfortunately under Windows, the "\" character is considered as the 
folder separation character. So the slim server displays the first track 
as "Discoth". The problem is worst when you have a directory name containing 
an "�" character. For example I have the maxi-CD "Discoth�que" by U2 
containing 4 different mixes of the "Discoth�que" title stored in the 
directory "U2 - Discoth�que". In this case, the Slim server detects a new 
artist called "U2 - Discoth" and all the 4 tracks are displayed as "Discoth".

Strangely enough, there is no problem with the "�" character (e with an acute 
accent) for example. I haven't check any special characters, but the bug could 
happen with other characters too eventually.

For the moment, I reverted to version 6.0.2, where this bug is not present.
-----------------------------------------------------------------
End of original report.

Thanks for your support.
Bernard