X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1210" "Wed" "26" "January" "1994" "12:19:47" "-0500" "Denys Duchier" "dduchier@csi.uottawa.ca" "<199401261721.AA11003@mail.cs.tu-berlin.de>" "29" "Re: Mapping a structure onto a design" "^Date:" nil nil "1" "1994012617:19:47" "Mapping a structure onto a design" (number " " mark " Denys Duchier Jan 26 29/1210 " thread-indent "\"Re: Mapping a structure onto a design\"\n") "<9401261653.AA25904@csi.UOttawa.CA>"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA10086; Wed, 26 Jan 94 18:22:22 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA28341; Wed, 26 Jan 94 18:21:18 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA11003 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Wed, 26 Jan 1994 18:21:16 +0100 Message-Id: <199401261721.AA11003@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 3918; Wed, 26 Jan 94 18:21:17 +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 3917; Wed, 26 Jan 1994 18:21:17 +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 1277; Wed, 26 Jan 1994 18:20:47 +0000 Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <9401261653.AA25904@csi.UOttawa.CA> Date: Wed, 26 Jan 1994 12:19:47 -0500 From: Denys Duchier Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Mapping a structure onto a design Status: R X-Status: X-Keywords: X-UID: 1313 Charles Wells writes: > David Rhead's suggestion that we separate structure and design > and have commands such as > > \mapping{structure}{design} > [...] > in Latex3 strikes me as exactly the right thing to do. However, > one problem that someone else in this discussion mentioned will > still occur: What happens if you fine-tune the article for the > A4 style if someone else maps the article structure > to the US default in printing out a copy that was emailed or > retrieved by FTP. One kind of fine-tuning is to insert a > pagebreak at a certain spot. That could cause a page with only > a few lines in another design. A long time ago, Frank suggested something along the lines of "explicitly labeled visual formatting commands". E.g.: \VisualFormattingCommand [a4] {\pagebreak} Such a command would only take effect when its label (here a4) has been included in a list of active labels. Thus, it would be possible to fine-tune the same document for a variety of situations, and only activate those labels that are relevant to your specific requirements. I don't know if Frank continues to stand by that proposal, but it still makes (practical) sense to me. --Denys