Publishers of journals have a wide range of requirements for the presentation of papers, and while many publishers do accept electronic submissions in (La)TeX, they don't often submit recommended macros to public archives.
Nevertheless, there are considerable numbers of macros of one sort or
another available on CTAN; searching for your journal name in
the CTAN catalogue
may well turn up what you're seeking.
Failing that, you may be well advised to contact the prospective publisher of your paper; many publishers have macros on their own web sites, or otherwise available only upon application.
Check that the publisher is offering you macros suitable to an environment you can use: a few still have no macros for current LaTeX, for example, claiming that LaTeX 2.09 is good enough\dots
Some publishers rekey anything sent them anyway, so that it doesn't really matter what macros you use. Others merely encourage you to use as few extensions of a standard package as possible, so that they will find it easy to transform your paper to their own internal form.
This is a requirement, for example, if one is preparing the proceedings of a conference whose papers were submitted in LaTeX.
There's no canned solution, but Matt Swift's includex and
moredefs packages (both part of the
bundle) offer a possible way forward.
includex enables you to `
\includedoc' complete articles
(in the way that you `
\include' chapter files in an ordinary
report). It doesn't do the whole job for you, though. You need to
analyse the package use of the individual papers, and ensure that a
consistent set is loaded in the preamble of the main report.
Another tedious problem to address is that LaTeX suppresses all
title-related commands after
\maketitle has been used once in a
document: thus you need to define replacements for all of them, for
use in the papers.
More work is plainly needed in this area, but at least a start has been made.
A framework class for Curricula Vitae, provided by Andrej
Brodnik, is available from
The class can be customised both for subject (example class option files are offered for both computer scientists and singers), and for language (both the options provided are available for both English and Slovene). Extensions may be written by creating new class option files, or by using macros defined in the class to define new entry types, etc.