## 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 >>]

 Subject: Re: private macros and journal .cls From: Phillip Helbig <[log in to unmask]> Reply To: Mailing list for the LaTeX3 project <[log in to unmask]> Date: Fri, 5 Dec 1997 13:43:27 GMT Content-Type: text/plain Parts/Attachments: text/plain (36 lines)
```>  > 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.
>  >
> to be honest, it never occured to me to think about macro name
> clashes; that seems to be the least of the problems. i guess most of
> us work an article at a time anyway.

I had been thinking about individual papers as well, and I don't know to
what extent this is a problem.  In any case, the variants on
\providecommand discussed a while back (in this case if undefined,
define, if defined, override) could solve this problem easily.

> the problem is that few typesetters use LaTeX; so the markup has to be
> converted to some other system (in our case, via SGML). converting
> LaTeX is hard, and hard-pressed workers adopt simplistic
> search-and-replace methods. obviously these fail if there are cutesy
> author-defined macros which affect the whole paper

It seems to me that it is much better for a few people to work hard at
LaTeX to HTML conversion, or whatever is required, rather than making
each author of each paper do a lot of unnecessary work.

--