[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>
[why]
The automatic release process updates the CSS files, but not the Cheat
Sheet file. This has been fixed by commit
3de381d5a CI: Automatically deploy Cheat Sheet
[how]
Do this one more time manually (do not want to trigger a release
workflow).
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Sometimes we change the font name just because ... reasons, without
having being oblieged to do that because of a reserved font name (RFN)
clause.
This is for example the case with M+ that we rename to MPlus (well, it
has both names in principle, but the human readable name in the original
fonts in M+).
Another is "Go Mono" that we rename to "Go-Mono" for whatever reason.
This would also have been needed when `Fira Code` was still RFN and we
got the special permission to patch it without dropping `Fira Code` from
the name (see [1]), to create the correct tagged list.
But Fira Code dropped the RFN some time ago, so no need for this font
anymore.
This also prevents our own Symbols Only fonts to be listed as having RFN.
[how]
But an explicit field into the fonts.json database if the font has an
RFN or not, and decide upon that.
[1] https://github.com/tonsky/FiraCode/issues/767
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
