On 11/6/10 12:24 PM, Bart Mathias wrote:
> Deron, you said, with regard to my not being able to print a PostScript file
> from PgS5.0.5.8a,
>
> "Is it a postscript file, or something else? Send me the file and I'll
> take a look if your not sure."
>
> Actually, I am sure it claims to be a postscript file, but I'm sending it
> anyway; maybe you will be able to see what is wrong with it.
>

Bart sent the file to me privately, but I thought I should post the fix
publicly in case any poor soul who is trying to get something to print
via postscript would like to improve their chances for success.

This change has not been tested extensively, and I can assure you that
changes to the way postscript fonts get encoded is dangerous at best.

Anyway, if you load the file
{PageStream5}/SoftLogik/Printers/PostScript.prolog into a text editor,
find the line (which is just a comment, it is code that was recently
removed in the great encoding changes.)

%/Encoding PGSEncoding 256 array copy def

And put this line just after it:
/Encoding Encoding 256 array copy def

Then Bart's file will print.

Deron

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

--- In PageStreamAmigaBeta@yahoogroups.com, PageStream Support <deron@...> wrote:

>
> Anyway, if you load the file
> {PageStream5}/SoftLogik/Printers/PostScript.prolog into a text editor,
> find the line (which is just a comment, it is code that was recently
> removed in the great encoding changes.)
>
> %/Encoding PGSEncoding 256 array copy def
>
> And put this line just after it:
> /Encoding Encoding 256 array copy def
>
> Then Bart's file will print.

I tried this for printing via a PS printer. I got a blip or two from the printer LAN connection, but no more. Please note that I have been lucky printing .ps files with AmiGS, whereas no one else seems to have had success.

Topic 2:

The pallette positions can be set manually in Pagestream5.prefs.
The Toolbox position cannot. Set the toolbox to Horizontal Block and move it to where you want it. Then use the MUI control to snapshot it. It will stay where you put it even if you change the prefs back to vertical. The main editing window can also be snapshotted for size and position using the MUI control.

Topic 3:

Although I am opening PGS in shell mode, I still have to open a new document before opening an existing document. Also, it is necessary to wait for a while until the font substitution requester has settled down and is displaying all the settings. If you can select each font and see the substitution then it is OK to click the OK button. PGS will then recover from the DSI.

Regards
Roy Leith

On 11/9/10 2:24 AM, royleith wrote:
>
> --- In PageStreamAmigaBeta@yahoogroups.com, PageStream Support<deron@...> wrote:
>
>> Anyway, if you load the file
>> {PageStream5}/SoftLogik/Printers/PostScript.prolog into a text editor,
>> find the line (which is just a comment, it is code that was recently
>> removed in the great encoding changes.)
>>
>> %/Encoding PGSEncoding 256 array copy def
>>
>> And put this line just after it:
>> /Encoding Encoding 256 array copy def
>>
>> Then Bart's file will print.
> I tried this for printing via a PS printer. I got a blip or two from the printer LAN connection, but no more. Please note that I have been lucky printing .ps files with AmiGS, whereas no one else seems to have had success.

Hmm. All this does is make a local copy of the Encoding vector. Bart was
using a "built-in" font and the PostScript code was trying to modify the
Encoding which was generating an error. The code snippet should not make
any problems. Very strange...

For those of you who can not print but should be able to, please make
sure you try some simple documents. Even a single plain box. Loading a
complex document and it not printing could be the result of many issues.

Deron

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

On 11/08/2010, PageStream Support wrote:

> [...]
> Bart sent the file to me privately,

Should I have posted it to a text or document drawer at Yahoo!'s AmigaBeta
site? From now on, I shall.

> [...] if you load the file
> {PageStream5}/SoftLogik/Printers/PostScript.prolog into a text editor,
> find the line (which is just a comment, it is code that was recently
> removed in the great encoding changes.)
>
> %/Encoding PGSEncoding 256 array copy def
>
> And put this line just after it:
> /Encoding Encoding 256 array copy def
>
> Then Bart's file will print.

Indeed it does! Thank you!

I don't think I tried anything like typing a simple line of text and seeing
whether it would print before making the change to the Prolog file. But
that also works after the change.
--
Bart Mathias
AmigaOne XE-G4 OS4.1u2

On 11/09/2010, royleith wrote:

> --- In PageStreamAmigaBeta@yahoogroups.com, PageStream Support
> <deron@...> wrote:
>
>> [Fix the PostScript.prolog file.]

