LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Wolfgang May <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Fri, 5 Dec 1997 14:13:14 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (51 lines)
On Thu, 4 Dec 1997 09:37:47 GMT Phillip Helbig said:

>One leading scientific journal is exemplary in REQUIRING 2e instead of
>2.09 but prohibits the use of private macros (even if defined in the
>preamble with no name clashes, redefinitions etc of standard commands or
>ones from the special journal .cls),
[]
>Is this something one must be prepared to accept in the long run?


Sebastian Rahtz writes:

 >  > while the author
 >  > usually provides an almost completely typeset manuscript,
 >  > publishers should _gladly_ accept anything the author is prepared to
 >  > deliver instead of imposing specific requirements.
 >
 > the problem is that the author "provides an almost completely
 > *non-portable* typeset manuscript". (my **).  sadly, this is not what
 > is needed in the world of electronic publishing. the cost of cleaning
 > up that "typeset manuscript" is really very high.
 >
 > yes, of course publishers screw you. its a bargain, we screw you, you
 > (the academic world) get to play games about tenure based on
 > publication rate. if you drop that absurdity, you can free yourselves
 > from the Faustian pact with the publishers.

For *one* paper, the way described by P.H. above works well. I suppose
that the main problem is that in most journals there are several
papers, so, if each of them has no clashes with latex2e and the
journal styles, there is also the problem of clashes *between* the
papers.

One possibility could be that every author guarantees that he only
defines macros which begin with an identifier which is unlikely
to clash with *any* other paper, e.g. names like

\phelbigXbla{...} or
\srahtzXblubb{...}
etc .pp.

Perhaps this can be a feasible compromise ?

Wolfgang

--------------------------------------------------------------------
Wolfgang May             E-mail: [log in to unmask]
Universitaet Freiburg    http://www.informatik.uni-freiburg.de/~may/
Institut fuer Informatik D-79110 Freiburg / Germany
Lehrstuhl fuer Datenbanken und Informationssysteme

ATOM RSS1 RSS2