2. Updated spec: in progress. The jdoconfig.xml has been added to
Appendix D. Should we also put jdo.xml, orm.xml, and jdoquery.xml to
Appendix D? No, probably better to add the dtd version of jdoconfig
to Appendix D.
AI Michelle look at how to automatically include the xsd and dtd
files into the spec.
From FrameMaker help:
Importing by reference
------------------------------------------------------------------------
You can import by reference by using File > Import > File, OLE
(Windows), Publish and Subscribe (Mac OS), or a graphic inset
editor (UNIX).
When you double-click a graphic imported by reference you:
* (Windows) Open the application
* (Mac OS) Open the Object Properties dialog
Importing by reference keeps the imported text or graphics linked
to the source file. FrameMaker stores the pathname to the source
file in the document. Each time you open the document, FrameMaker
locates the file on the disk and redisplays it. If the source file
was revised, FrameMaker updates the document with the latest
version. Importing by reference can reduce total file size because
it lets you use the same material in several places without
storing the contents of imported images or text in the FrameMaker
document. Text imported by reference is called a text inset.
For information on how the pathname is stored when importing by
reference, see Using pathnames when importing by reference.
I did a quick test of importing jdo_2_0.xsd. I applied the code
paragraph style and it looked good with no changes. When you import by
reference, you cannot edit the text from within Frame. When you select
the imported text (clicking anywhere within the import highlights the
entire block), Edit/Text Inset Properties brings up a dialog that
displays information and offers various actions.
-- Michelle
