Myself, I'd go even further and switch over to having XML as my sources. Why settle for doing <span class="dialogue" xml:lang="fr"> when you can do a simple <fr-dlg> or you can go straight to:
Code:
<recipe>
<title>Boiled Water in a Pan</title>
<ingredient qty="2" measure="L">water</ingredient>
<instructions>
<step no="1">Don't set the stove on fire while turning it on.</step>
</instructions>
</recipe>
instead of having to muddle around with classing divs and spans and other elements just so that you can target a few things with CSS?
The great thing about XML is that you can keep the content you're working on nice and cleanly semantic, and separate out dealing with the messy display quirks for the final output version.
You've probably already come across all this, but just in case:
Late Night Software has a bunch of
free AppleScript Scripting additions for XML and XSLT, and the Smile people have an
XMLLib one, along with some other possibly useful stuff.
Todd Ditchendorf's also written up a bunch of useful tools that integrate with Safari and are mostly
BSD licensed on Google Code. Good for testing things.
Some of them are kind of hidden away on his website due to some sort of reorg or something, so:
AquaXSL,
AquaPath,
XSLPalette.
And I've generally found
Marc Liyanage's TestXSLT useful for doing just what is says on the box. Helps one get the hang of things.