Hello,

> Subject: PageStream 5.0.5.6 Amiga-OS3-68k ready to download

I installed it and launched it once.
It asked my name and product key. I entered them and the program quitted.

So I executed it again. The GUI never opens.

Bug created:
http://www.pagestream.org/showbugs.php?id=303&q=-&status=Open

I remember there was some way to have more details on what happens. Was it creating an env variable?
Can you add this to the file Readme.Amiga.txt ?

Bye
--
Philippe 'Elwood' FERRUCCI
Sam440 Flex 733Mhz
http://elwoodb.free.fr

Did you run it from the shell or the workbench?

Deron

> Hello,
>
>
>> Subject: PageStream 5.0.5.6 Amiga-OS3-68k ready to download
>>
>
> I installed it and launched it once.
> It asked my name and product key. I entered them and the program quitted.
>
> So I executed it again. The GUI never opens.
>
> Bug created:
>http://www.pagestream.org/showbugs.php?id=303&q=-&status=Open
>
>
> I remember there was some way to have more details on what happens. Was it creating an env variable?
> Can you add this to the file Readme.Amiga.txt ?
>
> Bye
>

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

On 03/23/2010, Philippe Ferrucci wrote:

> Hello,
>
>> Subject: PageStream 5.0.5.6 Amiga-OS3-68k ready to download
>
> I installed it and launched it once.
> It asked my name and product key. I entered them and the program
> quitted.

Are you sure you waited long enough? It seems to me 5055 is a bit quicker
than 5056, but there is still a fairly long pause after the sign-up screen
disappears before the HD activity light comes on and tells you something is
going to happen if you wait a bit longer.
--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Hello,

On 23/03/2010, PageStream Support wrote:

> Did you run it from the shell or the workbench?

Workbench.
Some people use the shell?

Bye
--
Philippe 'Elwood' FERRUCCI
Sam440 Flex 733Mhz
http://elwoodb.free.fr

Hello,

> Did you run it from the shell or the workbench?

Ok, bug closed.
Sorry

Bye
--
Philippe 'Elwood' FERRUCCI
Sam440 Flex 733Mhz
http://elwoodb.free.fr

Hello,

On 23/03/2010, Bart Mathias wrote:

> Are you sure you waited long enough? It seems to me 5055 is a bit quicker
> than 5056, but there is still a fairly long pause after the sign-up screen
> disappears before the HD activity light comes on and tells you something is
> going to happen if you wait a bit longer.

Yes.
The problem was that this version must be launched from shell and not Workbench, as per the download instructions. :-/

Bye
--
Philippe 'Elwood' FERRUCCI
Sam440 Flex 733Mhz
http://elwoodb.free.fr

Greetings "Bart Mathias" <mathias@hawaii.edu>
On 23/03/2010 at 21:53 you wrote concerning
Re: [PageStreamAmigaBeta] PageStream 5.0.5.6 doesn't open

BM> On 03/23/2010, Philippe Ferrucci wrote:

Hello Bart and Philippe,

BM>>> Subject: PageStream 5.0.5.6 Amiga-OS3-68k ready to download
BM>>
BM>> I installed it and launched it once.
BM>> It asked my name and product key. I entered them and the program
BM>> quitted.

That's not a problem! That's the way the registration process seems to work. Just go to the executable icon or a shell and restart 5056. And, like Bart suggests, be patient, it does not respond quickly.

You can also mount the following little ARexx file on AmiDock, then you can start 5056 from a shell with a click on AmiDock.
------------
/* ARexx script 'StartupPgS5056.rexx' located in
** WorkageStream5056/
** sets the stack size and then RUNs the executable file PageStream5 located in
** WorkageStream5056/
*/

Address Command
"cd WorkageStream5056"
"Stack 300000"
"PageStream5"
------------------

Here, the above will open PageStream 5056 in about 45 seconds from the time you call the script into action from AmiDock. I get the Yellow alert, but one click allows the startup to continue. After closing 5056 and opening it a second time---successfully---the Yellow alert does not come up.

Before you run StartupPgS5056.rexx open it with «Icons -> Information...» and, in the Icon tab, set

