summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorIvan Timokhin <nixpkgs@ivan.timokhin.name>2023-08-20 17:40:34 +0300
committerIvan Timokhin <nixpkgs@ivan.timokhin.name>2023-10-26 22:52:23 +0300
commitefb9f909d6102d8f7eb02c2bec049a391578f6d4 (patch)
tree37a2a4da6012402b0f1ae1543efc1fb4b8a73a71 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent377a39f0a23899132e7fa61eab130547c631896f (diff)
junicode: 1.003 -> 2.001
Release announcement: https://github.com/psb1558/Junicode-font/releases/tag/v2.001 This is a breaking change, at least in font file naming (Junicode.ttf is now Junicode-Regular.ttf). In general, 2.0 adds a lot more font variants and opentype and web font versions of the font. Seeing as backward compatibility is broken anyway, I opted to break it a bit more and change custom install path (`junicode-ttf`) to seemingly more conventional `truetype`; new .otf and .woff2 variants are then naturally placed in corresponding directories. This does *not* affect the `fonts.packages` NixOS option, which rearranges font files anyway, but brings a degree of consistency with other fonts. Both the file renaming and the directory structure change break satysfi, however, so I adjusted its builder accordingly, copying over only those font variants that were also present in 1.0 series.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions