X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2989" "Fri" "28" "January" "1994" "17:04:56" "GMT" "David Rhead" "David_Rhead@VME.CCC.NOTTINGHAM.AC.UK" "<199401281711.AA17404@mail.cs.tu-berlin.de>" "54" "Form and content: liaise with publishers" "^Date:" nil nil "1" "1994012817:04:56" "Form and content: liaise with publishers" (number " " mark " David Rhead Jan 28 54/2989 " thread-indent "\"Form and content: liaise with publishers\"\n") nil]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA16305; Fri, 28 Jan 94 18:13:35 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA12564; Fri, 28 Jan 94 18:11:34 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA17404 (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 18:11:31 +0100 Message-Id: <199401281711.AA17404@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 4225; Fri, 28 Jan 94 18:11:30 +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 4223; Fri, 28 Jan 1994 18:11:30 +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 6473; Fri, 28 Jan 1994 18:11:03 +0000 Reply-To: Mailing list for the LaTeX3 project Date: Fri, 28 Jan 1994 17:04:56 GMT From: David Rhead Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Form and content: liaise with publishers Status: R X-Status: X-Keywords: X-UID: 1351 > Suppose I am undecided about whether to send a paper to journal X or > Y, where X and Y have different macros. While authors such as Mike Piff may, in the short term, have to circumvent the incompatibilities between different journal-editor's perceptions of structure, isn't the long-term solution to: * COMPLAIN TO THE JOURNAL-EDITORS that they are making you go through these contortions. Then, with a bit of luck (perhaps with the journal-editors realising that it's in their self-interest for them to be able to use each other's TeX macros for production purposes), ... * the journal-editors will talk to each other and decide that their structures aren't (or needn't be) all that different from each other. Hence ... * In the long-term the structures should converge (or at least there should be large common subsets). E.g., 400 biomedical journals have a common set of "instructions for authors". If a medic has a paper rejected by one of the group, s/he can submit it ABSOLUTELY UNCHANGED to any of the other 399. See, for example, British Medical Journal, New England Journal of Medicine, or any other journal in the "Vancouver group". (OK, they're submitting "typed manuscripts", not .tex files. But the editors did meet -- in Vancouver, hence the name of the group -- and solve the medic's version of Mike's problem.) If hundreds of biomedical editors can converge on a common view of "the structure of an article", WHY CAN'T THE MATHEMATICS EDITORS ALSO CONVERGE on a common view? In fact, I'd guess that: * there is already much common ground between mathematics editors about structure. I'd guess that this common view goes something like "Generally that article structure is OK, although it lacks stuff for front-matter. The AMSLaTeX stuff is pretty good as a bolt-on goodie." * problems can come if one journal opts for plain, and another for LaTeX. E.g., physicists may not be able to submit the same .tex file to the Institute of Physics as to Elsevier, because the former uses plain and the latter uses LaTeX. * the LaTeX3 project could build on the existing common ground by involving such editors in the "definition of the LaTeX3 article structure". E.g., if the LaTeX3 team could liase with the AMS, Elsevier and Springer (people from the first two are already on lists such as this, Springer are at Heidelberg whuch isn't far from Frank at Mainz), I'd guess that a structure-definition could be arrived at that would satisfy other publishers too. At this stage Mike's problem would be a non-problem. To summarize, I'd suggest that: * Mike complains to his target journals about any unnecessary incompatibility * the LaTeX3 project liaises with publishers, with a view to getting agreement about the structures that their articles have in common. David Rhead