[Framers] External cross-references in book documents - do not work in generated PDFs

[Robert Lauriston]

So call it a design flaw, it's still lame. It should be possible to
define relations between books in some persistent way.

Which is an example of a general problem with unstructured FM, that it
doesn't really have projects or templates.

On Mon, Jan 8, 2018 at 12:27 PM, Rick Quatro <rick at rickquatro.com> wrote:
> It's not a bug. It is the only way that FrameMaker can figure out what the
> parent book is for a particular external link. Remember that the link in the
> FrameMaker file is to a filename.fm, but the link in the PDF has to be to
> the bookname.pdf. When the link is to a file external to the book currently
> being processed, FrameMaker looks at the currently opened books to determine
> which PDF name to use for the link.
>
> Rick
>
> -----Original Message-----
> From: Framers
> [mailto:framers-bounces+rick=rickquatro.com at lists.frameusers.com] On Behalf
> Of Robert Lauriston
> Sent: Monday, January 08, 2018 3:22 PM
> To: An email list for people using Adobe FrameMaker software.
> <framers at lists.frameusers.com>
> Subject: Re: [Framers] External cross-references in book documents - do not
> work in generated PDFs
>
> I'd falsely assumed they had fixed that bug long ago. I first encountered it
> in FM6 if not 5.5.6.
>
> To avoid that issue, once computers had enough memory to deal handle it, I
> started putting the whole doc set in one PDF.
>
> On Mon, Jan 8, 2018 at 7:56 AM, Rick Quatro <rick at rickquatro.com> wrote:
>>
>> Let's say you are producing a PDF from Book A. Book A has links to Book B.
>> Book B has to be open in FrameMaker when you make the PDF from Book A
>> in order for the links to Book B to work.