Daniel O'Donnell wrote:
>I have lots of quick an dirty documents I work on where I would like the
>benefits of both worlds. I realise, of course, that it is a simple
>matter to build a basic tei>xhtml stylesheet or modify an existing one,
>but I find I'm always having to do that and this time wanted something
>in between to check my work as I was composing.
I write almost everything in TEI XML, as pretty much
a matter of religion; it just needs a bit of investment up
front. But in the same way, I bet your average Word user
has spent some time getting a template document
just the way they want it.
I alternate as appropriate between
1. read the XML in emacs
2. convert to static HTML on a command line and load to browser
3. copy into area on my machine where the local web server
will pick it up and render it
4. convert to PDF and read that
5. upload to main web server for others to read
you might read between those lines that the key to
my working day is
a) command-line tools, like "make"
b) a web server on my computer which is always ready
to spring into action
Note that 5. above is only needed when there is some complex
component like a database lookup that my machine is barred from
It sounds complex, and it is. But notice the stress on the
web in the above. I want my documents web-ready as soon
as I start writing, not one day maybe; but I also want them
nice-PDF-ready, and validated. TEI XML - you know it makes sense!
PS oh, and whatever else happens, get every document
into a version control system.... thats _every_ document.
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
OSS Watch: JISC Open Source Advisory Service