[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Neale Hays <nhays@xxxxxxx>, Framers@xxxxxxxxxxxxxx, Free Framers <framers@xxxxxxxxx>
Subject: URIs for cross-references in FM+SGML V5.5.6? (was Frame+SGML export and external XRefs)
From: Dan Emory <danemory@xxxxxxxxxxxx>
Date: Tue, 2 Feb 1999 14:52:10 -0700 (MST)
Sender: owner-framers@xxxxxxxxx
The behavior you describe is an FM+SGML "feature". I know of no way to change it. In XML, Universal Resource Identifiers (URIs) can, I believe, be used for such external cross-references, but I doubt seriously if FM+SGML 5.5.6 employs this approach in its XML implementation. The fact (as remarked by Kay Ethier in an earlier post today) that Adobe apparently has failed to document anything whatsoever about the new XML functionality in V5.5.6 doesn't help matters. If anyone knows for sure whether or not FM+SGML 5.5.6 can convert ID and IDREF attribute values to URIs I's like to know about it. ************************************************************************* At 08:09 PM 2/2/99 +0000, Neale Hays wrote: >Hi all, > >When exporting to SGML, Frame's default behavior for XRef elements >that it considers external (outside the scope of the SGML document >it is generating) is to export as text, thereby dropping all >SGML markup associated with the element. > >Is there any easy way of stopping it from doing this? I need >to be able to support cross-references between books in a suite, >and I'd prefer not to have to worry about authors exporting a >single chapter in a book and losing references to other chapters >in the book. ____________________ | Nullius in Verba | ******************** Dan Emory, Dan Emory & Associates FrameMaker/FrameMaker+SGML Document Design & Database Publishing Voice/Fax: 949-722-8971 E-Mail: danemory@primenet.com 10044 Adams Ave. #208, Huntington Beach, CA 92646 ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **