[why]
* We want to have the autocreated cheat-sheet file here 100% and not
only approximate, so create the file anew via generate-css.sh and
commit it here.
* "No results found" is kind of a lie, we have a result and the result
is that there are no hits while searching :-> Call me pedantic.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
After the last bullet point closing the <div> seems problematic and
results in a bit of garbage in the html page.
[how]
Just use the dashes as we historically used instead.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
I think the `</div> </details>` at the end of the v3.0.1 release notes was being parsed as part of the last `<li>` item, resulting in `</div> </details>` being escaped. This commit should fix the issue where in the HTML output, the v3.0.1 release `<details>` included the release notes for v3.0.0, v2.3.3, etc.
This step adds just the stuff generated via script in the master branch.
See pairing commit in the gh-pages branch:
Date: Wed May 3 17:54:44 2023 +0200
generate-css: Create cheat sheet with removed icons
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
After the glyph name fix done with commit
7e2d38b55 Fix some glyph names
we need to update the actual cheat sheet and CSS files.
[how]
Manually commit data from `generate-css.sh` run here.
Related: #1147
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Update from main repo to gh-pages was broken or is manual.
Changed update script.
[how]
Let script (new) run manually. To see if it works.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
When we do not rename a font that has the RFN flag set we do not list
the font as RFN-font.
This is for example the case with mononoki since the last commit.
[how]
Show the source font name not only when it differs but also when it is a
RFN.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
