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, 8 Sep 2009 15:15:10 +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, 08 Sep 2009 15:12:17 +0200. <[log in to unmask]>
Content-Type: text/plain; charset=iso-8859-1
From: Robin Fairbairns <[log in to unmask]>
Parts/Attachments: text/plain (25 lines)
Uwe Lück <[log in to unmask]> wrote:

> >Well, I don't like this very much: I prefer package code to be the primary
> >content and documentation to be extracted from comments. I find it much easier
> > for changing the code and testing it without needing ot extract it
> > first. (Same
> >problem as dtx.)
> 
> I understand and agree.

i don't mind dtx, particularly (i've been writing it for >15 years, and
my fingers wander to the necessary groove without prompting).

however, there are quite a few (significant) packages on ctan that have
lots of documentation as comments only.  if i could take one such and
produce a useful printable document, i could improve the quality of user
support quite a bit.

(i've dallied with editing the comments into a separate .tex file.
this works, but is time-consuming, and tempts one into editorial work.)

robin

(straying off-topic for the group.  again.)

ATOM RSS1 RSS2