bugGNUstep - Bugs: bug #16262, GScups Generate Invalid font Names


You are not allowed to post comments on this tracker with your current authentification level.

bug #16262: GScups Generate Invalid font Names

Submitted by:  Charles Philip Chan <cpchan>
Submitted on:  Tue Apr 4 07:02:05 2006  
Category: BackendSeverity: 3 - Normal
Item Group: BugStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open

Tue Oct 9 22:57:55 2007, comment #4:

Changed category to backend

Fred Kiefer <FredKiefer>
Project Member
Thu Feb 22 19:19:35 2007, comment #3:

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.

G√ľnther Noack <guenthernoack>
Tue Apr 25 20:48:34 2006, comment #2:

FYI, this is from the PostScript generation class - back/Source/gsc/GSStreamContext.m

Adam Fedor <fedor>
Project Administrator
Tue Apr 25 20:07:52 2006, comment #1:

Which GNUstep backend are you using and where do your fonts come from, if this is the art backend?

There seem to be name difference between the GNUstep backend font names and the Postscript font names, but I could not see, where the font traits would be left out by GNUstep.
The bad thing here is that each GNUstep backend has its own font name handling, we may need to fix more than one backend here.

Fred Kiefer <FredKiefer>
Project Member
Tue Apr 4 07:02:05 2006, original submission:

Hello all:

I am testing out printing in GNUstep with no success. After looking into the postscript files generated by gscups though gs, I found out that instead of outputing the font names, it is outputing the font family names. For example, NimbusSanL-Regu is generated as Nimbus Sans L and NimbusMonL-Regu is generated as Nimbus Mono L.


Charles Philip Chan <cpchan>


No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by FredKiefer (Posted a comment)
  • -unavailable- added by guenthernoack (Posted a comment)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follows 1 latest change.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue Oct 9 22:57:55 2007FredKieferCategoryGui/AppKit=>Backend

    Back to the top

    Powered by Savane 3.1-cleanup1