Given i.e. the page "ácido" and its hex sortkey 272b372d4301868d08010a00 retrieved through prop=categories, then packed and url-encoded, the request
doesn't start listing from "ácido" (it should be on the top).
Version: 1.24rc
Severity: normal
Given i.e. the page "ácido" and its hex sortkey 272b372d4301868d08010a00 retrieved through prop=categories, then packed and url-encoded, the request
doesn't start listing from "ácido" (it should be on the top).
Version: 1.24rc
Severity: normal
I wish cmsortkey didn't take input in binary; I suspect what's happening here is that some layer is trying to interpret the binary characters as UTF-8 and thereby screwing them up.
I think the real fix here will be deprecating cmstartsortkey and cmendsortkey in favor of something like cmstarthexsortkey and cmendhexsortkey that take the input hex-encoded.
gerritadmin wrote:
Change 159746 had a related patch set uploaded by Anomie:
API: Deprecate binary sortkey input in ApiQueryCategoryMembers
gerritadmin wrote:
Change 159746 merged by jenkins-bot:
API: Deprecate binary sortkey input in ApiQueryCategoryMembers
This should be deployed to WMF wikis with 1.24wmf22, see https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap for the schedule.