Index » PageStream Support » General » Summary of document data / information
Sign in to add a comment. Pages: 1
2012-07-03 12:08:05 CT #1
Brent W. Santin
From: Canada
Registered: 2007-11-02
Posts: 105

Here's another question:

Is there a way to generate a summary of data about a PageStream document?

Primarily, I'm interested finding out instantly a list of all the fonts used in a document - when I archive a document to CD-R I need to include the fonts on the disc so there are no nasty surprises when I try to open the document years later and it cannot find the original fonts.

But it would also be interesting to see a list of number of objects in a document, bitmap names, etc. etc.

Does anyone know if such a thing exists?

- Brent


2012-07-03 10:25:36 CT #2
David L. Stevens
From: United States
Registered: 2006-02-23
Posts: 567

On 7/3/2012 7:08 AM, Brent wrote:
>
> Here's another question:
>
> Is there a way to generate a summary of data about a PageStream document?
>

Menu Bar>Layout>Reports
>
>
> Primarily, I'm interested finding out instantly a list of all the
> fonts used in a document - when I archive a document to CD-R I need to
> include the fonts on the disc so there are no nasty surprises when I
> try to open the document years later and it cannot find the original
> fonts.
>
> But it would also be interesting to see a list of number of objects in
> a document, bitmap names, etc. etc.
>
> Does anyone know if such a thing exists?
>
> - Brent
>
>


--

DAVID L. STEVENS -- TEAM AMIGA --
Windows XP user (:^(> on Acer Aspire 9810 2.16 GHz Notebook
2 GB RAM; 3 150-GB Hard Drives; CanoScan LIDE 20
Canon i860 & Brother HL-5050 PageStream v5.0.5.7 Pro
<http://home.comcast.net/~dave_stevens/home.html
<http://home.comcast.net/%7Edave_stevens/home.html>>
I do not necessarily agree with my taglines

***
Man will occasionally stumble over the truth, but most times he will
pick himself up and carry on... Winston Churchill


2012-07-07 22:02:48 CT #3
Martin B. Brilliant
From: United States
Registered: 2008-03-15
Posts: 89

I just opened some one-page Pagestream documents that I created a few weeks ago, containing some lines of text in Aldine721 BT between some lines in Futura. When I opened them the text that was in Aldine721 BT wasn't there. At least it didn't appear to be there. Pagestream identified the font correctly but told me there was no text in that font. When I selected all the text in the document, copied it, and pasted it into Bean, the text appeared as I had originally entered it. Back in Pagestream, I selected everything from the end of the preceding line of Futura to the start of the following line of Futura. All it showed was zero-length lines. I changed the font, and when I changed it to some fonts I saw the text I had originally put there, in the newly selected font. There were also other fonts that just showed empty lines.

--
Martin B. Brilliant - mbrilliant@alum.mit.edu
Mac OS X version 10.6.8
PageStream (non-pro) 5.0.5.8


2012-07-09 07:53:43 CT #4
T.J. Zweers
From: Netherlands
Registered: 2006-02-07
Posts: 331

Well Martin,

all I can think off at the moment, is this:
You've added (Add or Update) the font Futura to PGS (with System
Preferences/Fonts...), and didn't Save it or simply clicked on Use.
If so, the font (Futura) doesn't exist when you reopen (!) PGS, and PGS
can't show it: empty lines.

Theo

Op 8-7-2012 4:02, Martin B. Brilliant schreef:
> I just opened some one-page Pagestream documents that I created a few weeks ago, containing some lines of text in Aldine721 BT between some lines in Futura. When I opened them the text that was in Aldine721 BT wasn't there. At least it didn't appear to be there. Pagestream identified the font correctly but told me there was no text in that font. When I selected all the text in the document, copied it, and pasted it into Bean, the text appeared as I had originally entered it. Back in Pagestream, I selected everything from the end of the preceding line of Futura to the start of the following line of Futura. All it showed was zero-length lines. I changed the font, and when I changed it to some fonts I saw the text I had originally put there, in the newly selected font. There were also other fonts that just showed empty lines.
>


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


2012-07-09 06:45:35 CT #5
Martin B. Brilliant
From: United States
Registered: 2008-03-15
Posts: 89

Thank you, Theo, for the suggestion. The font that did not show was Aldine721 BT, and Futura was OK, but that's beside the point. This morning the problem disappeared, and unless it recurs it may remain a mystery.

Anyway, I don't think your suggestion had anything to do with the problem. I went through each of the folders in System Preferences / Fonts, hitting Update for each one, then Saved. Also restarted PgS. I also unchecked Use System Fonts, Saved, then rechecked, Saved. Restarted Font Book. Restarted the Mac. PgS still did not recognize text in Aldine721 BT (and in several other fonts).

Then while playing with Fontforge I found that the spacebar no longer activated Quick Look. In fact Quick Look didn't work even when selected from the right click menu. I found a forum where someone blamed Sugarsync for that problem and fixed it by closing Sugarsync and relaunching Finder. I use Sugarsync and followed that suggestion, but then I found that all I had to do to restore Quick Look was relaunch Finder without closing Sugarsync.

Now this morning I opened the same document in PgS and everything was there, the text in Futura that was always OK and also the text in Aldine721 BT that was not there yesterday. Quick Look also works. Sugarsync is still running. I updated the text in Aldine721 BT and saved the document, no problem.

On Jul 9, 2012, at 1:53 AM, Theo Zweers wrote:

> Well Martin,
>
> all I can think off at the moment, is this:
> You've added (Add or Update) the font Futura to PGS (with System
> Preferences/Fonts...), and didn't Save it or simply clicked on Use.
> If so, the font (Futura) doesn't exist when you reopen (!) PGS, and PGS
> can't show it: empty lines.
>
> Theo
>
> Op 8-7-2012 4:02, Martin B. Brilliant schreef:
>> I just opened some one-page Pagestream documents that I created a few weeks ago, containing some lines of text in Aldine721 BT between some lines in Futura. When I opened them the text that was in Aldine721 BT wasn't there. At least it didn't appear to be there. Pagestream identified the font correctly but told me there was no text in that font. When I selected all the text in the document, copied it, and pasted it into Bean, the text appeared as I had originally entered it. Back in Pagestream, I selected everything from the end of the preceding line of Futura to the start of the following line of Futura. All it showed was zero-length lines. I changed the font, and when I changed it to some fonts I saw the text I had originally put there, in the newly selected font. There were also other fonts that just showed empty lines.
>>
>
>
> --
> PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.2 and PySide 1.1.0
> AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

