Mnyb;534266 Wrote: > My bug was in short "why does sbs care what file name is if it can be > found by the os how can sbs miss it ?" > > If a file has metadata the names are not that important. Exactly.
At least in the past, I think part of the problem was that SBS stores the file URL UTF8 encoded. And I think that SBS wasn't always sure when it was being handed file path data that was already UTF8 encoded. So in some instances it encodes it again...resulting in an invalid (double encoded) URL. I think that the problem was that whatever IsUTF8() function SBS was using was imperfect at detecting UTF8. Certain character combinations on certain operating systems posed problems that ended up getting fixed on an ad-hoc basis. That's my impression, anyway. Folks who know the code should correct me if I've got this all wrong. Anyway, this may or may not be at the root of the problem that you're seeing. But if you can look at the data in URL field in the TRACKS table for the file in question, you might be able to flesh out your bug report. With MySQL, the gui tools include the Query Browser which will allow you to peek into the TRACKS table. With SQLite, there are several free stand-alone gui "managers" for various operating systems which will let you open the .db file and poke around. -- gharris999 ------------------------------------------------------------------------ gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115 View this thread: http://forums.slimdevices.com/showthread.php?t=76350 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
