?? I presume Tom means "no disrespect to ... CTE" instead of to
Emacs, as Emacs works quite well with RELAX NG for complex
That said, it still may not be worth your while, Rosanna, to learn
Emacs. I absolutely *love* it, as it is extraordinarily powerful and
customizable, but even I have to admit that it is very far from
anything most users have ever done on their computer, and thus has a
very steep learning curve. (Nay, not a curve, a cliff.) It's not that
you would need many hours of time to learn it: you'll probably need a
full week. And in order to customize it for your shop, you will need
to learn the Emacs flavor of the LISP programming language. So make
it a full month.
And while Patrick's assertion that oXygen is close to "free" (as in
beer) is true -- it really is very inexpensive for what it does, it
is not at all free as in speech. This bothers me somewhat, but not
enough to avoid it. oXygen is the only propriety payware I use across
my various systems.
It is an excellent XML environment, has good support for TEI
built-in, and the folks who work at SyncRO have always been very
supportive of the TEI system and the TEI Consortium. (Ask James, who
just had a question on the oxygen-user list answered in ~22 hrs.)
 And even better with DTDs, but DTDs are not a modern schema
language. I still really really want someone to take psgml mode
(which uses DTDs) by the horns and teach it RELAX NG. I simply
don't have the time to do so myself -- I've forgotten much of my
Emacs LISP, too. Sigh.
 Note that oXygen has very reasonably licensing -- if you buy it,
you get to use it, on whichever of your computers you are on. Pay
for it once, and use it both on your GNU/Linux desktop at home
and your Mac OS X laptop on the road. You're not supposed to let
other people use your copy, of course. In ~2007 I broke that rule
and had my 11 year-old daughter use it to write her short
stories. Gives you an idea of how easy it can be to use oXygen.
> I mean no disrespect to Peter, nor to emacs, but I would strongly
> suggest that investing time and effort in adopting and learning an
> editor for TEI that doesn’t work well with modern schema languages
> for complex, documented-oriented XML would be a major mistake.