I've about had it with this crappy software. I can't print. When I try I get an error - "There was a problem processing document 'AMC_Template' (job xxx)".

I just printed something from my e-mail. I then loaded LibreWriter and a document - no problem printing from either -- no problem printing from anything except PgS. I ran the printing troubleshooter that pops up and I get a status message: "The printer's state message is 'usr/lib/cups/filter/pstopdf failed' "

All my printer will do with PgS is spit out nice blank sheets of paper. I have a display problem mentioned in another post. I also have a document that will be late AGAIN because I'm trying to use PgS. Looks like I'm going to have to go back to my Windows box and Pagemaker ONCE AGAIN to get my document out... late.

I'm not going to continue this. I bought what I thought was a well supported and worked out program. This is why I DIDN'T try Scribus. My other post has been up a week with no comments at all. Is there any real support for PgS? Once I get this next document out I might just d/l Scribus and see how it works. Either way, if I can't get help soon I'm ditching this garbage. I know how to work with DTP software, I know PgS works a bit differently than PM. The differences aren't a problem, I've been picking up on those as I actually use PgS surprisingly well. PgS just has some bugs and no real documentation so speak of either. The docs on the website have had no clues as to why my document isn't displaying as it should or why it won't print.

Well, PgS prints just fine for me. From what you are saying I can't offer any advice as to what might be going wrong for you.

As for the documentation, there's (other than scripting) pretty comprehensive documentation online. Maybe you don't like the online documentation, but that doesn't mean that it doesn't exist or that it doesn't cover using the application, the applications interface, and more. Even the scripting has a minimum level of documentation for all functions.

If some other software works better for you, that's great. I can't stand using any word processor, being completely spoiled by dtp in general and PgS specifically -- but that doesn't mean plenty of people don't get mileage out of word processors. Some people prefer Adobe InDesign, others Quark. What ever works for you is great.

Tim Doty

On Jun 24, 2012, at 3:21 PM, frank.swygert wrote:

> I've about had it with this crappy software. I can't print. When I try I get an error - "There was a problem processing document 'AMC_Template' (job xxx)".
>
> I just printed something from my e-mail. I then loaded LibreWriter and a document - no problem printing from either -- no problem printing from anything except PgS. I ran the printing troubleshooter that pops up and I get a status message: "The printer's state message is 'usr/lib/cups/filter/pstopdf failed' "
>
> All my printer will do with PgS is spit out nice blank sheets of paper. I have a display problem mentioned in another post. I also have a document that will be late AGAIN because I'm trying to use PgS. Looks like I'm going to have to go back to my Windows box and Pagemaker ONCE AGAIN to get my document out... late.
>
> I'm not going to continue this. I bought what I thought was a well supported and worked out program. This is why I DIDN'T try Scribus. My other post has been up a week with no comments at all. Is there any real support for PgS? Once I get this next document out I might just d/l Scribus and see how it works. Either way, if I can't get help soon I'm ditching this garbage. I know how to work with DTP software, I know PgS works a bit differently than PM. The differences aren't a problem, I've been picking up on those as I actually use PgS surprisingly well. PgS just has some bugs and no real documentation so speak of either. The docs on the website have had no clues as to why my document isn't displaying as it should or why it won't print.
>
>

I was ranting a bit... in case you didn't notice. I've used PageMaker since version 4 all the way through 6. Started on a little Mac Classic at a copy shop (rented time is expensive!) then bought a copy for Windows. Anything with the PageMaker name after 6 wasn't PageMaker, but a step between InDesign and PM -- totally different software that shouldn't have had the PM name on it (IMO). I really want to get away from Windows, and finding that PgS was a mature program (not a work in progress) that was apparently supported (I exepected better support) was what I was waiting for.

PgS is similar to PM -- enough that I want to use it so I'll have something that is supported and more up to date. I've just been having issues that don't appear to be related to my computer (everything else works/prints fine) that I can't find answers for. I'm already way past a deadline to get a quarterly publication out. I didn't want to have to revert to PM for this one, looks like I have no choice. I've not had this many issues with any other program. I expected PgS to be a lot more "polished" than it's turning out to be. I know -- and I keep reminding myself -- that a lot of the issues are just the learning curve of going to something different than what I'm used to...

The on-line documentation seems to be okay, I've just had a hard time finding answers. Part of that is the design philosophy differences between PM and PgS. I can't always find something where I think it would be, which leads to a lot more time/reading than expected, which gets frustrating after more than a few minutes. No index. I think a printed manual would be quicker in some respects. The documentation is incomplete as far as Linux is concerned.

