[why]
Very slender and tall icons will be scaled huge compared to their fatter
neighbors. This happens for example to the chess pieces (E25F ff) or
text style icons like italic (EB0D).
[how]
When a monospaced font is created use a slightly less tall cell height
for all icons (except icons that have to match the actual line height).
This can be prevented by the new scale control character `^` that
symbolizes maximized vertical size (height) within the real cell.
The smaller cell (now called icon cell) is less tall than the line
height, but higher than the cap height of the font; to prevent people
complaining that the icons shrunk too much.
It is about 1/3 higher than the cap height compared to the line height.
This is NOT applied to the other Nerd Fonts fonts variants (i.e. Regular
and Propo) because all icons are generally a bit bigger than the cap
height (no scaling down to fit into one advance width) and as the
scaling is far less pronounced the slender-and-tall icons scale
comparably and do not look out off place there.
Suggested-by: Aaron Bell @aaronbell
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
A more conceise version of the Powerline test, designed to show
the dreaded 'faint vertical lines' phenomenon from LCD antialiasing
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
We still fight with the faint lines on the big side of the powerline
glyphs. They come from the LCD antialiasing mode that has problems with
the borders.
Other fonts use far more overlap. We use only a modest amount of overlap
(1% of the width).
[how]
As the other fonts do, increase the overlap (to 6% now).
Add full-hight 'landing platforms' on the outsides of the glyphs,
which are 7% wide.
Related: a8b9e1da06
Related: #1245Fixes: #1547
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The glyph is extremely complex with very thin open spaces and bridges.
Obviously a conversion from some colored icon that has not been looked
at too hard.
[how]
Remove all the small crevices, smoothen the surface carefully and make
too thin strokes a bit wider.
We still keep the Devicons goal "very crisp icons" so that no rounding
of the paths and reduction of points is used.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Forgotten after update.
[note]
Also remove old old configure file that has been used for fast test
runs. It has the wrong format now anyhow.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The carons are all upside down.
The dcaron and tcaron should use an 'apothrophe'.
[how]
The simplify the fixing of all carons we take the excellent fork ofu
Rodrigo Batista de Moraes that (re?)creates the letters with caron from
references.
Just manually flip the caron and all combined glyphs will be fixed.
Create a combining-comma-above-right from the ordinary comma.
Reference that for dcaron and tcaron.
Rerun `make-bold` which creates the two otf files.
Fixes: #1492
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The code is rather convoluted and one can not follow what is done.
[how]
Add function that abstracts some steps away.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
This sets out to circumvent a problem with VisualStudio 2022. That
application seems to have problems with fonts when the ID16 is not a
prefix in ID1.
We have this when --makegroups >= 4, because
ID1 has the short name suffix 'NF'
ID16 has the long suffix 'Nerd Font'
These fonts can be selected in VisualStudio 2022, and the preview works
ok, but once active some replacement default font is used instead.
The problem vanishes if ID16 and ID1 have the same stem, or rather ID1
has someting added on top of ID16; but ID16 is a substring of ID1.
See more discussions in #1442
[how]
Write both forms in ID16 fields, 'NF' and 'Nerd Font' suffixes. This
works as long as the application considers all languages equal.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Albeight documented in the comment not all non English-US entries are
removed but just al TO_DEL ones.
[how]
Put the conditional in the right position.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
We need the glyphnames to be unique, or some glyphs will not be
accessible later (in the cheat sheet, css, glyphnames).
[note]
Also already remove one non-effective duplicate that is first an alias
and later a real glyph in i_seti.sh
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Two glyphs may not have the same name (normally).
Our glyphnames.json will break.
[how]
Do not add two entries with the same name but rather report the
codepoints in the bottom.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Forgot to increase with commit 136a84bc03.
Now we also have different original icons, lets have a new number.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Native MacOS has only an ancient Bash 3.x
But we use arrays... and rewriting only to support 15 year old shells?
[how]
Check the Major Bash version number and bail out if too old.
Fixes: #1505
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
