Not all TTF installed are showing on the font list.

Bug #345436 reported by Lucille
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

I've just installed a font called 'LSD Stencil 1' and it isn't showing on the list in the Text and Font menu. I have installed correctly and opened Inkscape .46 after installing the font, nothing I do will get it to show on the list.

Tags: fonts ui win32
Revision history for this message
LucaDC (lucadc) wrote :

I've noticed the same for the font Symbol that's very useful for placing symbols (indeed...).
Windows XP SP3, 0.46 devel

Revision history for this message
Lucille (l--hambling) wrote :

Sorry I should probably have said I use Win XP SP3 and Inkscape .46 and the beta version of the next version same problem with that version as well.

tags: added: fonts
tags: added: ui
Revision history for this message
goto (gotolaunchpad) wrote :

Using 0.47 here on WinXP SP3 and I'm missing a lot of fonts in Inkscape, which I have installed and show up in other programs.

Revision history for this message
David Winter (davewin1) wrote :

I'm having the same issue. I have a font (attached) that works perfectly with Word, Photoshop, PaintShop Pro, AutoCAD, heck, even 3D Studio. But I can not get it to show up on the font list for InkScape.

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

@David Winter - you don't mention you platform, but if you work on Windows, possibly your issue with the "custom font" is the same as

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

The character palette of Mac OS X lists your font as 'Pi font' (i.e. a Dingbat font). The font 'RCAFSTANDARD' gets loaded in Inkscape 0.48 and later on Mac OS X 10.5.8, but all glyphs are listed in the 'Private Use Area' range of Unicode and cannot be used inside Inkscape without knowing the Unicode or picking randomly one of the glyphs listed in the new 'Text > Glyphs' dialog.

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

… and comparing to what the osx font manager displays as repertoire of the font, I didn't insert any of the glyphs that are actually contained in the font either :/

Revision history for this message
David Winter (davewin1) wrote :

Hi. thank you for your time.

I'm on WindowsXP. The Characters in RCAF Standard are the numbers and upper case characters. A few standard ANSI characters as well such as ), #, and $.

There should be nothing private (I don't even know how you make part of a font private).

As I mentioned, this font works perfectly well with every single Windows Application I've tried so I really do not understand why it would fail on Inkscape unless Inkscape is doing something non-standard with Windows fonts.

I'm not sure what to do to resolve this.

Revision history for this message
David Winter (davewin1) wrote :

Here's the full font with all characters. Works great on all windows apps but this one. I have no idea how to resolve this.

Revision history for this message
David Winter (davewin1) wrote :

Sorry for spamming the bug log, but one other item to mention. My font is not listed on the Text->Glyphs dialog. So there's no way for me to select any "area". I have no idea what happens on a mac, I don't use them.

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

> I have no idea how to resolve this.

You can't resolve it - it's a type of font that Inkscape on Windows can't support yet (and does only partially other platforms).
See bug #165665.

Revision history for this message
David Winter (davewin1) wrote :

Actually I DID resolve it.

The problem was (maybe as you described and I simply didn't understand what you meant) was that the only script of the font available was "symbols". So opened my font editor and added support for Western (Laten1) and set this to the default script type.

Now the font is found in Inkscape. I think the thing that was throwing me off was all this mac information which means nothing to me.

Anyay, regardless, adding the Western support solved the problem.

thank you
David

su_v (suv-lp)
tags: added: win32
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.