trunk (win32): Adobe Type-1 fonts not found

[Alfred Bergkemper]

Translation:
------------

Inkscape 0.48+devel r11515
Windows XP with all updates

When loading a larger document created with Inkscape 0.48.2 in latest trunk build, some fonts are no longer rendered correctly.

The issue is reproducible.

The attached file renders the texts on the left side in Inkscape 0.48.2 with the assigned fonts as expected, in current trunk all fonts look similar to 'Arial'.

Original text:
--------------
Hallo,

Inkscape 0.48+devel r11515
Windows-XP mit allen Updates

beim testweisem Laden einer größeren mit v48.2 erzeugten Datei ist aufgefallen,
dass einige Fonts nicht mehr richtig dargestellt werden.

Der Fehler ist reproduzierbar.

Die angehängte Datei zeigt in v48.2 auch links alle Schriften korrekt, in der Testversion
sehen alle Schriften ähnlich wie Arial aus.

[su_v (suv-lp)]

Not reproduced with Inkscape 0.48+devel r11515 on OS X 10.7.4
(based on the provided sample file with the two fonts 'Hobo BT' and 'Reporter-Two' installed)

[Alfred Bergkemper (a-bergkemper)]

It seems that all of my installed Adobe Type-1-fonts are missing in the font list.

[Alvin Penner (apenner)]

what is the file extension name on the Type 1 fonts?

[Alfred Bergkemper (a-bergkemper)]

All of the missing fonts use *.pfb as file extension name.

[Alvin Penner (apenner)]

thanks, that explains it for me. I do not have any such fonts on my machines, one Windows 7 and one XP.
I did download the font Hobo BT.ttf and as far as I can tell, it is working perfectly with Inkscape. However, that is probably because it is ttf.

I have noticed a difference between Inkscape 0.48.3.1 and recent trunk, which may or may not be relevant here. I do not have the font Reporter-Two installed on either of my machines. In Inkscape 0.48.3.1 when I load your file and click on Reporter then the status bar at the bottom reports that the fontname is Sans. This is very useful because it tells me the font does not exist.

When I do this in recent trunk build, then it tells me that the font is Reporter-Two which is not true because that font does not exist on this machine.

[su_v (suv-lp)]

> It seems that all of my installed Adobe Type-1-fonts are missing
> in the font list.

I don't have the two fonts used in the sample file available as Adobe T1 fonts either (like Alvin I had to test it with ttf fonts offered as "free" downloads on the web). However, other T1 fonts are found and used by current trunk builds (with pango 1.30.1) on OS X 10.7.4 without problems (tested e.g. with URW fonts, and those T1 fonts shipping with X11).

(Probably unrelated note: With the quartz backend of GTK+ and pango (CoreText), Inkscape trunk uses those T1 fonts on-canvas just fine, but the font preview in the 'Text & Font' dialog reverted to a different fallback font (not an issue with the X11 backend of GTK+ and pango). This is probably an upstream issue (pango +quartz), but indicates that Inkscape accesses font information differently in different locations)

[Alfred Bergkemper (a-bergkemper)]

I have installed many fonts and I think, both trunks have problems.
I didn't notice this before.

In the attached picture you can see part of my fonts shown in both trunks.

On the right side there is the list of Inkscape 0.48.3.1 r9886 with type-1-fonts like Helvetica etc.

[su_v (suv-lp)]

Regression on Windows possibly due to the changes for bug #165665:
<http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/10742>

From the discussion on the mailing list prior to that commit:

On 13/11/2011 21:34, Richard Hughes wrote:
> On 2011-11-12 at 21:57, Alvin Penner wrote:
>> ref : https://bugs.launchpad.net/inkscape/+bug/165665
>>
>> I believe this bug can be fixed by disabling the flag USE_PANGO_WIN32 in
>> line 19 of src/libnrtype/FontFactory.h. (…)
(…)
>> Would there be any objection if I disable this flag, or does it serve a
>> specific purpose that is essential?
>
> I put that in (several years ago) because of a large number of
> problems encountered trying to use fontconfig on win32. From memory,
> these included:
>
> - Extremely slow application startup (with no visual feedback) on
> systems with a non-trivial number of fonts installed
>
> - Lack of access to Type 1 fonts
>
> - Poor integration with OS font management, meaning the fonts
> available to Inkscape were not necessarily the same as those available
> to other apps
(…)

</quote>
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/37630/focus=37631>