... doesn't like some graphics cards. Check to make sure yours is
'approved' for Windows 10. I had to purchase new graphics cards when I
upgraded two high-end HP workstations from Windows 7 to Windows 10.
Fortunately, like-new compatible cards were available on eBay for, get
this, only $30 each. I'
Hi Rick...
The import/export client may be expecting attributes or internal
metadata set on that node that you're not including when you create the
by whatever means you're doing that (since that's a
"temporary" element). The fm-xref is created (from an xref) by the
import/export client on X
Hi Scott,
Thanks for the reply. I am using FM 2019 with the default application. I
changed the elements to before exporting and I get valid
XML. I am still not sure why the r/w rules drop instead of
converting them to automatically to .
Rick
-Original Message-
From: Framers On
Behalf
Hi Rick...
Are you using the default FM DITA structure apps? Does your app
definition include the reference to the default import/export client? On
export, that client should create a proper from the
(hence, the drop rule). If you remove this client from the app, you
should get elements in
Hi All,
I'm not able to get graphics to display in FrameMaker. This is a structured
environment I've been trying to create based on mil-std 40051 DTD. I think I do
not know how to set up the RW-Rules.
This is how a graphic is coded in the XML data:
...
DTD:
EDD created in FM from
Hi All,
I am structuring some FrameMaker content to DITA and trying to save an XML
file. Initially, my elements were getting dropped until I
discovered this R/W rule:
fm element "fm-xref" drop;
I replaced it with this:
element "xref" is fm cross-reference element "fm-xref";
Now I get the el
