I'm not sure why this fixed my EDD/RW rules conflict but it did.
I changed my RW rules from:
is fm graphic element "Graphic";
to:
is fm graphic element "GRAPHIC";
This got it past the conflict error. I did a search on all the files concerned
and it is not in all caps anywhere else that I can find.
I still don't have a valid XML file due to my table definitions apparently
being a "hot mess" but it's progress!
Thanks for everyone's help. This list is a plethora of knowledge. I sure know
where to go for answers if I can't figure out my table issues.
From: Lisa Freeman
Sent: 03 06, 2013 9:59 AM
To: framers at lists.frameusers.com
Subject: RE: RW Rules vs EDD Conflict
Many thanks to Ian and Scott for your suggestions, but unfortunately this is
still not working for me. I've tried both methods below as well as every
combination of the two I could think of.
After pouring through all the reference material I have, I am still stumped on
this. Does anyone else have any ideas where my disconnect is?
>From Scott Prentice:
Try changing your rules to this (don't need the "Graphic" in the first rule) ..
element "Graphic"
{
is fm graphic element;
fm property entity value is "illus";
}
From: Ian Proudfoot [mailto:[email protected]]
Sent: 03 01, 2013 7:26 AM
To: Lisa Freeman; framers at lists.frameusers.com<mailto:framers at
lists.frameusers.com>
Subject: RE: RW Rules vs EDD Conflict
Hi Lisa,
I think you have misunderstood the rules a little. So try this:
element "Graphic"
{
is fm graphic element "Graphic";
attribute "illus" is fm property entity;
}
This will work if the "illus" attribute is defined as type ENTITY in the DTD.
In your EDD remove the attribute definition for "illus". This will not be
needed in the FrameMaker environment because the read/write rule is converting
the XML attribute into a FrameMaker property. The type mismatch was because the
attribute was defined as an Integer in the EDD.
If the DTD does not define "illus" as ENTITY, then use this rule instead:
attribute "illus" is fm property file;
That's all from memory, so I hope it all works for you.
Ian
Ian PROUDFOOT
Technical Director
www.antea.fr<http://www.antea.fr>
3 rue Etienne Dolet | 93400 Saint-Ouen | France
Tel : + 44 (0)7793 324 581
From: framers-bounces at lists.frameusers.com<mailto:framers-bounces at
lists.frameusers.com> [mailto:[email protected]] On Behalf
Of Lisa Freeman
Sent: 28 February 2013 18:36
To: framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>
Subject: RW Rules vs EDD Conflict
Hello All,
I am working a project using FrameMaker 8.0p277.
I have a conflict between my Read-Write Rules and my template (my EDD, I
presume) that has me stumped. When I do a check of my rules I get the following
error:
"Type mismatch for the FrameMaker element (Graphic). The type defined by the
read/write rules is different from that defined by the template."
The link takes me to the "is fm graphic element" statement below.
My rules are:
element "Graphic"
{
is fm graphic element "Graphic";
fm property entity value is "illus";
}
And I have the following defined in my EDD:
Element (Graphic): Graphic
Attribute list
Name: illus Integer Required
Initial graphic element format
In all contexts.
Insert imported graphic file.
Am I missing something that is totally obvious to anyone?
Thanks in advance for any suggestions!
Sincerely,
Lisa Freeman
Publication Support Analyst
O'NEIL & ASSOCIATES, INC.<http://www.oneil.com>
**********************************************************************
Confidentiality Notice
The information contained in this e-mail is confidential and intended for use
only by the person(s) or organization listed in the address. If you have
received this communication in error, please contact the sender at O'Neil &
Associates, Inc., immediately. Any copying, dissemination, or distribution of
this communication, other than by the intended recipient, is strictly
prohibited.
**********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.frameusers.com/pipermail/framers/attachments/20130306/0ab46136/attachment.html>
