dpotts;685957 Wrote: > I don't think ALBUMARTISTSORT can have anything to do with this bug. I > get the problem for artists who appear only on albums that have no > ALBUMARTIST or ALBUMARTISTSORT.
your example above, in post 15, did have those tags listed, so now i'm confused by your posts. but follow me for a second here... i do believe you and others are describing a bug that exists, with char sets. but the best way to show the devs a bug exists, is to go VERY methodically and show step by step what you did or added, and what the resulting change was. i think its important to first establish LMS behavior when using NORMAL characters with different tags. does AAS or CSort or other tags affect the sorting or not? i think LMS will respect AS and AAS tags. not sure about CS tags. but whether it does or not, its important just to know how it behaves when using those tags with normal chars. if we can establish that LMS does or does not handle sorting correctly given a certain set of tags with normal characters, it will be a lot easier to prove to the devs that LMS behavior is different somehow when accented characters are used. so in essense, there may be two bugs here, (chars and ignroing sort tags) or one bug (chars). dpotts;685957 Wrote: > I can make the problem go away by correcting either of the two > conditions I named: either remove the nonASCII characters (from > ARTISTSORT only, leaving the nonASCII characters in the other sort > order tags) or remove the offending names from COMPOSER and/or > CONDUCTOR. In the first case, the names are sorted properly as directed > by the sanitized ARTISTSORT tag. In the second, the names are sorted > properly even with nonASCII characters in the ARTISTSORT tag. i assume you have "composer" ticked in the LMS settings, to add it to the browsable listings? in any case, i would not assume from any of the above that LMS is doing X Y or Z b/c oftentimes, there is another reason then what you think for what LMS does. thats my exp anyway. dpotts;685957 Wrote: > LMS didn't always have this bug. It's relatively new, probably > introduced in SBS 7.6.0. The earliest clear description of the problem > I've found is in the bug report filed by Johan S in July of last year: > http://bugs.slimdevices.com/show_bug.cgi?id=17304 right, as i said earlier, i believe it is due to the stupid mandatory forcing of case and diacritics respect in LMS. some people, mostly americans, don't care or want to have diacritics and case respected, while some people, mostly europeans or the more anal among us, do. while either way is fine, it should be an option, and because it is not, it has had a lot of undesirable consequences for users, which i believe this is one example of. -- MrSinatra www.lion-radio.org using: sb2 & droid (my home) / duet & ipeng (parents' home) - sbs 7.7.2b - win7 ie9 & xp pro sp3 - p4(ht) 3.2ghz, 2gig ram - 1tb wd usb2 raid1 - d-link dir-655 - 49k+ mp3/flac ::VOTE FOR 'BUG 15604' (http://bugs.slimdevices.com/show_bug.cgi?id=15604)!!!:: ------------------------------------------------------------------------ MrSinatra's Profile: http://forums.slimdevices.com/member.php?userid=2336 View this thread: http://forums.slimdevices.com/showthread.php?t=90661 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
