Inkscape doesn't recognize some fonts installed on the system

Bug #887327 reported by tobias b köhler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Confirmed
Undecided
Unassigned

Bug Description

I am running Inkscape under Windows 7. I have installed a symbol font "ExtraS R" (self-made with FontLab Studio 5) which is recognized by other programs, such as OpenOffice.org, but not by Inkscape (it does not show up in the font menu at all and PDF documents containing text in the symbol font are converted to a standard font upon loading in Inkscape).
I am sending the symbol font as an attachment.

Tags: fonts win32
Revision history for this message
tobias b köhler (tbk-uncia) wrote :
Revision history for this message
su_v (suv-lp) wrote :

Duplicate of Bug #165665 “non-Unicode symbol fonts do not work on Windows”?
<https://bugs.launchpad.net/inkscape/+bug/165665>

tags: added: fonts win32
removed: font
Revision history for this message
su_v (suv-lp) wrote :

Not reproduced with Inkscape 0.48.2 on Mac OS X 10.5.8 (i386)
(screenshot attached)

Revision history for this message
Alvin Penner (apenner) wrote :

- confirmed on Windows XP, Inkscape build 10728.
- attached is a list of other fonts on XP that are not recognized by Inkscape, although they are useable by other programs such as Microsoft Word.

bssym3.ttf, cityb___.ttf, compi.ttf, counb___.ttf, panroman.ttf, supef___.ttf, symbol.ttf, technic_.ttf, webdings.ttf, wingdings.ttf.

These fonts all appear to have at least one thing in common, they are all reported as being of Family Class either 'symbolic' or 'no_classification' when they are viewed using the font program 'dp4 Font Viewer 2.0' which is available free from:
www.fontviewer.de

Changed in inkscape:
status: New → Confirmed
Revision history for this message
su_v (suv-lp) wrote :

Linking as duplicate to bug #165665 “non-Unicode symbol fonts do not work on Windows” - please add a comment here and revert the duplicate status if you don't agree and think these are different issues.

Revision history for this message
Alvin Penner (apenner) wrote :

@tobias - if you have access to this type of information in FontLab, then you might want to try setting the Family class to 'sans serif' to see if this helps.

Revision history for this message
su_v (suv-lp) wrote :

@alvin - see tobias' comment (#6) to bug #239631 (another duplicate of bug #165665): the workaround apparently is to change the character encoding of the custom symbol font.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.