|
21f0a4d5
|
2025-09-11T09:47:51
|
|
docs: add injust as a contributor for doc (#1927)
* docs: update CONTRIBUTORS.md
* docs: update .all-contributorsrc
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
690646ed
|
2025-08-21T08:10:34
|
|
Fix link in README
|
|
d46b97ac
|
2025-08-03T15:20:37
|
|
Put icon copyright into every font-readme [skip ci]
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
0def7818
|
2025-08-03T11:57:11
|
|
[ci] Update FontPatcher.zip
|
|
6c7910e5
|
2025-08-03T13:33:44
|
|
font-patcher: Link to icon sources in patched fonts
[why]
Some icon sets require mentioning of the original author, and we do this
on the website. But there is no indication that we have that list.
[how]
Remove the comment about the changelog (usually you look at the
changelog at the repo before you install a new font) and substitute it
for a link to the icon repo list.
Related: #1908
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
abc3c03a
|
2025-08-03T10:28:21
|
|
[ci] Update FontPatcher.zip
|
|
36ae3260
|
2025-08-03T12:22:36
|
|
Add details to icon sources
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
ebc376cb
|
2025-05-06T12:46:27
|
|
DejaVuSansMono: Fix monospaced (and remove subdirs)
[why]
The original / upstream version of DejaVuSansMono does not have the
trigrams at codepoint U+2630 - U+2637. These have been added manually
(together with some Powerline glyphs) with commit
bc1f35949 Updates DejaVu fonts from version 2.33 to 2.37 & adds trigrams (2630 through 2627) (fixes #100)
Unfortunately the newly added glyphs were just copied over from
DejaVuSansCondensed and the width does not match the monospaced width of
DejaVuSansMono: the resulting font is not monospaced anymore (but it
should be, by its name part Mono).
[how]
Take the glyphs again from DejaVuSansCondensed but instead of directly
transferring:
- export glyphs as svg from Condensed font
- in the Mono font set the width of the empty target glyphs to 1233
- import the svgs
- scale the glyphs X to 75% (100% in Y)
- center the glyphs within the width
The exact same glyphs have been used for all 4 fonts.
[note]
Also remove the subdir structure as this is the new way to hold the font
files. Remember to clean the patched-fonts/ directory up before release.
Fixes: #1864
Reported-by: @pmadzik
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
db46f01c
|
2025-06-07T15:03:38
|
|
[ci] Update FontPatcher.zip
|
|
fa7c3b9b
|
2025-06-07T16:58:30
|
|
docs: add mietzen as a contributor for bug (#1883)
* docs: update CONTRIBUTORS.md
* docs: update .all-contributorsrc
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
36c7c380
|
2025-06-07T15:31:05
|
|
font-patcher: Fix wrong specialities matching
[why]
When the name to parse has 'for' in it - even when it is in the middle
of a word like 'formidable', 'unfortunate', or, 'forced' the "For" part
will be cut off and separated from the rest.
[how]
The reason is the code to remove 'For Powerline' from font names.
Instead of matching 'For' and 'Powerline' individually and then removing
the 'Powerline' and 'For' token later on (which fails if there is just a
'For' token like with 'Un' 'For' 'Tunate'), we now match only on a 'For'
if it is followed by a 'Powerline'.
To make the removal of the other-token easier later on we rename/unify
the token to be CamelCase.
Fixes: #1877
Reported-by: @mietzen
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
f01ae021
|
2025-06-07T15:27:38
|
|
font-patcher: Fix comment
Never trust comments :-/
Obviously the code has been changed a bit, and the commend did not
reflect that.
Instead of having two different modes (the variable is gone completely)
it just automatically handles verbantim token different from
non-verbatim token (which must be regexes).
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
a9cb48e9
|
2025-06-06T16:04:51
|
|
Merge pull request #1881 from ryanoasis/feature/slash-in-name
font-patcher: Fix patching of fonts with slashes in name
|
|
89398e83
|
2025-06-06T16:00:36
|
|
font-patcher: Fix patching of fonts with slashes in name
This is just an empty commit to crate a PR for a directly pushed fix
(with the same name).
The PR is needed to create a nice release message :-}
|
|
bc12f6a4
|
2025-06-06T15:52:02
|
|
All contributors/add oktoling (#1880)
* docs: update CONTRIBUTORS.md
* docs: update .all-contributorsrc
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
05303b5d
|
2025-06-06T13:49:33
|
|
[ci] Update FontPatcher.zip
|
|
30a9b82e
|
2025-06-06T15:37:24
|
|
font-patcher: Fix patching of fonts with slashes in name
[why]
When trying to patch Anka/Coder fontforge reports it can not open the
font file.
[how]
When opening a font file we open all fonts within that file. For a ttf
or otf that is one font, but ttc can contain multiple fonts (of course).
The fontforge open function takes the font filename and the subfont name
in parenteses appended to the font filename. For example
`directory/folder/myfont.ttf` which contains just MyFont, it opens via
`directory/folder/myfont.ttf(MyFont)`.
That algorithm is not very smart, and so this fails
`directory/folder/AnkaCoder-r.ttf(Anka/Coder)` because it assumes the
directory goes up to the last slash and takes `Coder)` as filename.
But instead of using the concrete subfont name we can also specify the
index of the subfont in the font file, and that circumvents the problem.
[note]
The TTC opening feature is not well documented in Fontforge, best
described here:
https://fontforge.org/docs/ui/menus/filemenu.html#the-file-menu
Fixes: #1879
Reported-by: @oktoling
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
ad6ccb27
|
2025-05-21T10:55:43
|
|
CI: Create new FontPatcher.zip only at the end of release workflow
[why]
We have an obsolete glyhnames.json in the release FontPatcher.zip.
[how]
Packaging the FontPatcher.zip should be the last step when everything
has already been updated.
Some code from the zip-release.yml workflow is copied into the
release.yml :-/ but we need to do it at the exact right time.
Note that we need to commit-push before we call the
github-pages-deploy-action.
[note]
Related: #1868
Reported-by: @subframe7536
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
fcaadcab
|
2025-05-21T13:19:33
|
|
docs: add subframe7536 as a contributor for bug (#1869)
* docs: update CONTRIBUTORS.md
* docs: update .all-contributorsrc
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
b3c1b0cf
|
2025-05-09T18:22:44
|
|
docs: add peppapig450 as a contributor for bug (#1867)
* docs: update CONTRIBUTORS.md
* docs: update .all-contributorsrc
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
e8fa89bf
|
2025-05-09T17:58:32
|
|
install.sh: Add deprecation warning
[why]
I guess people do not know this probably, or gloss over it when reading the readme.md.
We would need to throw together something new that maybe utilizes
bin/scripts/fetch-archives.sh
But then, cloning the repo is no good idea in any situation. And how would
people get the new script without cloning. Not sure it's worth it.
Lets see if people complain with this warning.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
fe10f51a
|
2025-05-09T17:45:43
|
|
install.sh: Fix broken copy commands on MacOS
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
044a7c31
|
2025-05-09T17:29:43
|
|
install.sh: Add info on actually used bash version
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
dfe30cd8
|
2025-05-09T17:13:05
|
|
Merge pull request #1866 from ryanoasis/feature/downgrade-install-bash-3
Downgrade install.sh to bash 3
|
|
2c710f0d
|
2025-05-09T16:52:58
|
|
install.sh: Work around find-on-MacOS
Note that `find` on MacOS does not know `-printf`
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
d0793d02
|
2025-05-09T16:11:00
|
|
install.sh: Drop most bashisms
[why]
We want to have this scripts working with the standard MacOS bash, which
is an ancient version 3.
[how]
Change the shebang to `sh` and use checkbashisms and shellcheck.
Afterwards change to `bash` again. See note in the code about
exceptions:
# This script must run with bash 3
# In fact it is checked against `checkbashisms` and no bashisms are
# used, except (because the workarounds are too involved):
#
# - <( ) process substitution
# - read -d option
# - $'\0' to supply a nullbyte to read -d
# - <<< here-string
See also https://askubuntu.com/questions/1059265/whats-the-problem-with-bashisms
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
0cbf1822
|
2025-05-08T13:36:07
|
|
install.sh: Reintruduce extension parameter
[why]
At the moment we have every font only in one format (ttf or otf), so the
preference option does not do much (does not do anything).
Anyhow, it was there before and maybe at some point we take the multiple
formats up again, and then we are prepared.
[how]
Instead of the previous solution to search for all formats and then try
to remove the duplicates we search first for the desired format and if
we find not one font we search for the other format. This is slightly
different but the outcome is the same.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
13cb21c4
|
2025-05-09T10:08:36
|
|
install.sh: Make bash 3 compatible
[why]
Vanilla MacOS has just some very old bash 3 installed by default. People
might want to use the install.sh, but not install a newer bash (via
Homebrew for example).
[how]
The `nerdfonts_dirs` array is replaced by a normal bash variable (string)
where the directories are '/' separated. Because there are never
subdirectories in the list but only direct children of 'patched-fonts/'
it is possible to use slash as unique and out-of-band separator.
The `fonts` array is replaced by a function that delivers the list of
files in null-byte separated form. That means we can not manipulate the
list and thus the duplicate checking is dropped. As we do not have any
font in both formats (anymore) it will never happen anyhow.
Dropping the duplicates check also removes the extension preference
option functionality. We keep the now defunct option, though.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
3f915946
|
2025-05-08T13:17:21
|
|
install.sh: Refactor
Pull some common code out of a nested double case into a function.
That makes the code much more readable (for me).
Also simplify find expression.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
4b952a9d
|
2025-05-08T13:14:20
|
|
install.sh: Fix usage
Some things changed but the usage information has not been updated.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
cad5f305
|
2025-05-08T10:55:52
|
|
install.sh: Remove unused code
[why]
This is a forgotten leftover from commit
6edfff3d3 install.sh: Avoid arbitrary cmd exe
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
ca0b8c60
|
2025-05-08T10:48:52
|
|
install.sh: Small improvements
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
6edfff3d
|
2025-05-08T10:39:56
|
|
install.sh: Avoid arbitrary cmd exe
[why]
There is some risk that an arbitrary command can be smuggled in and
possibly executed with root rights in some situations.
See PR #1861.
[how]
Use xargs instead of eval to store the predefined filter arguments (that
come as one string) into individual arguments of the find command.
Reported-by: Nick Brady <nbgeniu1@gmail.com>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
7f220bd8
|
2025-04-28T21:35:54
|
|
docs: add Pairadux as a contributor for bug (#1859)
* docs: update CONTRIBUTORS.md
* docs: update .all-contributorsrc
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
e2d930d2
|
2025-04-28T15:32:35
|
|
docs: add sliva0 as a contributor for doc (#1856)
* docs: update CONTRIBUTORS.md
* docs: update .all-contributorsrc
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
b71ca20f
|
2025-04-28T11:43:10
|
|
Update cheatsheet-foot.txt
fix random plus sign
|
|
a27373ef
|
2025-04-25T09:48:40
|
|
gh-pages: Add more explicit wording on MD update on cheat-sheet
Fixes: #1795
Tried this already via
7a6b90f1 Add more explicit wording on MD update
but of course that is wrong and has to be changed in the generator
instead.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
6f0099ab
|
2025-04-25T09:39:42
|
|
doc: Update font-patcher options
[why]
We dropped one option and got two new ones...
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
3a50bbe6
|
2025-04-24T19:32:28
|
|
[ci] Update FontPatcher.zip
|
|
dc4e3309
|
2025-04-24T20:21:16
|
|
CI: Prepare for update casks workflow run [skip ci]
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
64695779
|
2025-04-24T19:51:49
|
|
Fix Atkinson image preview font
Relates to PR #1802
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
cabcc4a6
|
2025-04-24T19:31:36
|
|
doc: Fix typo
:grimacing:
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
8b025c8b
|
2025-04-24T19:27:56
|
|
doc: Fix typo
Fixes: #1853
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
fa7b8599
|
2025-04-24T16:34:56
|
|
[ci] Regenerate CSS files
|
|
8e29089e
|
2025-04-24T16:33:44
|
|
[ci] Regenerate fontconfig
|
|
ae57d274
|
2025-04-24T16:28:01
|
|
[ci] Rebuild patched fonts
|
|
896b9e12
|
2025-04-24T16:25:19
|
|
[ci] Bump release version
|
|
3946e4ae
|
2025-04-24T13:48:47
|
|
[ci] Update .gitignore file
|
|
bfd14fc1
|
2025-04-24T15:45:26
|
|
Fix Atkinson's folder name in fonts.json
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
532cb9ec
|
2025-04-24T13:46:35
|
|
font-patcher: Improve node-rounding on Mono fonts [skip ci]
[why]
Sometimes, due to rounding issues, we get monospaced glyphs that have a
small negative rhs bearing (i.e. extend out of the cell). That should
not be the case and all of the glyph should be inside the 'cell' (i.e.
advance width).
[how]
After changing the glyph size to the final size (before shifting) the
actual bounding box is checked, and when it extends outside the expected
limits the glyph is rescaled (from the original glyphs, not scaled a
second time) a bit smaller. As much smaller as the first try was too
big.
That can again fail due to rounding, so we try this three times with
increasing magnitude of the correction.
[note]
Also change the Monospace glyph size check for Mono fonts, so that
glyphs with (positive) overlap are never checked.
This is skipped because we do not care if the overlap is one em-unit
more or less, we are too big already anyhow. And re-scaling takes time
that can be saved.
This fixes PR #1851
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
2b205d12
|
2025-04-23T16:04:57
|
|
Trigger Release 3.4.0
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
c8157b4e
|
2025-04-23T15:37:16
|
|
Merge pull request #1852 from ryanoasis/bugfix/monospace-groups [skip ci]
Fix alignment for some glyhs in propo
|
|
52446fd9
|
2025-04-23T12:47:53
|
|
font-patcher: Fix NFP scaling for pa on monospaced set
[why]
When we create a Nerd Font Propo the 'xy' streched glyphs should fill
the whole target cell (vertically and horizontally), but when 'pa'
scaling is selected the advance of the original glyph should be
preserved.
Fixes: #1822
Fixes: #1847
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
9cdd3301
|
2025-04-23T02:00:50
|
|
font-patcher: Whitespace changes
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
0202a308
|
2025-04-23T01:49:51
|
|
font-patcher: Use modern scale group for brackets
[why]
The old ScaleGlyph group can not align the glyphs correctly, because it
has a lot assumptions that just do not hold. Especially we want the
monospace flag being set for the group.
Fixes: #1822
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
3589e704
|
2025-04-23T14:12:46
|
|
Merge pull request #1851 from ryanoasis/feature/smaller-otfs [skip ci]
font-patcher: Create smaller otf files
|
|
20ca4d1d
|
2025-04-23T00:46:58
|
|
font-patcher: Reconsider borderline scale issues
The previous solution is maybe too complicated and again assumes to
much. For example it allows glyphs to be up to (but less than) one
em-unit too wide. Because we warn only then, but even if it is 0.8
em-units wider than intended it is still too wide.
So instead we aim (calculate) to a width that is one em-unit smaller.
This means under all circumstances the resulting glyph will not wider
than our target (even with rounding problems), but some will be a tiny
bit smaller than possible.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
81182008
|
2025-04-23T00:30:23
|
|
font-patcher: Fix rounded scales in borderline cases
[why]
The unrounded scaling is more or less exact. But if we round the
coordinates it can happen that the leftmost node moves to the left and
the rightmode node moves to the right (due to the rounding), so that the
width in total grew by more than 1 EM-unit. This is escpecially bad for
the Nerd Font Mono fonts where the whole glyph should be within the
bounding box.
[how]
Check the bounding box after scaling and retry (paste again and scale
again) with a one unit smaller aim in the rare cases that the problem
occurs.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
d2506e1e
|
2025-04-22T22:40:05
|
|
docs: add badlydrawnface as a contributor for code (#1821)
* docs: update CONTRIBUTORS.md
* docs: update .all-contributorsrc
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
15fbd311
|
2025-04-22T20:33:41
|
|
[ci] Update .gitignore file
|
|
e55e6fac
|
2025-04-22T22:31:14
|
|
Merge pull request #1819 from badlydrawnface/adwaita
Add Adwaita Mono
|
|
aa9eed84
|
2025-04-22T20:51:00
|
|
Fix fonts.json sorting
[why]
The sorting should be alphabetical, apart from Plex ;-)
See src/unpatched-fonts/README.md where the script should return the
same sequence of fontnames with and without the sort.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
b52196c8
|
2025-04-22T20:37:57
|
|
Update fontfilenames file
This adds AdwaitaMono to the fontfilenames file, and corrects some
issues with the meta file(s) (unrelated to AdwaitaMono).
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
ad2feeb4
|
2025-04-22T19:49:41
|
|
Correct version number
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
332a7075
|
2025-03-22T16:08:54
|
|
typo in fonts.json
|
|
ba0b15ea
|
2025-03-22T15:30:56
|
|
Fix font name in README
|
|
46edd22a
|
2025-03-22T14:41:04
|
|
Add Adwaita Mono
|
|
7444f9cb
|
2025-04-22T19:17:01
|
|
font-patcher: Create smaller otf files
[why]
The patched fonts in otf format are much bigger than the ttf
counterparts. Even when the same font is used as source.
The factor is about 2 to 3.5 in size.
[how]
Fonts in ttf format can not store nodes with sub-integer precision. The
coordinates are rounded on export. But otf fonts can have real numbers
(may it be floating point or fixed point notation, I am not sure right
now and it does not matter) for coordinates, but the more precise
numbers take much more space in the font file. If an otf is created
where the coordinates are already integer this extra space is not
needed.
So we do all the calculations with real numbers (including decimals) and
only in the last step the coordinates of the added glyphs are rounded to
integer (i.e. to the EM size grid).
Fixes: #1848
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
c240c95e
|
2025-04-22T17:30:26
|
|
Merge pull request #1849 from ryanoasis/feature/use-unrounded-source [skip ci]
Use unrounded glyphs as source
|
|
5bc55281
|
2025-04-22T15:57:17
|
|
docs: add duytrung as a contributor for bug (#1850)
* docs: update CONTRIBUTORS.md
* docs: update .all-contributorsrc
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
b179e0fc
|
2025-04-22T15:48:53
|
|
CI: Fix broken font-patcher check
[why]
With commit
801fb9fe8 Update CascadiaCode to 2407.24
(PR #1844) we dropped the subdir structure of Cascadia Code.
The workflow file did not follow that change.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
421df25b
|
2025-04-22T15:26:58
|
|
Switch devicons file to otf
See previous commit for explanation.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
d98bcd58
|
2025-04-22T15:19:21
|
|
Switch octicons file to otf
[why]
We construct the octicons font file from the original svgs.
To put them into the font file the svg is interpreted and transformed
into the font coordinate system, and then again scaled.
The resulting font file is then saved as `ttf`, thereby rounding all
coordinates. That font is then used as source for the real patching
process - and will be rounded again (possibly).
The rounding errors accumulate and we should only round once. That means
intermediate fonts need to be `otf`.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
37f53303
|
2025-04-17T00:29:26
|
|
Merge pull request #1846 from ryanoasis/feature/Monaspace1200
Update Monaspace to 1.200
|
|
e092ed7f
|
2025-04-17T00:26:37
|
|
Update Monaspace to 1.200
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
5f579870
|
2025-04-17T00:17:33
|
|
Merge pull request #1844 from ryanoasis/feature/cascadia240724
Update Cascadia to 2407.24
|
|
9b0a1efa
|
2025-04-17T00:09:04
|
|
Merge pull request #1845 from ryanoasis/feature/iosevka3321
Update Iosevka to 33.2.1
|
|
5f17007f
|
2025-04-17T00:01:46
|
|
IosevkaTerm: Update to 33.2.1
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
dc01c4e1
|
2025-04-16T23:58:13
|
|
Update Iosevka to 33.2.1
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
59f91d51
|
2025-04-16T23:52:21
|
|
Update CascadiaMono to 2407.24
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
801fb9fe
|
2025-04-16T23:40:27
|
|
Update CascadiaCode to 2407.24
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
40de7708
|
2025-04-16T22:58:43
|
|
Merge pull request #1842 from ryanoasis/feature/mplus1007
Update MPlus to 1.007
|
|
1b81f7a8
|
2025-04-16T22:56:49
|
|
Merge pull request #1843 from ryanoasis/feature/noto-2.015
Update Noto to 2.015 (only Sans and Serif)
|
|
48bbcfbc
|
2025-04-16T22:48:45
|
|
Merge pull request #1841 from ryanoasis/feature/Martian110
Update MartianMono to 1.1.0
|
|
91d7d8ac
|
2025-04-16T21:47:26
|
|
Update MartianMono to 1.1.0
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
7fe06a49
|
2025-04-16T22:45:55
|
|
Merge pull request #1839 from ryanoasis/feature/InconsolataLGC-1.13
Update InconsolataLGC to 1.13
|
|
0d761ad0
|
2025-04-16T20:44:44
|
|
[ci] Update .gitignore file
|
|
a38af432
|
2025-04-16T22:42:31
|
|
Merge pull request #1840 from ryanoasis/feature/lilex-2600
Update Lilex to Release 2.600
|
|
3275bea9
|
2025-04-16T22:40:21
|
|
Merge pull request #1838 from ryanoasis/feature/Geist-1401
Update Geist Mono to 1.401
|
|
41e0adca
|
2025-04-16T22:38:39
|
|
Merge pull request #1836 from ryanoasis/feature/ubuntusans-1.006
Update UbuntuSans to 1.006
|
|
e6b4febf
|
2025-04-16T22:24:18
|
|
Update Noto to 2.015 (only Sans and Serif)
There is no new version for Sans-Mono (still 2.014).
And of course the ancient Noto Mono is still at 1.000.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
d37f4190
|
2025-04-16T21:56:11
|
|
Update MPlus to 1.007
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
10df54c9
|
2025-04-16T21:35:44
|
|
Update Lilex to Release 2.600
Note that the version in-file is 2.530.
Upstream added Italic and dropped Lilex-ExtraThick.ttf
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
b904ddd8
|
2025-04-16T19:05:59
|
|
[ci] Update FontPatcher.zip
|
|
c6ecdac3
|
2025-04-16T21:03:17
|
|
Merge pull request #1802 from joshestein/atkinson-hyperlegible-mono
Atkinson hyperlegible mono
|
|
177d63e0
|
2025-04-16T18:44:15
|
|
Update InconsolataLGC to 1.13
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
ea736c1a
|
2025-04-16T16:08:14
|
|
Update UbuntuSans to 1.006
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
df47b9c9
|
2025-04-16T18:29:32
|
|
Update Geist Mono to 1.401
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|
2a190fbb
|
2025-04-16T15:55:33
|
|
Merge pull request #1803 from my4ng/master
Update 0xProto to 2.300
|
|
0c2ae970
|
2025-04-16T13:10:04
|
|
Fix typo in issue template
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|