id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
18442	Should we delete fontforge ?	ken@…	blfs-book	"ISTR that in the distant past we needed fontforge for a kde-related font, and later I used fontforge in my 'font analysis' (show the glyphs in a font) as the only practical way to extract a ttf file from a ttc collection. That was years ago, I've only just come back to doing font analysis and I've now found that the ttc format has become uncommon for freely-available screen fonts.

Looking for the current versions of fonts I previously looked at which were in a ttc (NotoSansCJK and the Mono equivalent) they are either in language-specific ttfs, or (for Mono) no-longer maintained, but with some ttf files available elsewhere.

At the moment I have the original zip file for NotoSansCJK-Regular.ttc, and  I can extract one of the language variants to a ttf. But for the current versions I do not need to do that.

The background to ttc files is covered at [https://fontsaga.com/ttc-file-extension/?expand_article=1] and there are apparently now perl modules to extract a ttf from a ttc [https://metacpan.org/pod/Font::TTF::Ttc] and Python tools [https://fonttools.readthedocs.io/en/latest/]

I'll be tagging fontforge when I've checked a few other things, but it seems to be such a niche product that I find it hard to believe any BLFS users actually use it. "	task	closed	normal	12.1	BOOK	git	medium	wontfix