Otherwise, the problem with converting nested topics to DITA s is that sections cannot be nested one inside the other. In my opinion it's more correct to convert the nested topics to nested concepts. It's perfectly legal according to the DITA standard to have nested topics (with any depth level). Not sure if this will work for us, the lower level elements should be "sections" or "subsections", right? Maybe this option is not available with the version of oXygen that comes with Ixiasoft? See my screenshot for a complete list of Refactoring operations that are offered to me.Īs director, you have activated the following equipment:ītw, I can see from the preview that all "topic" elements are converted to "concept" elements, even for those on a lower level. I chose xr_dita_convert_resource_to_concept as Refactoring operation, because that seemed to be the closest to what I want achieve, but I got lots of errors when I tried to execute it. I checked for the refactoring stylesheet you referred to by using menu XML -> XML Refactoring. So I could try to replace step 3 with what you suggest. I use XML -> Apply Transformation Scenario(s) to apply my own stylesheet on the DITA topic. To convert this to DITA (topic class), I choose Export as DITA Topic in the DITA preview tab.ģ. Note that our version of the oXygen editor (XML Author 20.1, build: 2018161313) is included in Ixiasoft's DITA CMS so things might look a little bit different in this context.ġ.
I wasn't aware that there is such a refactoring action included for what I am trying to do. Thank you very much for your quick and helpful answer. XML-Refactoring-Ixiasoft-DITA-CMS.png (75.3 KiB) Viewed 7507 timesHi Radu, Our XSLT stylesheet has some extensions which can only be used when it's bundled with an XML refactoring operation:Īlso Oxygen's XML refactoring operations avoid expanding the DOCTYPE declaration and thus adding default attributes when the XML document is processed via XSLT. OXYGEN_INSTALL_DIR\frameworks\dita\refactoring\dita-files-conversion-stylesheets\convert-resource-to-concept-entrypoint.xsl And we also do this with XSLT, the top level XSLT which converts any DITA topic type to concept is this one: You can just right click inside the opened DITA topic and choose "Refactoring=>Convert to concept". But without having your entire XSLT stylesheet it's hard to know.Ībout your original task of converting a DITA topic to a concept, Oxygen already has an XML refactoring action included for this. Probably it appears because you make a mistake somewhere in the XSLT, match the attribute and output it as a text node. That particular "topic/li" is the original attribute set on the.
0 kommentar(er)
