toggle quoted messageShow quoted text
You can have a look at the vrm and vrmlist elements, which are used for versioning information. You can put these elements in the map or topic metadata, which means they should be available in the merged file and everywhere else.
On October 19, 2016 9:44:19 PM PDT, "Patrik Stellmann patrik@... [dita-users]" wrote:
I have a bookmap and want to add a version to it in such a way that I
1. reference it within my content
2. read it by my PDF and Webhelp XSLs to add it to the footer
Currently I'm defining a keyref within a subject schema map like this:
This works fine for referencing it in the content using keyref="Version"/>.
My current solution for the publishing is
Set @processing-role to "normal" for the subject schema map and the
keydef to keep it from being removed so it is available in the
Passing the url of
the root map to the XSL for processing the topics
and read this using doc() function (for every single topic again).
It works but still I'm wondering if there is a better way since this
feels to be more a workaround than a solution?
Thanks and regards,
Posted by: Patrik Stellmann
Yahoo Groups Links
<*> To visit your group on the web, go to:
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo Groups is subject to: