Getting into Condition

[John Sgammato]

FrameMaker 8 unstructured
After years and years of working with FrameMaker, I am finally venturing
into (for me) uncharted territory: the wild world of conditional text.
I am not completely sure I understand what I am getting into, so I hope
for some advice from this august body.
I produce three types of deliverables from a single source, and am
adding a fourth deliverable: Printed, OnlineDoc, OnlineHelp, and now
Training. So far I have managed it all without conditions. The Training
materials will have some content that is not in the others, so
conditional text seems the way to go. 

My normal routine is to finish the writing phase and then to movine into
production of each deliverable one at a time, moving the source files
into a series of output folders for each deliverable. I go to Online Doc
folder and generate the color PDF. Then I go to Print Doc folder and
generate the hi-res B/W PDF. Then I go to Online Help, change the book
structure around a bit, and generate help with Mif2Go. Now I am adding a
fourth output, Training Materials, which will be PDF workbooks with
another different book structure.

Does it make sense to have four conditions (listed above), each of which
is shown throughout the writing phase of the project, and then
shown/hidden as I produce each of the deliverables? 

I hope to move into Structured FrameMaker soon - am I making that
project more complex by introducing conditions now?

A Lucky Strike! Extra question: the trainer wants x-refs to books in the
printed doc set. I know how to keep live x-refs within the training
materials, but I really can't imagine a way to keep good references to
external books.

John Sgammato
Principal Technical Writer
Imprivata, Inc.
[v] (781) 674-2441

www.imprivata.com

There are few pure-play appliance offerings in the identity and access
management (IAM) market space. Imprivata is one of the exceptions. Read
IDCs profile of 5 Imprivata customers - their needs, strategies and why
they implemented Imprivata OneSign.
___


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.

Re: Mif2Go Prev and Next navigation macros

[Jim Owens]

Thanks as always for the prompt response.

I've tried your suggestions, but without success. To spare others, we 
can continue off-list until this is resolved.


Jeremy H. Griffith wrote:
 On Wed, 05 Nov 2008 15:21:53 -0500, Jim Owens [EMAIL PROTECTED] wrote:
 
 I'd like to use these, but I'm having trouble.

 The latest beta revision history file for Mif2Go explains that the 
 $_prev and $_next macros have been updated to support browsing backwards 
 in true sequence, even across chapter breaks. (Formerly, according to 
 the documentation, the Prev button would leap from the first topic of 
 a chapter to the first topic of the previous chapter.) The history file 
 also says that the [FileSequence] section has been deprecated.

 I've downloaded and installed the latest dwhtm, m2gframe, and m2rbook 
 dll's.
 
 First, please recheck that you have the *very* latest betas.  We 
 update them quite often, and this is a feature we just completely 
 recoded with many improvements.  It does work for the User's Guide.
 
 I've set StartingSplit=Yes as suggested in the history file. For 
 personal preference, I've set UseNavButtons=Yes. Because the
 [FileSequence] section is deprecated, I haven't added it to my ini file.
 
 That's all good.
 
 I've referenced a macro for [Inserts} Top=, and in the macro I've 
 invoked $_prev$_next.
 
 Correct.
 
 The buttons appear in the output as expected, and within a given chapter 
 they work. However, they do not go from chapter to chapter. At the end 
 of a chapter, the Next button does nothing. At the beginning of a 
 chapter, the Prev button does nothing. In addition, for the first topic 
 in a chapter, the text in the Prev button reads Test File from Mif2Go.
 
 So the inter-chapter links are not working.  See if you have
 a .lst file in your working directory; if not, you may not have
 the latest m2rbook and m2gframe DLLs installed.  You should also
 have a file m2g_log.txt, which may contain entries descriptive
 of the problem, another new feature.  If so, we'd like to know
 what the log says.
 
 There is a special consideration regarding my Framemaker source: each 
 chapter begins with a single paragraph tagged either Chapter or 
 Appendix, followed by an h1 paragraph. I am using the h1 paragraph 
 as a split point.
 
 That should work.
 
 The Chapter and Appendix paragraphs are not used as split points. They 
 provide for some fancy formatting on the chapter title page and in the 
 TOC. Each one contains a ChapterNumber variable, some autonumber text 
 (set to white), and a Frame Above. I have assigned =Delete to them in 
 [HTMLStyles], but I suspect that they are causing an HTML file to be 
 created anyway.  Regardless of how I set StartingSplit (Yes or No), the 
 output includes an HTML file named for the chapter, and this file 
 contains three a name= elements, as well as the standard header and 
 footer that we use on all pages. 
 
 Yes.  The history file really isn't the full doc; that will be
 in the next User's Guide, in final production right now for 52.
 But this file is indeed created, and necessary.  When you use 
 [Automation], though, it is not retained in the Wrap directory,
 so it does not become part of your deliverable.
 
 This file is the one linked from the Test File from Mif2Go button. 
 
 That is *not* right.  However, we see the problem.  Even though
 you have marked the para for Delete, it is still there, and
 Mif2Go knows it.   You see, StartingSplit simply allows a
 split before the starting para, provided that para is indeed
 set to Split in [HTMLStyles].  It sounds like yours isn't.
 So as far as Mif2Go is concerned, the first file is still part
 of the deliverable.  Does the Prev button on the first file
 actually link back to the previous file?  If so, the links
 *are* working; likewise, the Next button at the end should
 link to the first (removed) part of the next file.
 
 In that case, what you need to do is fairly simple.  Just use 
 Frame conditional text to remove the first unwanted part of 
 each file for this output.  Mif2Go can handle hiding this 
 condition for you, another newly-added feature.  That's the 
 easiest way to get what you want.
 
 This isn't a bug; Delete has a more limited purpose, by
 design.  It only removes the paragraph content, and any
 Frames Above/Below, from the output.  But the para content
 is still usable in macros; in fact, we use such paras that
 way for special purposes in producing the User's Guide.
 Delete does *not* remove any anchored frames or tables
 that are anchored in the Deleted para, so it is also used
 to remove anchor paras that are not wanted in HTML output.
 Conditional text would, in that case, remove the figures
 and tables too, not what you want.
 
 If I comment out Chapter=Delete, I get the same file, but containing 
 the Frame Above referenced by the Chapter tag.
 
 Right, but in that it's not used anyway, conditioning it
 out would be better.
 
 I even tried deleting the Chapter tag 

RE: Page numbers

[Nina Rogers]

Thanks, everyone for your helpful advice on hyphenated page numbers for
appendices. I really needed some advice, and quick, and I was not
disappointed.

I ended up doing the following:

1. Going into the Master Pages for each appendix and changing the
$curpagenum footer to $chapnum-$curpagenum. (I know I could
probably have done this using an import, but I was halfway through
before I thought about it.)

2. Going into the book file, selecting Appendix A and having it use
alphabetic numbering. (Also saying it needed to be Chapter 1 so it
would translate it as A.)

3. Selecting Appendices B through E (from the book file) and having them
use alphabetic numbering, continuing from Appendix A/Chapter 1.

4. Saving the book file.

Thanks again, everyone. I really appreciate your help.

Nina
___


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.

tbl from xml file

[nodea.lo...@wartsila.com]

Hi!
I've been thinking of a way on how to show/open a table as is in
Structured FrameMaker (v.8), while the table I mentioned is embedded in
an xml file. Could anyone help me please? :)

-nlopez



-Original Message-
From: framers-boun...@lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of
framers-request at lists.frameusers.com
Sent: 4 November 2008 16:00
To: framers at lists.frameusers.com
Subject: Framers Digest, Vol 37, Issue 4

Send Framers mailing list submissions to
framers at lists.frameusers.com

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.frameusers.com/mailman/listinfo/framers
or, via email, send a message with subject or body 'help' to
framers-request at lists.frameusers.com

You can reach the person managing the list at
framers-owner at lists.frameusers.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Framers digest..."


