Re: [docbook-apps] Re: Including a variable in an xlink:href value

2018-01-10 Thread Janice Manwiller
Thanks so much for the suggestion. I actually tried again to create and refer to an entity file, and this time it worked and wasn't rejected - I have no idea what I did differently. And the entity reference in the link destination also works correctly. Janice On Wed, Jan 10, 2018 at 8:55 AM,

Re: [docbook-apps] Re: Including a variable in an xlink:href value

2018-01-10 Thread Dave Pawson
Is this a case of the simpler the docbook, the more chance of understanding what's happening? Add a 'framework', and as Mark explains you need to understand two levels of complexity? I rate docbook as 'hard sums', and fight shy of adding more - though I'm sure others find it adds its own

Re: [docbook-apps] Re: Including a variable in an xlink:href value

2018-01-10 Thread Mark Craig
Hello Janice, Since you're using Maven, as a workaround you could use bare Maven expressions and perform Maven filtering on the source before using the docbkx plugin. Maven filtering replaces expressions like ${project.version} with the values of their Maven properties. For example, in a

[docbook-apps] Re: Including a variable in an xlink:href value

2018-01-10 Thread Janice Manwiller
I probably should clarify that the notation is specific to the Maven docbkx plugin, which we use to generate the output. I also tried to create an entity file containing a version entity using the info from http://www.sagehill.net/docbookxsl/Db5Entities.html. When I tried to add the DOCTYPE