Jeremy, Thanks for this info. However, I have one question: Since I'm not generating the target document (HTML or CHM), how will I know the anchor to specify in the Hypertext command?
Elise -----Original Message----- From: Jeremy H. Griffith [mailto:jer...@omsys.com] Sent: 12 d?cembre 2006 15:03 To: Nantel, Elise Cc: framers at FrameUsers.com Subject: Re: External xrefs from FM to... CHM or HTML On Mon, 11 Dec 2006 12:07:55 -0500, "Nantel, Elise" <Elise.Nantel at verint.com> wrote: >When in Robohelp, I merged the Reference Guide CHM file >into the Programmer Guide, and was able to do external >cross-references from the Programmer Guide to the >Reference Guide (typically on class or interface names). >However, now in FrameMaker, how can I do that? From what >I see, I can only do xrefs to another FM document. That's correct. Frame xrefs are only for use with other Frame docs. However, you can use Frame hypertext links to anything. To do that, you would place a Frame marker of type Hypertext with content like: message URL ./path/filename.htm#anchor for a file in a subdirectory below the Frame file. You need to specify a path that will be valid from the HTML produced for the Frame file. To mark the hotspot for the link, apply a char format (which can be all "as is") to the hotspot text; the marker must also be within the span of the char format. See the Frame docs for more on the many kinds of hypertext markers available. HTH! -- Jeremy H. Griffith, at Omni Systems Inc. <jeremy at omsys.com> http://www.omsys.com/ __________________________________________________________________________________________ This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail. (1)
