Closed GoogleCodeExporter closed 8 years ago
Folders are made to mimic collection nodes to enable search. That makes the
regular collection options, such as 'delete collections' show up as well, but
since folders are not actually collections, they don't (and shouldn't) work -
just ignore them.
The sorting does seem to be off though, even after removing my search
modifications. Mikheil: perhaps you know more about this?
Original comment by quisvir
on 3 Mar 2012 at 3:55
Folders use "unicode" sort order. (why have mixed case folders anyway?)
I don't quite get what collections have to do with it...
Original comment by msukhias...@gmail.com
on 3 Mar 2012 at 8:06
Why have mixed case folders anyway?
>> Because default Sony has. Look at Internal_Memory.jpg with database, Digital
Editions and ScreenShots
OTOH, I think you should do some kind of "smart" sorting process. I mean, look
at Sorting_Test_Page1 and Sorting_Test_Page2. For a plain user, who does not
know about "unicode", they are just WRONG.
You're current system does not correctly sort neither ç nor ñ. I'm not sure
about ç, as it's not used in Spanish (although I think it's mixed with c, I
mean, for sorting order, c and ç are equivalent). French or Portuguese help
needed.
But I can tell you that ñ is a letter with all the same rights any other one
has and its order is between n and o. Spanish alphabet goes ...-l-m-n-ñ-o-p-...
Original comment by alr...@gmail.com
on 4 Mar 2012 at 6:09
Attachments:
(Double post but for a good reason).
I'll post it also in FR thread, but there I cannot attach screenshots so I use
bug-tracker.
Sony sorting is also wrong. Look at the screenshot.
+ Sony correctly mixes upper and lower case.
+ But it doesn't detect Ç and Ñ as normal latin letters.
+ And I've just noticed that accented letters are also wrong. Look at the last
books in "*" section. (Forget about the starting "El", it's a Spanish article
and it's correctly filtered out since the fixes made for
http://code.google.com/p/prs-plus/issues/detail?id=287). "ú" should be treated
like "u", but it appears as an "out-of-alphabet" letter. (And ü, á, é, í,
ó...)
Original comment by alr...@gmail.com
on 4 Mar 2012 at 6:38
Attachments:
There is a new google-doc spreedsheet PRS+Alphabet&Sort I've set up.
Reason is to collect Sortorder and possible popup-characters for the keyboard
Don't know if a custon sort could be implemented without tweaking the binaries
but lets start to collect the needed Infos
https://docs.google.com/spreadsheet/ccc?key=0AvEpfPLpz-UKdDB0MUtSaUJjaFRDVzFkcjB
FX0xmRkE
Original comment by Mark.N...@gentlemansclub.de
on 4 Mar 2012 at 9:09
Ok I'll download and modify and update es version ASAP.
Nevertheless one suggestion about sorting which your spreadsheet doesn't seem
to cover:
+ There are some characters which are equivalent for sorting. Example lower and
upper case and accented not accented letters.
I mean: sorting "ultimo" (1st singular person in present of "ultimar" - to give
the final touches to something) before "última" (last in feminine) is wrong.
It doesn't matter if "u" uses accent or not. You can chose if you want "ultimo"
before or after "último", (last in masculine), but "última" and "ultima" (3d
singular person in present of "ultimar") always should go before "ultimo" and
"último".
+ OTOH, "ñ" does always go after "n" and before "o". (And as I said before, I
don't know if this also happens with "ç" or if "ç" is like an accented "c").
So I think you need more info than what you are covering in your spreadsheet.
Original comment by alr...@gmail.com
on 4 Mar 2012 at 9:41
>You're current system does not correctly sort neither ç nor ñ
They come _after_ lower/upper case Latin letters in Unicode tables and are
sorted accordingly.
Please note that sorting ("collation") is a complex subject, there is no
universal sorting that fits all, each language has its quirks even if you stick
to the same alphabet.
Original comment by msukhias...@gmail.com
on 4 Mar 2012 at 9:47
[deleted comment]
Sony's code (in general) mixes uppercase and lowercase simply by adding
toLowerCase(), which we could also do. For complex characters, Mikheil is
absolutely right in saying it's incredibly complicated (I was not aware of
this, tbh). See for example:
http://www.unicode.org/reports/tr10/
We could consider implementing something like this:
http://www.indiscripts.com/post/2010/10/alphabetical-sort-in-javascript-and-inde
sign
but I reckon these things very quickly become overkill for our purposes (due to
memory/cpu limits).
Original comment by quisvir
on 4 Mar 2012 at 3:12
The problem here is, in case of "books" view, it's not JS, but binary function.
We currently use porkupan's binary, without having source for it.
Putting it on hold for a while, we might get back to it later.
Original comment by msukhias...@gmail.com
on 9 Mar 2012 at 12:26
Original issue reported on code.google.com by
alr...@gmail.com
on 3 Mar 2012 at 8:01Attachments: