Setting up structure for PDF rendering
I created the APA pdf.xsl file which calls the main article_to_pdf.xsl file, and tested it. Then I stored the pdf_page_masters.xsl file in the database itself, under db/teiJournal/settings/default/style/, and set up an XQuery file which can retrieve such files when passed the filename as a parameter. The XSL generation now calls that generation system through the cocoon:// protocol. The current setup assumes that if there's any kind of a user file in /settings/user/style/, it should use that; otherwise, it uses the default file. This is a large assumption, and a more graceful approach, similar to that of the CSS system, would be to find the default file, then iterate through all the named attribute sets and look for similar sets in the user file, substituting them where they exist. I'll implement that next. For the moment, basic PDF generation is still working after the XSLT rearrangement.