Today's Topics:

   1. Subject: creating a table with row headings instead of column
  headings (Wim Hooghwinkel - idtp)
   2. Re: Subject: creating a table with row headings instead of
  columnheadings (Peter Gold)
   3. Re: Sorting: Ignoring periods 
  (Butler,  Darren J CTR USAF AFMC 584 CBSS/GBHAC)
   4. RE: Batch production of PDFs (Kelly McDaniel)
   5. RE: Subject: creating a table with row headings instead of
  columnheadings (Kelly McDaniel)
   6. Re: Sorting: Ignoring periods (Peter Gold)
   7. Re: Sorting: Ignoring periods  (Rick Quatro)
   8. PDF file-to-file cross references (Kelly McDaniel)
   9. Re: Sorting: Ignoring periods (Shmuel Wolfson)
  10. RE: Sorting: Ignoring periods (Fred Ridder)
  11. RE: ?cran (Pinkham, Jim)
  12. RE: Sorting: Ignoring periods
  (Butler,  Darren J CTR USAF AFMC 584 CBSS/GBHAC)
  13. RE: Search for random characters (Nancy Allison)
  14. Re: Search for random characters (Rick Quatro)
  15. RE: creating a table with row headings instead of column
  headings (Ben Hechter)
  16. RE: creating a table with row headings instead of column
  headings (Fred Ridder)
  17. RE: Sorting: Ignoring periods (Robert Evans)
  18. Recommendation for PDF to HTML converter? (Anne Urban)
  19. Re: Recommendation for PDF to HTML converter?
  (Bodvar Bjorgvinsson)
  20. Framemaker 8.0 (Robinson, Lee L CIV DLA J6UIB)


--

Message: 1
Date: Mon, 3 Nov 2008 09:27:23 +0100
From: "Wim Hooghwinkel - idtp" 
Subject: Subject: creating a table with row headings instead of column
headings
To: 
Cc: 'Ben Hechter' 
Message-ID: 
Content-Type: text/plain;   charset="us-ascii"

Hi Ben, 

To make a table with (repeating) row headers you can use a rotated
frame,
create  table and rotate the text. In fact you turn the tabel (90
degrees)
and use rotated the text (-90 degrees) so the display will be 'normal'.
You could make a special master page with a rotated text frame to hold
the
table and maintain table continuation.

HTH


Vriendelijke groet,

Wim Hooghwinkel

Adobe Certified Expert (ACE) in FrameMaker

iDTP

International DTP and Documentation Consultancy

tel. +31652036811
info at idtp.eu 
www.idtp.eu





--

Message: 2
Date: Mon, 3 Nov 2008 07:50:04 -0600
From: "Peter Gold" 
Subject: Re: Subject: creating a table with row headings instead of
column  headings
To: "Wim Hooghwinkel - idtp" 
Cc: framers at lists.frameusers.com, Ben Hechter 
Message-ID:
<905e72990811030550t6fdbd48ft981645d2ce7922c6 at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

Great solution, Wim!

Regards,

Peter Gold
KnowHow ProServices


On Mon, Nov 3, 2008 at 2:27 AM, Wim Hooghwinkel - idtp 
wrote:
> Hi Ben,
>
> To make a table with (repeating) row headers you can use a rotated
frame,
> create  table and rotate the text. In fact you turn the tabel (90
degrees)
> and use rotated the text (-90 degrees) so the display will be
'normal'.
> You could make a special master page with a rotated text frame to hold
the
> table and maintain table continuation.
>
> HTH
>
>
> Vriendelijke groet,
>
> Wim Hooghwinkel
>
> Adobe Certified Expert (ACE) in FrameMaker
>
> iDTP
>
> International DTP and Documentation Consultancy
>
> tel. +31652036811
> info at idtp.eu
> www.idtp.eu


--

Message: 3
Date: Mon, 3 Nov 2008 09:03:34 -0500
From: "Butler,  Darren J CTR USAF AFMC 584 CBSS/GBHAC"

Subject: Re: Sorting: Ignoring periods 
To: 
Message-ID:

<0A3BCB96867F3C4189717E5D03CDF03202354521 at VFGAMLAO12.Enterprise.afmc.ds.
af.mil>

Content-Type: text/plain;   charset="us-ascii"

Fred Ridder wrote:
>>The cause is easy.  Period follow spaces in the standard sort order.
Any entry that includes Heidi followed by a space will sort before an
entry that has Heidi followed by a period (or almost any other
punctuation character). 