> I tried this for printing via a PS printer. I got a blip or two from
> the printer LAN connection, but no more. Please note that I have been
> lucky printing .ps files with AmiGS, whereas no one else seems to have
> had success.

I'm not quite sure what this means. Are you saying that AmiGS would open and
print a postscript file created by PgS 5.0.5.8a, although it would not
print if sent directly to the printer from PageStream? That sounds strange.

I just now AmiGS'ed a simple PostScript file I created in ram: with
PageStream a few minutes ago, ram:test.ps, and printed it from AmiGS as
test2.ps.

5.OS41:> list ram:
Directory "ram:" on Tuesday 09-Nov-10
test2.ps 8263 ----rw-d Today 10:53:13
test.ps 164056 ----rwed Today 10:41:43

AmiGS opens the new file but it looks downright ugly. I tried again, but set
resolution to 600x600 with

test3.ps 7461 ----rw-d Today 10:58:38

as a result. AmiGS hasn't been able to open test3.ps as of this moment! (Why
do they keep getting smaller?)

> [...]
> Topic 3:
>
> Although I am opening PGS in shell mode, I still have to open a new
> document before opening an existing document. Also, it is necessary to
> wait for a while until the font substitution requester has settled down
> and is displaying all the settings. If you can select each font and see
> the substitution then it is OK to click the OK button. PGS will then
> recover from the DSI.

I am able to open an existing document without doing a new one first. But
this time when I did, just to be sure I'm not lying about it, it did take
an *awfully* long time. Sometimes my font substitution requester is filled
as soon as it opens (about five fonts, including "Artistic Normal," which
should not even be in the document in question).
--
Bart Mathias
AmigaOne XE-G4 OS4.1u2

On 11/9/10 1:48 PM, Bart Mathias wrote:
> On 11/08/2010, PageStream Support wrote:
>
>> [...]
>> Bart sent the file to me privately,
> Should I have posted it to a text or document drawer at Yahoo!'s AmigaBeta
> site? From now on, I shall.

No, you did nothing wrong. I get files privately all the time. That is
obviously the only way to deal with private content. Pretty soon I will
start suggesting folks open a bug report, where you can attach file to
the bug report, but PageStream5.0 Amiga is a bit "raw" for that.

>> [...] if you load the file
>> {PageStream5}/SoftLogik/Printers/PostScript.prolog into a text editor,
>> find the line (which is just a comment, it is code that was recently
>> removed in the great encoding changes.)
>>
>> %/Encoding PGSEncoding 256 array copy def
>>
>> And put this line just after it:
>> /Encoding Encoding 256 array copy def
>>
>> Then Bart's file will print.
> Indeed it does! Thank you!
>
> I don't think I tried anything like typing a simple line of text and seeing
> whether it would print before making the change to the Prolog file. But
> that also works after the change.

Glad to hear!

Deron

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

Deron,

I created a new docuemnt consisting of a gradient filled
pentagon with a gradient filled circle on top of it. I
placed one of the borders around it, then added some brief
text run through TextFX. Finally I added a simple table with
no text in it. Saved it as a .ps file and then printed from
AmiPS to the networked Xerox PS color laser.

The pentagon's gradient was not gradated at all. The
grandient in the circle printed out as a square of curved
gradients over the outline of the circle. The TextFX text
printed, but in solid black. It was supposed to be stroked
in black and filled with gray. The border and the table
printed correctly.

Clearly not correct, but better than I've gotten up to this
point.

--
--
--
Paul Zager

Proud Builder of Frankenthousand, the monster A1000
'030@50MHz, 2 megs chip/32 megs fast, 2 hard drives, OS 3.9
4xSCSI CD-ROM, SyJet, 56kHayes, 19" flicker free display

"Bride of Frankenthousand" A4000 Gave her life for her young

The Young Frankenthousand AmigaOne G4-XE, ATI Radeon 9250,
Catweasel, 2048 MB . . . now running OS4.1

On 11/09/2010, Paul R.Zager wrote:

> Deron,
>
> I created a new docuemnt consisting of a gradient filled
> pentagon with a gradient filled circle on top of it. I
> placed one of the borders around it, then added some brief
> text run through TextFX. Finally I added a simple table with
> no text in it. Saved it as a .ps file and then printed from
> AmiPS to the networked Xerox PS color laser.
>
> The pentagon's gradient was not gradated at all. The
> grandient in the circle printed out as a square of curved
> gradients over the outline of the circle. The TextFX text
> printed, but in solid black. It was supposed to be stroked
> in black and filled with gray. The border and the table
> printed correctly.

