I've got a new problem: PgS stopped printing. There is a print progress bar,
but that is all. Everything looks to be setup fine and I printed quite
recently. The only thing I can remember doing was downloading the new PgS
5.0.2.12Pro. Is anyone else having trouble printing?

Tim Doty

On Tuesday 07 March 2006 06:55 am, Tim Doty wrote:
> I've got a new problem: PgS stopped printing. There is a print progress
> bar, but that is all. Everything looks to be setup fine and I printed quite
> recently. The only thing I can remember doing was downloading the new PgS
> 5.0.2.12Pro. Is anyone else having trouble printing?

Okay, this was caused by PgS sending a font to the printer that made it *very*
unhappy. Power cycle the printer, clear jobs, etc., and avoid fonts that PgS
can't handle (the trick is, which ones are those)

Tim

> > I've got a new problem: PgS stopped printing. There is a print progress
> > bar, but that is all. Everything looks to be setup fine and I printed quite
> > recently. The only thing I can remember doing was downloading the new PgS
> > 5.0.2.12Pro. Is anyone else having trouble printing?
>
>Okay, this was caused by PgS sending a font to the printer that made it
>*very*
>unhappy. Power cycle the printer, clear jobs, etc., and avoid fonts that PgS
>can't handle (the trick is, which ones are those)

At this point PageStream does not "trim" a large unicode font, but will
download the entire thing. Could that be the problem? Ghostscript was able
to handle these large downloaded fonts, but some postscript interpreters
might easily run out of memory.

>Tim

Deron Kazmaier - support@pagestream.org
Grasshopper LLC Publishing -http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows

On Tuesday 07 March 2006 10:56 am, PageStream Support wrote:
> > > I've got a new problem: PgS stopped printing. There is a print progress
> > > bar, but that is all. Everything looks to be setup fine and I printed
> > > quite recently. The only thing I can remember doing was downloading the
> > > new PgS 5.0.2.12Pro. Is anyone else having trouble printing?
> >
> >Okay, this was caused by PgS sending a font to the printer that made it
> >*very*
> >unhappy. Power cycle the printer, clear jobs, etc., and avoid fonts that
> > PgS can't handle (the trick is, which ones are those)
>
> At this point PageStream does not "trim" a large unicode font, but will
> download the entire thing. Could that be the problem? Ghostscript was able
> to handle these large downloaded fonts, but some postscript interpreters
> might easily run out of memory.

That might be. It looks like the fifth font in my list causes the problem (and
checking for that exposes another bug). Except that I *know* it isn't that
font. Unfortunately as a side effect of the noted bug I can't tell for sure
the preceding fonts. Checking.

Tim Doty

On Tuesday 07 March 2006 05:22 pm, Tim Doty wrote:
> On Tuesday 07 March 2006 10:56 am, PageStream Support wrote:
> > > > I've got a new problem: PgS stopped printing. There is a print
> > > > progress bar, but that is all. Everything looks to be setup fine and
> > > > I printed quite recently. The only thing I can remember doing was
> > > > downloading the new PgS 5.0.2.12Pro. Is anyone else having trouble
> > > > printing?
> > >
> > >Okay, this was caused by PgS sending a font to the printer that made it
> > >*very*
> > >unhappy. Power cycle the printer, clear jobs, etc., and avoid fonts that
> > > PgS can't handle (the trick is, which ones are those)
> >
> > At this point PageStream does not "trim" a large unicode font, but will
> > download the entire thing. Could that be the problem? Ghostscript was
> > able to handle these large downloaded fonts, but some postscript
> > interpreters might easily run out of memory.
>
> That might be. It looks like the fifth font in my list causes the problem
> (and checking for that exposes another bug). Except that I *know* it isn't
> that font. Unfortunately as a side effect of the noted bug I can't tell for
> sure the preceding fonts. Checking.

Okay, I got a postscript file and tried to convert to PDF:

