the problem is not how to build a variable CFF2 font, varLib does that already; it's how to cut static instances from it, ideally as CFF 1.0 fonts
of course not. I just mentioned Adobe is likely to have tools to instantiate or remove overlaps from CFF2
at the moment I don't have the time to work on it, maybe somebody else will
Hey folks, I'm new to programming in general.
I would love to get some pointers related to font subsetting, which I believe is the way to embed only the required glyphs to
More concretely, how would one go about font subsetting for truetype, type3, type42 fonts. (which I believe are different ways to structure fonts, and if I'm not wrong one could delegate this task to
(also it'd be completely fine if one were to point out any mistake or conceptual problems with what I want to achieve)
I would love to get some pointers related to font subsetting, which I believe is the way to embed only the required glyphs to
pdf or svg or ps output.More concretely, how would one go about font subsetting for truetype, type3, type42 fonts. (which I believe are different ways to structure fonts, and if I'm not wrong one could delegate this task to
fonttools)(also it'd be completely fine if one were to point out any mistake or conceptual problems with what I want to achieve)
hi! have a look at fonttools' pyftsubset. i don't know if type3/42 is supported
of course COLR right now means COLRv0, for v1 you'd have to wait..
v1 will come in due course, don't know nor I can say when
you may as well try and see if it works, if you know how to. I don't
I never built an android app so I would not know how to embed a font in it. If you do know, you can try and check if it works.
or check again later, I asked a colleague in california but they are sleeping right now
We have an older document(https://www.iconfont.cn/help/detail?helptype=code), but I have never developed an Android client 😂🤣.
I asked a couple people, both were not sure, they said it should be supported but they would not know offhand
you'd better try out yourself
The bad news, Apple may not support COLRv1 in a short time
To be honest, their own support for svg in ot is also terrible.
Not supporting <use> increases the font file size and also increases the development cost of open source tools. googlefonts/nanoemoji#266
(for context, this is me with working code for ttLib wanting to avoid the need to cycle type-1 fonts through makeotf solely to make them readable. On the plus side, all I do with them is read them; I don't need to build any type-1 binaries...)
Cool; thanks!
Font stuff would sure be a lot easier without all the corner cases.
(I dunno if anyone else has noticed that.)
🚀🚀🚀
yes, it's impressive! haven't had a chance to dig into it yet though