Default tool: Sys:C/rx
Start from: Workbench

I think there is something wrong with my script above, since a shell-like looking window opens with title WAIT and hangs around until I close 5056, but it does not impede the opening of 5056.

BM> Are you sure you waited long enough? It seems to me 5055 is a bit quicker
BM> than 5056, but there is still a fairly long pause after the sign-up screen
BM> disappears before the HD activity light comes on and tells you something is
BM> going to happen if you wait a bit longer.

Like Bart suggests, it is slow to open.

Cheers Don (Green Dragon)
--

On 03/24/2010, Ferguson, Don wrote:

> [...]
> You can also mount the following little ARexx file on AmiDock, then you
> can start 5056 from a shell with a click on AmiDock. ------------
> /* ARexx script 'StartupPgS5056.rexx' located in
> ** WorkageStream5056/
> ** sets the stack size and then RUNs the executable file PageStream5
> located in ** WorkageStream5056/
> */
>
> Address Command
> "cd WorkageStream5056"
> "Stack 300000"
> "PageStream5"
> ------------------

Is there a specific advantage to increasing the stack from the default (?)
65,528?

> [...]
> I think there is something wrong with my script above, since a
> shell-like looking window opens with title WAIT and hangs around until
> I close 5056, but it does not impede the opening of 5056.

What if you changed the last command to "run >nil: PageStream5"? I haven't
tried that specifically, too lazy to write an ARexx thing, but I typee
RA^E"pgs," which runs this fancy Shell script:

run >nil: testpartition:pgs5056/PageStream5

I used to get a shell-like window (but not labelled "Wait"--I think it said
"Output" or "Output Window") until I added the ">nil:" to it.

--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Greetings "Bart Mathias" <mathias@hawaii.edu>
On 25/03/2010 at 22:09 you wrote concerning
Re: [PageStreamAmigaBeta] PageStream 5.0.5.6 doesn't open

Hi Bart,

BM> On 03/24/2010, Ferguson, Don wrote:

<<snip>>
BM>> Address Command
BM>> "cd WorkageStream5056"
BM>> "Stack 300000"
BM>> "PageStream5"
BM>> ------------------

BM> Is there a specific advantage to increasing the stack from the default (?)
BM> 65,528?

I doubt it! Long time ago when people were experimenting with opening from a shell, Deron suggested that 300,000 should be more than enough, so I usually throw in "Stack 300000" to be "on the safe side" although I don't really know why 300000 is any 'safer' than 65,528. I'll change the script to a smaller value and see I can notice a difference.

BM>> [...]
BM>> I think there is something wrong with my script above, since a
BM>> shell-like looking window opens with title WAIT and hangs around until
BM>> I close 5056, but it does not impede the opening of 5056.

BM> What if you changed the last command to "run >nil: PageStream5"? I haven't
BM> tried that specifically, too lazy to write an ARexx thing, but I typee
BM> RA^E"pgs," which runs this fancy Shell script:

BM>> nil: testpartition:pgs5056/PageStream5

BM> I used to get a shell-like window (but not labelled "Wait"--I think it said
BM> "Output" or "Output Window") until I added the ">nil:" to it.

I'll try what you suggested.............And he did. No problem opening with the stack set to 32768, however when I call PageStream5 into action (>nil: or NO >nil I still get the shell window. No sweat! After a few trials, it is not at all clear that PageStream's performance is affected by the 'Stack' setting.

However, the main change I made was to take the file
«UserPrefs/PageStream5 Fonts»
that I use in PageStream 5.0.3.3 and copied it into UserPrefs/ for 5056! Did this in the hope of 5056 becoming better behaved when I reach for the text cursor.

Did not work, although I received a surprise when I opened the «5.0 Flyer.pgs» document. I tried to do a font substitution by replacing Arial with Garamond Antiqua, and I think it worked because when PageStream displayed the Flyer, the text was in some pleasant body font which looked like Garamond Antiqua, but as soon as I attempted to find out by grabbing the text cursor, the GR comes, and, on return to PageStream 5056, one finds the program dead. At least Arial was not replaced by Artistic Normal.

