This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [docbook-apps] "Unresolved internal destination" error and id attribute of reference element


I'll bet you have a <partintro> in your reference element, right?  I can see
there is a bug in the logic of how a partintro in a reference is handled,
and it affects the id for the reference.  Can you please file a bug report
on the SourceForge DocBook site about this?  Thanks.

http://sourceforge.net/projects/docbook/

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: <Jere.Kapyaho@nokia.com>
To: <docbook-apps@lists.oasis-open.org>
Sent: Thursday, March 31, 2005 4:50 AM
Subject: [docbook-apps] "Unresolved internal destination" error and id
attribute of reference element


Hi all,

I'm getting an "unresolved internal destination" error from XEP 4.2 when
transforming DocBook XML markup containing 'reference' elements to PDF
(using the DocBook XSL FO stylesheets v1.68.1).

For example, this markup:

<book>
  <title>Sample book for ID testing</title>
  <!-- stuff removed -->
  <reference id="REF-1" xreflabel="Reference part 1">
    <title>Reference part 1</title>
etc.

causes the error message to be emitted and ToC of the resulting PDF to have
a '?' instead of the page number for the reference element. It happens both
in this simplified example and a larger production project.

Seems like the 'id' attribute of the 'reference' element is not output to
the generated XSL-FO markup. I inserted the 'id' attribute to the XSL-FO
block of the reference element by hand and then ran the XSL-FO to PDF
transformation again -- no problem there.

Could this be related to the ID issue described in this thread:
http://lists.oasis-open.org/archives/docbook-apps/200401/msg00070.html? The
workaround in the thread does not seem to work in this case. (?) Thanks in
advance for any ideas or pointers to a solution.

Best regards,
Jere

-- 
Jere Käpyaho (jere.kapyaho@nokia.com)
Specialist, Java Platform Standardization
Technology Platforms
Nokia Corporation




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]