pomax / cff-glyphlet-fonts Goto Github PK

right now the code assumes OffSize 1 on a lot of things, which may need changing when real outline paths are added in. I doubt things need to go past OffSize 2, (the whole point is tiny glyphlet fonts), but it'll be good to make sure the bytecode sets itself up correctly

Hi there, I saw your comment from an announcement of the original Adobe Blank font from years ago. You mentioned:

It might be possible to create a minimal full-unicode font by using format 4 and 12 CMAP entries with full-range segments, both pointing to the non-spacing, non-marking glyph. This would probably give us a legal OpenType font that’s around 1kb. I’ll see if I can play around with that over the weekend. If I can, I’ll put it on github.

Did anything ever come of that? Is that this or one of the other repos here?

Could you explain how to use your tool to generate custom OpenType data URIs? E.g. I would like to replace the word "foo" with a custom SVG path.

I'm looking at your article and the process of generating the OpenType data URI is placed in the uglified generator.js file, so I'm having trouble figuring out how this works.

Maybe it would make sense to provide an API which would enable generating the data URI, e.g.

var dataURI = generate({
    "custom": "M 20 -20 L 20 680 700 680 700 -20 20 -20 M 170 130 L 550 130 550 530 170 530",
    "foo": "…",
    "bar": "…"
});

DICTINSTRUCTION(NUMBER(...)) will generate a [[val]] array, instead of [val]

Hi,

thank for your great A bit of font generation article, it is amazing!

But there is error in downloaded woff font sample. SFNT tables offsets are relatively to TABLE DIRECTORY beginning, while they need to be relatively to WOFF file beginning (see WOFF File Format 1.0)

BTW May I ask one more thing.
Everywhere there is a statement that type2 fonts do allow to use cubic beziers. However, reading Type 2 Chastrings specification I can see charstrings commands for quadratic beziers only. Could you pls, explain

Currently only Firefox seems to accept the GSUB table used in the generated font. Chrome and IE need to accept it too, before this can be considered a correct GSUB table

I'm having a discussion on Twitter about your method of replacing custom words with OpenType ligatures. Would it be possible to add the ligature to the original font so that we don't have to wrap the custom word in a dedicated element like <span class="custom">?

subject says it all.

In order to make the string index smaller, it might be possible to drop strings with a predefined SID, and then refer to lower numbers in the charset.