LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Mon, 24 Nov 2008 09:42:03 -0500
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
Content-Type:
text/plain; charset=us-ascii; format=flowed
From:
peter wilson <[log in to unmask]>
Parts/Attachments:
text/plain (35 lines)
Will Robertson wrote:
> Hello,
> 
> Packages (or "modules") in the expl3 bundles use the l3doc class for  
> documentation in the tradition of ltxdoc. Up until now, l3doc was  
> provided as a straight .cls file, which was in a bit of a mess.
> 
> This evening I was a little tired, so rather than attempting to write  
> any actual code (or work on my thesis), I bundled l3doc.cls into a  
> proper .dtx file and tidied it up somewhat. It's now a bit more  
> readable, and I managed to remove some code that was duplicated  
> elsewhere or was otherwise not really being used.
> 
> One maybe big change, though: it now loads the full expl3 suite and  
> declares itself as an "ExplClass". It doesn't actually use much LaTeX3  
> code, yet, but this is a change from some time ago when the  
> documentation for the LaTeX3 code could still be compiled using LaTeX2e.
> 
> If there's any problem with this, please let me know and I'll reverse  
> my decision.
> 
> ***
> 
> Meanwhile, if any members of this list would like to volunteer with  
> maintaining this class, it would be wonderful to create a Franken- 
> monster of l3doc, hypdoc, xdoc, and gmdoc. What little time I have  
> available now I'm spending on the expl3 test suite, so I suspect  
> without outside help this class will remain a patchwork of hacked- 
> together code to support whatever markup we happen to want/need while  
> writing the expl3 modules.

     You might consider throwing the docmfp package into the mix as well.

Peter W.

ATOM RSS1 RSS2