I believe I found out why I'm having a printer problem -- PgS expects a PostScript printer. There is nothing in the documentation about non-Postscript printers except concerning Windows, Mac, and Amiga. Then it says that Windows and Macs use the native print drivers -- which is what I expected Linux to do as well. I just have to figure out how to make PgS use a non-postscript printer in Linux now.

--- In PageStreamSupport@yahoogroups.com, Tim Doty <thoromyr@...> wrote:
>
> Well, PgS prints just fine for me. From what you are saying I can't offer any advice as to what might be going wrong for you.
>
> As for the documentation, there's (other than scripting) pretty comprehensive documentation online. Maybe you don't like the online documentation, but that doesn't mean that it doesn't exist or that it doesn't cover using the application, the applications interface, and more. Even the scripting has a minimum level of documentation for all functions.
>
> If some other software works better for you, that's great. I can't stand using any word processor, being completely spoiled by dtp in general and PgS specifically -- but that doesn't mean plenty of people don't get mileage out of word processors. Some people prefer Adobe InDesign, others Quark. What ever works for you is great.
>
> Tim Doty
>
> On Jun 24, 2012, at 3:21 PM, frank.swygert wrote:
>
> > I've about had it with this crappy software. I can't print. When I try I get an error - "There was a problem processing document 'AMC_Template' (job xxx)".
> >
> > I just printed something from my e-mail. I then loaded LibreWriter and a document - no problem printing from either -- no problem printing from anything except PgS. I ran the printing troubleshooter that pops up and I get a status message: "The printer's state message is 'usr/lib/cups/filter/pstopdf failed' "
> >
> > All my printer will do with PgS is spit out nice blank sheets of paper. I have a display problem mentioned in another post. I also have a document that will be late AGAIN because I'm trying to use PgS. Looks like I'm going to have to go back to my Windows box and Pagemaker ONCE AGAIN to get my document out... late.
> >
> > I'm not going to continue this. I bought what I thought was a well supported and worked out program. This is why I DIDN'T try Scribus. My other post has been up a week with no comments at all. Is there any real support for PgS? Once I get this next document out I might just d/l Scribus and see how it works. Either way, if I can't get help soon I'm ditching this garbage. I know how to work with DTP software, I know PgS works a bit differently than PM. The differences aren't a problem, I've been picking up on those as I actually use PgS surprisingly well. PgS just has some bugs and no real documentation so speak of either. The docs on the website have had no clues as to why my document isn't displaying as it should or why it won't print.
> >
> >
>

one other thing to check, make sure you have ghostscript installed as well.

On Tue, 26 Jun 2012 19:23:11 -0400, frank.swygert <frank.swygert@yahoo.com> wrote:

>
> I was ranting a bit... in case you didn't notice. I've used PageMaker since version 4 all the way through 6. Started on a little Mac Classic at a copy shop >(rented time is expensive!) then bought a copy for Windows. Anything with the PageMaker name after 6 wasn't PageMaker, but a step between InDesign >and PM -- totally different software that shouldn't have had the PM name on it (IMO). I really want to get away from Windows, and finding that PgS was a >mature program (not a work in progress) that was apparently supported (I exepected better support) was what I was waiting for.

[Non-text portions of this message have been removed]

On Jun 26, 2012, at 6:23 PM, frank.swygert wrote:

> I believe I found out why I'm having a printer problem -- PgS expects a PostScript printer. There is nothing in the documentation about non-Postscript printers except concerning Windows, Mac, and Amiga. Then it says that Windows and Macs use the native print drivers -- which is what I expected Linux to do as well. I just have to figure out how to make PgS use a non-postscript printer in Linux now.

No, that is not an issue. PgS is providing the postscript output to the linux print system. You are mistaken, PgS can print to non-postscript printers on linux just like any other linux application. However, PgS does a *lot* more with postscript than other applications which can cause "fun" issues.

As an example, there's a bug/unimplemented feature in Brother's "postscript" implementation (it is called "brother script" to avoid licensing issues) having to do with font unloading. PgS allows you to set font unload per page or per document or unlimited. Most applications don't give you this level of access to postscript output -- and with brother printers don't set it to 'unload on page' or you will have problems.

