FontForge retweeted
The MFEK Foundation is now maintaining sfdLib, a @FontForge library primarily for converting SFD fonts to UFO (but which is easily extended to support non-UFO formats) originally by @KhaledGhetas (thank you!).
@fr_brennan just made its first PyPI release: pypi.org/project/sfdLib/
Replying to @andrew_shadura @dubovsky_jan
Yes and you could check them into Git so even if FontForge wrongly deletes them you can reclaim them.
Replying to @dubovsky_jan
This does happen, unfortunately.
There could be some autosave data in your Config directory, probably in .config/fontforge of your user home directory. If not there's not much more to be done unless you may have a backup of that directory during the time you were working.
If you work a lot with SFD files, there is now a tested Python library for encoding/decoding the quoted strings in them.
sfdutf7·py — github.com/ctrlcctrlv/sfdutf…
PyPI: pypi.org/project/sfdutf7/
~ @fr_brennan
This is the most horrifying code I've ever written.
Thanks for the IMAPClient implementation @mjs0 lol
github.com/ctrlcctrlv/sfdutf…
Replying to @fefodois
"perfeito" ... no. Not even a little!
How about "sometimes adequate"? That seems about right.
Replying to @FontForge @RatanKarna
(Oh, also, this is @fr_brennan, this is a shared account. I wasn't answering the one who first answered you. Hi.)
If my idea to use dev2{dflt} for 'pres' 19 does not work you're probably going to want to make a GitHub issue, there are limits to what can be solved via Twitter. 🙇
Replying to @FontForge @RatanKarna
I also don't understand why you only specified non-dflt languages for 'pres' lookup 19.
Stick to {dflt} unless you've a good reason, there's no reason you'd ever need a set including {dflt} as {dflt} is the set of all languages for the script.
Replying to @FontForge @RatanKarna
Meanwhile 'pres' lookup 11 looks alright to me, although you probably can cut latn{dflt}.
You can't mix dev2 and deva like this and expect it to work.
Also, I must caution you, Indic shaping is likely broken in MetricsView. Please rely on HarfBuzz. Cf github.com/fontforge/fontfor….
Replying to @RatanKarna
I took a look. Sorry to tell you I'm not an expert in Indic shaping, which uses very different (script-dependent) rules than normal OpenType shaping.
However I still may know what's wrong. Only the lookup marked 'pres' Pre Base Substitutions lookup 19 has this strange metadata:
③ Maybe someday ufo2ft will support it so `fontmake` can just build a font that has SVG data in its .glif files.
Workarounds for SVG-in-OT:
① You can try a script called SVGinOTlayersCompositor·py by @glukfonts: github.com/glukfonts/SVGinOT…
② You can use @FontTools ttLib class `table_S_V_G_`, passing `<svgDoc>` elements to `font["SVG"].fromXML("svgDoc", …)` as a post-processing step.
By "SVG font", FontForge means the outmoded SVG 1.1 standard, *not* SVG-in-OpenType, a type of OpenType font which contains SVG files for its glyphs, which it cannot yet create.
And, even its SVG 1.1 support has issues, cf. e.g. github.com/fontforge/fontfor….
Workarounds below.
If you've ever tried to use FontForge in Wine you may have found you had no keyboard input.
A workaround is now available: github.com/fontforge/fontfor…
One shouldn't need FontForge in Wine, this is mostly of interest to developers or those wanting to use Windows-only Python code.









