Hi Russ,
there's nothing bad about a good plug. In this case, the customer does not own FrameSLT and the project will not require it for anything else, so I will have to solve it in the read-write rules (so that no additional scripting is required) or maybe do it from ExtendScript if all else fails. There is only one table with a specific framemaker element name that requires fixed settings for its columns. I am checking various options, might even be able to do this via the EDD.
Thanks
Jang
Got it !!!
Turned out to be simple, but the info was more or less hidden in the Dev Ref Guide: I had already put the "fm property column widths is value " line in but did not know the syntax for the values. Turns out you need to delimit the values by spaces, not commas. The parser does not give ANY useful information about this, just mentions 'syntax error near somewhere' or completely ignores the values you specify.
This is how the rule for my DITA properties element now works out:
element "properties" {
is fm table element;
fm property columns value is "3";
fm property column widths value is "5cm 5cm 6cm";
}
It works. I earn 10 points for answering my own question. :-)
Ciao
Jang