Hi Dean,
I would suggest breaking down the process into steps and examining the
output of each step.
So I would run xmllint --xinclude on the file to generate a document
with XIncludes resolved, in which you can look for the id in question.
Then generating a temporary .fo file using your stylesheet, and checking
for the id. And then passing that to FOP to make the PDF. That will
show which stage is producing the error.
Bob Stayton
Sagehill Enterprises
[email protected]
On 10/29/2015 9:43 AM, [email protected] wrote:
Bob
Last night I ran the 1.79.0 load with my system (xsltproc, DB 4.5, fop 1.1)
For the most part, everything works as expected. However, I am now
getting a FOP warning when I use an XPointer. It looks like it adds it
to the list of FOP destinations, but does not use it. Hence :
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude";
href="../metriguard/loc-corpinfo.xml" xpointer="met-company"/>
and
<corpauthor id="met-company">&CORP_TITLE;</corpauthor>
produces this warning:
[WARN] FOUserAgent - Destination: Unresolved ID reference "met-company"
found.
The FOP process produces a correct document, it just complains. Here is
the rub and why I am concerned: it works just fine with the stock
stylesheets, no warnings and also with the 1.78.1 sytylesheets WITH my
customizations. So this has me a little stumped. I also noticed in the
release notes that there was some work in this area. Somehow, the new
stylesheet allow FOP destinations that should not be there?
Since it works with the stock stylesheets, I am wondering how I can
troubleshoot this in my own stylesheets and am asking for some input.
Any clues or ideas?
Thanks
Dean Nelson
In a message dated 10/21/2015 3:35:40 P.M. Pacific Daylight Time,
[email protected] writes:
It has been about a week since candidate DocBook XSL 1.79.0 was
released, and it has been downloaded about 150 times. Has anyone who
has tried it run into any problems yet? If so, please let me know so
they can be fixed for the 1.79.1 release.
--
Bob Stayton
Sagehill Enterprises
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
