Noob needs help w/xforming DocBook>DITA
Posted: Tue Jul 01, 2014 12:13 am
I'm reasonably technically competent, but I've spent the last few months learning DocBook and OxygenXML and, boy, there's a lot to grasp. Now I need to migrate the documents I've been creating in DocBook 5 into DITA. I understand that no transformation is plug-and-play, and that as well as tweaking the transformation, I will need to break my documents into single-topic DITA documents.
However, my concern is getting over the first hurdle of simply transforming the basic document tagging, and I'm making slow, bumpy progress. Looking for a little help, or pointers to help. (I searched YouTube but didn't find much.)
What I've done so far:
- installed an updated version of the DITA OT by replacing the version in Oxygen's frameworks/dita folder. I changed the folder name to DITA-OT so it could be found without having to go change paths all over the place. That seems to have worked.
- Downloaded the docbook2dita.xsl plug-in, which is actually a whole folder full of files. I placed this folder in the frameworks/dita/DITA-OT/plugins folder, which was my best guess for how to install it. Is that right?
- With one of the DocBook files I want to transform open in Oxygen, called up the Configure Transformation Scenarios dialog and created a new XML transformation with XSLT, which I associated with the file:/Applications/OxygenXML/frameworks/dita/DITA-OT/plugins/dbdita/db2dita/docbook2dita.xsl.
- Specified in the Output section of the dialog that it should prompt me for file output, figuring that would at least tell me the darned script was running at all.
Then I tried running the transformation on ${currentfileURL}. When the file save dialog did, indeed, appear, I gave it a name and destination. The script ran fast and smooth and produced a lovely DITA document with no content in it at all.
I'm just taking my best guesses here, and that's not quite enough, it seems. Do I need to explicitly point it at the source file even though it is the open, active file in Oxygen? Is there something I didn't configure?
Any suggestions? I'm happy to post any other specifics that might be needed to help, or, as I said, take pointers to a tutorial or other appropriate resource.
This is a LOT to learn! But that's cool.
Thanks for the help.
However, my concern is getting over the first hurdle of simply transforming the basic document tagging, and I'm making slow, bumpy progress. Looking for a little help, or pointers to help. (I searched YouTube but didn't find much.)
What I've done so far:
- installed an updated version of the DITA OT by replacing the version in Oxygen's frameworks/dita folder. I changed the folder name to DITA-OT so it could be found without having to go change paths all over the place. That seems to have worked.
- Downloaded the docbook2dita.xsl plug-in, which is actually a whole folder full of files. I placed this folder in the frameworks/dita/DITA-OT/plugins folder, which was my best guess for how to install it. Is that right?
- With one of the DocBook files I want to transform open in Oxygen, called up the Configure Transformation Scenarios dialog and created a new XML transformation with XSLT, which I associated with the file:/Applications/OxygenXML/frameworks/dita/DITA-OT/plugins/dbdita/db2dita/docbook2dita.xsl.
- Specified in the Output section of the dialog that it should prompt me for file output, figuring that would at least tell me the darned script was running at all.
Then I tried running the transformation on ${currentfileURL}. When the file save dialog did, indeed, appear, I gave it a name and destination. The script ran fast and smooth and produced a lovely DITA document with no content in it at all.
I'm just taking my best guesses here, and that's not quite enough, it seems. Do I need to explicitly point it at the source file even though it is the open, active file in Oxygen? Is there something I didn't configure?
Any suggestions? I'm happy to post any other specifics that might be needed to help, or, as I said, take pointers to a tutorial or other appropriate resource.
This is a LOT to learn! But that's cool.
Thanks for the help.