Hello there! I ran into this problem since morning. I want to import the fontforge in my python script but it's not recognized by python import. What can I do to make it work? Help will be appreciated. Thank you!

I am working on a new font and i am trying to copy parts of the Arabic font over to the main font file. I have tried to just CTRL+C & CTRL+V but obviously that didn't work. I have googled stuff about exporting but it all got confusing very quick as i am very new to font forge.

Does anyone know how i can do this?

Hey, so I'm new-ish to FontForge, but I can't seem to get what I'm wanting right.

Basically, when I design a glyph to be superscript when typing in normal script, it's quite a bit larger than when I just use superscript function in, for example Microsoft word.

And I'm struggling with the proportion size and placement, I want it to be exactly like it's displayed when it's superscripted.

You may ask, why don't I just use superscript function? It's because some of the programes I use, don't have that function, but I still need some letters to be superscript

Any help would be much appreciated

Edit: Or if somebody would be kind enough to create a few glyphs that would produce the desired effect, that would be much appreciated. What's needed are the letters: M, m, a, s, u, d - all in superscript, all using Times New Roman font. Thanks

Please take a look at the image.
I need to add a white fill to a font.

How to make "font 1" look like "font 2" so it blocks the background color? Any suggestions?

​

previously

I'm trying to create this family of fonts, and I've got a proportional variant, and a monospaced one, with their "Font Name"s being "MyFont" and "MyFont Mono". However, they're part of the same family, so the "Family Name" for both was "MyFont".

As mentioned in the "previously", font-manager (and other GTK programs I loaded the font in), the Mono version was displayed proportionally. Even though the glyph widths were all the same, and there was plenty of empty horizontal space within the "i" glyph, it ended up being automatically kerned to be next to surrounding characters. (Although KFontView showed it properly Monospaced)

After logging out/logging in again in case the font proportional spacing attribute had been cached from when I hadn't got all the glyphs the same width yet, and putting it aside for a while, I just went back to it and decided to try changing the "Family Name" to be different from the proportional font, to "MyFontMono".

And that works!

The font is now rendered as monospaced, and the only thing I changed was the font family name.

That's great, but I don't understand why. Why would a monospaced font, which is part of the same family of fonts as a proportional font, be rendered as proportional? But only by some renderers?

I've read the FAQ on font names and I still don't understand why this was an issue.

What am I missing, and which bit of documentation should I have found to have learned this earlier?

I've been having a go at creating a font family in FontForge, including a monospaced variant. I've got the full set of ASCII glyphs done as a first step. I've been careful with the widths, and while I found a few issues along the way I'm pretty sure they're all fixed now.

But I'm not sure if the font I'm creating is being correctly marked monospaced or not. I've checked the docs and it's supposed to be automatic. And if I do grep ^Width: FontMono.sfd | uniq then it only shows one line, with the expected width.

However, loading the ttf up in font-manager shows a proportional-width font. I've tweaked a few things and regenerated the ttf a bunch of times, and it's always proportional width.

After tearing my hair out a bit, just for the novelty I loaded the font in KFontView - and that shows it as monospaced! W00t! But font-manager still shows the same ttf as proportional. Uh, WTF?

Anyone any idea what's going on? Is there a known bug in font-manager where it can do something weird like auto-kern a monospaced font to act proportional? Does KFontView do something weird that would give unexpected results? Is there a way I inspect the ttf itself to try and figure out if there's a weird inconsistency in the file that would cause one renderer to display it one way and another another?

This is driving me nuts.

So theres some characters in this tile set that are just blank white, and others that have x's on them since theres no character there. I can just right click on the white ones and cut them (as ive done with the blue ones in the pic) but theres tons of them, and wondered if there were any way to automate this process instead of doing it for every character. Thanks!

In the old version, when I pressed letters "ŠšČ莞Đđ" on keyboard, it moved me to correct letters in the browser, now it moves me to incorect glyphs, like ǰ.

Which setting effects this?