Hi Tim,

I downloaded your new version of FontSpec (v.1.4.2) and installed the
contents of the zip file in my PageStream scripts directory (replacing
the earlier versions). I then tried to run the script in PGS, but --
alas -- the results were the same as previously. (That is, I got
through to the 'Proceed' button, clicked on that, got the 'Creating
Fonts' box, but was soon returned to the PGS start-up page, with no font
pages created.) I read the documentation, and tried saving the blank new
document first, before running the script to fill it, but it made no
difference.

Seeing as it works OK on your system, there must be some flaw in my
set-up. Don't lose any sleep over this -- I was just trying it out as a
matter of interest. If I run into any problems that really thwart my
usage of PGS for important purposes in future, then I'll yell for help!

Cheers,

Malcolm

--

Malcolm Kays
Hobart Tasmania AUSTRALIA

The same here (using the latest 1.4.2).
Tried the output as bitmap, PostScript file, and Windows printer.
When I open a new document, this document is gone, when the script is done.

Theo

Op 31-7-2012 14:01, M. Kays schreef:
> Hi Tim,
>
> I downloaded your new version of FontSpec (v.1.4.2) and installed the
> contents of the zip file in my PageStream scripts directory (replacing
> the earlier versions). I then tried to run the script in PGS, but --
> alas -- the results were the same as previously. (That is, I got
> through to the 'Proceed' button, clicked on that, got the 'Creating
> Fonts' box, but was soon returned to the PGS start-up page, with no font
> pages created.) I read the documentation, and tried saving the blank new
> document first, before running the script to fill it, but it made no
> difference.
>
> Seeing as it works OK on your system, there must be some flaw in my
> set-up. Don't lose any sleep over this -- I was just trying it out as a
> matter of interest. If I run into any problems that really thwart my
> usage of PGS for important purposes in future, then I'll yell for help!
>
> Cheers,
>
> Malcolm
>

--
PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0
AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM

