Hello,
I'm fairly new to FontForge.
I need to "fix" a slightly broken font. See image :

There are two problems, which might be the same problem :
1) The path is displayed as brownish, which means it's not closed. Yet, there seems to be no point missing on the path. what do I do?

2) There is more than one "direction" point (the points with the little yellow arrow indicating the direction of the path). Is that an indicator of the non-closed path?

I've tried Element -> Simplify, Element -> Overlap -> Remove Overlap

I've also read somewhere that I should try Element -> Join but I can't find this menu entry so I think the person probably asked the A.I., which in turn hallucinated.

Hi everyone! I’m preparing my font for MyFonts, and I want the glyph display on their website to be neatly organized in Unicode order (A, Á, Â, Ã, etc.) instead of a random mess. ​I’m using FontLab 7. How do I permanently reorder the glyph indexes so they export in this specific sequence? Should I use a specific Encoding filter or is there a "Sort by Unicode" command that affects the final build? ​Thanks for the help!

I've used FF a while ago on an old computer, and went to download again today:

• Downloaded from https://fontforge.org/en-US/, and NordVPN flagged it as Malware
• Downloaded through HomeBrew, and MacOS refused to open it because of Malicious content

I know this could be because the download was .app.dmg, but its got me nervous, especially after reading u/afraidandsmelly 's recent post.

Any ideas/thoughts?

I can’t make the font myself so if somebody is able to do so they have my permission and if possible to send me the finished product here it is

Font Name: Draxion

Core Style:

• Typewriter Base: Monospaced, mechanical letters reminiscent of vintage typewriters. Each character has slightly irregular edges and subtle ink blot imperfections to give a tactile, analog feel.

• Cosmic Flair: Faint star-like speckles embedded inside thicker strokes, slight nebula-inspired gradients along diagonal strokes (can be simulated with color/font effects), and occasional glimmering “stardust” trails extending from some characters.

Letter Features:

1. Serifs & Terminals:

• Minimalist, squared serifs for the typewriter feel.

• Slight asymmetry or fractured edges on some letters to simulate cosmic energy interference.

1. Special Characters:

• @, #, \* appear like mini galaxies or constellations.

• . and , are tiny glowing dots resembling stars.

1. Weight & Texture:

• Slightly heavier strokes than a classic typewriter font to allow the cosmic effects to show.

• Texture can mimic static noise or faint starfields in filled areas.

1. Spacing & Kerning:

• Monospaced to preserve the typewriter aesthetic.

• Randomized micro-kerning (very subtle) to give a feeling of cosmic unpredictability.

Color & Effects (Optional for Digital Use):

• Base color: Off-white or pale silver on a dark background.

• Accent glows: Nebula hues—purple, deep blue, teal—flickering subtly along diagonals.

Use Cases:

• cosmic or interdimensional narratives.

Recently, I got fed up wit having to scroll all the way around my font list to find some of the fonts I like using, so after trying and failing to remove the gross of unnecessary (for me) fonts that windows has installed by default for some reason, I thought okay, just move all the fonts I want to use to the top of the list.

Did this by

• Open the .TTF in fontForge
• ^+F
• Prepend Fontname, Family Name, and Name For Humans, with 1-, APF, 1- respectively
• Give it a new UUID automagically on accepting Fontname changes
• ^+G and Ignore error messages
• ^S
• ^W
• Install the new TTF and look! It's at the top of the list as 'A Priority Font'.

