hi,
we have encountered strange behavior in fm 8. our xml has element graphics attribute set matches 100% frame graphic properties, like:
image position="below" href="graphic.jpg" etc..
rw-rules maps position position property , href file property etc..
if open file w/o using frame's xslt in middle frame behaves expected (like 7.x did).
we had small , simple xsl stylesheet (almost pass-through) , if added in structapps results odd in frame:
- href got mapped file property, appeared in structure view!. since href property, edd had no counterpart. href shown invalid in structure view.
also, frame no ignored position totally, graphics got default "at insertion point" value. happened if tried force property "below" in rw-rules.
all worked in fm 7.x.
has noticed similar behaviour?. i'd consider serious bug.
br, martti
we have encountered strange behavior in fm 8. our xml has element graphics attribute set matches 100% frame graphic properties, like:
image position="below" href="graphic.jpg" etc..
rw-rules maps position position property , href file property etc..
if open file w/o using frame's xslt in middle frame behaves expected (like 7.x did).
we had small , simple xsl stylesheet (almost pass-through) , if added in structapps results odd in frame:
- href got mapped file property, appeared in structure view!. since href property, edd had no counterpart. href shown invalid in structure view.
also, frame no ignored position totally, graphics got default "at insertion point" value. happened if tried force property "below" in rw-rules.
all worked in fm 7.x.
has noticed similar behaviour?. i'd consider serious bug.
br, martti
martti, post "almost pass-through" xsl?
when opening xml files xsl processing applied before r/w rules thing. there ways intercept intermediate xml files, maybe @ xsl helps.
- michael
when opening xml files xsl processing applied before r/w rules thing. there ways intercept intermediate xml files, maybe @ xsl helps.
- michael
More discussions in FrameMaker Structured
adobe
Comments
Post a Comment