Thanks for the bug report. It turns out I slipped and didn't make the correction complete: printing 6 to a page still wouldn't work (if there are too many bugs I'll re-architect it simply to correct bugs, this was a victim of that issue)

It'll be re-uploaded soon as v1.4.3

Tim Doty

On Jul 31, 2012, at 7:01 AM, M. Kays wrote:

> Hi Tim,
>
> I downloaded your new version of FontSpec (v.1.4.2) and installed the
> contents of the zip file in my PageStream scripts directory (replacing
> the earlier versions). I then tried to run the script in PGS, but --
> alas -- the results were the same as previously. (That is, I got
> through to the 'Proceed' button, clicked on that, got the 'Creating
> Fonts' box, but was soon returned to the PGS start-up page, with no font
> pages created.) I read the documentation, and tried saving the blank new
> document first, before running the script to fill it, but it made no
> difference.
>
> Seeing as it works OK on your system, there must be some flaw in my
> set-up. Don't lose any sleep over this -- I was just trying it out as a
> matter of interest. If I run into any problems that really thwart my
> usage of PGS for important purposes in future, then I'll yell for help!
>
> Cheers,
>
> Malcolm
>
> --
>
> Malcolm Kays
> Hobart Tasmania AUSTRALIA
>
>

I probably need to be a bit more explicit in the usage:

1. Download archive
2. Extract wherever you want
3. Open FontSpec1.pgs
4. Ensure font substitution replaces the fonts (not display only)
5. Make sure the document title has not changed*
6. Save document and close
7. Repeat 3, 4, 5 and 6 for FontSpec6.pgs**
8. Run script***

* It *must* be FontSpec for the script to work. If it says FontSpec1 it will not work

** To avoid above problem never have both open at the same time

*** To avoid issues don't have either document open when running the script

The script quietly opens the document in the background. You should never see it, just progress bars and print output.

I have not tested "Custom Layout". At one time I know that it worked, but I have no idea at this point.

Tim Doty

On Jul 31, 2012, at 7:37 AM, Theo Zweers wrote:

> The same here (using the latest 1.4.2).
> Tried the output as bitmap, PostScript file, and Windows printer.
> When I open a new document, this document is gone, when the script is done.
>
> Theo
>
> Op 31-7-2012 14:01, M. Kays schreef:
> > Hi Tim,
> >
> > I downloaded your new version of FontSpec (v.1.4.2) and installed the
> > contents of the zip file in my PageStream scripts directory (replacing
> > the earlier versions). I then tried to run the script in PGS, but --
> > alas -- the results were the same as previously. (That is, I got
> > through to the 'Proceed' button, clicked on that, got the 'Creating
> > Fonts' box, but was soon returned to the PGS start-up page, with no font
> > pages created.) I read the documentation, and tried saving the blank new
> > document first, before running the script to fill it, but it made no
> > difference.
> >
> > Seeing as it works OK on your system, there must be some flaw in my
> > set-up. Don't lose any sleep over this -- I was just trying it out as a
> > matter of interest. If I run into any problems that really thwart my
> > usage of PGS for important purposes in future, then I'll yell for help!
> >
> > Cheers,
> >
> > Malcolm
> >
>
> --
> PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0
> AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM
>
>

Hi Tim!

A quick look at this.

Op 31-7-2012 14:59, Tim Doty schreef:
> I probably need to be a bit more explicit in the usage:
>
> 1. Download archive
> 2. Extract wherever you want
> 3. Open FontSpec1.pgs

Done that!

> 4. Ensure font substitution replaces the fonts (not display only)

Also done.

> 5. Make sure the document title has not changed*

??? If I open FontSpec1.pgs, then the document name is FontSpec1.pgs and
not FontSpec.pgs?!

> 6. Save document and close

Saved it as FontSpec.pgs

> 7. Repeat 3, 4, 5 and 6 for FontSpec6.pgs**

According to you (?) (see 5 and 6) I must replace FontSpec.pgs with this
one? Must not be called FontSpec6.pgs?

> 8. Run script***

6 fonts per page, selected 6 fonts. Proceed...
...and gone is the document.

The trouble (my), I remember that I had it once (years ago!) working.
OK, not this version (1.4.2 ).
Waiting for 1.4.3.

Theo

>
> * It *must* be FontSpec for the script to work. If it says FontSpec1 it will not work
>
> ** To avoid above problem never have both open at the same time
>
> *** To avoid issues don't have either document open when running the script
>
> The script quietly opens the document in the background. You should never see it, just progress bars and print output.
>
> I have not tested "Custom Layout". At one time I know that it worked, but I have no idea at this point.
>
> Tim Doty
>
>
> On Jul 31, 2012, at 7:37 AM, Theo Zweers wrote:
>
>> The same here (using the latest 1.4.2).
>> Tried the output as bitmap, PostScript file, and Windows printer.
>> When I open a new document, this document is gone, when the script is done.
>>
>> Theo
>>
>> Op 31-7-2012 14:01, M. Kays schreef:
>>> Hi Tim,
>>>
>>> I downloaded your new version of FontSpec (v.1.4.2) and installed the
>>> contents of the zip file in my PageStream scripts directory (replacing
>>> the earlier versions). I then tried to run the script in PGS, but --
>>> alas -- the results were the same as previously. (That is, I got
>>> through to the 'Proceed' button, clicked on that, got the 'Creating
>>> Fonts' box, but was soon returned to the PGS start-up page, with no font
>>> pages created.) I read the documentation, and tried saving the blank new
>>> document first, before running the script to fill it, but it made no
>>> difference.
>>>
>>> Seeing as it works OK on your system, there must be some flaw in my
>>> set-up. Don't lose any sleep over this -- I was just trying it out as a
>>> matter of interest. If I run into any problems that really thwart my
>>> usage of PGS for important purposes in future, then I'll yell for help!
>>>
>>> Cheers,
>>>
>>> Malcolm
>>>
>>

--
PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0
AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM

There is a difference between the document name and file name.

File name: this is the name of the file, e.g., MyDoc.pgs

Document name: this is the name assigned to the document. Go to the menu, it's the document property (as opposed to chapter name or page name)

If you change the file names the script won't work. If you change the document name the script won't work. The *only* thing to do is ensure that font substitution won't occur. Anything else will break the script. I can't provide documents that will avoid font substitution for all users. PageStream doesn't permit silently accepting the defaults in the font substitution or I could prevent the issue in the script.

Tim Doty

On Jul 31, 2012, at 9:38, Theo Zweers <tjzwrs@gmail.com> wrote:

> Hi Tim!
>
> A quick look at this.
>
> Op 31-7-2012 14:59, Tim Doty schreef:
>> I probably need to be a bit more explicit in the usage:
>>
>> 1. Download archive
>> 2. Extract wherever you want
>> 3. Open FontSpec1.pgs
>
> Done that!
>
>> 4. Ensure font substitution replaces the fonts (not display only)
>
> Also done.
>
>> 5. Make sure the document title has not changed*
>
> ??? If I open FontSpec1.pgs, then the document name is FontSpec1.pgs and
> not FontSpec.pgs?!
>
>> 6. Save document and close
>
> Saved it as FontSpec.pgs
>
>> 7. Repeat 3, 4, 5 and 6 for FontSpec6.pgs**
>
> According to you (?) (see 5 and 6) I must replace FontSpec.pgs with this
> one? Must not be called FontSpec6.pgs?
>
>> 8. Run script***
>
> 6 fonts per page, selected 6 fonts. Proceed...
> ...and gone is the document.
>
>
> The trouble (my), I remember that I had it once (years ago!) working.
> OK, not this version (1.4.2 ).
> Waiting for 1.4.3.
>
> Theo
>
>>
>> * It *must* be FontSpec for the script to work. If it says FontSpec1 it will not work
>>
>> ** To avoid above problem never have both open at the same time
>>
>> *** To avoid issues don't have either document open when running the script
>>
>> The script quietly opens the document in the background. You should never see it, just progress bars and print output.
>>
>> I have not tested "Custom Layout". At one time I know that it worked, but I have no idea at this point.
>>
>> Tim Doty
>>
>>
>> On Jul 31, 2012, at 7:37 AM, Theo Zweers wrote:
>>
>>> The same here (using the latest 1.4.2).
>>> Tried the output as bitmap, PostScript file, and Windows printer.
>>> When I open a new document, this document is gone, when the script is done.
>>>
>>> Theo
>>>
>>> Op 31-7-2012 14:01, M. Kays schreef:
>>>> Hi Tim,
>>>>
>>>> I downloaded your new version of FontSpec (v.1.4.2) and installed the
>>>> contents of the zip file in my PageStream scripts directory (replacing
>>>> the earlier versions). I then tried to run the script in PGS, but --
>>>> alas -- the results were the same as previously. (That is, I got
>>>> through to the 'Proceed' button, clicked on that, got the 'Creating
>>>> Fonts' box, but was soon returned to the PGS start-up page, with no font
>>>> pages created.) I read the documentation, and tried saving the blank new
>>>> document first, before running the script to fill it, but it made no
>>>> difference.
>>>>
>>>> Seeing as it works OK on your system, there must be some flaw in my
>>>> set-up. Don't lose any sleep over this -- I was just trying it out as a
>>>> matter of interest. If I run into any problems that really thwart my
>>>> usage of PGS for important purposes in future, then I'll yell for help!
>>>>
>>>> Cheers,
>>>>
>>>> Malcolm
>>>>
>>>
>
> --
> PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0
> AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>