ESP Ghostscript 8.15.0: Failed to interpret TT instructions of the font
aakar-Medium. Continue ignoring instructions of the font.
Error: /invalidfont in -dict-
Operand stack:
--nostringval-- --nostringval-- AdobePiStd --dict:12/12(L)-- Font
AdobePiStd --dict:12/12(L)-- AdobePiStd
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3
%oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2
--nostringval-- --nostringval-- --nostringval-- 2 %stopped_push
--nostringval-- 4 5 %oparray_pop 5 5 %oparray_pop
--nostringval-- --nostringval-- --nostringval-- 9 6 %oparray_pop
--nostringval-- 9 6 %oparray_pop
Dictionary stack:
--dict:1133/3371(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)--
--dict:210/302(L)-- --dict:82/200(L)-- --dict:17/17(ro)(G)--
Current allocation mode is local
Last OS error: 2
Current file position is 1600087
ESP Ghostscript 8.15.0: Unrecoverable error, exit code 1

> > > > > I've got a new problem: PgS stopped printing. There is a print
> > > > > progress bar, but that is all. Everything looks to be setup fine and
> > > > > I printed quite recently. The only thing I can remember doing was
> > > > > downloading the new PgS 5.0.2.12Pro. Is anyone else having trouble
> > > > > printing?
> > > >
> > > >Okay, this was caused by PgS sending a font to the printer that made it
> > > >*very*
> > > >unhappy. Power cycle the printer, clear jobs, etc., and avoid fonts that
> > > > PgS can't handle (the trick is, which ones are those)
> > >
> > > At this point PageStream does not "trim" a large unicode font, but will
> > > download the entire thing. Could that be the problem? Ghostscript was
> > > able to handle these large downloaded fonts, but some postscript
> > > interpreters might easily run out of memory.
> >
> > That might be. It looks like the fifth font in my list causes the problem
> > (and checking for that exposes another bug). Except that I *know* it isn't
> > that font. Unfortunately as a side effect of the noted bug I can't tell for
> > sure the preceding fonts. Checking.
>
>Okay, I got a postscript file and tried to convert to PDF:
>
>ESP Ghostscript 8.15.0: Failed to interpret TT instructions of the font
>aakar-Medium. Continue ignoring instructions of the font.

I just downloaded a copy of aakar-Medium. Is your letter F all screwed up?
I'm not so sure the font is not just screwed... I'll look into it.

Deron

Deron Kazmaier - support@pagestream.org
Grasshopper LLC Publishing -http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows

Yes, the 'F' is no good and the font is probably bad. My problem is that it
installed with SuSE 10. One thing I would like is the ability for PgS to
(optionally) not use the system fonts. SuSE 10 includes a whole mess of fonts
that I don't mind being there for use with other applications, but it just
clutters up PgS.

Tim

>Yes, the 'F' is no good and the font is probably bad.

I will do what I can to make PageStream deal with the munged font. That is
always good behaviour!

>My problem is that it
>installed with SuSE 10. One thing I would like is the ability for PgS to
>(optionally) not use the system fonts. SuSE 10 includes a whole mess of fonts
>that I don't mind being there for use with other applications, but it just
>clutters up PgS.

I think font suitcases would be best for this. I could easily add an option
to not add system fonts, but that would make the whole lot go away. Then
you would have to somehow copy the ones you want to another folder
(guessing by the cryptic names), and then add them.

Deron

>Tim

Deron Kazmaier - support@pagestream.org
Grasshopper LLC Publishing -http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows

On Wednesday 08 March 2006 10:38 am, PageStream Support wrote:
> >Yes, the 'F' is no good and the font is probably bad.
>
> I will do what I can to make PageStream deal with the munged font. That is
> always good behaviour!
>
> >My problem is that it
> >installed with SuSE 10. One thing I would like is the ability for PgS to
> >(optionally) not use the system fonts. SuSE 10 includes a whole mess of
> > fonts that I don't mind being there for use with other applications, but
> > it just clutters up PgS.
>
> I think font suitcases would be best for this. I could easily add an option
> to not add system fonts, but that would make the whole lot go away. Then
> you would have to somehow copy the ones you want to another folder
> (guessing by the cryptic names), and then add them.

I'm not saying the option would be for everyone, but for me it would be good
because I almost entirely use a given set of fonts. Many of my documents use
Times Roman/Triumvirate from my Amiga days (though I've been switching to
Times New Roman/Arial) and most of the other fonts I commonly use are not
distributed with SuSE either.

I think making all the system fonts in a system suitcase makes sense. That way
they can be easily toggled as desired (defaulting to "on" of course).

Admittedly OS X has provisions for font categories (the FontBook application),
but as PgS is multiplatform having this built in to the core makes sense.

Tim Doty