[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Invalid postscript generated from simple Ink
From: |
Riccardo Mottola |
Subject: |
Re: Invalid postscript generated from simple Ink |
Date: |
Mon, 18 Jul 2016 23:29:07 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 |
Hoi Fred,
I tested your commit, but it does't work for me. Ghostscript displays
everything in a genric font.
I think the issue is the name itself. IN the PS I see:
/DejaVuSans-(null) findfont [12 0 0 -12 0 0 ] makefont setfont
I suppose the (null) part in the postscript name is not correct.
I tried to print a document with many fonts, and they all look to have
the same error:
/DejaVuSans-(null) findfont [12 0 0 -12 0 0 ] makefont setfont
/CenturySchoolbookL-(null) findfont [12 0 0 -12 0 0 ] makefont setfont
/URWChanceryL-(null) findfont [12 0 0 -12 0 0 ] makefont setfont
and so on. Looking at our code, the postscritName suffix should be the
face., perhaps if we have no face, we should return just the family as
in case of Regular?
Or is it instead a but that the face is not set because
NSFontFaceAttribute should always be preset, at most being Regular?
As a test, I removed the -(null) part and all fonts displayed fine
RIccardo