Re: Problem with Bookmarks in PDFs coming from structured framemaker documents (bis)

2007-01-31 Thread Shlomo Perets

Lodewijk,

You wrote:


... In the result so far we notice that not only

head(Level1)
head(Level2)
head(Level3)

appears as bookmark but also

head(Level1)TOC
head(Level2)TOC
head(Level3)TOC

It is as if head(Level1),  head(Level3), head(Level3)  have a wildcard so 
that also elements with a suffix added to these respective names are used 
for bookmarks.


Is this a known problem?



I'm not sure whether this is a bug or an intended feature, but bookmark 
settings that you have in individual book components are processed *in 
addition* to the book-level bookmark settings.


It's likely that your TOC file has the head(LevelX)TOC paragraph tags 
indicated as bookmarks (inherited from a template, or populated by FrameMaker).


Open the TOC file and select Format  Document  PDF Setup; move the 
paragraph tags to the Don't Include box (you can hold down the Shift key 
and click the arrow to move all items at once).


Upon recreating the PS file from the book, the extra TOC bookmarks should 
not be present anymore.



Shlomo Perets

MicroType, http://www.microtype.com * ToolbarPlus Express for FrameMaker
FrameMaker/Acrobat training  consulting * FrameMaker-to-Acrobat 
TimeSavers/Assistants



___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]

or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Problem with Bookmarks in PDFs coming from structured framemaker documents (bis)

2007-01-31 Thread Nollet, Lodewijk (Gent)
Hello all, 
 

Structured Framemaker-to-PDF problem, noticed using 7.0 and 7.2. 
 

We use head elements as headers of generic sections. 
 
The layout of the head depends on the context and is defined with a
level rule in the EDD. 
All levels also have a context label Level1, Level2 etc. defined in the
EDD.
 
We use the head(Level1), head(Level2) and head(Level3) elements to
construct our table of contents. 
 
In the generated, unstructured table of contents we have forseen styles 
head(Level1)TOC, 
head(Level2)TOC and 
head(Level3)TOC. 
 
(We've made a number of modifications to the default unformatted styles
in the reference pages, but maintained the style names).
 
 
When we want to create a PDF-file and set up the bookmarks, we go to the
FM Print Window  PDF setup  Bookmarks, 
then we select to become bookmarks 
head(Level1)
head(Level2)
head(Level3)
 
After that we create a PS-file and distill the PDF. 
 
In the result so far we notice that not only 
 
head(Level1)
head(Level2)
head(Level3)
 
appears as bookmark but also 
 
head(Level1)TOC
head(Level2)TOC
head(Level3)TOC
 
It is as if head(Level1),  head(Level3), head(Level3)  have a wildcard
so that also elements with a suffix added to these respective names are
used for bookmarks. 
 
Is this a known problem? 
 
Any help is appreciated. 
 
Kind regards, 
 
Lodewijk 
 
 
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Problem with Bookmarks in PDFs coming from structured framemaker documents (bis)

2007-01-31 Thread Shlomo Perets
Lodewijk,

You wrote:

>... In the result so far we notice that not only
>
>head(Level1)
>head(Level2)
>head(Level3)
>
>appears as bookmark but also
>
>head(Level1)TOC
>head(Level2)TOC
>head(Level3)TOC
>
>It is as if head(Level1),  head(Level3), head(Level3)  have a wildcard so 
>that also elements with a suffix added to these respective names are used 
>for bookmarks.
>
>Is this a known problem?


I'm not sure whether this is a bug or an intended feature, but bookmark 
settings that you have in individual book components are processed *in 
addition* to the book-level bookmark settings.

It's likely that your TOC file has the head(LevelX)TOC paragraph tags 
indicated as bookmarks (inherited from a template, or populated by FrameMaker).

Open the TOC file and select Format > Document > PDF Setup; move the 
paragraph tags to the "Don't Include" box (you can hold down the Shift key 
and click the arrow to move all items at once).

Upon recreating the PS file from the book, the "extra" TOC bookmarks should 
not be present anymore.


Shlomo Perets

MicroType, http://www.microtype.com * ToolbarPlus Express for FrameMaker
FrameMaker/Acrobat training & consulting * FrameMaker-to-Acrobat 
TimeSavers/Assistants





Problem with Bookmarks in PDFs coming from structured framemaker documents (bis)

2007-01-31 Thread Nollet, Lodewijk (Gent)
Hello all, 


Structured Framemaker-to-PDF problem, noticed using 7.0 and 7.2. 


We use "head" elements as headers of generic "sections". 

The layout of the "head" depends on the context and is defined with a
"level rule" in the EDD. 
All levels also have a context label Level1, Level2 etc. defined in the
EDD.

We use the head(Level1), head(Level2) and head(Level3) elements to
construct our table of contents. 

In the generated, unstructured table of contents we have forseen styles 
head(Level1)TOC, 
head(Level2)TOC and 
head(Level3)TOC. 

(We've made a number of modifications to the default unformatted styles
in the reference pages, but maintained the style names).


When we want to create a PDF-file and set up the bookmarks, we go to the
FM Print Window > PDF setup > Bookmarks, 
then we select to become bookmarks 
head(Level1)
head(Level2)
head(Level3)

After that we create a PS-file and distill the PDF. 

In the result so far we notice that not only 

head(Level1)
head(Level2)
head(Level3)

appears as bookmark but also 

head(Level1)TOC
head(Level2)TOC
head(Level3)TOC

It is as if head(Level1),  head(Level3), head(Level3)  have a wildcard
so that also elements with a suffix added to these respective names are
used for bookmarks. 

Is this a known problem? 

Any help is appreciated. 

Kind regards, 

Lodewijk