X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["541" "Fri" "28" "January" "1994" "11:18:19" "GMT" "David Carlisle" "carlisle@cs.man.ac.uk" "<199401281120.AA07682@mail.cs.tu-berlin.de>" "14" "Re: Term sought" "^Date:" nil nil "1" "1994012811:18:19" "Term sought" (number " " mark " David Carlisle Jan 28 14/541 " thread-indent "\"Re: Term sought\"\n") "<9401281108.AA25951@m1.cs.man.ac.uk>"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA14304; Fri, 28 Jan 94 12:22:38 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA09736; Fri, 28 Jan 94 12:21:00 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA07682 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Fri, 28 Jan 1994 12:20:58 +0100 Message-Id: <199401281120.AA07682@mail.cs.tu-berlin.de> Received: from TUBVM.CS.TU-BERLIN.DE by tubvm.cs.tu-berlin.de (IBM VM SMTP V2R2) with BSMTP id 1485; Fri, 28 Jan 94 12:20:58 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin MAILER@DHDURZ1) by TUBVM.CS.TU-BERLIN.DE (LMail V1.2a/1.8a) with BSMTP id 1484; Fri, 28 Jan 1994 12:20:58 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin LISTSERV@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 3611; Fri, 28 Jan 1994 12:20:36 +0000 Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <9401281108.AA25951@m1.cs.man.ac.uk> (message from Robin Fairbairns on Fri, 28 Jan 1994 10:06:12 +0000) Date: Fri, 28 Jan 1994 11:18:19 GMT From: David Carlisle Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Term sought Status: R X-Status: X-Keywords: X-UID: 1338 Joachim writes: ... Joachim, why did you want this term. Is it (say) for naming a directory where it has to be a single word (preferably with less than 8 letters), or for documentation. If it is for documentation, then as my learned friends with thesauri have shown, there does not appear to be a good word for it. In the 2e documentation (docclass.dtx, features.tex) I think we used `class or package file' to denote the concept. Not exactly snappy, but accurate, and conveys the meaning of `class or package file' rather well :-) David