Getting into Condition

[John Sgammato]

After years and years of working with FrameMaker, I am finally venturing
into (for me) uncharted territory: the wild world of conditional text.
I am not completely sure I understand what I am getting into, so I hope
for some advice from this august body.
I produce three types of deliverables from a single source, and am
adding a fourth deliverable: Printed, OnlineDoc, OnlineHelp, and now
Training. So far I have managed it all without conditions. The Training
materials will have some content that is not in the others, so
conditional text seems the way to go. 

My normal routine is to finish the writing phase and then to movine into
production of each deliverable one at a time, moving the source files
into a series of output folders for each deliverable. I go to Online Doc
folder and generate the color PDF. Then I go to Print Doc folder and
generate the hi-res B/W PDF. Then I go to Online Help, change the book
structure around a bit, and generate help with Mif2Go. Now I am adding a
fourth output, Training Materials, which will be PDF workbooks with
another different book structure.

Does it make sense to have four conditions (listed above), each of which
is shown throughout the writing phase of the project, and then
shown/hidden as I produce each of the deliverables? 

I hope to move into Structured FrameMaker soon - am I making that
project more complex by introducing conditions now?

A Lucky Strike! Extra question: the trainer wants x-refs to books in the
printed doc set. I know how to keep live x-refs within the training
materials, but I really can't imagine a way to keep good references to
external books.

John Sgammato
Principal Technical Writer
Imprivata, Inc.
[v] (781) 674-2441

www.imprivata.com

"There are few pure-play appliance offerings in the identity and access
management (IAM) market space. Imprivata is one of the exceptions." Read
IDCs profile of 5 Imprivata customers - their needs, strategies and why
they implemented Imprivata OneSign.

Mif2Go Prev and Next navigation macros

[Jim Owens]

Thanks as always for the prompt response.

I've tried your suggestions, but without success. To spare others, we 
can continue off-list until this is resolved.


Jeremy H. Griffith wrote:
> On Wed, 05 Nov 2008 15:21:53 -0500, Jim Owens  wrote:
> 
>> I'd like to use these, but I'm having trouble.
>>
>> The latest beta revision history file for Mif2Go explains that the 
>> $_prev and $_next macros have been updated to support browsing backwards 
>> in true sequence, even across chapter breaks. (Formerly, according to 
>> the documentation, the "Prev" button would leap from the first topic of 
>> a chapter to the first topic of the previous chapter.) The history file 
>> also says that the [FileSequence] section has been deprecated.
>>
>> I've downloaded and installed the latest dwhtm, m2gframe, and m2rbook 
>> dll's.
> 
> First, please recheck that you have the *very* latest betas.  We 
> update them quite often, and this is a feature we just completely 
> recoded with many improvements.  It does work for the User's Guide.
> 
>> I've set StartingSplit=Yes as suggested in the history file. For 
>> personal preference, I've set UseNavButtons=Yes. Because the
>> [FileSequence] section is deprecated, I haven't added it to my ini file.
> 
> That's all good.
> 
>> I've referenced a macro for [Inserts} Top=, and in the macro I've 
>> invoked <$_prev><$_next>.
> 
> Correct.
> 
>> The buttons appear in the output as expected, and within a given chapter 
>> they work. However, they do not go from chapter to chapter. At the end 
>> of a chapter, the Next button does nothing. At the beginning of a 
>> chapter, the Prev button does nothing. In addition, for the first topic 
>> in a chapter, the text in the Prev button reads "Test File from Mif2Go".
> 
> So the inter-chapter links are not working.  See if you have
> a .lst file in your working directory; if not, you may not have
> the latest m2rbook and m2gframe DLLs installed.  You should also
> have a file m2g_log.txt, which may contain entries descriptive
> of the problem, another new feature.  If so, we'd like to know
> what the log says.
> 
>> There is a special consideration regarding my Framemaker source: each 
>> chapter begins with a single paragraph tagged either "Chapter" or 
>> "Appendix", followed by an "h1" paragraph. I am using the h1 paragraph 
>> as a split point.
> 
> That should work.
> 
>> The Chapter and Appendix paragraphs are not used as split points. They 
>> provide for some fancy formatting on the chapter title page and in the 
>> TOC. Each one contains a ChapterNumber variable, some autonumber text 
>> (set to white), and a Frame Above. I have assigned "=Delete" to them in 
>> [HTMLStyles], but I suspect that they are causing an HTML file to be 
>> created anyway.  Regardless of how I set StartingSplit (Yes or No), the 
>> output includes an HTML file named for the chapter, and this file 
>> contains three  elements, as well as the standard header and 
>> footer that we use on all pages. 
> 
> Yes.  The history file really isn't the full doc; that will be
> in the next User's Guide, in final production right now for 52.
> But this file is indeed created, and necessary.  When you use 
> [Automation], though, it is not retained in the Wrap directory,
> so it does not become part of your deliverable.
> 
>> This file is the one linked from the "Test File from Mif2Go" button. 
> 
> That is *not* right.  However, we see the problem.  Even though
> you have marked the para for Delete, it is still there, and
> Mif2Go knows it.   You see, StartingSplit simply allows a
> split before the starting para, provided that para is indeed
> set to Split in [HTMLStyles].  It sounds like yours isn't.
> So as far as Mif2Go is concerned, the first file is still part
> of the deliverable.  Does the Prev button on the first file
> actually link back to the previous file?  If so, the links
> *are* working; likewise, the Next button at the end should
> link to the first (removed) part of the next file.
> 
> In that case, what you need to do is fairly simple.  Just use 
> Frame conditional text to remove the first unwanted part of 
> each file for this output.  Mif2Go can handle hiding this 
> condition for you, another newly-added feature.  That's the 
> easiest way to get what you want.
> 
> This isn't a bug; Delete has a more limited purpose, by
> design.  It only removes the paragraph content, and any
> Frames Above/Below, from the output.  But the para content
> is still usable in macros; in fact, we use such paras that
> way for special purposes in producing the User's Guide.
> Delete does *not* remove any anchored frames or tables
> that are anchored in the Deleted para, so it is also used
> to remove anchor paras that are not wanted in HTML output.
> Conditional text would, in that case, remove the figures
> and tables too, not what you want.
> 
>> If I comment out Chapter=Delete, I get the same file, but containing 
>> the Frame Above referenced by the Chapter 

