User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
References: <4A7921CF.5020803@morningstar2.co.uk>                      
            <4A86949D.3090500@morningstar2.co.uk>                      
            <4A886BA8.2000209@morningstar2.co.uk>                      
            <0417DF73-EC19-4262-B9DF-5C870D47BFCE@gmail.com>                   
            <4A893816.2090807@residenset.net>                      
            <4A89610D.8060108@morningstar2.co.uk>                      
            <4A8C71CC.7000006@residenset.net>                      
            <4A8D0048.4070101@morningstar2.co.uk>                      
            <4A946AD7.4020506@residenset.net>                      
            <4A9C2DF7.6070002@morningstar2.co.uk>           
            <E6A84A92-B935-4144-9618-6BA45293958F@gmail.com>
            <4A9CCC56.80001@morningstar2.co.uk>
OpenPGP: url=http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x50A89B42
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Message-ID:  <4A9CF90D.5030100@elzevir.fr>
Date:         Tue, 1 Sep 2009 12:35:57 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: =?ISO-8859-1?Q?Manuel_P=E9gouri=E9-Gonnard?= <mpg@ELZEVIR.FR>
Subject: Re: l3doc, was Re: xparse
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <4A9CCC56.80001@morningstar2.co.uk>
Precedence: list
Status: R

Hi,

Joseph Wright a écrit :
> I'd imagine that the code needs a careful overhaul at some stage, as
> things are very much a mish-mash at the the moment. However, that
> depends on what we want, as you say. For example, the gmdoc approach of
> not needing \begin{macrocode} ... \end{macrocode} is interesting: I
> wonder if it makes it easier for new users to write documented files?
> 
As a matter of personnal feeling, I'm really tired of the dtx format. If find it
too complicated to write, read and modify. In general (for my normal documents
also) I prefer rather light markup and dtx format seems like the opposite of
light to me.

I didn't have time to look too deeply in gmdoc, but I tend to think it is a more
usable approach.


While discussing l3doc, I'd like to make a quite unrelated remark (to which JF
would most probably agree). It would be great to think that a documentation is
not necessarily just a PDF, but that some information may be converted in other
format and/or reused in applications (eg a webapp like Context's (I can't
remember the name right now, or a database of which package defines which
command, etc.).

While LaTeX output in many formats (esp. XHTML-based) is a difficult problem in
general, some parts of a documentation, such as the command syntax and a summary
of the arguments, are a subset with sufficiently "rigid" structure so that it
should be doable.

I don't know if some such things was allready planed or at least discussed, so
just to be sure...

Manuel.