nlct wrote:It may be that \texdbivalue{imagepath} doesn't simply expand to the path name. (For example, it may perform a check to determine if the key exists.)
I'm kinda confused. It may check if what key exists? This code works perfectly if it's not included as an \includegraphics argument. In other words, if i put \texdbivalue{imagepath} anywhere else in the document, it inflates perfectly with the image path.
nlct wrote:A new package called
ratexdb has just been announced. Maybe that might suit your purposes.
Thanks, I'm checking this out. I see that it is a preprocessor which works completely seperately from latex, producing only a second latex file which is complete with all of the requested database fields.
One problem is that it does not seem to support the \input command to include other files in your document. This is kinda essential as my entire document is spread out across multiple folders in many files. Discarding this multi-file structure would be quite counterproductive for me, as many of the files are inputed several times into the document.
Does anyone know of a preprocessor that will combine all of my files into one tex document right before it is processed by ratexdb?
In other words, something that would work like this:
Code: Select all
preprocessor catalog.tex > catalogcompiled.tex
ratexdb catalogcompiled.tex > catalogfinished.tex
pdflatex catalogfinished.tex > catalogfinished.pdf