XSL vs. text insets

[JohannesKrueger]

Hello,

Generally, XML entities are resolved when parsed. As a consequence for working with structured FM, you can either apply XSL transformations to the markup on import and export or keep entities as text insets and variables.

I wonder if there is a workaround to keep entities as text insets and variables after applying an XSL transformation with FM? If so, maybe you could share how to set up a  workable solution.

Thanks in advance,

Johannes

[Michael_Müller-Hillebrand-basb · Accepted solution]

Johannes,

I am not sure I understand your requirement correctly.

FrameMaker 9.0.3 comes with a structured client DLL (including source code) named PreserveEntities.dll that creates processing instructions in addition to each entity when saving as XML. Those can be used to recreate the entities using a preprocessing XSL stylesheet (example is included) when opening an XML file.

Was this your intention?

- Michael Müller-Hillebrand, cap-studio.de

[JohannesKrueger]

Thanks for your reply, Michael, this sounds like what I'm looking for, except that I'm still using FM8. So this is not a solution for me right now, but could be one of the better reasons to update ...

Meanwhile I consider using an extra attribute to identify which parts of a 'monolithic' file will be extracted into external entities and then referenced. I'll see if this turns out to be workable. After all, it's primarily the modular structure in markup what I'd like to retain, as useful real text insets on the FM side would be.

Kind regards

Johannes

[Michael_Müller-Hillebrand-basb]

Johannes,

I would also recommend using attributes. Text insets as well as variables are no real structured elements. For a better solution comparable to Text insets you may want to have a look at the plug-in InsetPlus at

http://www.weststreetconsulting.com/

It comes with a tutorial.

- Michael Müller-Hillebrand