[as an aside I *tried* to report the issue to brother, but couldn't get past the help desk "reinstall the printer driver and reboot windows" script monkeys]

So, unless you demonstrate an actual problem with PgS's postscript output (which I gave some pointers on how to verify) it is unlikely to be a PgS bug as others are able to print. It is far more likely that your printer configuration is broken, but not in a way that impacts other applications that don't exercise postscript as much or at all.

Tim Doty

You say you are using Windows but want to get away from it. Windows has
very good printer drivers. I use them. You don't have to use PostScript.
Try the Windows printer drivers.

On 6/26/2012 6:23 PM, frank.swygert wrote:
>
> I was ranting a bit... in case you didn't notice. I've used PageMaker
> since version 4 all the way through 6. Started on a little Mac Classic
> at a copy shop (rented time is expensive!) then bought a copy for
> Windows. Anything with the PageMaker name after 6 wasn't PageMaker,
> but a step between InDesign and PM -- totally different software that
> shouldn't have had the PM name on it (IMO). I really want to get away
> from Windows, and finding that PgS was a mature program (not a work in
> progress) that was apparently supported (I exepected better support)
> was what I was waiting for.
>
> PgS is similar to PM -- enough that I want to use it so I'll have
> something that is supported and more up to date. I've just been having
> issues that don't appear to be related to my computer (everything else
> works/prints fine) that I can't find answers for. I'm already way past
> a deadline to get a quarterly publication out. I didn't want to have
> to revert to PM for this one, looks like I have no choice. I've not
> had this many issues with any other program. I expected PgS to be a
> lot more "polished" than it's turning out to be. I know -- and I keep
> reminding myself -- that a lot of the issues are just the learning
> curve of going to something different than what I'm used to...
>
> The on-line documentation seems to be okay, I've just had a hard time
> finding answers. Part of that is the design philosophy differences
> between PM and PgS. I can't always find something where I think it
> would be, which leads to a lot more time/reading than expected, which
> gets frustrating after more than a few minutes. No index. I think a
> printed manual would be quicker in some respects. The documentation is
> incomplete as far as Linux is concerned.
>
> I believe I found out why I'm having a printer problem -- PgS expects
> a PostScript printer. There is nothing in the documentation about
> non-Postscript printers except concerning Windows, Mac, and Amiga.
> Then it says that Windows and Macs use the native print drivers --
> which is what I expected Linux to do as well. I just have to figure
> out how to make PgS use a non-postscript printer in Linux now.
>
> --- In PageStreamSupport@yahoogroups.com
> <mailtoageStreamSupport%40yahoogroups.com>, Tim Doty <thoromyr@...>
> wrote:
> >
> > Well, PgS prints just fine for me. From what you are saying I can't
> offer any advice as to what might be going wrong for you.
> >
> > As for the documentation, there's (other than scripting) pretty
> comprehensive documentation online. Maybe you don't like the online
> documentation, but that doesn't mean that it doesn't exist or that it
> doesn't cover using the application, the applications interface, and
> more. Even the scripting has a minimum level of documentation for all
> functions.
> >
> > If some other software works better for you, that's great. I can't
> stand using any word processor, being completely spoiled by dtp in
> general and PgS specifically -- but that doesn't mean plenty of people
> don't get mileage out of word processors. Some people prefer Adobe
> InDesign, others Quark. What ever works for you is great.
> >
> > Tim Doty
> >
> > On Jun 24, 2012, at 3:21 PM, frank.swygert wrote:
> >
> > > I've about had it with this crappy software. I can't print. When I
> try I get an error - "There was a problem processing document
> 'AMC_Template' (job xxx)".
> > >
> > > I just printed something from my e-mail. I then loaded LibreWriter
> and a document - no problem printing from either -- no problem
> printing from anything except PgS. I ran the printing troubleshooter
> that pops up and I get a status message: "The printer's state message
> is 'usr/lib/cups/filter/pstopdf failed' "
> > >
> > > All my printer will do with PgS is spit out nice blank sheets of
> paper. I have a display problem mentioned in another post. I also have
> a document that will be late AGAIN because I'm trying to use PgS.
> Looks like I'm going to have to go back to my Windows box and
> Pagemaker ONCE AGAIN to get my document out... late.
> > >
> > > I'm not going to continue this. I bought what I thought was a well
> supported and worked out program. This is why I DIDN'T try Scribus. My
> other post has been up a week with no comments at all. Is there any
> real support for PgS? Once I get this next document out I might just
> d/l Scribus and see how it works. Either way, if I can't get help soon
> I'm ditching this garbage. I know how to work with DTP software, I
> know PgS works a bit differently than PM. The differences aren't a
> problem, I've been picking up on those as I actually use PgS
> surprisingly well. PgS just has some bugs and no real documentation so
> speak of either. The docs on the website have had no clues as to why
> my document isn't displaying as it should or why it won't print.
> > >
> > >
> >
>
>

