X-VM-VHeader: ("Date:" "Resent-Date:" "From:" "Sender:" "Resent-From" "Originally-From:" "Originally-To:" "To:" "Apparently-To:" "Cc:" "Subject:") nil X-VM-Bookmark: 3 X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1512" "Wed" "9" "June" "93" "12:21:59" "+0200" "kris@DIKU.DK" "kris@DIKU.DK" nil "40" "LaTeX3 modularity" "^Date:" nil nil "6"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/1.9.92 ) id AA26298; Wed, 9 Jun 93 12:45:13 +0200 Received: from vm.urz.Uni-Heidelberg.de (vm.hd-net.uni-heidelberg.de) by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA10139; Wed, 9 Jun 93 12:45:09 +0200 Message-Id: <9306091045.AA10139@sc.zib-berlin.dbp.de> Received: from DHDURZ1 by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with BSMTP id 9459; Wed, 09 Jun 93 12:43:49 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 3857; Wed, 09 Jun 93 12:43:36 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 3855; Wed, 09 Jun 93 12:43:34 CET Reply-To: Mailing list for the LaTeX3 project Date: Wed, 9 Jun 93 12:21:59 +0200 From: kris@DIKU.DK Sender: Mailing list for the LaTeX3 project To: Multiple Recipients of Subject: LaTeX3 modularity Status: R X-Status: X-Keywords: X-UID: 1042 Dear \LaTeX3 people, I am a volunteer on the \LaTeX3 ``Syntax of Commutative Diagrams'' [CD] research task. Our task has, however, some problems that seem fundamental to the \LaTeX3 project: First of all, any CD implementation is bound to be rather large---current implementations range from 50 to 300k---and should thus be in a seperate module. Thus: Question 1: What restrictions should externally programmed \TeX\ modules obey in order to interface with and be useful from within \LaTeX3? Second, CD implementations might make use of a general picture environment of \LaTeX3, so: Question 2: Is an enhanced picture environment planned for \LaTeX3? If such a module is planned but is itself an optional module, then Question 3: Will there be guidelines for interfacing and ``requiring'' one optional module from within another, i.e., is there a standard way for testing whether an option is loaded? I am realy looking forward to reactions to these questions; in fact I have a proposal for a general picture environment and modularity idioms myself which you may retrieve in PostScript form from ftp.diku.dk:diku/users/kris/xycore27beta.psZ Regards, Kristoffer ______________________________________________________________________ Kristoffer H{\o}gsbro ROSE Internet: kris@diku.dk DIKU (Semantics group), University of Copenhagen Voice: +45 35321420 Universitetsparken 1, DK-2100 Copenhagen {\O} Fax: +45 35321401