Martin Holmes

I think this issue is complete, but only through the ad-hoc hack of adding the specific character concerned into the regex. Somehow or other, we should keep this around to...

Note: Saxon 12.5 was released in July, so I'll add a ticket for upgrading to it, and link it to this ticket. If the upgrade goes smoothly we should be...

Saxon 12.5 now merged, so this can be tested and the hack removed if no longer required.

Tested this today, and unfortunately the hack is still required. I'm waiting to find out if there is an ETA for a release of Saxon with updated Unicode data.

Quick question to @joeytakeda : We already have a What's New section in the documentation, and it has a section "Changes in version 2.0", which is where we should enumerate...

The answer is possibly 12.6, but definitely by 13.0. When that happens, we can test and update.

We already have working sort keys for desc filters -- see e.g. the Despatches on Jenkins, where there are meta tags like this: `` which are used to sort checkboxes...

Rather than have the JS check the length of every single name in the JSON, I think it would make more sense to calculate this at build time and store...

@joeytakeda has implemented $minNameLength as a param in the feature filter JSON output; over to me to have the JS parse it and use it.

I think we should output a pseudo-table-header at the top of the search results, with a column for each filter that's configured for sorting; that control should first sort ascending,...