Hi all,

I have been following this thread with interest.

I have PGS 5.0.5.8 Pro installed since it came out, and have had no
problems using it for my purposes (which -- I must admit -- have been
fairly limited in recent times, but I will be making heavier use of it
again soon). Also, after a few hassles, I successfully installed Python
2 about the same time (I have the 64-bit version of Windows 7, and at
first tried to install the 64-bit version of Python, only to find that
wouldn't work with PGS).

Anyway, as this thread developed, I decided it would be interesting to
try out the 'FontSpec' script myself. I fired up PGS, clicked on the
'Scripts' menu, found that 'Play External Script...' was available,
double-clicked on the 'FontSpec' script, got the little requester-box
window, selected 'Six fonts per page', left the other choice on 'All
fonts', then clicked on the 'Proceed' button, and . . . nothing.
Actually, it was worse than that: the 'new document' blank page I had
opened after starting PGS disappeared and the PGS screen returned to the
grey background with the PageStream Navigator box in the centre, as if
PGS had just been started up again. On my third try, I actually got a
little further: a little box saying 'Creating fonts' came up for a
moment, but then it disappeared and I was returned to the PGS start-up
screen again.

Actually, my problem seems to go beyond the 'FontSpec' script. I
thought I should try some others, so I selected the 'TechReport' one: a
little box came up saying 'Preparing Report', the progress bar below
went along three blocks, stopped, and then a message saying 'not
responding', next to 'Please wait' in the box's title bar. The box then
disappeared. At least in this case the new, blank document I had opened
at the outset remained open.

I obviously have a problem. Any suggestions would be greatly appreciated.

Malcolm Kays

--

Malcolm Kays

On Mon, 30 Jul 2012 08:04:42 -0400, M. Kays <mkays@netspace.net.au> wrote:

>
> Hi all,
>
> I have been following this thread with interest.
>
> I have PGS 5.0.5.8 Pro installed since it came out, and have had noproblems using it for my purposes (which -- I must admit -- have beenfairly limited in recent times, but I will be making heavier use of itagain soon). Also, after a few hassles, I successfully installed Python2 about the same time (I have the 64-bit version of Windows 7, and atfirst tried to install the 64-bit version of Python, only to find thatwouldn't work with PGS).
I too became curious about this.. tried the fontspec script and had problems..
I opened the script in an editor and found this line in the comments

>> # Only compatible with PageStream 5.0.2.12+ due to interface requirements<<

if there were changes made from that version then that is where the problem is.

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

Hello All,

The script requires at least PgS 5.0.2.12 -- if you have an *older* version of PgS the script will not work.

Second, apparently I "did a bad thing" when I last edited the script. I primarily code in C-style languages and my fingers automatically put a semicolon at the end of two lines. That is an error in Python.

Third, the script does printing by addressing the document name and PgS does not allow a document to have one of the specified names (this is the *document* name, not the *file* name).

I have uploaded v1.4.2 of the script tohttp://pagestream.ylansi.net -- it includes fixes for the mentioned bugs. I cannot presently test printing, but I can testify that it sure tries to print (each page is a separate print job, I had fun clearing my print queue

*Please* read the documentation. It has important information on using the script. Do not expect it to work without taking action as described in the documentation. Deron, if PgS OpenDocument() function was able to force default decision on font substitution this could be avoided.

Finally, this is an old and clunky script. It is just barely a port from ARexx to Python and is not well written as a result. If there is sufficient interest I will improve the script, but as I personally have no use for it unless there is I won't bother. Regardless, I *will* fix any bugs that are brought to my attention.

Tim Doty

On Jul 30, 2012, at 9:51 AM, admfubar@gmail.com wrote:

> On Mon, 30 Jul 2012 08:04:42 -0400, M. Kays <mkays@netspace.net.au> wrote:
>
> >
> > Hi all,
> >
> > I have been following this thread with interest.
> >
> > I have PGS 5.0.5.8 Pro installed since it came out, and have had noproblems using it for my purposes (which -- I must admit -- have beenfairly limited in recent times, but I will be making heavier use of itagain soon). Also, after a few hassles, I successfully installed Python2 about the same time (I have the 64-bit version of Windows 7, and atfirst tried to install the 64-bit version of Python, only to find thatwouldn't work with PGS).
> I too became curious about this.. tried the fontspec script and had problems..
> I opened the script in an editor and found this line in the comments
>
> >> # Only compatible with PageStream 5.0.2.12+ due to interface requirements<<
>
> if there were changes made from that version then that is where the problem is.
>
> [Non-text portions of this message have been removed]
>
>