MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID:  <32095.1251814519@cl.cam.ac.uk>
Date:         Tue, 1 Sep 2009 15:15:19 +0100
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: Robin Fairbairns <Robin.Fairbairns@CL.CAM.AC.UK>
Subject: Re: l3doc, was Re: xparse
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  Your message of Tue, 01 Sep 2009 15:17:46 +0200. 
              <5.1.0.14.0.20090901150944.026507a0@pop3.web.de>
Precedence: list
Status: R

Uwe Lück <uwe.lueck@WEB.DE> wrote:

> At 12:35 01.09.09, Manuel Pégourié-Gonnard wrote:
> > 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 learned it long enough ago that it (finally) comes as second nature.

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

i've thought that, too, but never quite got off the ground with it.  the
probable cause is lack of time.

> That's why I made niceverb and makedoc (in tug.ctan.org/pkg/nicetext;
> somewhat clumsy still difficult with hyperref, but it serves me to
> maintain a book class), and I find Paul Isambert's CodeDoc very nice
> which extracts package code while typesetting the documentation.

all these things feature in a faq answer that i've no more than a sketch
of.  while i would like to sort it all out for myself, i've more
important things to do for the faq, and spend more time on the big
picture than on this one pending answer

r