So far, I cannot get by the text cursor. Can others use the text cursor with success? Until we can, things are nay so good.

Cheers Don (Green Dragon)
--

On 03/26/2010, Ferguson, Don wrote:

> [...]
>> What if you changed the last command to "run >nil: PageStream5"? I
>> haven't tried that specifically, too lazy to write an ARexx thing, but
>> I typee RA^E"pgs," which runs this fancy Shell script:
>
>>> nil: testpartition:pgs5056/PageStream5
>[...]
>
> I'll try what you suggested.............And he did. No problem opening
> with the stack set to 32768, however when I call PageStream5 into
> action (>nil: or NO >nil I still get the shell window.

Must be the difference in the OS versions again.

> However, the main change I made was to take the file
> «UserPrefs/PageStream5 Fonts»
> that I use in PageStream 5.0.3.3 and copied it into UserPrefs/ for
> 5056! Did this in the hope of 5056 becoming better behaved when I reach
> for the text cursor.
>
> Did not work, although I received a surprise when I opened the «5.0
> Flyer.pgs» document. I tried to do a font substitution by replacing
> Arial with Garamond Antiqua, and I think it worked because when
> PageStream displayed the Flyer, the text was in some pleasant body font
> which looked like Garamond Antiqua, but as soon as I attempted to find
> out by grabbing the text cursor, the GR comes, and, on return to
> PageStream 5056, one finds the program dead. At least Arial was not
> replaced by Artistic Normal.

My attempts to change font--to hit anything but "OK" in the font
substitution requester--have roused a GR. Or possibly all but one; I have a
dim memory of doing something like what you did, but it's probably a false
memory.

I too have copied an older PageStream5 Fonts into 5056 preferences.

However, here is a somewhat Curious Thing. Last month I was hoping to be
able to use 5055 to do my Faculty Retirees Association announcement for
March (I was going to link it here, but both OWB and IBrowse fail to find
the site right now! "Couldn't resolve host name." That's kind of scary! Yet
AmiTradeCenter finds it OK. But I digress.). As you may recall, 5055 also
brought up all text as Artistic, but it was changeable. So when I opened
the draft version from 5054, which I had made running OS4 off the OS4.1
install disk, it was all Artistic.

I changed the text of the document from Artistic to Bitstream Vera Serif (or
was it Times?). I was going to change the font in a yellow banner running
up the left side of the page, but I couldn't remember off hand what font it
was supposed to be in, without looking at it with an earlier PageStream. In
the meantime I found out that I wouldn't be able to complete the job with
5055 after all, though I can't remember why at the moment, so I never
changed the banner font. I did save it to 5055/Documents, however.

Now here is the interesting part. If I open the 5054 version in 5056,
everything comes out falsely in Artistic, but if I open the 5055 version
with the font change, only the unchanged banner is in Artistic. The rest is
Bitstream Vera or whatever!

I wish that were all. There's something maybe stranger. I have long since
saved the banner part of the document as a template to base the next
month's announcement on. I have a copy of that dated 2009-04-06 in 5054
Documents that opens as other than Artistic in 5056, while another copy of
that in the same drawer dated 2010-01-04 opens as Artistic. I have another,
newer version of that in 5055 Documents.
The same drawer I can open the announcement from and get non-Artistic text
except for the banner, but the template opens with the banner *not* in
Artistic.

I hope by now you are as confused as I.

> So far, I cannot get by the text cursor. Can others use the text cursor
> with success? Until we can, things are nay so good.

Nay.

All of a sudden, my browsers can find the announcement again. If you're
curious enough, this is what it is supposed to look like:
http://www.frauhm.org/newsletter.html. It's a jpeg, SGrabbed from a
PageStream PDF export.
--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Since january 2009 I have composed and printed, mail-merged, a monthly
announcement for my faculty retirees association. It's time to do it for
our May meeting, but all of a sudden 5.0.3.3 has taken to stalling at the
"Loading Filters..." stage. I recall that this was a problem with one of
the newer 5.x.x.x's, but it never happened with 5.0.3.3 before as far as I
can recall.

I haven't tried yet, but I suspect I won't be able to mail-merge printing
with 5.0.5.6 because of the font problems. Anyone know a secret how to get
past Loading Filters?
--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Greetings "Bart Mathias" <mathias@hawaii.edu>
On 28/04/2010 at 07:31 you wrote concerning
Re: [PageStreamAmigaBeta] PageStream 5.0.3.3 revolting

Hi Bart.

BM> Since january 2009 I have composed and printed, mail-merged, a monthly
BM> announcement for my faculty retirees association. It's time to do it for
BM> our May meeting, but all of a sudden 5.0.3.3 has taken to stalling at the
BM> "Loading Filters..." stage. I recall that this was a problem with one of
BM> the newer 5.x.x.x's, but it never happened with 5.0.3.3 before as far as I
BM> can recall.

BM> I haven't tried yet, but I suspect I won't be able to mail-merge printing
BM> with 5.0.5.6 because of the font problems. Anyone know a secret how to get
BM> past Loading Filters?

Sorry Bart, have not encountered that problem with any of the PageStreams.

Cheers Don (Green Dragon)
--

On 04/28/2010, Ferguson, Don wrote:

> Greetings "Bart Mathias" <mathias@hawaii.edu>
> On 28/04/2010 at 07:31 you wrote concerning
> Re: [PageStreamAmigaBeta] PageStream 5.0.3.3 revolting
>
> Hi Bart.
>
>
>> Since january 2009 I have composed and printed, mail-merged, a monthly
>> announcement for my faculty retirees association. It's time to do it
>> for our May meeting, but all of a sudden 5.0.3.3 has taken to stalling
>> at the "Loading Filters..." stage. I recall that this was a problem
>> with one of the newer 5.x.x.x's, but it never happened with 5.0.3.3
>> before as far as I can recall.
>[...]
> Sorry Bart, have not encountered that problem with any of the
> PageStreams.

I think maybe it was 5.0.5.5 I also had it with, but maybe that's the one
where if one waited long enough something would finally happen? I can't
remember, because it was over a week ago that I last messed with 5.0.5.5,
and I accidentally deleted it. I can't image why 5.0.3.3. should catch (a
worse version of) the bug. I can't remember changing anything of moment in
the last month.

