Bug#982468: [Pkg-fonts-devel] Bug#982468: fonts-noto-color-emoji: U+1F52B PISTOL shows a water-spraying toy instead

For a little more context, see discussion at https://github.com/googlefonts/noto-emoji/pull/213. In particular note that this design upstream (i.e. in Noto) is actually motivated by a need to be consistent with Apple, which made the change from pistol to water gun about two years earlier. In this c

Bug#978365: [Pkg-fonts-devel] Bug#978365: fonts-inter: FTBFS: fontmake: Error: In 'src/Inter.glyphs' -> 'master_ufo/Inter.designspace' -> 'master_ufo/instance_ufo/Inter-Thin.ufo': Compiling UFO failed

Here's a bunch more context on this failure: https://github.com/rsms/inter/issues/184 https://github.com/googlefonts/fontmake/issues/581 https://github.com/rsms/inter/issues/200 https://github.com/rsms/inter/issues/210 I'm surprised the fonts-inter package is still using fontmake directly instead

Bug#950405: python3-fonttools: warning SyntaxWarning: "is" with a literal. Did you mean "=="?

This was fixed upstream two days ago: https://github.com/fonttools/fonttools/commit/39b02fd2240325af1261d1b57733edbb001d50ea but a new fonttools release has not been made yet.

Bug#900777: fontmake: fails to rebuild fonts-firacode from its glyphs source

Aha! I didn't have the correct versions of the dependencies as packaged in sid. Your error is the same as in the original email. The error "Glyph psili cannot be in both @MC_top and @MC_topleft" I believe was fixed by https://github.com/googlei18n/ufo2ft/pull/276, and should not occur with ufo2ft

Bug#900777: fontmake: fails to rebuild fonts-firacode from its glyphs source

Hm, I'm unable to reproduce this error with fontmake 1.6.1 and the latest version of FiraCode from https://github.com/tonsky/FiraCode. My output: $ fontmake -g FiraCode.glyphs INFO:fontmake.font_project:Building master UFOs and designspace from Glyphs source INFO:glyphsLib.classes:Parsing "FiraCod

Bug#900777: fontmake: fails to rebuild fonts-firacode from its glyphs source

It's possible that this font actually contains illegal feature syntax, which is still accepted by Glyphs. Or of course it could be an issue with some component of fontmake; it's worth posting an issue on Github to have it triaged (I was planning to do this soon when I have time).

Bug#900778: fontmake: fails to build fonts-comicneue from its ufo sources

Looks like this is already fixed in the latest version of fontmake (release 1.5.1, commit 90b0534620d74180f63501d0c8a03a190ce493f8).

Bug#900777: fontmake: fails to rebuild fonts-firacode from its glyphs source

I filed this upstream here: https://github.com/googlei18n/fontmake/issues/445

Bug#865283: fontmake

I was happy to have just now found this thread, while making a table of fontmake and all its dependencies at https://wiki.debian.org/Fonts# Font_Tools. RFPs have now been filed for all of fontmake's dependencies, so now I suppose the only thing to do is create those packages. -- James Go

Bug#868006: RFP: ufo2ft -- A bridge from UFOs to fonttools objects

Package: wnpp Severity: wishlist * Package name: ufo2ft Version : 0.5.3 Upstream Author : Tal Leming * URL : https://github.com/googlei18n/ufo2ft * License : MIT Programming Lang: Python Description : A bridge from UFOs to fonttools objects This library

Bug#868005: RFP: glyphsLib -- Library for opening and converting Glyphs font sources

Package: wnpp Severity: wishlist * Package name: glyphsLib Version : 1.7.5 Upstream Author : Google Internationalization Team * URL : https://github.com/googlei18n/glyphsLib * License : Apache-2.0 Programming Lang: Python Description : Library for openin

Bug#868004: RFP: cu2qu -- Python library for cubic-to-quadratic bezier curve conversion

Package: wnpp Severity: wishlist * Package name: cu2qu Version : 1.2.0 Upstream Author : Google Internationalization Team * URL : https://github.com/googlei18n/cu2qu * License : Apache-2.0 Programming Lang: Python Description : Python library for cubic-t