On Tue, Sep 10, 2002 at 06:14:49PM -0400, Paul Tremblay wrote:
[...]
I agree that a xml file format has advantages and you have listed
some of then.
> Paul
>
>
> <?xml version="1.0"?>
> <!DOCTYPE notes_on_xml>
> <!--a very incomplete version of what a LyX document might look like if
> converted to XML-->
>
> <lyx_doc>
> <definitions
> lyxformat="218"
> textclass="article"
> language="english"
> inputencoding="auto"
> fontscheme="default"
> graphics="default"
> paperfontsize="default"
> spacing="single"
> papersize="Default"
> paperpackage="a4"
> use_geometry="0"
> use_amsmath="0"
> paperorientation="portrait"
> secnumdepth="3"
> tocdepth="3"
> paragraph_separation="indent"
> defskip="medskip"
> quotes_language="english"
> quotes_times="2"
> papercolumns="1"
> papersides="1"
> paperpagestyle="default"
> />
No definitions is not sensible. What about the user preamble?
It should be something like:
<lyx_doc lyxformat="218">
Or maybe this is information is alread present in the <!DOCTYPE...>
as this refers to the xml format itself. The same goes for the
textclass, as this will condition the document allowed structure.
Then we could have something like:
<header>
<!-- option is the same as the previous definition -->
<option name="use_geometry" value="0">
<option name="inputencoding" value="auto">
<preamble><![CDATA[ ... ]]>
</header>
<body>
Notice that tables are almost xml, as they stand now.
> <part>
> <table
[...]
> <!--Don't know what to do with the formatting for each column.
> Can't think of a good xml solution right now-->
>
> <column nu="1"
we should not care about the column number.
> alignment="center"
[...]
> </row>
> </table>
> </part>
> <section number="false">
> <para type="standard">standard text</para>
> <para type="verse">verse</para>
> <para type="standard" added_space_top="smallskip"> text</para>
>
> </section>
> </lyx_doc>
>
>
> --
>
> ************************
> *Paul Tremblay *
> *[EMAIL PROTECTED]*
> ************************
--
Jos� Ab�lio Matos
LyX and docbook a perfect match. :-)
