the offline branch is often behind, because in the gh-pages branch, the .md files are edited,
which in the offline branch are inlined as json in search.js.
you can take the json data from visiting the online version (gh-pages), finding the search.js in the sources, and applying a lot of regexes to make the formatting the same as the old search.js, and the diff clean.
I'll try to list the exact regex replacements next time i sync the data with gh-pages.
(need to use some groups and dollars, like replacing ( )( keywordsWK:.*$) with $2 (second group),
or ^.*elementsWK: "",.*\n with nothing, for example)
the offline branch is often behind, because in the gh-pages branch, the .md files are edited, which in the offline branch are inlined as json in search.js.
you can take the json data from visiting the online version (gh-pages), finding the search.js in the sources, and applying a lot of regexes to make the formatting the same as the old search.js, and the diff clean.
I'll try to list the exact regex replacements next time i sync the data with gh-pages. (need to use some groups and dollars, like replacing
( )( keywordsWK:.*$)
with$2
(second group), or^.*elementsWK: "",.*\n
with nothing, for example)