LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Tue, 1 Sep 2009 15:15:19 +0100
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: Your message of Tue, 01 Sep 2009 15:17:46 +0200. <[log in to unmask]>
Content-Type: text/plain; charset=iso-8859-1
From: Robin Fairbairns <[log in to unmask]>
Parts/Attachments: text/plain (30 lines)
Uwe Lück <[log in to unmask]> 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

ATOM RSS1 RSS2