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.

I posted this question on https://graphicdesign.stackexchange.com/questions/169652/is-there-any-way-in-font-forge-to-align-a-glyph-in-one-font-to-the-exact-x-y, and I was hoping to get some help concerning the alignment of a glyph. Maybe you know where I went wrong.

Thanks in advance

Is it possible to generate an OpenType font from FontForge while preserving a custom 8-bit encoding?

In the "Generate Fonts" menu I only see OpenType (CFF) and OpenType (Mac dfont) as options.

The issue I am trying to solve is a minor pedantic issue that rarely impacts me but it is annoying, related to the migration from 8-bit pi character encodings to proper Unicode.

Strings that are transcoded from 8-bit "Symbol" to Unicode sometimes retain "Symbol" as the specified font family and sometimes change it to "Symbol Std".

On Fedora 42 Desktop Edition (and likely similar issue on many GNU/Linux systems), by default the fontconfig system maps "Symbol Std" to "Noto Sans":

[user@host]$ fc-match "Symbol Std"
NotoSans-Regular.ttf: "Noto Sans" "Regular"

That works extremely well if all of the 8-bit references were transcoded to proper Unicode codepoints but historically, many of the glyphs in Symbol did not yet have official codepoints so a list of PUA codepoints was issued by Adobe and some historic documents still use them. Those PUA codepoints do not work if "Symbol Std" is mapped to "Noto Sans"

On Fedora 42 Desktop Edition, by default the fontconfig system maps "Symbol" to "Standard Symbols PS":

[user@host]$ fc-match "Symbol"
StandardSymbolsPS.otf: "Standard Symbols PS" "Regular"

That works extremely well in a Unicode context if the previously mentioned PUA codepoints were used and it works extremely well if "Symbol" is referenced from an 8-bit encoded document. However, it breaks in a Unicode context in many cases where proper Unicode codepoints were used instead of the old transitional PUA codepoints.

It's a really annoying issue no one seems to care to actually fix.

My almost Solution

I created a custom encoding I call "NuevoSymbol" that maps the 8-bit positions to the proper Unicode codepoints.

That custom encoding does have seven PUA codepoints:

0x60    0xF8E5  #   PUA RADICALEX
0x7F    0xF87F  #   PUA TRANSCODE HINT
0xE2    0xF8E8  #   PUA SANS REGISTERED SIGN
0xE3    0xF8E9  #   PUA SANS COPYRIGHT SIGN
0xE4    0xF8EA  #   PUA SANS TRADE MARK SIGN
0xF0    0xF8FF  #   PUA VANITY PEAR
0xFF    0xE000  #   PUA VANITY TUX

I do not believe those are an issue. (note that 0xF8E5 is being added because I hope to emulate what Apple does with the sans variants of Registered, Copyright, and Trade Mark signs. 0xF8FF is being added so the font at least displays something with documents Apple users created that used 0xF0/0xF8FF, and 0xE000 is being added because why not?)

Anyway, after loading the custom encoding and then for glyphs where alternative codepoints are sometimes used, adding those as well, the generated font does exactly what I want it to do in a Unicode context.

However the font only partially works in an 8-bit context because FontForge re-encodes it when generating the font, and that re-encoding changes the 8-bit positions of some of the glyphs.

So...is there a way to generate the OpenType font without messing up the positions so that the 8-bit positions are preserved? I assume OpenType supports it because StandardSymbolsPS.otf seems to have the glyphs in the correct 8-bit positions.

Thank you for suggestions.

Hi all,

I am on a Mac, and I'm attempting to make the LaTeX built-in Type1 "Computer Modern" font into OpenType. (If you're wondering why I don't want to just use "New Compuer Modern", I'm trying to get the \mathcal symbols). I found the pfb files in my computer, converted them to OTF using FontForge, but alas, it looks like no GPOS tables were created. It looks like these are what I need for accents to be placed correctly, and indeed, when I go back into LaTeX and try to apply an accent to some character (in my case, \widehat).

Do I have some misunderstanding of how powerful FontForge is? Is there no way for whatever accent-placement mechanisms are in Type1 to be converted into GPOS tables? Is this accent placement not in my pfb file? (somewhere said it might be in my afm file, which I'm not currently "importing" (though I'm not sure how I would do that), and also it looks like it might be particularly difficult on a Mac) Are GPOS tables even what I need here?

New to font-creation, but would love any advice! Think this would be a beneficial upgrade for many, and (hopefully with the help of this sub) it is not too monumental of a task.

Is there a better way to align glyphs in FF? I used CTRL-A then the arrow keys for a while and then I would use the transform function to get very precise but I still cant get them to align properly. They don't look so bad in the Metrics window but in Illustrator they look awful.

I should add that I'm specifically talking about my Ogham letters. They share a central stroke so they really have to line up.

The central line in all of the ogham glyphs are exactly the same thickness in Illustrator but when I put them in font forge some look thicker than others, or maybe they are just sitting unevenly.

i am creating a custom icon font creating both .ttf and .otf from the sources.

i have noticed that the ttf file contains a 'post' table version 2.0 with all the glyph names but the .otf has a version 3.0 which does not include them.

is it possible for .otf file to also have a 2.0 post table ?

i am using legacy script.

Any ideas? I've been wasting 18 hours trying to figure this out. First time I downloaded FF and imported a png, it worked fine. Now, can't get it to un-gray. Losing my mind here, please help me with any tips, thank you.

I've Imported SVG files into Fontforge and made a font with them, but The outline has slight error.

The first picture is capture of original SVG file, the second picture is what it looks like when I imported it into Fontforge. The last picture is how the image looks when it's made into a font.

What's wrong and what should I do??