But I found an unexpected route out of my problem. Somebody else designed
the announcement this time; I only need to change the PDF to .iff; load it
into FinalWriter, and print it out. I had never used FinalWriter's
mail-merge, but it turns out to be a snap to use, compared to PageStream's.
--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Hi Bart,

> AmigaOne XE-G4 OS4.1u1
5.0.3.3 stopped working with the OS4 Update 1, (at least for me)
I have a partition with the previous AOS4 to use with PageStream 5.0.3.3

On 04/30/2010, pvannicvt wrote:

>
>
> Hi Bart,
>
>> AmigaOne XE-G4 OS4.1u1
> 5.0.3.3 stopped working with the OS4 Update 1, (at least for me)
> I have a partition with the previous AOS4 to use with PageStream
> 5.0.3.3

Yes! Now I remember! Thanks for that.

To use 5.0.3.3 I had to boot from my 4.1 install disk! Will I remember that
in August when I need it again? (Of course, by then we'll all have 5.0.6.7,
working perfectly.)

My memory is getting really bad, but my doctor just laughed at me when I
asked him to put in for a brain transpland.

--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Greetings "Bart Mathias" <mathias@hawaii.edu>
On 29/04/2010 at 08:05 you wrote concerning
Re: [PageStreamAmigaBeta] PageStream 5.0.3.3 revolting

Hi Bart,

<<snip>>

BM> But I found an unexpected route out of my problem. Somebody else designed
BM> the announcement this time; I only need to change the PDF to .iff; load it
BM> into FinalWriter, and print it out. I had never used FinalWriter's
BM> mail-merge, but it turns out to be a snap to use, compared to PageStream's.

Well ..... that's a sneaky and roundabout trick, but since it words! Why not?

However, it is time that these kind of gnats be eliminated. It's been a long wait.

Cheers Don (Green Dragon)
--

Greetings "pvannicvt" <pvanni@inwind.it>
On 30/04/2010 at 07:27 you wrote concerning
[PageStreamAmigaBeta] Re: PageStream 5.0.3.3 revolting

