It's actually even easier than shown: You can build an "SVG Font" inside your Inkscape document directly, then load the file _as a whole_ into FontForge for final adjustments and exporting (FontForge will just import the SVG Font table).

Fontforge does not resize the o. Best you can do is design your font with the visual look of smaller letters in mind.

It is the job of the designer, not the app, to know about these things and apply that knowledge.

Dear my teacher, please make us a tutorial on how to create an editable Text Effect with LPE in Inkscape

Yes, font metadata is a HUGE iceberg and there are surprising number of features you can do as part of the font file itself. To start with: - Kerning: This adjusts the spacing between letters, because (for example) a combination of "A" and "W" appears to have more separation than "A" and "M", even if the separation between their logical bounding boxes is the same. - Similarly, you can create glyphs that are larger than their allocated space (which is simply a "width" value). The old DOS "box drawing" characters for example occupy 100% of their defined width and/or height, so that when placed together there is no separation visible between them. - Glyph substitution. You can set up rules in the font metadata that basically say "if glyph X appears next to glyph Y, render glyph Z in place of one (or both) of them". This was mostly intended for letters with diacritics (so that you don't need to define a separate glyph for _every_ diacritic on _every_ letter) but should be functional for general usage, like making glyphs link together the way they might do in handwriting.

Yes, it is kind of a mess, but the upside is you can define glyphs in Inkscape then load the file as a whole into FontForge for further refinement.

The size is based on the page size in inkscape and the em width in fontforge. The letters are scaled so that their “real” size is the same based on those reference sizes.

There is also a typography template in inkscape, I think if you placed a line at the top of that, you could move the guides in such a way that you only need to delete the line after importing.

@@NotRexButCaesar -- The size never matches. The x height and the full height are always smaller than the ones in ff. I wish I could work out what the ff dimensions are so I can make my own inkscape typeface template. Trial and error is getting so frustrating. all I need is the numbers and units. argh !

Glyph design is a large subject in and of itself. But here's an overview: - XY coordinates within a glyph are measured in terms of "em units", an "em" representing the distance between two lines (baselines) of text. A lot of fonts specify 1024 (a power of 2) as their "em height", meaning that every 1024 units on canvas represents one line of text, so your glyphs should definitely be smaller than 1024 units high. - In general, a typical letter should have a "full height" about 70% of the em-height, leaving the rest open to provide separation between lines (because a glyph that occupies 100% of the em-height would pack together vertically with no natural separation between lines). - There is also the "x-height" which defines the height of lowercase letters, if it is different from the full height. Lowercase letters can have distinct glyphs, be "small caps" versions of uppercase, or just be duplicates of the uppercase letters directly. - "Ascender" height refers to how far e.g. stems on lowercase "d" and "h" reach above the x-height. This can be the same (or different) from the "full height" of a letter. Depending on the desired alphabet and/or script style, uppercase letters can have ascenders reaching above the usual full-height. - "Descender" height is the amount that e.g. the tails of lowercase "g", "p", "q", and "y" dip below the baseline. Uppercase letters (e.g. "Q") also have descenders. - Letters with rounded edges (e.g. "o") generally overflow their intended metrics by just a little, to compensate for the rounded edges. Otherwise they'd appear unintentionally smaller than letters with straight edges.

Use the pixel size. For example, the X-height size is 700px. When copied and pasted into FontForge the size will be fixed and does not need to be enlarged or reduced again.

Copy-paste between different programs has always been ... finicky. But it's lovely when it works!

same problem here

ive got the same problem!!! by any chance did you fin d a solution for that problem? id appriciated if you reply

On the FontForge side, when you tell it to generate a font it performs a number of validation checks specifically to alert you to any problems that might prevent the compiled font file from loading.

Try checking your display mode. Go to: View > Display Mode and make sure you have Normal selected

@@LogosByNick thank you so much sir, now it's working

You actually can ... sort of. Under Inkscape's "Text" menu there's a section for "SVG Fonts" where you can actually assign paths to named glyph slots, then you can load the SVG file directly into FontForge. It saves the work of manually copy-pasting glyphs one at a time.

In defense of Nick's approach, as a teacher, it makes sense to ensure the process is accessible - as a first pass - to dip your toe as a total novice. Then you can go deeper into the pool, session by session or video by video. If you throw people into the deep end, guess what? - most will be put off and won't even try font making. ✌️🎊🎉👏

Why not ff?

Why not ff?

It feels a bit clumsy but I've never used anything else and I only use open source software. What do you use ?

@@timetraveller6643 I'm looking for an alternative

@@felipedutra5276 because FF is a pretty obtuse, probably just takes time to get used to though.

There must be a way to choose letter space precisely, not randomly by eye.

@@FAKKER_rap Yes there is. On the FontForge side you can manually specify "left" and "right" spacing (the guidelines on the grid are just a shortcut for doing that), both per glyph and as a default value for all glyphs.