We keep the Seti css logo, as the abstract hash tag is prone to 'misuse'
for other purposes and an update of the logo would break it. Anyhow CSS
shield is the current logo before the newly added one, and anyone who
used the Seti css logo (i.e. hash tag) would probably mean something
entirely different.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Fontforge's cvs import sometimes struggles (hard) on transforms.
[how]
Apply the transform before saving. It's not that we want to edit it
anyhow, so no reason to keep that abstraction.
Also remove some meta-information.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Some bash scripts we have need bash version 4 or better. For example native
arrays where added with that version in 2009.
Unfortunately Apple decided to keep a very very old version of bash in
their setup which will not work.
[how]
Add information on needed bash version at least in the readme file.
We could now rewrite all scripts to work with bash 3; I tried that but that
is a tremendous amount of work and I guess the time is spent better on some
real problems; especially because only a small number of users are affected
and they could also just switch to recent bash version.
We could also add checks for the bash version to the scripts. This is not
done here.
[note]
Also remove obsolete explanatory entry; that subdir has been deleted.
Fixes: #1680
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
When the icon sets have changed (added or names changed) the i_*.sh
files are (hopefully) up to date, but the glyphnames.json file is only
updated on release.
Unfortunately the font-patcher uses the glyphnames.json to determine the
patched-in glyphs' names, but in the workflow the json file is only
updated after all fonts have been patched.
[how]
Like the version number in the font-patcher file we also create a
transient glyphnames.json in each patching job, that the font-patcher
can then utilize.
Still the in-repo glyphnames.json is only updated after successful
release. So in pinciple we call the generate-css.sh (which also
generates the glyphnames.json) once for every font in the font matrix
(just before patching) and then finally after all patching has been done
again and that is committed back to the repo.
Fixes: #1745
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The script is extremely slow.
[how]
Instead of spawning a new subshell for each glyph (to determine the
codepoint of a char), execute the printf within the current shell.
Before:
./generate-css.sh 25,06s user 33,26s system 101% cpu 57,414 total
After:
./generate-css.sh 1,89s user 0,50s system 102% cpu 2,330 total
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
No options changed, but it just looks better to have a more recent
version number in the example.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
With the latest release the numbers were just changed (in the svg) but
the flow graph stayed the same. The relative proportions can now look a
bit out of place.
[how]
Completely regenerate the graph from the Sankey generator.
Afterwards some manual adjustments to get the color and the position
right (in Inkscape).
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The main readme is already too big anyhow.
We should extract topics into sub-pages rather than adding more.
[how]
Use the Wiki instead and link the Wiki clearly, with entries in the TOC.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The icon change with Devicons update is not clearly marked as
'breaking'.
[how]
Add a 'breaking' paragraph.
Also add some more items and clarify others.
Reported-by: Xavier Chanthavong <xavier@atsign.com>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Mention Font Fallback in the readme. The manual can not be complete and
it just points users in that direction.
Fixes: #670
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
I am not sure why this is wrong, maybe someone renamed the Cask?
Ah, here it is:
87e1c59a2b
[how]
Follow the renaming done by Homebrew.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The Cask-fonts repo has been incorporated into the main Cask repo.
On releases we would use an obsolete repository to create the Cask into.
The casks are now in a dedicated subdirectory (Casks/font) and under that
we have one subdirectory for each font name starting character (to have a
smaller number of files per directory I assume).
[how]
Change the repository path.
Put part of the new (longer) path, the fixed part, just in the CI process,
while the generator script takes care about the one-directory-per-startchar
substructure.
Fixes: #1635
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
The CI first builds the fonts and THEN calls `generate-css`.
Which was ok, previously.
But now we store the glyphnames in the font files, and they are taken
from `glyphnames.json`, and THAT is only updated with the CSS file.
So the font files will get OLD names, if the symbol fonts got updated.
For now I just manually run the `glyphnames.json` update
(`generate-css.sh`) manually now, with this commit.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
