X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1150" "Wed" "3" "November" "93" "15:41:04" "CET" "Michael Downes" "MJD@MATH.AMS.ORG" nil "31" "$({\\it colon}," "^Date:" nil nil "11"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA17177; Wed, 3 Nov 93 15:42:42 +0100 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 AA24025; Wed, 3 Nov 93 15:42:39 +0100 Message-Id: <9311031442.AA24025@sc.ZIB-Berlin.DE> Received: from DHDURZ1 by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with BSMTP id 1613; Wed, 03 Nov 93 15:41:27 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 6463; Wed, 03 Nov 93 15:41:22 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 6461; Wed, 03 Nov 93 15:41:19 CET Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <01H4VG243B52O2J6MW@MATH.AMS.ORG> Date: Wed, 3 Nov 93 15:41:04 CET From: Michael Downes Sender: Mailing list for the LaTeX3 project To: Multiple Recipients of Subject: $({\it colon}, Status: R X-Status: X-Keywords: X-UID: 1074 Joachim wrote: > We have hundreds of long-living documents that use constructs like > > $({\it colon}, {\it space})$ > > all over the place. If they won't work with a new system, I won't > switch. And I will recommend the same action to _everybody_ in a > similar situation. I'm curious about one part you didn't mention: Why isn't there higher-level markup in those hundreds of documents like \syntax{\character{colon}, \character{space}} That would not eliminate the problem of incompatibility if \it can no longer work in math, but it would concentrate the points of change to a much smaller locus, which is useful in many ways beyond just dealing with LaTeX upgrade changes. (I know I'm only repeating here an obvious and well-known to you principle---but that's why I'm curious about the history of those documents.) Also, if your documents started with a (self-documenting) command such as \TeXformat{LaTeX}{2.09}{} it would be easier to preserve compatibility. But the \TeXformat command would have to be recognized by the format file, of course. Michael Downes mjd@math.ams.org (Internet)