--

DAVID L. STEVENS -- TEAM AMIGA --
Windows XP user (:^(> on Acer Aspire 9810 2.16 GHz Notebook
2 GB RAM; 3 150-GB Hard Drives; CanoScan LIDE 20
Canon i860 & Brother HL-5050 PageStream v5.0.5.7 Pro
<http://home.comcast.net/~dave_stevens/home.html
<http://home.comcast.net/%7Edave_stevens/home.html>>
I do not necessarily agree with my taglines

***
Computers are useless. They can only give you answers.
Pablo Picasso

PgS still won't print directly to the printer, but I have a work around now. I created a new template document and can save it as a PDF then print the PDF file.

As far as I'm concerned this is a kludge -- there is a still a bug in the software preventing it from printing even to my Postscript printer. I'm going to work with it for now, but to me this is a serious, unacceptable issue for what is supposed to be a mature commercial package. This isn't the first Linux edition. I hope this will be looked into and fixed shortly.

Not to lay it all on PgS -- I'm contacting Mint support to see if anyone else has had a problem with Postscript printing. It's possible that there is a bug/problem with the printer drivers.

You can't use Windows printer drivers with a different OS. I only have Linux on my computer, do not want to use Windows systems any longer. Can't use the Windows drivers with a Mac either. I agree, the Windows drivers worked well when I was using Windows. Never tried PgS with windows -- would have if I'd kept using Windows as PageMaker 6 is starting to get dated.

Printing is still an issue, but I have managed to get a good workable template now! Just have to save as a PDF file then print from the PDF viewer. A little irritating, but workable. I do send some out as a PDF file so I have to save it as a PDF anyway. It's only inconvenient if I just want to see how one page might print. But it's just an inconvenience I can live with for now. I still don't consider the printing issue "closed" simply because the software shouldn't behave as it does. Am I the only one who has had a problem with print drivers in the Linux version? Anyone without problems running Ubuntu 11.10 (or Mint 12)??

I figured out Chapters and am using that in the template instead of negative page numbers. It takes a little getting used to, but seems to work better. I had a little trouble getting the page numbering to work like I wanted, but finally figured out to set page numbering in the second chapter as "manual" to start at page 1.

In PageMaker when you select double sided facing pages it will display that way on screen, and print according to the printer paper size. PgS works very differently in respect to double sided facing pages. It will display on screen correctly, but when printing it will print the DS facing pages on a single page. If you only have an 8.5x11 printer and have the page size set correctly to 8.5x11, it will print the two pages on one 8.5x11 sheet, shrinking to fit, rather than two 8.5x11 sheets. This is strange to me, not only because PM doesn't behave that way, but because I have the pages set to 8.5x11, and the rulers agrees with that. So why does it insist on 11x17 paper or shrinking the pages? This subverts the reason for displaying on screen as facing pages. I was told (by Deron) that the DSFP feature was mainly used to display a graphic that spread over two pages, but you would have to go back and change to single pages before printing. I'm not sure that can even be done... not enough time to try it now.

--- In PageStreamSupport@yahoogroups.com, "David L. Stevens" <dave_stevens@...> wrote:
>
> You say you are using Windows but want to get away from it. Windows has
> very good printer drivers. I use them. You don't have to use PostScript.
> Try the Windows printer drivers.
>

On 6/27/12 5:15 AM, frank.swygert wrote:
> PgS still won't print directly to the printer, but I have a work around now. I created a new template document and can save it as a PDF then print the PDF file.

What did you try, and what were the results? Did you do as I suggested
and print a single box in a new document?

Deron

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

First, a Clarification for David Stevens -- I was using Windows XP, and I still have my old computer up and running XP. I just have it as a back-up and to use a mailing database program (for now). I had to revert to it for my last magazine due more to time constraints with learning the differences between PgS and PM6. I almost have a handle on that now.

Now, to the PgS team and users --- AN APOLOGY. It appears that converting from a PS file to a print file has been a recurring problem with Ubuntu/Debian based systems since 2008. There have been fixes, but it appears that the fixes were geared more to problems printing PDF files from various software. A few of the old bug reports/fixes indicated the problem was with PS printers and PPDs, but all were related to printing PDF files. Those bugs were supposedly fixed in the latest printer handling modules, but there is obviously still a bug in PS printer handling.

I'm truly sorry for ranting so much about PgS not printing. PgS is the only software I have that assumes a PS printer, which is apparently the crux of the problem I'm having. Since it's the only ting that wouldn't print (I printed from 3-4 different programs to make sure) I assumed it was the problem. Again, I apologize for the error on my part.

--- In PageStreamSupport@yahoogroups.com, "frank.swygert" <frank.swygert@...> wrote:
>
> PgS still won't print directly to the printer, but I have a work around now. I created a new template document and can save it as a PDF then print the PDF file.
>
> As far as I'm concerned this is a kludge -- there is a still a bug in the software preventing it from printing even to my Postscript printer. I'm going to work with it for now, but to me this is a serious, unacceptable issue for what is supposed to be a mature commercial package. This isn't the first Linux edition. I hope this will be looked into and fixed shortly.
>
> Not to lay it all on PgS -- I'm contacting Mint support to see if anyone else has had a problem with Postscript printing. It's possible that there is a bug/problem with the printer drivers.
>

On Jun 27, 2012, at 9:12 PM, frank.swygert wrote:

> In PageMaker when you select double sided facing pages it will display that way on screen, and print according to the printer paper size. PgS works very differently in respect to double sided facing pages. It will display on screen correctly, but when printing it will print the DS facing pages on a single page. If you only have an 8.5x11 printer and have the page size set correctly to 8.5x11, it will print the two pages on one 8.5x11 sheet, shrinking to fit, rather than two 8.5x11 sheets. This is strange to me, not only because PM doesn't behave that way, but because I have the pages set to 8.5x11, and the rulers agrees with that. So why does it insist on 11x17 paper or shrinking the pages? This subverts the reason for displaying on screen as facing pages. I was told (by Deron) that the DSFP feature was mainly used to display a graphic that spread over two pages, but you would have to go back and change to single pages before printing. I'm not sure that can even be done... n!
> ot enough time to try it now.

I don't (actually, didn't) have a problem with that. I use facing pages for a newsletter, to see how opposite pages would look to the reader. For example, page margins should be balanced, headlines on opposite pages should not be at slightly different heights, etc. For printing, I went to Layout, Master Page Setup and unchecked Facing Pages.

--
Martin B. Brilliant - mbrilliant@alum.mit.edu
Mac OS X version 10.6.8
PageStream (non-pro) 5.0.5.8

On 6/28/12 8:06 AM, frank.swygert wrote:
> I'm truly sorry for ranting so much about PgS not printing. PgS is the only software I have that assumes a PS printer, which is apparently the crux of the problem I'm having.
>

I would like to clarify this. CUPS is the standard way to print on
Linux. With CUPS, you pass it a file to print. Like a bitmap in JPEG
format, or a text file. Or a PostScript file. Applications don't drive
printers directly. Now, PageStream could send bitmaps instead of
postscript to CUPS, but when you output to PDF or a postscript printer,
it would be sending a bitmap image of the page to the PDF or printer and
loose all vector capabilities.

PageStream is not assuming a postscript printer. It is simply passing a
vector definition of the page to be printed. If a simple box is not
printing, then someone is very wrong with your setup. The CUPS system is
built to work this way. If it is not, then it needs to be corrected! Not
only will PageStream be happier, so will many other applications which
you have not yet tried.

Deron

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

On Thu, 28 Jun 2012, PageStream Support wrote:

> On 6/28/12 8:06 AM, frank.swygert wrote:
>> I'm truly sorry for ranting so much about PgS not printing. PgS is the only software I have that assumes a PS printer, which is apparently the crux of the problem I'm having.
>>
>
> I would like to clarify this. CUPS is the standard way to print on
> Linux. With CUPS, you pass it a file to print. Like a bitmap in JPEG
> format, or a text file. Or a PostScript file. Applications don't drive
> printers directly. Now, PageStream could send bitmaps instead of
> postscript to CUPS, but when you output to PDF or a postscript printer,
> it would be sending a bitmap image of the page to the PDF or printer and
> loose all vector capabilities.
>
> PageStream is not assuming a postscript printer. It is simply passing a
> vector definition of the page to be printed. If a simple box is not
> printing, then someone is very wrong with your setup. The CUPS system is
> built to work this way. If it is not, then it needs to be corrected! Not
> only will PageStream be happier, so will many other applications which
> you have not yet tried.

if you linux mint or one of the ubuntu distros you can install cups from a
terminal by typing

sudo apt-get install cups

(then you type your password for your user account)

pagestream has been printing my documents fine from both linux mint
(debian based and xubuntu). a couple of years ago I had to do the save as
pdf and then print from the pdf thing but recently no problem with
straight forward pages. however i have not made up whole newsletters
recently.

>
> Deron
>
>
>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bonnie Dalzell, MA
mailO box 9767 Baldwin, MD, USA 21013 | EMAIL:bdalzell@qis.net
shipping adddress:5100 Hydes Rd 21082 (Hydes Post Office closed Jan 2012)
Freelance anatomist, vertebrate paleontologist, writer, illustrator, dog
breeder, computer nerd & iconoclast... Borzoi info at www.borzois.com.
HOME www.batw.net ART bdalzellart.batw.net BUSINESS www.boardingatwedge.com

Bonnie, what version of Mint are you using, and what versions of Ghostscript and CUPS does it use?

I'm running Ghostscript-cups 9.04. CUPS is 1.5.0.8ubuntu6. I e-mailed one of the CUPS developers and got some feedback. They asked for an error log and a copy of the Postscript output file. It was suggested that Ghostscript might be the problem, that the PS to PDF filter is working properly, assuming the Postscript file that PgS is generating is a proper PS file.

"The PostScript file which PgS has generated seems to be broken. All these commands lead to Ghostscript erroring out:

1. gs printout
(The simplest test, should display PS file on the screen)

2. ps2pdf printout
(Ghostscript's command line tool to convert PS to PDF)

3. /usr/lib/cups/filter/pstopdf 1 1 1 1 '' printout-PgS.ps > out.pdf
(pstopdf CUPS filter like it gets called by CUPS)

If you think that the PostScript file is OK, please report a bug to Ghostscript"

If no one else is having a problem with PgS PS output then the problem must be in Ghostscript. It's either that of Ghostscript doesn't like the PS file that PgS generates for some reason.

I have a copy of the error log that the developer used to come up with this theory if anyone is interested.

Adobe Document Viewer 3.2.1 has a problem generating the first three pages of the Postscript document that PgS generated. They aren't complicated pages, just some text and simple graphics that were imported from a PDF file using the copy feature of Adobe PDF Viewer. There are 7 pages total, and pages 4-7 display fine. This leads me to believe that something isn't working right in the Postscript output of PgS instead of Ghostscript. Maybe the PgS Postscript generation is having a problem translating the pasted in images copied from a PDF file? Not all three of the first three pages have images pasted from a PDF though, only the second and third pages do -- the first one does not. GIMP won't display the file either, it errors out, but I didn't expect GIMP to display a multi-page document. Adobe Reader won't display it either, but that may be because it's a PS and not a PDF file.

So I'm back to square one -- is this a PgS Postscript output problem or a Ghostscript translation problem? The PS file in question is posted in the files section as "printout". I don't know enough about PS to see if anything is wrong with the file, and Abobe Viewer seems to be the only thing I have that should read and display a PS file. I even tried PgS, but it won't open the PS file, and trying to import doesn't work -- it treats it as a single EPS graphic. I checked Libre Office -- have to go translate the PS file into a EPS with a third program. I'd really like to know if this file is good before filing a bug report with the Ghostscript developers.

--- In PageStreamSupport@yahoogroups.com, admfubar@... wrote:
>
> one other thing to check, make sure you have ghostscript installed as well.
>

--- In PageStreamSupport@yahoogroups.com, Bonnie Dalzell <bdalzell@...> wrote:
>
>pagestream has been printing my documents fine from both linux mint
(debian based and xubuntu). a couple of years ago I had to do the save as pdf and then print from the pdf thing but recently no problem with
straight forward pages. however i have not made up whole newsletters
recently.

The file that won't display from Adobe Document Viewer (the PS output from PgS) is 9.5Mb, so I can't upload it here. If anyone would like a copy drop me a line and I'll e-mail it.

most email won't allow attachments that big, either. does it get any smaller when zipped?

feel free to email me directly. Even if the file can't be attached we can work something out.

Tim Doty
On Jul 1, 2012, at 2:06 PM, frank.swygert wrote:

> The file that won't display from Adobe Document Viewer (the PS output from PgS) is 9.5Mb, so I can't upload it here. If anyone would like a copy drop me a line and I'll e-mail it.
>
>

On Sun, 1 Jul 2012, frank.swygert wrote:

> Bonnie, what version of Mint are you using, and what versions of
> Ghostscript and CUPS does it use?

cups 1.5.2-5

ghostscript 9.05-dfsg-3

linux mint xfce is from the linux mint linuxmint-9-xfce-cd-i386.iso

linux kernel is: 3.2.0-2-486

does this help?

Incidently if anyone wants a picture of mint leaves for a linuxmint
desktop background write me. I have not beena ble to successfully join
the linux mint list to offer it to mintniks.

>
> I'm running Ghostscript-cups 9.04. CUPS is 1.5.0.8ubuntu6. I e-mailed
> one of the CUPS developers and got some feedback. They asked for an
> error log and a copy of the Postscript output file. It was suggested
> that Ghostscript might be the problem, that the PS to PDF filter is
> working properly, assuming the Postscript file that PgS is generating is
> a proper PS file.
>
> "The PostScript file which PgS has generated seems to be broken. All
> these commands lead to Ghostscript erroring out:
>
> 1. gs printout
> (The simplest test, should display PS file on the screen)
>
> 2. ps2pdf printout
> (Ghostscript's command line tool to convert PS to PDF)
>
> 3. /usr/lib/cups/filter/pstopdf 1 1 1 1 '' printout-PgS.ps > out.pdf
> (pstopdf CUPS filter like it gets called by CUPS)
>
> If you think that the PostScript file is OK, please report a bug to
> Ghostscript"
>
>
> If no one else is having a problem with PgS PS output then the problem
> must be in Ghostscript. It's either that of Ghostscript doesn't like the
> PS file that PgS generates for some reason.
>
> I have a copy of the error log that the developer used to come up with
> this theory if anyone is interested.
>
> Adobe Document Viewer 3.2.1 has a problem generating the first three
> pages of the Postscript document that PgS generated. They aren't
> complicated pages, just some text and simple graphics that were imported
> from a PDF file using the copy feature of Adobe PDF Viewer. There are 7
> pages total, and pages 4-7 display fine. This leads me to believe that
> something isn't working right in the Postscript output of PgS instead of
> Ghostscript. Maybe the PgS Postscript generation is having a problem
> translating the pasted in images copied from a PDF file? Not all three
> of the first three pages have images pasted from a PDF though, only the
> second and third pages do -- the first one does not. GIMP won't display
> the file either, it errors out, but I didn't expect GIMP to display a
> multi-page document. Adobe Reader won't display it either, but that may
> be because it's a PS and not a PDF file.
>
> So I'm back to square one -- is this a PgS Postscript output problem or
> a Ghostscript translation problem? The PS file in question is posted in
> the files section as "printout". I don't know enough about PS to see if
> anything is wrong with the file, and Abobe Viewer seems to be the only
> thing I have that should read and display a PS file. I even tried PgS,
> but it won't open the PS file, and trying to import doesn't work -- it
> treats it as a single EPS graphic. I checked Libre Office -- have to go
> translate the PS file into a EPS with a third program. I'd really like
> to know if this file is good before filing a bug report with the
> Ghostscript developers.
>
>
> --- In PageStreamSupport@yahoogroups.com, admfubar@... wrote:
>>
>> one other thing to check, make sure you have ghostscript installed as
>> well.
>>
>
> --- In PageStreamSupport@yahoogroups.com, Bonnie Dalzell <bdalzell@...>
> wrote:
>>
>> pagestream has been printing my documents fine from both linux mint
> (debian based and xubuntu). a couple of years ago I had to do the save as pdf and then print from the pdf thing but recently no problem with
> straight forward pages. however i have not made up whole newsletters
> recently.
>
>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bonnie Dalzell, MA
mailO box 9767 Baldwin, MD, USA 21013 | EMAIL:bdalzell@qis.net
shipping adddress:5100 Hydes Rd 21082 (Hydes Post Office closed Jan 2012)
Freelance anatomist, vertebrate paleontologist, writer, illustrator, dog
breeder, computer nerd & iconoclast... Borzoi info at www.borzois.com.
HOME www.batw.net ART bdalzellart.batw.net BUSINESS www.boardingatwedge.com