On 12/12/07, <b class="gmail_sendername">Anduin Withers</b> <<a href="mailto:awithers@anduin.com">awithers@anduin.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This may be a good argument for comparing filenames, when sorting, without<br>their extensions. This issue is similar to the brokenness of title compares<br>in -fixes where what is being compared may not be obvious (in the titles
<br>case not only is it not obvious but it can be wrong).</blockquote><div><br>Unfortunately, I think the case for sorting by the metadata is stronger because I know in my case when I do IMDB lookups, the file names are not necessarily reflective of the full / accurate title. An example would be a file called "GITS_:_SAC_Vol_01_Ep_1.avi" but the metadata title is "Ghost in the Shell: Stand Alone Complex Vol 01 Ep 1" and I would hope / expect the title to be sorted by metadata, not file name.
<br><br>The real problem here for me is the sort order. I do however understand the problematic nature of the sorting implementation and the difficulty in finding a single approach that works in all locales and situations. (I have read the thread about Myth removing brackets and their contents in filenames to generate titles.)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Sorting sucks. As for it making sense, sort T. S. Elliot and Trotsky. Did<br>you compare r to . or S? The example is contrived but if you look at the
<br>confused sorting you currently see and pretend you skip the . before the<br>extension it makes sense.</blockquote><div><br>Is this a problem that we can push out to the user at all? I mean, Myth can take a stab at it's best guess for sorting, but then add to Myth the configurable option to sort based on different criteria. In other words, Myth's default is to sort based on title metadata in the natural ordering provided by the local or database or whatever. But if the user chooses, they can indicate to Myth to sort by file name (case [in]sensitive and / or matching a pattern for unconsidered characters), or perhaps they wish to sort by some other metadata criteria (such as genre) and within the genre they files are sorted as Myth's default (maybe more options are added for n-level sorts, but probably not). Thoughts?
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> [test in another e-mail where collation and ls don't work]<br><br>I don't Ubuntu, but ls should be honoring your locale setting (ls
<br>--sort=none should confirm it normally sorts).<br></blockquote></div><br>I ran this command and did verify that ls does sorting - the locale environment variable simply had no effect on the order.<br><br>Brion<br>