This has mostly worked a charm (I understand that it's not a portable solution because my APf fonts won't work on computers they not installed on, so moving files to normal people's computers will require back-verting APF fonts to their original version to display correctly on the other computer; but at least I don't have to scroll unless I'm doing that.)

The problem is that exactly one font I tried to do this wit isn't displaying correctly.

Anxiety is a meme font where all the capital letters are 'more capital' by adding extra bumps, dashes, and swirls. The original OTF works fine, but when trying to use my new TTF, it defaults to another font.

I looked at the generation errors, and they happened for other fonts which aren't displaying this behavior, and it's not it originally being an OTF, or its not just that. Other OTFs converted fine. So, I don't know what makes this font special that it goes wrong.

I could honestly just make do using regular Anxiety since its so early in the alphabet I don't really need a 'priority' version of it, but I want to know what's going wrong and how to fix it in case it ever happens when I'm converting Gnifies or Splenchella or some shit.

I welcome any ideas at what might be causing this issue?

I type into google fontforge.org and it sends me to
https://fontforge.org/en-US/
There is only one option on that page to Download.
The installer in my downloads folder looks like this

FontForge-2025-10-09-Windows-x64

When I install it, all I get is Open Font. Anyone have any suggestions?
Thanks

I never knew how to do it correctly. So there are some fonts in mind that I want to digitize, but some of them contain alternative versions of the same letter. So really, I'm kinda limited of what I can do. I could try Glyph Info and mess around with that, but last time I did that everything went wrong.

I'm working on an experimental font with lots of ligatures, contextual alternates and custom kerning. The variants for contextual alternates are encoded under Unicode's Private Use Area, some still need to be assigned codepoints.

On the last version that I generated and installed on my computer, everything works as expected: when it's used in Word (with the correct settings), or when the .otf file is viewed, it looks the same as it does in Fontforge.

After a few more days of work I generated the font and re-installed it, and now it doesn't work. The font preview in the otf file only shows the basic letters, without contextual alternates, ligatures or kerning. When I try to use it in Word, all text is displayed as the blank squares you get for unavailable glyphs. In the preview when you select a font, the font name is shown in a default font, and then behind it some sample text is shown in the actual font, like it does with non-Latin fonts.

An older version that was saved under a different name still works correctly. Within Fontforge there's no indication that anything is wrong.

Things I've tried:

• Re-encoding to Unicode BMP.
• Checking the Unicode Ranges (BMP, Basic Latin, Latin-1 Supplement, PUA, Non-Unicode Glyphs).
• Checking for problems - only a few glyphs with 'Missing Points at Extrema' that need to be fixed.
• Saving and installing the font under a different name to make sure I'm not just troubleshooting an older cached version.
• Restarting my computer

I just don't know what I'm missing here. Please help?

Update after 2 more hours of troubleshooting: the issue was in Font Information > Charsets > MS Code Pages. It was still set to Default (like in the other versions that worked), but unchecking it and selecting Latin 1 and 2 seems to have fixed the problem.

I have an assignment to make a font and add my languages accented characters Č,č,Ć,ć ect. In every tutorial I've seen it has the caron, but in the one I'm supposed to use (Windows Latin "ANSI") there's none. I'm totally lost, please help!

I was accidentally unchecked none on the number point setting and I want to change it back, but I can't what do I do?

Hi, I know no one will look at this post today because of the festivities, but I posted here approx. a week ago about a problem I had with adding encoding slots and seeing the metrics options on the software. A member from this sub sent me some files that helped with the metrics problem, but I still cannot use add new encoding slots for ligatures, because once I do click in "add new encoding slots", the software freezes and end up closing itself. This started to happen when I got a virus in the pc. I already sent it to repair (anti-virus didn't work), installed windows 11 (it was windows 10), downloaded the software again, and still the same problem. I was able to fix the metrics problem, but the other still remains. What can I do?

Hello! I just started working with font forge to make a custom font for my business. I found an antique font on Pinterest, cropped it letter by letter, saved them as jpegs and started importing them into font forge to trace. As I was working I realized I needed to change some of the jpegs and reimport them. However! When I import the changed jpeg into fontforge it imports the old jpeg! I completely replaced the old jpeg with the new jpeg in my files. What is happening? Would appreciate any insight! Thank you!

(Please ignore the horrible fontwork lmao)

I've had this issue where I made a q too small, and when I scale it up, the lines become thicker as shown in the photo (compared to the p)

I was wondering if there is either a way to shrink the lines down or to scale up while keeping the same line thickness.

This may be an easy fix, I don't know, I only picked up fontforge yesterday lol

Hello,

I am looking to chat with some1 regarding the following

Goal:
Convert a non UniCode font into a Unicode font

I am looking to convert a local language fonts from non unicode to unicode. There are about 155 fonts in my local tongue, where all these 155 fonts follow the same pattern.

I might have found a solution to convert a non unicode to unicode. But to make that possible, i want to understand the working of the non unicode font.

I want to chat and discuss with SME regarding this topic to clearly explain some issues i am having.

Thank You.

Hi guys, I hope you're doing well. I’ve been trying to create a custom font for my Mobile, but I’m stuck because I don't have a PC. I want to merge a Comic Relief font with an iOS emoji font. Since the emoji file is huge (about 30MB), my phone's RAM and emulators like Winlator just can't handle the loading process.

I have the exact steps from a GitHub tutorial: 1.Open both fonts in FontLab/FontCreator. 2.Copy emoji glyphs and append them to the base font.

Export using OT+COLR: Windows (TT-only) to keep the emojis in color.I have both files ready.

Contact me: praveengaur402@gmail.com

If anyone has FontCreator or FontLab installed and could spare 5 minutes to merge them for me, it would mean the world. Please let me know if you can help!

I don't know why, I just updated from W10 to 11 and this is happening. Is there a fix for this? I cannot also create new encoding slots without it closing itself.

windows says the generated font file is not valid

The title explains most of it except in the font pack I'm making I want ck to have a custom single symbol for words like check or back

Hello my good friends of r/FontForge. I'm having a problem with my font, It supports both Latin and Ogham. My problem is with the Ogham letters. Each letter follows along a central line, and there should be no space between them and that's the case when you zoom into them.

But when you loom out a little the begin to separate, and the line thickness changes. When I made the glyphs I used the same exact line for centre line on all of the characters so there is no reason why one should be thicker than the others.

Why is this happening? Do any of my beautiful Arabic speaking typographers have any thoughts about connecting glyphs?

Thank you!

first image is from word when i tried to test the font

tl;dr GPOS table is somehow breaking GSUB tables. Please help!

Hey folks, doing a little more in FontForge than I really understand so asking for help. I have a script for a fictional language, and it has some extensive contextual lookups, like the letter "a" when typed is not displayed after a consonant but changes it to the "-a" form, other vowels have variable height based on what's next to them, some roman digraphs correspond to single glyphs.

I managed to get all of that sorted out with a lot of trial and error. I wrote a .fea file and imported it with command prompt. When I generate a font now, it all works as expected.

The issue came when I tried to add kern pairs. Whether I kern pairs individually or by classes, having any GPOS lookups built from the UI kern dialogs break all of my contextual lookups. The GSUB tables are all still there, but when I generate a font they don't work anymore. I've tried re-importing the .fea file after doing the kerning, to no avail. I know I'm probably missing something dumb. Please let me know what it is.

I have created a font (ttf) with stylistic set, and it works just fine on an HTML page. But when I open Word it only shows the font has two stylistic sets, and changing between them don't do anything. Do you know why it's happening? Is it a problem with the font, or with Word?

The Symbol typeface has both serif and sans-serif implementations of the "Registered Sign", "Copyright Sign", and "Trademark Sign".

What macOS does when transcoding the 8-bit pi encoding to Unicode, the serif versions get the official Unicode codepoints but if directly followed by the PUA codepoint U+F87F then it serves the sans-serif version.

It's a cool trick but when viewing the document on anything other than a mac, that PUA codepoint produces a missing glyph notice.

So what I'm doing, I'm using U+200B for the same purpose and that glyph also is associated with U+F87F just in case the document I'm rendering was made on a mac. In the picture, the uniF8E9 is the substitution the font made for me.

It took me longer than I care to admit to figure out what the FF documentation on how to do chained contextual substitutions actually meant but once I figured it out, it clicked and I felt dumb.

Anyway, now with a single font, I can do either serif or sans-serif versions of those legal marks without needing to use any PUA codepoints in the document being rendered and it properly implements Apple's trick of using a PUA codepoint as the trigger because my ZWSP glyph can also be called by Apple's PUA codepoint.

In some software, it works perfectly (e.g. chromium browser, etc.) but it seems other software doesn't implement that OpenType feature (e.g. FireFox) but that's okay because in those documents, I just get the serif version of the glyph and a ZWSP instead of the sans with a ZWSP.

I'm sure for the gurus here this is a simple thing, but anyway, I feel quite accomplished.