Re: Invalid postscript generated from simple Ink

[Fred Kiefer]

Hi Riccardo,

thank you for your analysis. It looks like line 271 in the file 
NSFontDescriptor.m needs an added test for face being null. But you are also 
correct that this case should not happen,  looks like we commented out setting 
the font face in the attributes dictionary in GSFontInfo.m line 796 for some 
reason. I cannot remember when and why and don't have the time to inspect this 
until after my holidays. Adding the first fix should help you for now.

Fred

On the road

Am 18.07.2016 um 23:29 schrieb Riccardo Mottola <address@hidden>:

> 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
> 
> _______________________________________________
> Gnustep-dev mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnustep-dev