Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Nov 2008 18:47:17 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id mAOHlEIl030545 for ; Mon, 24 Nov 2008 18:47:15 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id mAOHg0md000445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Nov 2008 18:42:01 +0100 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id mAOAbaG1001634; Mon, 24 Nov 2008 18:41:53 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 173281 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 24 Nov 2008 18:41:53 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id mAOHfr4k028445 for ; Mon, 24 Nov 2008 18:41:53 +0100 Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id mAOHfcci015193 for ; Mon, 24 Nov 2008 18:41:42 +0100 Received: from [71.35.168.107] (helo=[192.168.2.3]) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1L4fRK-0003BV-8z for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 24 Nov 2008 12:41:38 -0500 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060212 Fedora/1.7.12-5 X-Accept-Language: en-us, en MIME-Version: 1.0 References: <9A98C2E5-6170-4AA4-9E26-CCB96A234D76@gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 2d75d9567fada10dc3b6ad7bd0984c4474bf435c0eb9d47888f6b5e87b9bb51cc5c35f3f392fb5f7daf949ad53bc8384350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 71.35.168.107 Message-ID: <492ABD3B.8080205@earthlink.net> Date: Mon, 24 Nov 2008 09:42:03 -0500 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: peter wilson Subject: Re: Documenting LaTeX3 packages (l3doc) To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <9A98C2E5-6170-4AA4-9E26-CCB96A234D76@gmail.com> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -2.599 () BAYES_00 X-Scanned-By: MIMEDefang 2.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 24 Nov 2008 17:47:17.0590 (UTC) FILETIME=[B1558760:01C94E5C] Status: R X-Status: X-Keywords: X-UID: 5461 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.