Add support for externalised sorting per language #748
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR attempts to fix #724 and #254 by moving away from liquid's in-built
sort
function and to use a bespoke sorting provided bysort-glossary.py
.There are two important changes:
glossary.yml
file used to be copied into the_data
folder to act as the served content to liquid/jekyll. This has now changed in that the python script creates a_data/{lang}/glossary.yml
file for each language and the template loads the specific data file based on the selected language. It also dumps out non-Latin characters in Unicode to avoid ambiguity in rendering - humans are not meant to read this_data
version of the glossary!