Hi Scott
Thanks for your reply. After more research and reading, plus some trial
and error, I came up with the same rule that you have below, and it
works. FM knows what to do if you then give the @outputclass attribute a
value of 270. I guess you can also use 90 or 180.
I also tried it using a custom attribute called @rotated, with values of
"yes" or "no". That works too, and it's not difficult to add the
attribute to the DTD. At least, it's not difficult to do it the wrong
way, by modifying the DITA DTD directly rather than using a
customization layer. But since @outputclass works and we don't need it
for anything else, I think I'll go with that.
Thanks again,
Roger
On 04/02/2013 5:22 PM, Scott Prentice wrote:
Hi Roger...
Interesting. I've not played with this to see how (or if) this can be
done through the rules file. Did you try this (without the value..
line) ..
element "entry" {
is fm table cell element;
attribute "outputclass" {
is fm property rotate;
}
}
I'd think that if @outputclass was set to 0, 90, 180, or 270 .. this
might rotate the cell. I know this isn't really a workable solution,
but would be interesting to see if it works. I think the idea is that
you'd have an attribute called "rotation" (or whatever) that you'd set
to the desired value .. also not really feasible with DITA since you
can't really add attributes.
DITA-FMx supports rotated cells by adding a data element to the entry
and stores the rotation value in there, then sets the cell rotation
when you open the file (via FDK coding).
Do let me know if you get this working via the rules file.
Cheers,
...scott
Scott Prentice
Leximation, Inc.
www.leximation.com
+1.415.485.1892
On 2/4/13 8:20 AM, Roger Shuttleworth wrote:
Hello All
FM 11.0.1 structured, using DITA 1.2.
I'm hoping some read-write rules guru will be able point me in the
right direction...
We have some tables in which occasional cell contents are rotated. To
do this manually, we select the text and go to the Graphics menu. But
since we are using DITA XML, I'd like to save the rotation property
to the XML and have FM apply it again when the XML file is reopened.
Clearly a job for read-write rules.
So after a thorough study of the Structured Application Developer's
Guide and the corresponding Reference, as well as the FM11 help,
etc., I have attempted with the following:
element "entry" {
is fm table cell element;
attribute "outputclass" {
is fm property rotate;
value "rotate" is fm value "270";
}
}
When I set @outputclass to "rotate" and save as XML, the attribute
value is not written. If I edit the XML in a text editor and then
open in FM, the @outputclass is set to "no value". So clearly nothing
is happening using @outputclass and/or my rule.
The Developer Reference gives tantalizing information such as
"FrameMaker extends the possible values to allow rotations of 0, 90,
80, and 270 degrees." I've tried a whole lot of alternative rules and
values, but nothing seems to do anything (except generate an error,
that is).
Do I need to use or define a different attribute than @outputclass?
Or is there some other secret syntax that eludes me? Or does it just
not work?
Thanks for your help..
Roger Shuttleworth
London, Canada
_______________________________________________
_______________________________________________
You are currently subscribed to framers as [email protected].
Send list messages to [email protected].
To unsubscribe send a blank email to
[email protected]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [email protected]. Visit
http://www.frameusers.com/ for more resources and info.
