Last modified: 2012-12-30 20:59:18 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T34585, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 32585 - allow customizing of category sections
allow customizing of category sections
Status: NEW
Product: MediaWiki
Classification: Unclassified
Categories (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-22 14:04 UTC by Bergi
Modified: 2012-12-30 20:59 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Bergi 2011-11-22 14:04:37 UTC
Each category has its own sorting order (customizing of that is Bug 28397), and when a category is shown the collation is splitted up by starting letters (of the sort key). For big categories and categories sorted by a date it would be very useful to change the behavior of that splitting prozess.
E.g. in a category where all sortkeys start with a year the sections should be titled with four digit numbers.

I think the easiest approach would be have a magic function where you can declare how many digits should be used to split the item list. So {{#categorysections:4}} would make "Hello World" stand under "Hell" and "1984 (book)" under "1984".

It also could be more flexible by defining in what ranges the rule should apply. E.g. {{#categorysections:4|1|9}} would make "1984 (book)" stand under "1984" and "984" stand under "984" cause they're in the range from 1* to 9*, but "Hello World" would stand under "H" as regular.
Comment 1 Bawolff (Brian Wolff) 2011-11-22 15:15:51 UTC
This would be difficult to implement for uca based collations (I believe anyways). For the "uppercase" and "identity" collations it would be more do-able to implement (not sure how it'd work with the magic we do for Hangul syllables though), but I'm not exactly sure how one would cleanly hook a parser func into Collation::getFirstLetter.


This is very similar and possibly a dupe of bug 2802.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links