Hi Sam,
Can you please file a bug report on SourceForge for this problem?
It can only resolve it recursively during collection if the target of the nested olink
is in the same document, since that is the scope of the collection process.
Regarding regression, is it possible that formerly the processing environment had an
olinkdb.xml (or rather the file identified by the $target.database.document parameter)
to open so it could resolve the nested olink? In your earlier mail you said you
didn't have an olinkdb.xml, but if you are using olinks, how are you resolving them?
If you think this is a regression, can you identify the last version in which it
worked without error?
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Sam Steingold" <[email protected]>
To: "Bob Stayton" <[email protected]>
Cc: <[email protected]>; <[email protected]>
Sent: Wednesday, July 07, 2010 1:26 PM
Subject: Re: [docbook-apps] warning: failed to load external entity
Hi Bob,
On 7/7/10, Bob Stayton <[email protected]> wrote:
Is it possible that one of your olinks in the offending file is referencing
an element whose title contains an olink?
I think this requirement is a regression.
I have had olinks in titles for a long long time (5+ years) and I see
this problem only now.
If so, then when the information is gathered for the olink database, it has to
process
that nested olink to get its text for the database.
so let it do it recursively!
the error I observe happens in the olink db generation process.
--
Sam Steingold <http://sds.podval.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
