WIP: First attempt for DITA -> DocBook with Python #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Avoids conflicts with standard Dietrich config file (which ends by .config)
We need the same XMLParser properties again, so create a argparse.Namespace object
This DITA summary file (by default: $TMPDIR/ditasummary.xml) contains all essential information about the whole directory; for example, xml:base of the directory, href of the current dita file, list of keywords, list of conrefs. The structure is flat, each dita file contains a <ditafile> element with all the necessary information.
* collect_linkends: Collect all linkends of the converted files * copyimages: Copy all image files
Currently, applying dita2docbook_template.xsl to DITA files creates empty outputs. Would it be better to call the saxon9 script instead?
tomschr
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After I've had thought about implementing the extension functions into
pyproc.py, I realized, this has to be done in a much deeper level. Therefor I tried to "rewrite" the shell script with Python asditatodocbook.py. Hope nobody will kill me.Sorry, but I can't stand the shell syntax and do at the same time complex XML juggling. For such a complex task (and it will getting worse), shell is not the best tool. I think this limits us a lot.
I see the following benefits with the Python approach:
-voptionpyproc.py(used as a "library")lxmlCurrently, the script does almost its job. The design is mostly based on the shell script, but shifting things into functions to make it easier to call them separately.
However, there are still some things to do:
ditasummary.xmlfile in the temp directory. This is an excerpt of all important properties we need to deal with (keywords, conrefs, ...) in a flat structure. Maybe we can use this file to load this into our stylesheets and to make transformation a bit easier. Not sure, if this is feasible...convert2dbto really do the transformation from DITA to DocBook. Currently, this is done by thesaxon9script. For some reason, xsltproc (or lxml) create empty DocBook files.copyimages()andcollect_linkends()functions