--
Martin B. Brilliant - mbrilliant@alum.mit.edu
Mac OS X version 10.6.8
PageStream (non-pro) 5.0.5.8


2012-07-09 18:31:32 CT #6
T.J. Zweers
From: Netherlands
Registered: 2006-02-07
Posts: 331

Martin,

I was even a bit more beside the point, I realize now (not the other
font, just overlooked it Smile ).
But IF PGS doesn't recognize a font, it simply asks you with which font
it should replace (font substitution).
So, PGS did en does know the font (Aldine), but couldn't find (because
some program on your OS, or OS itself, blocked it) a way to show it:
empty lines.

I hope that this was the bug (Sugarsync). You, with the help of other
forums, found the (possible) bug.

(I had a bug on Windows 7, and PGS of course, where PGS 5.0.5.8 (not
5.0.5.7!) refused to open a document (once in a while) for about two
years. I suggested some possibilities where it could go wrong on the
forum and the Bug Tracker (on which I blamed PGS 5.0.5.Cool. No one had
this bug...
After a new installation (32 bit to 64 bit) Windows 7, the bug was gone!
(I myself did some re-installations of the 32 bit Windows 7, but that
bug remained).)

Theo

Op 9-7-2012 12:45, Martin B. Brilliant schreef:
> Thank you, Theo, for the suggestion. The font that did not show was Aldine721 BT, and Futura was OK, but that's beside the point. This morning the problem disappeared, and unless it recurs it may remain a mystery.
>
> Anyway, I don't think your suggestion had anything to do with the problem. I went through each of the folders in System Preferences / Fonts, hitting Update for each one, then Saved. Also restarted PgS. I also unchecked Use System Fonts, Saved, then rechecked, Saved. Restarted Font Book. Restarted the Mac. PgS still did not recognize text in Aldine721 BT (and in several other fonts).
>
> Then while playing with Fontforge I found that the spacebar no longer activated Quick Look. In fact Quick Look didn't work even when selected from the right click menu. I found a forum where someone blamed Sugarsync for that problem and fixed it by closing Sugarsync and relaunching Finder. I use Sugarsync and followed that suggestion, but then I found that all I had to do to restore Quick Look was relaunch Finder without closing Sugarsync.
>
> Now this morning I opened the same document in PgS and everything was there, the text in Futura that was always OK and also the text in Aldine721 BT that was not there yesterday. Quick Look also works. Sugarsync is still running. I updated the text in Aldine721 BT and saved the document, no problem.
>
> On Jul 9, 2012, at 1:53 AM, Theo Zweers wrote:
>
>> Well Martin,
>>
>> all I can think off at the moment, is this:
>> You've added (Add or Update) the font Futura to PGS (with System
>> Preferences/Fonts...), and didn't Save it or simply clicked on Use.
>> If so, the font (Futura) doesn't exist when you reopen (!) PGS, and PGS
>> can't show it: empty lines.
>>
>> Theo
>>
>> Op 8-7-2012 4:02, Martin B. Brilliant schreef:
>>> I just opened some one-page Pagestream documents that I created a few weeks ago, containing some lines of text in Aldine721 BT between some lines in Futura. When I opened them the text that was in Aldine721 BT wasn't there. At least it didn't appear to be there. Pagestream identified the font correctly but told me there was no text in that font. When I selected all the text in the document, copied it, and pasted it into Bean, the text appeared as I had originally entered it. Back in Pagestream, I selected everything from the end of the preceding line of Futura to the start of the following line of Futura. All it showed was zero-length lines. I changed the font, and when I changed it to some fonts I saw the text I had originally put there, in the newly selected font. There were also other fonts that just showed empty lines.
>>>
>>
>> --
>> PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.2 and PySide 1.1.0
>> AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM
>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>


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


Sign in to add a comment. Pages: 1
Index » PageStream Support » General » Summary of document data / information

This topic is closed due to inactivity.