If you have information about your company’s product or services that needs to be delivered to customers, whether it’s in print or electronic form, chances are you have heard of XML.
Are you finding yourself in the position of having to explain to others:
Last week, Single-Sourcing Solutions held a webinar to talk about best practices for doing DITA stylesheets in Arbortext Styler.
The presentation focused on several key points that contribute to a successful DITA implementation: understanding fall-back processing, using read-only stylesheets, and developing with modular stylesheets.
In case you missed it, you can sign up to view the recording here or, because the event had a live Twitter stream, you can read through the highlights here.
Attached zip file contains the recording of the above meeting. The recording runs approximately 45 minutes.
During my presentation on producing PDFs from Bookmaps, the question came up as to whether the OT fills in the PDF document properties from the information in bookmeta. The answer is that this doesn't happen with the base OT.
However, one of the attendees, Simcha Gralla, sent me the following information about how this information can be pushed to the PDF.My thanks to hm for sharing this information with all of us. Basically you'll have to write an XSLT to handle how the different processors handle providing that information.
On Aug 25, 2010, I gave a presentation about producing PDFs using BookMaps. Part of that demo was an examination of the XSL file that contained the template overrides I used when producing Practical DITA.