Made some final fixes to XSLT and CSS based on the W3C validator, and reported to the editors as follows:

I've finished a first pass through generating the XHTML output from the two documents we've marked up so far. The results are here and here.

Some points to note:

• Both XHTML and CSS validate, according to the W3C validator.
• My choices as to fonts, spacing, sizing etc. are just arbitrary; I'll need your input into that.
• Wherever APA has anything to say about how something should be presented, I've tried to follow it (for instance, in the display of tables with no vertical and few horizontal lines), but I may have missed some APA diktats, so do let me know if you see anything odd.
• Notes and references work as popups on the right of the text (hence the larger margin on the right). However, if the user has JavaScript turned off, they should just work as straightforward internal links.
• Images embedded in the text are links to full-size versions of themselves.
• Metadata is embedded in the source of the document as Dublin Core meta tags. I plan to add some JavaScript which can parse it out from the header and present it to the user in a more human-readable form, but the meta tags are important for machine-reading, and for folks who turn off their JavaScript.

I think it would be useful at this stage to concentrate on making sure all the display features are working as they should, and following APA, and on making some basic choices about font style and display characteristics. Once we've got an XHTML appearance we're happy with, I can start porting that over into the XSL:FO/PDF output, which is a bit more tricky.

Other things on my mind:

I'm wondering if it would be useful to have a view of the text in which the JavaScript and CSS is embedded directly into the document, so that it would function as a single portable file. This portability would be undermined by the fact that images would still have to be externally linked, though, so perhaps it's pointless.

Tables have a minimum width which is determined by the minimum wrappable size of their content cells, so they sometimes stick out beyond the text column -- see, for instance, Table 3 in Yaden, with your browser window sized a bit smaller than usual.

This is probably unavoidable, but if you'd like to put some thought into ways to avoid it, I'd be happy to have suggestions.