Font Forum

Ah, yes, I wish I had version 10, but I haven't been invited to the beta testing for awhile now.

But I'm glad it works now!

Actually, they know about it. See here in this dev thread for texlive . Problem is that they aren't sure how to solve it. I'm actually surprised this is a problem, but it is! And I don't want to use another font manager. I have used and tested for MainType for awhile now! My heart's already here and...

Well, is there a way to make MainType install fonts by copying them into the Windows Font Folder instead of using shortcuts? Neither TexLive (lualatex) nor Lilypond can read fonts that are installed via shortcut. So I am forced NOT to use MainType as a font manager and if I want to use any fonts wit...

What and where is the "system font table"? I can't find it by googling.

I beg to differ. In my own screenshot you can see that the path is not c:\windows\fonts. But the folder that is open in Windows Explorer IS c:\windows\fonts. You can also see the little shortcut icons on the icons that are not in c:\windows\fonts. Oh - I think I understand what you mean: If I open c...

Mr. Denissen,

Really? My C:\fonts folder is full of shortcut files pointing to font files installed by MainType. I only use MainType to install fonts.
You can see my screenshot.

The target of the shortcut is one of the folders used by the MainType library.

Okay, so texlive CANNOT read fonts that are installed via shortcuts. Check this thread: https://github.com/lualatex/luaotfload/issues/270#issuecomment-105914058 They are marking this as a wontfix unless someone makes a patch for them. So, is there a way to have MainType not use shortcuts to install ...

On my computer I use TexLive (lualatex) which is able to use fonts that are installed on the computer. But I am having trouble with getting it to use fonts that are installed via MainType. When I go and explore c:\windows\fonts, I discover that the fonts installed by MainType are done via shortcut. ...

Okay, well, I finally fixed the font (thank you, Mr. Denissen, for your help).
I did change the em-size to 1000 using the procedures you all posted above.

But what really fixed the problem was exporting the font with CFF outlines instead of TrueType outlines.

Okay, well, something is causing my MainType to malfunction, then!

So, I had to restart MainType. Now it's working correctly. Must have been something in the sequence of install/delete that caused the hangup.

Erwin,
Okay, now switch between those fonts and see if the Font Properties *Panel* changes.

Working with FontCreator and MainType, I updated my font and adjusted the em spacing from 2048 to 1000 and the font revision from 1.305 to 1.306 and then exported the font. Then in MainType I refreshed the library and pulled in my new font. However, when I view the font's properties in MainType - fo...

Okay, the cut and paste trick worked well for resizing the em spacing. The general and metrics settings look about the same now in my font as they do in the one my friend edited in FontForge. However, my font still won't embed properly - it keeps giving the error. But my friend's font works just fin...

So, in the end, you can use the extensions interchangeably. But it is good practice to use .otf if you include opentype layout features, and .ttf if you don't. This sounds reasonable.
Why doesn't FontCreator switch the extension to .ttf automatically if you don't export the opentype layout features?

We figured this out! So, I am using LaTeX to create a pdf using a particular font. The pdf opens just fine. But when I PLACE that pdf in InDesign and export it as a pdf, I get this error: screenshot_Adobe Reader (Adobe Reader ) [AcroRd32]_022.png I sent the font to a friend, and they adjusted the em...