This made me want to give it a try. I set up a new document, drew a
rectangle and an oval (pretty close to square and circle, although I didn't
think to hold Shift).

Then I created the new colors Red and Blue. I filled the oval with Red,
radially gradiated to White, and the rectangle with Blue gradiated to Red
with some sine function.

They came out fine on screen. I saved it as PDF and viewed it with AmiPDF.
The oval was fine, but the rectangle was blue with sets of four vertical
lines. I printed the PDF and it came out looking much like the original
screen view, except the gradiation was a little bit too sharp. I then
printed from PageStream directly to the printer and it came out looking
like it did on screen. Very pleasing results.

Having to set up the colors every time is a bit of a pain. One possible way
out might be to open a full-color old document, then create the new one on
new pages, then delete the old document's pages? No time to try that today.
--
Bart Mathias
AmigaOne XE-G4 OS4.1u2

--- In PageStreamAmigaBeta@yahoogroups.com, Bart Mathias <mathias@...> wrote:

> I'm not quite sure what this means. Are you saying that AmiGS would open and
> print a postscript file created by PgS 5.0.5.8a, although it would not
> print if sent directly to the printer from PageStream? That sounds strange.
>
Yes, that's bang on.

> as a result. AmiGS hasn't been able to open test3.ps as of this moment! (Why
> do they keep getting smaller?)
>
Perhaps I knew to quit while I was ahead? I will try a wider selection of print tests and see if I can catch it out.

> > Topic 3:
Sometimes my font substitution requester is filled
> as soon as it opens (about five fonts, including "Artistic Normal," which
> should not even be in the document in question).

I will try again with added patience and see what happens.

Regards
Roy Leith

--- In PageStreamAmigaBeta@yahoogroups.com, "royleith" <r.m.leith@...> wrote:
>
>
>
> --- In PageStreamAmigaBeta@yahoogroups.com, Bart Mathias <mathias@> wrote:
>
> > I'm not quite sure what this means. Are you saying that AmiGS would open and
> > print a postscript file created by PgS 5.0.5.8a, although it would not
> > print if sent directly to the printer from PageStream? That sounds strange.
> >
> Yes, that's bang on.
>
>
> > as a result. AmiGS hasn't been able to open test3.ps as of this moment! (Why
> > do they keep getting smaller?)
> >
> Perhaps I knew to quit while I was ahead? I will try a wider selection of print tests and see if I can catch it out.
>

I have added a green square with a yellow to cyan gradient fill and a red circle with a blue to white radial fill to my text test file. I have, also, changed some of the text colour. To add the new colours it was necessary to set black to zero. Then CMYK colours could be set with the appropriate CMY slider positions. The sample colour square was entirely wrong in both the editor and the colour palette, but the colours end up correctly associated with the colour name (e.g. Red is 100% Magenta and 100% Yellow).

PGS still does not print direct to the printer. Seeng that someone else has successfully printed directly to a LAN connected printer, I may have another go.

PDF

Please note that this is with Deron's 'patch' as I am too lazy to take it out.

I saved as PDF. Loading into AmiPDF produces an error report and the following final lines were preceeded with lots more 'XPDF error: Illegal entry in bfchar block in ToUnicode CMap' lines.

XPDF error: Illegal entry in bfchar block in ToUnicode CMap
XPDF error: Illegal entry in bfchar block in ToUnicode CMap
XPDF error: Illegal entry in bfchar block in ToUnicode CMap
XPDF error: Missing or invalid Encoding entry in Type 0 font
XPDF error: Unknown font tag 'F3'
XPDF error: Unknown font tag 'F3'
XPDF error: Unknown font tag 'F3'ar block

The AmiPDF display is in colour, but in an ugly layout with some text in the wrong fonts. That resulted in text going beyond the right margin and the line spacing being erratic. Also, words inset in sentences and in a different colour, overlapped the incorrect larger font selected for the surrounding paragraphs.

Printing to the Workbench printer produces the same ugly layout, offset down and to the right, and in greyscale. Printing to Postscript (PS) produced the same ugly layout and offset, but in full and correct colour.

PS

Changing the Printer Settings to print to a Postscript file rather than PAR: resulted in a file that appeared almost perfectly in AmiGS. One character in a font that I did not over-write with Deron's set in Fonts: came up with a 'no character' square. If I replace the OS4.1 files with Deron's, that might go away.

Printing to the Workbench printer printed with the offset and greyscale reported above for PDF. Printing to Postscript (PS) produced the correct objects, fonts, layouts and colours.

