alex said:

I suppose there's no way to get the source for that .py?

the best way in the world to get it is to write it yourself, alex. i'll be happy to answer every question you have along the way. here's a push to get you started: 1. read in the .zml file. 2. separate text into chunks, splitting on double-linebreaks. 3. examine each chunk to determine its structure, and tag it. 4. ... 5. wrap each chunk with its appropriate markup, and output. (you'll find there is a step necessary between step 3 and step 5, which is why i labeled it thus, but don't worry about it at first.) this is not a hard program to write. i rewrite it often, for _fun_. and for my own education. each time i try to write it differently. this time i am using python, with .html5 as the output format... doing it time after time teaches me about the hidden "gotchas", and allows me to locate the most streamlined and graceful path. but it's also taught me the value of actually _doing_ the coding, rather than just picking up code from somebody else to run it, which is why i am disinclined to simply hand it to someone else. i worked very hard, for a good many years, to make this simple. so i need to see a similar willingness to work, that i can reward. -bowerbird p.s. i started the current python script on thanksgiving day -- hence its name -- when i was stranded without my computer (and thus had to start from scratch), while waiting for turkey. so i can say, with great certainty, it doesn't take a lot of time.