Maybe .fm files have to be in the directory containing the .book file
or a subdirectory of that directory?

On Fri, Aug 23, 2013 at 4:39 AM,  <dave.st...@gdc4s.com> wrote:
> 2013-08-23-05T11:40Z
>
> Robert -
>
> Thanks for the info.  I, too, haven't done this since years ago.  So
> long ago, in fact that I've tracked down my materials from Shlomo
> Perets' training back in 2002.
>
> Yes, all the files are part of dir_Abc_Def.book.  The odd thing, for
> myself, is that the "child" file, is outside the folder that contains
> the rest of the book.
>
> Nothing I've tried so far works, so I'm hoping that someone on the list
> can help me find the "secret sauce" that I'm missing from the "recipe."
>
> Regards,
> Dave Stamm
> Information Engineer
> General Dynamics C4 Systems, Inc.
>
> -----Original Message-----
> From: robert.lauris...@gmail.com [mailto:robert.lauris...@gmail.com] On
> Behalf Of Robert Lauriston
> Sent: 2013-08-22-Thursday 16:24
> To: Stamm, David-P45904
> Cc: framers@lists.frameusers.com
> Subject: Re: Hypertext links not working
>
> I haven't done that sort of thing in some years, but it used to be that
> if you defined cross-references between .fm files in different
> directories, all the files had to be open when you saved a book as PDF.
>
> Also, the PDFs have to have the same relative directory relationship.
> If you have ./foo/foo.book and ./bar/bar.book, links in foo.pdf will be
> to ../bar/bar.pdf.
>
> If BEGIN_HERE.pdf is generated from an .fm file instead of a .book, that
> might be a problem.
>
> On Thu, Aug 22, 2013 at 1:00 PM,  <dave.st...@gdc4s.com> wrote:
>> 2013-08-22-04T20:00Z
>>
>> Windows 7 Enterprise Service Pack 1
>> 4 GB RAM
>> 64-bit operating system
>> FrameMaker 11.0.2.384
>> FrameMaker installed on workstation
>> Folder and all files on a server on the local area network in
>> accordance with corporate policy
>>
>> I am unable to consistently encode hypertext links among five files in
> one unstructured book.
>>
>> Here's how the files are arranged:
>>
>>         NOTE:  The .book file and all the target files are "children"
> of folder \Abc_Def.  File BEGIN_HERE.fm is "sibling" of folder \Abc_Def
> and is to contain links to all four targets.
>>
>> Folder \Abc_Def
>>         File dir_Abc_Def.book
>>         File targetA.fm
>>         File targetB.fm
>>         File targetC.fm
>>         File targetD.fm
>> File BEGIN_HERE.fm
>>
>> I moved File BEGIN_HERE.fm out of folder \Abc_Def because a recipient
> of the informational product (portable document format files) wants it
> that way.  I am using a character tag to constrain both the newlinks and
> gotolinks to small amounts of text.  Before I moved file BEGIN_HERE.fm
> out of folder \Abc_Def, crossreferences among all files worked
> flawlessly.
>>
>> My latest attempt has been to specify named destinations (for example,
> newlink dir_About.fm) and jumps to named destinations (for example,
> gotolink dir_About.fm).
>>
>> In the source .fm files, these jumps work only a small part of the
> time.  In the deliverable .pdf files, they don't work at all.
>>
>> Dave Stamm
>> Information Engineer
>>
>> _______________________________________________
>>
>>
>> You are currently subscribed to framers as rob...@lauriston.com.
>>
>> Send list messages to framers@lists.frameusers.com.
>>
>> To unsubscribe send a blank email to
>> framers-unsubscr...@lists.frameusers.com
>> or visit
>> http://lists.frameusers.com/mailman/options/framers/robert%40lauriston
>> .com
>>
>> Send administrative questions to listad...@frameusers.com. Visit
>> http://www.frameusers.com/ for more resources and info.
_______________________________________________


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

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

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

Reply via email to