Hello, A question for the developers or other Plucker experts: Normally, Plucker parses and converts all HTML pages referenced by the base page (up to MAXDEPTH), and puts the final product in a single .pdb database. Is it possible to either: 1). Force the parser to generate separate .pdb's for each converted HTML page or 2). Parse/convert the HTML pages separately, but have links operate ACROSS databases? Here's what I'm getting at: --------- A bible/concordance combination) example: If I generate a Bible .pdb from HTML page(s) containing named verse tags, e.g. ... <A NAME="Mt1:5"> v.5 </A> Salmon the father of Boaz... ... but reference it from a separate concordance/topic listing, e.g. <A HREF="./Bible.html#Mt1:5>Boaz<A> ... <A HREF="./Bible.html#Mt1:5>Salmon<A> then I can have a combined topic index and bible text database, which is nice in itself. However, if I wanted to update the topic index (frequently), it would be nice to avoid the parsing/uploading overhead of the main text by making it a separate database from the topic index. ------- I've searched the help pages and tried to make separate databases, but the Plucker parser doesn't seem to support the cross-references between databases...am I wrong? Is this something that the developers might consider adding? Thanks for any info Rob Grace [EMAIL PROTECTED]