> > > Topic 3:
> Sometimes my font substitution requester is filled
> > as soon as it opens (about five fonts, including "Artistic Normal," which
> > should not even be in the document in question).
>
> I will try again with added patience and see what happens.
>

It worked. On running PGS for the first time I get an immediate recoverable DSI. Going away and making a cup of tea seems to be enough time to get the substituted fonts displayed and the document opened. Closing PGS and then reopening does not generate the DSI and the font substitutes appear much more quickly. However, the delay is variable.

> Regards
> Roy Leith
>

Not exactly a simple box test, but since you still managed to get
something to print then the problem would lie with specific
objects/combinations. If you want to send the actual PageStream document
to me at support@pagestream.org I'll take a look.

Deron

On 11/9/10 8:57 PM, Paul R.Zager wrote:
> Deron,
>
> I created a new docuemnt consisting of a gradient filled
> pentagon with a gradient filled circle on top of it. I
> placed one of the borders around it, then added some brief
> text run through TextFX. Finally I added a simple table with
> no text in it. Saved it as a .ps file and then printed from
> AmiPS to the networked Xerox PS color laser.
>
> The pentagon's gradient was not gradated at all. The
> grandient in the circle printed out as a square of curved
> gradients over the outline of the circle. The TextFX text
> printed, but in solid black. It was supposed to be stroked
> in black and filled with gray. The border and the table
> printed correctly.
>
> Clearly not correct, but better than I've gotten up to this
> point.
>
>

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

Greetings "royleith" <r.m.leith@btinternet.com>
On 09/11/2010 at 09:24 you wrote concerning
[PageStreamAmigaBeta] Re: printing PS on AmigaBeta 5.0.5.8a

Hi Roy,

<<snip>>
r>> %/Encoding PGSEncoding 256 array copy def
r>>
r>> And put this line just after it:
r>> /Encoding Encoding 256 array copy def
r>>
r>> Then Bart's file will print.

r> I tried this for printing via a PS printer. I got a blip or two from the printer LAN connection, but no more. Please note that I have been lucky printing .ps files with AmiGS, whereas no one else seems to have had success.

Not here, not yet!

r> Topic 2:

r> The pallette positions can be set manually in Pagestream5.prefs.
r> The Toolbox position cannot.

Here, I've been able to locate both Toolbox and Edit Palette where I want them by modifying the data in PageStream5.prefs

r> Set the toolbox to Horizontal Block and move it to where you want it. Then use the MUI control to snapshot it. It will stay where you put it even if you change the prefs back to vertical. The main editing window can also be snapshotted for size and position using the MUI control.

Don't understand what you mean by "Then use the MUI control to snapshot it." Obviously, I've not tried what you have achieved.

r> Topic 3:

r> Although I am opening PGS in shell mode, I still have to open a new document before opening an existing document. Also, it is necessary to wait for a while until the font substitution requester has settled down and is displaying all the settings. If you can select each font and see the substitution then it is OK to click the OK button. PGS will then recover from the DSI.

Finally able to confirm Roy's observation about first applying "New" from the Navigator, fiddling with the 'new' doc a bit and then dumping it. Then opening an old file was successful. This patttern observed on two trials.

Yes, the above describes my interaction just a few minutes ago. After a few clicks on the font names displayed in the "Font substitution" requestor/panel, the panel's response became consistent. This was after a recovery from a DSI error too. Don't recall recovering from a DSI error report before. However, perhaps that DSI error is the cause of the current failure of 5058a to progress in printing a document. After about 10 minutes, there appears to be no movement in the progress bar.

Impatience overcame me. Reboot. Reopened MeatSauce again, after doing your 'New' doc fiddle, and NO DSI came along. Trying to print MeatSauce again now that a DSI has not intervened. Within 10 seconds printing progress bar moves to about 20-25% and then stalls.

I gave up! Will have to try again later.

Cheers Don (Green Dragon)
--

--- In PageStreamAmigaBeta@yahoogroups.com, "Ferguson, Don" <fergdc@...> wrote:
>
Hi Don,
>
> r> I tried this for printing via a PS printer. I got a blip or two from the printer LAN connection, but no more. Please note that I have been lucky printing .ps files with AmiGS, whereas no one else seems to have had success.
>
> Not here, not yet!
>

Have you tried using another program to print to a PS file? Can you use AmiPS to print that? If not, then there is a preferences problem, somewhere. I seem to remember that you use a PS printer. Have you selected the PS printer driver or have you selected one of the manufacturer drivers?

