xml from ed

[Edward Glowacki]

Quoted from Marcel Kunath on Fri, Jul 27, 2001 at 10:39:23AM -0400:
> Or are you only concerned by converting EdBook to DocBook but not Docbook to
> EdBook?

I only care about the one-way conversion from "EdBook" to DocBook.
I just want something that I can markup documents in that's a lot
simpler than docbook.  I'm trying to do things "the right way",
but there's so many different ways to deal with XML that I really
don't know where to begin, even though I've spent time online
looking for information.  I just downloaded some stuff for Python,
and the example to translate comma separated values to XML has 3
different methods included it, each using an entirely separate
"technology" if you will to do the conversion.  I believe the
technical term for my condition is "information overload".  =P

Ultimately what I'd like is a better environment for editing
documentation, but to get there (and sort of a way to experiment
with what I really want) I thought I'd try using scripts to simulate
actual editing functions, then incorporate those scripts into a
text editor somehow for use.  Maybe set it up so most editing is
done in (structured) plaintext, but converted to XML (docbook,
edbook, whatever) sort of on-the-fly:

\n\n            ---> </para><para>
- [text]        ---> <listitem><para>[text]</para></listitem>
= [text]        ---> <section><title>[text]</title>
                     </section> 

I wouldn't have to change the way I usually edit files too much
to make this system work, since I already do \n\n between
paragraphs and use "- text" to denote lists.

-- 
Edward Glowacki				glowack2@msu.edu
GLLUG Peon  				http://www.gllug.org
Imagination is the one weapon in the war against reality.
                -- Jules de Gaultier