Hi pvanni,

p>> AmigaOne XE-G4 OS4.1u1

p> 5.0.3.3 stopped working with the OS4 Update 1, (at least for me)
p> I have a partition with the previous AOS4 to use with PageStream 5.0.3.3

Good Lord! What rotten news. More obstacles for Deron to solve. Bummer!

<<snip>>

Cheers Don (Green Dragon)
--

I have a document I must get to people soon, with a new-to-me problem. The
docuement comprises a jpeg on the first page, some text on the second page,
and another jpeg below.

Both jpegs come out fine, but I get no text, and meanwhile a window opens
reporting the below (I have left out the beginning which is exactly the
same as the first lines below).

Can anyone give me a hint as to what new way I have discovered to do
something wrong?

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: 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: 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: 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: 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 'F1'
XPDF error: No font in show/space
XPDF error: No font in show
XPDF error: No font in show
XPDF error: No font in show
XPDF error: No font in show
XPDF error: No font in show
XPDF error: No font in show
XPDF error: No font in show/space
XPDF error: No font in show

--
Bart Mathias
AmigaOne XE-G4 OS4.1u3

On 11/15/11 1:26 PM, Bart Mathias wrote:
> I have a document I must get to people soon, with a new-to-me problem. The
> docuement comprises a jpeg on the first page, some text on the second page,
> and another jpeg below.
>
> Both jpegs come out fine, but I get no text, and meanwhile a window opens
> reporting the below (I have left out the beginning which is exactly the
> same as the first lines below).
>
> Can anyone give me a hint as to what new way I have discovered to do
> something wrong?
>
> 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: 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: 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: 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: 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 'F1'
> XPDF error: No font in show/space
> XPDF error: No font in show
> XPDF error: No font in show
> XPDF error: No font in show
> XPDF error: No font in show
> XPDF error: No font in show
> XPDF error: No font in show
> XPDF error: No font in show/space
> XPDF error: No font in show
>

Hello Bart,

Do you know if the file works in other browsers? The ToUnicode CMap is a
part of the definition in an embedded font, so if it doesn't like that
CMap it might decide to discard the entire font definition which leaves
you with no text.

More recent versions of PageStream of course may really on more
complicated PDF features which are not always well supporting in PDF
viewers. Complex gradient fills, and using more then 256 characters from
a font are ones that come to mind.

Your welcome to send the PDF to me at support@pagestream.org and I'll
see if I can open it here.

Deron

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

On 11/15/2011, PageStream Support wrote:

> On 11/15/11 1:26 PM, Bart Mathias wrote:
>> I have a document I must get to people soon, with a new-to-me problem.
>> The docuement comprises a jpeg on the first page, some text on the
>> second page, and another jpeg below.
>>
>> Both jpegs come out fine, but I get no text, and meanwhile a window
>> opens reporting the below [...]
>> 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 'F1'
>> XPDF error: No font in show/space
>> XPDF error: No font in show
>> XPDF error: No font in show/space
>> XPDF error: No font in show
>
> Hello Bart,
>
> Do you know if the file works in other browsers? The ToUnicode CMap is
> a part of the definition in an embedded font, so if it doesn't like
> that CMap it might decide to discard the entire font definition which
> leaves you with no text.

Knowing that AmiPDF often has trouble with PDFs that AmiGS handles well, I
should have thought to try AmiGS before posting my problem. Indeed, the
document displays just as it should in AmiGS, and I believe that I can
assume it will display properly for just about anyone I e-mail it to.

Not a PageStream problem, just a Bart problem. Thanks for the quick and very
helpful response.

It's still a bit odd, though, because I use that font (Bitstream Vera Serif)
in the monthly announcements I write, and this is the first time I have had
this reaction.

> More recent versions of PageStream of course may really on more
> complicated PDF features which are not always well supporting in PDF
> viewers. Complex gradient fills, and using more then 256 characters
> from a font are ones that come to mind.
>
> Your welcome to send the PDF to me at support@pagestream.org and I'll
> see if I can open it here.

--
Bart Mathias
AmigaOne XE-G4 OS4.1u3