I've been trying to fix an issue for some time, and I'm hoping someone here can give me some pointers.

I have two symbol fonts that I need for some specific designs. The fonts are TTF, and have worked in a previous version of Inkscape on a different computer. I'm using Windows 10.

The problem is: I can select the fonts from the font drop down menu, but when I do, the text isn't effected.

I have checked the file source code, and the font is applied to the source. When I view the SVG in my browser, it looks fine. I have also tried to manually write an SVG file with the fonts, which also displays fine in my browser, but which displays the default font when loaded into Inkscape. I have tried to upgrade Inkscape to the newest version and to uninstall and reinstall the fonts, which didn't work.

Any help of this issue would be much appreciated. My only alternative to using these fonts would be to re-draw all the symbols (about 150 highly detailed ones) manually, which I would be quite sad to have to do.

Any chance that you are using a third-party font manager?

What Version of Inkscape do you use? 0.92.0 ?
I observe similar behaviour on Win7/64 wíth Inkscape 0.91, but not with Win7/64 Inkscape 0.92.0

Edit:
The Symbol Font where I observed the similar thing is Windows Latin (ANSI)-enconded.
If I create a copy of that font and load it into FontForge (https://fontforge.github.io) and force it to be encoded in Unicode, I can see this font even under Win7/64 and Inkscape 0.91
So, apparently something changed from 0.91 to 0.92 about handling of non-Unicode Fonts.

Thank you for your answers so far.

Mr. Durden
Nope, just the vanilla Windows 10 font folder. I didn't even know it was a thing until now.

theozh
I had the issue with 0.91.?, so I installed the 0.92.0 r15299 version.

I downloaded FontForge, and it looks like you are on to something (see warnings below). Being unfamiliar with working with fonts (another thing I'd love to look in to - if only I had an infinite amout of time ), I'm uncertain as to how to proceed. When I select 'Encoding' and 'Compact', it displays the symbols starting from F020 as discribed in the table (see below).

Is there an easy fix to this in FontForge, or will I have to re-map the symbols manually (and if so, how)?

Warnings

The following table(s) in the font have been ignored by FontForge
Ignoring 'PCLT' PCL 5 data table
Ignoring 'hdmx' horizontal device metrics table
Use of a range offset of 0xffff to mean a missing glyph in cmap table
Windows will reject fonts with an OS/2 version number of 0
The glyph named space is mapped to U+F020.
But its name indicates it should be mapped to U+0020.
The glyph named exclam is mapped to U+F021.
But its name indicates it should be mapped to U+0021.
The glyph named quotedbl is mapped to U+F022.
But its name indicates it should be mapped to U+0022.
The glyph named numbersign is mapped to U+F023.
But its name indicates it should be mapped to U+0023.
The glyph named dollar is mapped to U+F024.
But its name indicates it should be mapped to U+0024.
The glyph named percent is mapped to U+F025.
But its name indicates it should be mapped to U+0025.
The glyph named ampersand is mapped to U+F026.
But its name indicates it should be mapped to U+0026.
The glyph named quotesingle is mapped to U+F027.
But its name indicates it should be mapped to U+0027.
The glyph named parenleft is mapped to U+F028.
But its name indicates it should be mapped to U+0028.
The glyph named parenright is mapped to U+F029.
But its name indicates it should be mapped to U+0029.
The glyph named asterisk is mapped to U+F02A.
But its name indicates it should be mapped to U+002A.
The glyph named plus is mapped to U+F02B.
But its name indicates it should be mapped to U+002B.
The glyph named comma is mapped to U+F02C.
But its name indicates it should be mapped to U+002C.
The glyph named hyphen is mapped to U+F02D.
But its name indicates it should be mapped to U+002D.
The glyph named period is mapped to U+F02E.
But its name indicates it should be mapped to U+002E.
The glyph named slash is mapped to U+F02F.

Unfortunately, I am as well not too familiar with FontForge and all its details and options, but what simply worked for me was
1) load Font
2) Ignore all warnings
3) Menubar | Encoding | Force Encoding | ISO 10646-1 (Unicode,Full)
4) Menubar | File | Make the font (or Ctrl+Shift+G) and select TrueType
5) Ignore all warnings or errors
6) in Windows install the font by double clicking and replacing/overwriting the old one
No guarantee that this also works for you...
Don't forget to keep somewhere a separate copy of your original font which you can re-install if something goes wrong.
I assume (and I would understand) that you probably prefer not to publicly share your font for testing?!

I tried to enforce the encoding, but it didn't work. Ended up manually setting the Unicode value for each glyph, which did the trick. Really odd error, but at least now I can use my font again!

You can see the full font here (I have a licensed version to allow me to create derivative works). As you can imagine, re-drawing these symbols would have been quite a pain: http://www.dafont.com/tanks-ww2.font

Thank you very much for your help - you've saved me a bazillion hours of frustration!

...glad, that I could help
Still it's strange, because I had a similar issue with Inkscape 0.91 but which seems to work under 0.92 without the need of re-encoding.
If the problem is satifactorily solved for you, I encourage you to put [solved] in front of your first post title, so that people browsing/searching the forum titles easily see "no further help needed" and people with a similar problem can expect a "working" solution.

theozh wrote:If the problem is satifactorily solved for you, I encourage you to put [solved] in front of your first post title, so that people browsing/searching the forum titles easily see "no further help needed" and people with a similar problem can expect a "working" solution.

Done. Thank you again!

I don't think it's really necessary for people to mark their topic solved. There is plenty of functionality in the forum, to help you know which threads still need help, and which ones don't.

Did you ever notice that tiny red square in front of the topic title? If you click that, it will take you to the first new message in that topic, that you haven't already read. If there's no tiny red square, there is no new message in that thread, since the last time you looked at it. So if a topic is solved, there will be no tiny red square.

If you click on Quick Links up near the top, there are several more convenient options for browsing the forum, besides using the tiny red square. Personally, I use Unread Posts, together with the tiny red square. Essentially it only shows you topics which have a new message. If a topic is solved, it will not appear in that list, because there will be no new messages. Or there might be some other option in the Quick Links, that you prefer to use.

As for future visitors being able to expect a working solution, that's really quite relative. A solution for one person is not necessarily a solution for anyone else. Especially with Inkscape working on 3 different operating systems, with different issues and bugs and features for each one. This forum doesn't even tell us which kind of system someone is using. People looking for a solution will be more likely to use the forum search, rather than read down the pages and pages of topics. And if I see a topic marked solved, in a search I performed, I would not automatically think I had found a solution, until I read the whole thread. There are just way too many variables to think one person's solution will be my solution.

To be honest, I have a beef about forums which require users to mark their topic solved. If there were some mechanism to prevent people from posting into topics marked solved, then it might make sense. But there's nothing like that here, and I haven't actually heard of it in any open source forum software (unless the admin was a programmer who wrote her own custom mod). People post in topics marked solved all the time. Just like I'm doing now. Hhm....I guess this means you might not see it though?? Well, for whatever it's worth

This issue is solved for the original poster. Marking it as such is a service to others that at least one solution was found.

If the solution does not work for others, they can post a new topic that references this topic as related, but not a solution in their case.

They can, but often they won't. Often as not they'll post again in the old topic.