[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #16262] GScups Generate Invalid font Names
From: |
Günther Noack |
Subject: |
[bug #16262] GScups Generate Invalid font Names |
Date: |
Thu, 22 Feb 2007 19:19:35 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 |
Follow-up Comment #3, bug #16262 (project gnustep):
I can confirm this is a problen in GSStreamContext in -back. I'm not a
PostScript expert, but as far as I understand the issue, this is how it can
be solved:
As far as I understand it, PostScript interpreters usually only understand
the fonts Helvetica, Courier and Times. Looking at some LaTeX-generated
PostScript-files, I found out that it's possible to include fonts in
PostScript code. This seems to be pretty straightforward using pfb fonts
(Search for pfb2ps in the code search engine of your choice), but is probably
harder for TrueType fonts. (However, it's not impossible, since UNIX word
processing applications seem to do it.)
A related problem is the improper glyph alignment in printed documents. This
is caused by NSLayoutManager placing the individual glyphs based on the size
of the glyphs as AppKit sees them. When both AppKit and the PostScript
interpreter / printer
With the DPS-ish architecture, GNUstep is in theory a very good application
framework for printing things. Unfortunately, small issues like this make
printing unusable for real-world scenarios. Fixing this bug could be a pretty
big step for a relatively small effort.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?16262>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #16262] GScups Generate Invalid font Names,
Günther Noack <=