>> >its almost insane that anyone would even argue this point. >> And yet you continue to argue. > >i argue for sanity. > And therefore by self implication you are almost insane ;-)
>so, you don't NEED spaces! so, it was a PROBLEM for you that you had >to fix! > No I didn't need those spaces, and in fact I didn't want those spaces. So, when I was aware that I had a couple of occurances, I got rid of them. I didn't moan about it - just opened the files and removed the spaces. It wasn't a big deal, and now I am happier in knowing I'll never have a problem in any app in the future. >the point you don't seem to get, (and not unlike another issue i can >think of), is that you are AWARE of this issue, you knew to look for >it, you knew how to figure it out and how to fix it. > But how likely is it that there will be leading/trailing spaces that will be a problem for users. There's hardly any reports since 7.6 went out (the few reports where people have noticed/cared are mostly changes in caps, diacritics, etc). Most users receive from metadata sources, which almost certainly don't have leading/trailing spaces; they are removed from source. I wouldn't expect many actual cases of leading/trailing spaces existing and causing a problem. After all, if all albums had for example an extra space on the end, then all songs on an album would still match the same album name, and thus also not a problem. So, it's only really a problem if different songs on an album have different leading/trailing spaces. I think you are going a bit over the top (as usual) with how widespread an issue this is really going to be. I imagine that most users with problems are obtaining music from illegitimite sources, or users are editing their own tags and thus know how to do it. Either way, I'm pretty sure they will be aware of tagging and how to resolve. I'd much rather the developers spent time fixing real problems that don't have solutions/workarounds by the user. There's plenty of more important things to be looking into. >so any fix wouldn't apply to you anyway! this is just a simple return >to previous function. no good reason not to do it. > Appart from all the reasons stated that you ignored. >but what i do know, is that it adds extra noise (not data) >to the DB which is unnecessary and could result in slower queries. > Garbage. >duh. but then again, i never needed to worry about them before the >diacritics fix. > I don't think this is related to relaxed/strong comparisons with diacritics or case sensitivity. An additional change must have been consciously made to trim spaces. >i also would point out that i have never needed to worry about figuring >out blank comments from comments with only spaces. total make work >situation. > And you still won't need to. No matter what text exists in comments, it doesn't make any difference to music library browsing. _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