Page numbers

[Nina Rogers]

Thanks, everyone for your helpful advice on hyphenated page numbers for
appendices. I really needed some advice, and quick, and I was not
disappointed.

I ended up doing the following:

1. Going into the Master Pages for each appendix and changing the
<$curpagenum> footer to <$chapnum>-<$curpagenum>. (I know I could
probably have done this using an import, but I was halfway through
before I thought about it.)

2. Going into the book file, selecting Appendix A and having it use
alphabetic numbering. (Also saying it needed to be "Chapter 1" so it
would translate it as "A.")

3. Selecting Appendices B through E (from the book file) and having them
use alphabetic numbering, continuing from Appendix A/Chapter 1.

4. Saving the book file.

Thanks again, everyone. I really appreciate your help.

Nina

frame > pdf - opening links in new window

[Jo Watkiss]

I'm converting a Frame file to PDF.  The file includes numerous links to
other files, which I need to open in new windows.  In the past, I've
used a document-level javascript (openinplace) in the pdf file to make
all links open in new windows.  However this no longer works in Acrobat
8, so I want to set this action in the Framemaker file.  (The
alternative is to use an application-level javascript in the pdf - but I
have no idea how to do that.)

The hyperlink I'm currently using is "openpage "
Is there a way to force this to open in a new window?

Thanks,
Jo Watkiss
FrameMaker 6, Acrobat Pro 8, Win XP
_ 
Disclaimerhttp://www.watkiss.com/terms.htm
This email is confidential and intended solely for the use of the individual to 
whom it is addressed. 
Any views or opinions presented are solely that of the author and do not 
necessarily represent those of Watkiss Automation Ltd.
If you are not the intended recipient, be advised that you have received this 
email in error and that any use, dissemination, forwarding, printing, or 
copying of this email is strictly prohibited. 
If you received this email in error please notify Watkiss Automation Ltd on 
telephone +44 1767 685700.