[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Invalid postscript generated from simple Ink
|
From: |
Gregory Casamento |
|
Subject: |
Re: Invalid postscript generated from simple Ink |
|
Date: |
Fri, 15 Jul 2016 06:01:05 -0400 |
Fred
On Friday, July 15, 2016, Fred Kiefer <address@hidden> wrote:
OK, could we please all stick to a new rule when talking about printing? That rule being that you have to state first which operating system, backend and printing setup you are using.
Agreed. This makes total sense. For reference my config is Linux (Debian 7), Cairo backend, cups. My printer is a Xerox 4500DT (dual sided).
Riccardo almost did so in this mail. The only missing information is the printing setup, lpd or cups.
Got it above
I will look into the space in font name issue, as it should be easy to resolve, but please remember that xlib is a deprecated backend that is normally not supported.
Fred
On the road
Am 15.07.2016 um 01:08 schrieb Riccardo Mottola <address@hidden>:
> Hi,
>
> on a very "standard" computer setup: Ubuntu on x86, if I try to print a simple "Hello" from Ink I get a PS file which is reported as invalid from ghostscript.
>
> Errpr: undefined: OffendingCommand: Sans
>
> What is invalid and why is it? on the other few computer where I am able to print, I don't get this issue.
>
> I fear the font name can't contain a space?
>
> Could this be backend dependent? This is running xlib and not cairo and most systems were I use xlib, I have other issues with printing.
>
> the cairo PS is so much more complex than the xlib, but at a first comparison, it looks as if the cairo one contains font names without space.
>
> Riccardo
> <GSLPRPrintJob-acer_103a_1d384df1_0.ps>
> _______________________________________________
> Gnustep-dev mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnustep-dev
_______________________________________________
Gnustep-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/gnustep-dev
--