I know we should do all of the below. At the moment (1) I just haven't
gotten around to setting up--and since we don't do this much more than a
couple of times a year, and we're hopefully going to switch to Roma
soon, I probably will never bother; (2) requires a little more
work--someone needs both to learn and to set up the process, and
document it all for the EpiDoc process, which neither I nor anyone else
has the time to at the moment. It is somewhere in the top ten of our
list of priorities, though (and as we have *hundreds* of bugs and
features to work through, the top ten is pretty good).
So, as always when you call the doctor or the mechanic... The moment I
ran the pizzachef again to confirm my suspicion that what it was in fact
doing was completely ignoring the extension files and giving default TEI
setting--it now runs without a problem. I've changed nothing. Nothing. Hmph.
Thanks for the advice, anyway.
Sebastian Rahtz wrote:
> PS you might find it easier to run the carthage software locally on your
> files, so you can embed it in your local build process and see the log
> files locally.
> Uploading to the web site is a bit clumsy for daily use.
> There is a command-line script "maketeidtd" which does
> the job for you.
> If it was me, I'd rewrite the Epidoc extensions in the ODD language
> and add a "P4 compatibility" set of extensions. The effect is to
> produce a P4-useable DTD now, and would let you move to P5
> easily in future. The p4compat extensions are fairly easy to write
> (there is a simple example in the P5 test set).
Dr Gabriel BODARD
Inscriptions of Aphrodisias
Centre for Computing in the Humanities
King's College London
7, Arundel Street
London WC2R 3DX
Email: [log in to unmask]
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980