> Are you sure you don't have conflicting tags?  Proper Unicode support 
> is of course a priority, and should be fine with SQLite too.
I could well have conflicting tags - I will check further when I have
time over the weekend.

However, there does appear to be a difference in handling these issues
between MySQL and SQLite.  Note I'm not saying it's wrong - potentially
I consider the new handling to be the expected behaviour (subject to
further investigation, as I'm guessing a bit with the limited play that
I've had with it so far).

I raised a bug (http://bugs.slimdevices.com/show_bug.cgi?id=10324) in
the past that diacritics were not treated as different artists - it was
non-deterministic what you get in the app depending on which source file
was scanned first/last.  eg. If I had an album with songs by an artist
called "Help" and another with the artist called "Hélp", they would be
treated as one artist, and they would be reported as one or the other
(other properties of the artist may not be consistent with that - eg.
sort order, search version of the name, etc).

I argued that they should be treated as different tag values, forcing
two Artist records.  I think Michael was agreeing (or was just a bit
confused due to the original bug report), but then the bug got closed as
Won't Fix.

So it appears that they are now scanned as different artists, which may
be by accident, but I consider that the correct behaviour, in that it is
easier to identify iffy tags and get them fixed, and the behaviour is
deterministic.


-- 
Philip Meyer
------------------------------------------------------------------------
Philip Meyer's Profile: http://forums.slimdevices.com/member.php?userid=95
View this thread: http://forums.slimdevices.com/showthread.php?t=64890

_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta

Reply via email to