Hi all,
I have a custom XSD and am I styling for PDF using the APP engine in Editor 6.0 M10.
I am looking for a way to store things like numbering and other context related information in attributes. An example of this would be storing the font family and size as it is applied by the stylesheet in the attributes of the element being styled.
This will mean that an external system which receives the XML data would be able to tell that a title was "printed" in a certain font and size.
I have had a look at using xpath in genetated text, but have not been able find a logical solution. I assume one would need to capture the generated text for numbering in some sort of variable and then write that variable's value into the attribute of the relevant element.
I would appreciate a pointer in the right direction.
Thanks,
Duan
Hi Duan,
Interesting problem for which I don't have any answer other than writing anXSL taking the stylesheet as an input. Line numbers sound like even more of a challenge since they require multiple formatting passes.
Purists (beware), many of whomwho don't live in the real world where we need to communicate with the less-than-pure, would say you're missing the point of course ...
Regards,
- Lou Argyres
Continuing Education of the Bar - California
Oakland, CA
In Reply to Duan Gauche:
Hi all,
I have a custom XSD and am I styling for PDF using the APP engine in Editor 6.0 M10.
I am looking for a way to store things like numbering and other context related information in attributes. An example of this would be storing the font family and size as it is applied by the stylesheet in the attributes of the element being styled.
This will mean that an external system which receives the XML data would be able to tell that a title was "printed" in a certain font and size.
I have had a look at using xpath in genetated text, but have not been able find a logical solution. I assume one would need to capture the generated text for numbering in some sort of variable and then write that variable's value into the attribute of the relevant element.
I would appreciate a pointer in the right direction.
Thanks,
Duan
Hi Duan,
Sounds very similar to something we've recently been doing for a customer that augments the XML, in this instance with line and page break information. This follows a similar idea to what Gareth is suggesting but augmenting the XML with custom PI's durring the formatting pass and returns this to Editor (outside of the integrated APP and using a direct APP template). So this does work well if you chose this approach.
Regards
Chris
Chris Western
tformat ltd
Arbortext sVAR/MSP
www.tformat.com