Hi Bob,
On 7/7/10, Bob Stayton <> wrote:
> Can you please file a bug report on SourceForge for this problem?
https://sourceforge.net/tracker/?func=detail&aid=3026590&group_id=21935&atid=373747
> 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.
this is the case: the olinks in titles refer back to the current document.
> 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?
I don't have a file named olinkdb.xml.
instead, I have files
clink.tdb (for clisp-link.xml)
man.tdb (for clisp.xml)
chunk.tdb (for chunked impnotes)
pile.tdb (for impnotes in one file).
the failing command actually creates clink.tdb
> If you think this is a regression, can you identify the last version in
> which it worked without error?
I can try to play with svn...
--
Sam Steingold <http://sds.podval.org>
