As always, I cheat a little on ‘X’ day.
Yes, six months in, but I’m still working on the A-Z Challenge.
Applying Styles to Document Elements
Splitting taxonomy and presentation of domain objects was a really good idea. The style details are stored in a file much like the taxonomy file, parsed out and applied as needed.
It’s still a good idea for document objects, but document elements represent the document hierarchy, not a a taxonomy. A chapter has sections, but a section is not a chapter. There is little opportunity to inherit presentation details.
Unless I have different ‘chapter types’ and different ‘section types’, there isn’t much point to using the taxonomy-based mechanism.
Also, the sectioning mechanisms built into LaTeX work differently from the code I’m using for domain objects.
In the end, I’m going to either work around the sectioning code, or reframe how it works. My first tests show it can be done, though.
The image above wasn’t built with the full workflow. That is, from style definition in Word through XML transformations through LateX. This does show that I can use the same tcolorbox definitions for both game elements and document elements.
I’ve got all the pieces I need. There is some work to be done to apply them, but I know now how to do it.
Applying Styles to Diagram Nodes
Ah, back to the driver for this entire series of posts. I haven’t coded for this one either, but it should be straightforward.
First, build out the the DOT diagrams and convert the results to XML. Then prepare the pubtex file and apply style information from the style file and override file. I see where all the pieces will lie, I just need to code them.
Closing Comments
This post is one that either can short and a abstract, or detailed and really long. Since I don’t have all the details at hand, I’m picking ‘short and abstract’. I’ll post the details when I have them.