>
> r> Topic 2:
>
> r> Set the toolbox to Horizontal Block and move it to where you want it. Then use the MUI control to snapshot it. It will stay where you put it even if you change the prefs back to vertical. The main editing window can also be snapshotted for size and position using the MUI control.
>
> Don't understand what you mean by "Then use the MUI control to snapshot it." Obviously, I've not tried what you have achieved.
>

There is a fourth icon, top right, on my installation. It is at the left hand end of the row and takes the form of a downward facing arrowhead pointing at an underline. Clicking on this brings up a menu which includes 'snapshot'. In most MUI installations this is set up with MUI settings. However, there appears to be no such setting in PGS. If you cannot see the icon I suggest looking for the global MUI preferences program. I am hoping it is there by default for all of us.

>
> r> Topic 3:
>
>
> Impatience overcame me. Reboot. Reopened MeatSauce again, after doing your 'New' doc fiddle, and NO DSI came along. Trying to print MeatSauce again now that a DSI has not intervened. Within 10 seconds printing progress bar moves to about 20-25% and then stalls.
>
For both successful printing to a PS file and unsuccessful printing to my printer, the print progress bar always quickly makes it to the end. I don't know why your installation is giving you the stalling problem.
>
Regards, Roy Leith

Greetings "royleith" <r.m.leith@btinternet.com>
On 18/11/2010 at 11:05 you wrote concerning
[PageStreamAmigaBeta] Re: printing PS on AmigaBeta 5.0.5.8a

Hi Roy,

<<snip>>
r>> r> I tried this for printing via a PS printer. I got a blip or two from the printer LAN connection, but no more. Please note that I have been lucky printing .ps files with AmiGS, whereas no one else seems to have had success.
r>>
r>> Not here, not yet!
r>>

r> Have you tried using another program to print to a PS file? Can you use AmiPS to print that?

Well ..... yes and no.

With PgS 4.1.5.6 I opened an old file which contained text and graphics. A one page Table of Contents, a three page Preface, and 16 pages of text and graphics. Saving this as a PostScript file, then opening the PostScript version with AmiGS was okay. Printing a single page (in colour) from AmiGS was okay and the printout was true to what appeared on the screen presented by AmiGS. However, what appeared on the AmiGS screen was a very poor rendition of the original. Lots of errors!

So I tried the same using PgS 5033. While 4156 produced a measly PostScript file of 549,838 bytes, version 5033 produced 2,207,859 bytes, and each version was translating the same file.

However, AmiGS refused to print the PostScript file created by 5033. Some complaint about the GhostScript interpreter.

r> If not, then there is a preferences problem, somewhere. I seem to remember that you use a PS printer. Have you selected the PS printer driver or have you selected one of the manufacturer drivers?

Yes, I have the same Postscript printer as The Bart, and we use the same PPD file, which as I recall, he shipped to me a LONG time ago. I use the same PPD file on my iMac where PageStream 5058 (for OS X) uses the PPD file nicely.

r>> r> Set the toolbox to Horizontal Block and move it to where you want it. Then use the MUI control to snapshot it. It will stay where you put it even if you change the prefs back to vertical. The main editing window can also be snapshotted for size and position using the MUI control.
r>>
r>> Don't understand what you mean by "Then use the MUI control to snapshot it." Obviously, I've not tried what you have achieved.
r>>

r> There is a fourth icon, top right, on my installation. It is at the left hand end of the row and takes the form of a downward facing arrowhead pointing at an underline. Clicking on this brings up a menu which includes 'snapshot'. In most MUI installations this is set up with MUI settings. However, there appears to be no such setting in PGS. If you cannot see the icon I suggest looking for the global MUI preferences program. I am hoping it is there by default for all of us.

Okay, I found the icon and the related drop-down menu with the «snapshot» option. Had no idea what it was for! Some days, one learns something new! Thanks! So I moved things around a bit and tried the «snapshot» option. This was using 5033.

After exiting 5033, which does not work properly since the MUI screen hangs around, I had to reboot. Starting 5033 again revealed the Toolbox and the Edit Palette in the same old locations, although the frame for the text page had been altered. So .... !! I should try this out on 5058a and see what happens.

<<snip>>
r> For both successful printing to a PS file and unsuccessful printing to my printer, the print progress bar always quickly makes it to the end. I don't know why your installation is giving you the stalling problem.

No idea about the stalling!

Cheers Don (Green Dragon)
--