Question
Frame XSLT processing screws graphics mappings
Hi,
We have encountered strange behavior in FM 8. Our XML has element for graphics with attribute set that matches 100% to frame graphic properties, like:
image position="below" href="graphic.jpg" etc..
rw-rules maps position to position property and href to file property etc..
If I open the file w/o using frame's XSLT in the middle frame behaves as expected (like 7.x did).
We had a small and simple xsl stylesheet (almost pass-through) and if that was added in structapps the results were odd in frame:
- href got mapped to file property, but also appeared in structure view!. Since href was a property, edd had no counterpart. Href was shown as invalid in structure view.
Also, frame no ignored position totally, all graphics got the default "At insertion point" value. This happened even if I tried to force the property to "below" in rw-rules.
All this worked in fm 7.x.
Has anyone noticed similar behaviour?. I'd consider this a serious bug.
BR, Martti
We have encountered strange behavior in FM 8. Our XML has element for graphics with attribute set that matches 100% to frame graphic properties, like:
image position="below" href="graphic.jpg" etc..
rw-rules maps position to position property and href to file property etc..
If I open the file w/o using frame's XSLT in the middle frame behaves as expected (like 7.x did).
We had a small and simple xsl stylesheet (almost pass-through) and if that was added in structapps the results were odd in frame:
- href got mapped to file property, but also appeared in structure view!. Since href was a property, edd had no counterpart. Href was shown as invalid in structure view.
Also, frame no ignored position totally, all graphics got the default "At insertion point" value. This happened even if I tried to force the property to "below" in rw-rules.
All this worked in fm 7.x.
Has anyone noticed similar behaviour?. I'd consider this a serious bug.
BR, Martti
AdChoices