Rockbox

  • Status Closed
  • Percent Complete
    100%
  • Task Type Patches
  • Category User Interface
  • Assigned To No-one
  • Operating System All players
  • Severity Low
  • Priority Very Low
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by Killaruna - 2006-11-20
Last edited by jdgordon - 2010-10-14

FS#6359 - Correctly (Latin1) sorted filenames in tree browser

This is a tiny patch to correct the file ordering for the Latin-1 charset when browsing the file tree: Characters with accents and the german Umlaute are sorted to the same positions as their normal (i.e. unaccented) versions instead of to the end of the list. The new sort order overrides the old non-case-sensitive sorting. Case-sensitive sorting is still using the old method.

Closed by  jdgordon
2010-10-14 12:21
Reason for closing:  Rejected
Additional comments about closing:  

there is no perfect solution for this, and trying to make one for a small subset of the supported charsets is no better than using ascii value sorting

How does it sort æøå/ÆØÅ? In Danish at least, they traditionally come at the end of the alphabet, after z/Z. I don’t know about other languages which use these characters (Primarily Swedish and Norwegian).

Like aoa - I’ve put all special characters to the same position as the closest normal character, assuming that these are the correct places… But basically you can sort the characters as you like, the function works with a priority table (just as the original strncasecmp).

I believe those should be moved to be directly after z, as this is the case in all languages which use them (http://en.wikipedia.org/wiki/Danish_and_Norwegian_alphabet and http://en.wikipedia.org/wiki/Swedish_alphabet). Æ, ø and å are not considered as “variations” of a o and a, but as characters, so sorting them next to a and o would be really strange. Luckily, this goes for all languages using æøå - the sorting of ö and ä is, as you can see in the Swedish alphabet (where they are considered separate characters) not so clear-cut.

OK, I see… I’ve put these characters to the end of the alphabet again - thanks for the feed-back!

Are you considering default codepage for that?
the same byte values stand for different characters in other codepages (non-unicode) so you should know how to interpret the values…

MikeS commented on 2006-11-29 19:54

Why are we using anything but Unicode internally? :
I’d like a good reason that can’t possibly have a good solution and compels the use of codepages.

HINT: The good solution isn’t “use codepages” ;)

Collation is language-specific, so there’s no general purpose solution here.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing