I am not able to convert a postscriptfile made in Pagestream 5.0.4.29 Pro to
pdf using ps2pdf. This is the output:

[anders@localhost ~]$ ps2pdf -dCompatibilityLevel=1.4 -dPDFSETTINGS=/prepress
-dEmbedAllFonts=true -dUseFlateCompression=true -sPAPERSIZE=a5 Test.ps
test.pdf
Error: /ioerror in --eexec--
Operand stack:
--nostringval-- --nostringval-- --dict:8/12(L)-- --dict:8/12(L)--
Private --dict:0/16(L)-- RD
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --
nostringval-- 2 %stopped_push--nostringval-- --nostringval-- --
nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904
1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3
%oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval--
--nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 1762
4 5 %oparray_pop --nostringval--
Dictionary stack:
--dict:1154/1684(ro)(G)-- --dict:0/20(G)-- --dict:72/200(L)-- --
dict:208/300(L)-- --dict:72/200(L)-- --dict:1154/1684(ro)(G)-- --
dict:0/16(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 708406
GPL Ghostscript 8.63: Unrecoverable error, exit code 1

Anders

Hello,

You mentioned in a prior email that Print Setup crashes, so I'm not sure
if you got that straightened out.

First, what problems did you have the Save as PDF? 5.0.4.29 should be
almost perfect. I think the only thing not supported is Shape fill, and
patterned gradient fills. Neither of which are very common and not
directly supported in PDF format (to support these items will require
rendering those objects into a bitmap and embedding the bitmap in the
PDF which is not an idea solution either).

To the problem mentioned, the error output is pretty meaningless. I'm
betting you are hitting a problem with a specific font? (This is coming
up with odd fonts on the mac as well, and is always a complex TrueType
font). Try printing just a box, and some simple text with a few fonts
(just one font at a time of course).

Deron

> I am not able to convert a postscriptfile made in Pagestream 5.0.4.29 Pro to
> pdf using ps2pdf. This is the output:
>
> [anders@localhost ~]$ ps2pdf -dCompatibilityLevel=1.4 -dPDFSETTINGS=/prepress
> -dEmbedAllFonts=true -dUseFlateCompression=true -sPAPERSIZE=a5 Test.ps
> test.pdf
> Error: /ioerror in --eexec--
> Operand stack:
> --nostringval-- --nostringval-- --dict:8/12(L)-- --dict:8/12(L)--
> Private --dict:0/16(L)-- RD
> Execution stack:
> %interp_exit .runexec2 --nostringval-- --nostringval-- --
> nostringval-- 2 %stopped_push--nostringval-- --nostringval-- --
> nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904
> 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3
> %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval--
> --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 1762
> 4 5 %oparray_pop --nostringval--
> Dictionary stack:
> --dict:1154/1684(ro)(G)-- --dict:0/20(G)-- --dict:72/200(L)-- --
> dict:208/300(L)-- --dict:72/200(L)-- --dict:1154/1684(ro)(G)-- --
> dict:0/16(L)--
> Current allocation mode is local
> Last OS error: 2
> Current file position is 708406
> GPL Ghostscript 8.63: Unrecoverable error, exit code 1
>
>
> Anders
>

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

Fredag 21 november 2008 18:22:02 skrev PageStream Support:
> Hello,
>
> You mentioned in a prior email that Print Setup crashes, so I'm not sure
> if you got that straightened out.

If I try to access the Printer setup PGS simply close down, so it is not
possible to eg. change the printer .....

> First, what problems did you have the Save as PDF? 5.0.4.29 should be
> almost perfect. I think the only thing not supported is Shape fill, and
> patterned gradient fills. Neither of which are very common and not
> directly supported in PDF format (to support these items will require
> rendering those objects into a bitmap and embedding the bitmap in the
> PDF which is not an idea solution either).

PDF export seems to work quite well now ..... but eps clipart is not exported
to the pdf file, so it is useless to me. That is why I always print to a
postscript file and covert it to pdf using ps2pdf

> To the problem mentioned, the error output is pretty meaningless. I'm
> betting you are hitting a problem with a specific font? (This is coming
> up with odd fonts on the mac as well, and is always a complex TrueType
> font). Try printing just a box, and some simple text with a few fonts
> (just one font at a time of course).
>
> Deron

Well, it works ok in the former versions of Pagestream, so there must have
been made some changes in the newest version ...?

> > I am not able to convert a postscriptfile made in Pagestream 5.0.4.29 Pro
> > to pdf using ps2pdf. This is the output:
> >
> > [anders@localhost ~]$ ps2pdf -dCompatibilityLevel=1.4
> > -dPDFSETTINGS=/prepress -dEmbedAllFonts=true -dUseFlateCompression=true
> > -sPAPERSIZE=a5 Test.ps test.pdf
> > Error: /ioerror in --eexec--
> > Operand stack:
> > --nostringval-- --nostringval-- --dict:8/12(L)--
> > --dict:8/12(L)-- Private --dict:0/16(L)-- RD
> > Execution stack:
> > %interp_exit .runexec2 --nostringval-- --nostringval-- --
> > nostringval-- 2 %stopped_push--nostringval-- --nostringval-- --
> > nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop
> > 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3
> > %oparray_pop --nostringval-- %errorexec_pop .runexec2
> > --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push
> > --nostringval-- 1762 4 5 %oparray_pop --nostringval--
> > Dictionary stack:
> > --dict:1154/1684(ro)(G)-- --dict:0/20(G)-- --dict:72/200(L)-- --
> > dict:208/300(L)-- --dict:72/200(L)-- --dict:1154/1684(ro)(G)-- --
> > dict:0/16(L)--
> > Current allocation mode is local
> > Last OS error: 2
> > Current file position is 708406
> > GPL Ghostscript 8.63: Unrecoverable error, exit code 1
> >
> >
> > Anders

>
> Well, it works ok in the former versions of Pagestream, so there must have
> been made some changes in the newest version ...?
>
>

The general postscript output has not changed, but a few bugs have been
fixed and significant changes to the generation and encoding of fonts
has been made. New fonts are always coming out, and when it comes to
TrueType/OpenType fonts, there is no rest for a programmer.

Deron

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

fredag 21 november 2008 skrev Anders Drejer:
> > You mentioned in a prior email that Print Setup crashes, so I'm
> > not sure if you got that straightened out.
>
> If I try to access the Printer setup PGS simply close down, so it
> is not possible to eg. change the printer .....

Perhaps I was a bit too quick in my mail 01 NOV to say that there are
no problems with ...29. I simply hadn't tried the print setup as I
continued to use the same printer. Now, when checking, I have the
same close down when accessing print setup.

Furthermore, if I copy and paste any object and then undo that PGS
shuts down directly as I select "Undo Paste".

Regards
Jan
--
Jan Simonson

Fredag 21 november 2008 19:08:14 skrev PageStream Support:
> > Well, it works ok in the former versions of Pagestream, so there must
> > have been made some changes in the newest version ...?
>
> The general postscript output has not changed, but a few bugs have been
> fixed and significant changes to the generation and encoding of fonts
> has been made. New fonts are always coming out, and when it comes to
> TrueType/OpenType fonts, there is no rest for a programmer.
>
> Deron

I am not a programmer, but if it is a font issue, you must have changed
something. My last project was created in PGS 5.0.4.29 and it failed to make a
"correct" postscript output. Then I loaded the project in PGS 5.0.4.3 and then
the postscript output was OK.

Anders

> Fredag 21 november 2008 19:08:14 skrev PageStream Support:
>
>>> Well, it works ok in the former versions of Pagestream, so there must
>>> have been made some changes in the newest version ...?
>>>
>> The general postscript output has not changed, but a few bugs have been
>> fixed and significant changes to the generation and encoding of fonts
>> has been made. New fonts are always coming out, and when it comes to
>> TrueType/OpenType fonts, there is no rest for a programmer.
>>
>> Deron
>>
>
> I am not a programmer, but if it is a font issue, you must have changed
> something.

Umm.. and that is what I said. "significant changes to the generation
and encoding of fonts has been made".

You must have missed the prior email where I asked to do some simple
tests. Did you do that and what were the results? We should verify first
that it is a font issue and if so does it involve a few specific fonts,
most or all.

"Try printing just a box, and some simple text with a few fonts (just
one font at a time of course)."
> My last project was created in PGS 5.0.4.29 and it failed to make a
> "correct" postscript output. Then I loaded the project in PGS 5.0.4.3 and then
> the postscript output was OK.
>

Yes, obviously something is not right.
> Anders
>
>

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

Lørdag 22 november 2008 22:18:09 skrev PageStream Support:
> > Fredag 21 november 2008 19:08:14 skrev PageStream Support:
> >>> Well, it works ok in the former versions of Pagestream, so there must
> >>> have been made some changes in the newest version ...?
> >>
> >> The general postscript output has not changed, but a few bugs have been
> >> fixed and significant changes to the generation and encoding of fonts
> >> has been made. New fonts are always coming out, and when it comes to
> >> TrueType/OpenType fonts, there is no rest for a programmer.
> >>
> >> Deron
> >
> > I am not a programmer, but if it is a font issue, you must have changed
> > something.
>
> Umm.. and that is what I said. "significant changes to the generation
> and encoding of fonts has been made".
>
> You must have missed the prior email where I asked to do some simple
> tests. Did you do that and what were the results? We should verify first
> that it is a font issue and if so does it involve a few specific fonts,
> most or all.
>
> "Try printing just a box, and some simple text with a few fonts (just
> one font at a time of course)."

It seems to be a font issue. For some strange reason some of my fonts (Windows
TrueType fonts maybe?) has two "names" for the same thing ... eg. Arial normal
and Arial regular. Normal is the Danish word for regular. Also the italic
"version" has two names - italic and kursiv (Danish for italic).
If I use Arial regular the postscript output fails, but if I use Arial normal
the postscropt output is OK.

It seems to be a Pagestream only problem. Eg. Openoffice and Scribus does not
this problem with two names for the same font.

Anders

On Monday 24 November 2008 08:05:30 am Anders Drejer wrote:
> It seems to be a Pagestream only problem. Eg. Openoffice and Scribus does
> not this problem with two names for the same font.

You may not find a program that accepts a broader range of fonts than
PageStream. My PageStream lists something like 1166 fonts and. Open Office
Writer 2.4.0 only has about 700 fonts available. I have not tried to use
Scribus lately, but it looks like they are now up to about 1100 fonts in
Scribus 1.3.3.9. So your other programs are probably junking some of your
fonts, without telling you.
Some time back, maybe a couple of years, Deron took the font names from a
different part of the font description, I think. So for one version font
names were changed as you describe--Normal/Regular, Italic/Kursiv, etc. Next
version old documents required the names to be changed again. You might
check to see if changing the font selection helps.
Also, maybe Scribus has messed you up? On my computer it had a lot
of "modified font" messages the first time I ran it, but not the second time.
So a file or something has been created. I may have your problem when I go
to print again.
Also, OpenSuse just had an upgrade yesterday to CUPS. I didn't check to see
why, but these all live in the same fish bowl, so to speak.
I hope you can find a satisfactory resolution to your problem, Anders.

--
No Jesus, No life. Know Jesus, Know life!  The beginning of Wisdom is
 the Fear of the Lord. The wages of sin is death, but the gift of God is
 eternal life through Jesus Christ our Lord!http://Quest4Life.net/glsmith/
http://MSGen.net/http://Quest4Life.net/http://JustForSomeone.com/

> Furthermore, if I copy and paste any object and then undo that PGS
> shuts down directly as I select "Undo Paste".
>

I think the undo ability is new all together, but certainly shouldnt' be
crashing. Thanks for the report, I did manage to reproduce and fix this.

Deron

> Regards
> Jan
>

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

Anders Drejer wrote:
> Lørdag 22 november 2008 22:18:09 skrev PageStream Support:
>
>>> Fredag 21 november 2008 19:08:14 skrev PageStream Support:
>>>
>>>>> Well, it works ok in the former versions of Pagestream, so there must
>>>>> have been made some changes in the newest version ...?
>>>>>
>>>> The general postscript output has not changed, but a few bugs have been
>>>> fixed and significant changes to the generation and encoding of fonts
>>>> has been made. New fonts are always coming out, and when it comes to
>>>> TrueType/OpenType fonts, there is no rest for a programmer.
>>>>
>>>> Deron
>>>>
>>> I am not a programmer, but if it is a font issue, you must have changed
>>> something.
>>>
>> Umm.. and that is what I said. "significant changes to the generation
>> and encoding of fonts has been made".
>>
>> You must have missed the prior email where I asked to do some simple
>> tests. Did you do that and what were the results? We should verify first
>> that it is a font issue and if so does it involve a few specific fonts,
>> most or all.
>>
>> "Try printing just a box, and some simple text with a few fonts (just
>> one font at a time of course)."
>>
>
> It seems to be a font issue. For some strange reason some of my fonts (Windows
> TrueType fonts maybe?) has two "names" for the same thing ... eg. Arial normal
> and Arial regular. Normal is the Danish word for regular. Also the italic
> "version" has two names - italic and kursiv (Danish for italic).
> If I use Arial regular the postscript output fails, but if I use Arial normal
> the postscropt output is OK.
>
> It seems to be a Pagestream only problem. Eg. Openoffice and Scribus does not
> this problem with two names for the same font.
>
> Anders
>

Ok, can you take a look and see if you have unnecessary font paths added
via PageStream's File->System Prefs->Fonts? If any exist, try removing
them and starting over.

Do you have two of the same or similar fonts installed on your system? I
can't think of any other reasons why duplicates would exist.

If you put the lines "DEBUG SHOWFONTS" and "DEBUGFILE" (no quotes, each
to its own line at the end of the file) in your PageStream5.prefs file
(~/.PageStream5/PageStream5.prefs) , then run PageStream, it should
create a debug file called AppDebug.txt in the same location as the
PageStream5.prefs file. If you can send that to me it might help
identify what could be wrong.

Deron

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

Tirsdag 25 november 2008 04:22:44 skrev PageStream Support:
> Anders Drejer wrote:
> > Lørdag 22 november 2008 22:18:09 skrev PageStream Support:
> >>> Fredag 21 november 2008 19:08:14 skrev PageStream Support:
> >>>>> Well, it works ok in the former versions of Pagestream, so there must
> >>>>> have been made some changes in the newest version ...?
> >>>>
> >>>> The general postscript output has not changed, but a few bugs have
> >>>> been fixed and significant changes to the generation and encoding of
> >>>> fonts has been made. New fonts are always coming out, and when it
> >>>> comes to TrueType/OpenType fonts, there is no rest for a programmer.
> >>>>
> >>>> Deron
> >>>
> >>> I am not a programmer, but if it is a font issue, you must have changed
> >>> something.
> >>
> >> Umm.. and that is what I said. "significant changes to the generation
> >> and encoding of fonts has been made".
> >>
> >> You must have missed the prior email where I asked to do some simple
> >> tests. Did you do that and what were the results? We should verify first
> >> that it is a font issue and if so does it involve a few specific fonts,
> >> most or all.
> >>
> >> "Try printing just a box, and some simple text with a few fonts (just
> >> one font at a time of course)."
> >
> > It seems to be a font issue. For some strange reason some of my fonts
> > (Windows TrueType fonts maybe?) has two "names" for the same thing ...
> > eg. Arial normal and Arial regular. Normal is the Danish word for
> > regular. Also the italic "version" has two names - italic and kursiv
> > (Danish for italic). If I use Arial regular the postscript output fails,
> > but if I use Arial normal the postscropt output is OK.
> >
> > It seems to be a Pagestream only problem. Eg. Openoffice and Scribus does
> > not this problem with two names for the same font.
> >
> > Anders
>
> Ok, can you take a look and see if you have unnecessary font paths added
> via PageStream's File->System Prefs->Fonts? If any exist, try removing
> them and starting over.
>
> Do you have two of the same or similar fonts installed on your system? I
> can't think of any other reasons why duplicates would exist.
>
> If you put the lines "DEBUG SHOWFONTS" and "DEBUGFILE" (no quotes, each
> to its own line at the end of the file) in your PageStream5.prefs file
> (~/.PageStream5/PageStream5.prefs) , then run PageStream, it should
> create a debug file called AppDebug.txt in the same location as the
> PageStream5.prefs file. If you can send that to me it might help
> identify what could be wrong.
>
> Deron

I will as soon as I get rid of the Pagestream expired alert

Anders

Fredag 21 november 2008 18:49:40 skrev Anders Drejer:

> > First, what problems did you have the Save as PDF? 5.0.4.29 should be
> > almost perfect. I think the only thing not supported is Shape fill, and
> > patterned gradient fills. Neither of which are very common and not
> > directly supported in PDF format (to support these items will require
> > rendering those objects into a bitmap and embedding the bitmap in the
> > PDF which is not an idea solution either).
>
> PDF export seems to work quite well now ..... but eps clipart is not
> exported to the pdf file, so it is useless to me. That is why I always
> print to a postscript file and covert it to pdf using ps2pdf

Am I the only one having this problem with EPS grapics not being exported when
using "Export to PDF"?

Anders