gnustep-dev
[Top][All Lists]
Advanced

[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: Wed, 20 Jul 2016 11:35:12 +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 improved the generation of the PS description in case of NIL face and now it works muchbetter, as we supposed.
But, while testing a rich document with many fonts and faces selected:
1) we print always the base face - obviously we don't set it
2) for once specific font, ghostscript still shows a generic substitution font, even if the name in the .ps file seems reasonable. Perhaps it is still not correct

Fred Kiefer wrote:
Checking the file history, I think you never "removed" support for the face 
attribute, but checked it in that way many years ago. Look at this commit:
>
>https://github.com/gnustep/gui/commit/e1bb31f0d2851291efbdde2c2e596baca94120ab
Thank you for looking this up. I remember that change now, it was something I 
did to get Emacs to compile with GNUstep again. We needed basic 
NSFontDescriptor handling for that. I implemented that by taking some code from 
mystep and adding the rest myself.
But I still have no recollection on why I commented the face attribute out. 
Maybe I need to enable that bit and try the results.


I tried to uncomment the code yesterday and it is clear why it is commented: you never implemented it, it is not something that was removed.

I tried to look at the code, the face is treated in the font enumerator, but in the specific method fontDescriptor, where could I get it from? You access traits, fontName and familyName - it would be easy to keep also fontFace, but where should it be initialized? I don't undestand the fontInfoForFontName method fully. woere is initWithFontName really implemented??

I noticed that adding a fontFace ivar and just adding the attributes breaks every font display! perhaps elsewhere the "null" value is treated badly.

Riccardo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]