Convert LaTeX Papers Between Publisher Templates

This skill converts an existing LaTeX academic paper from one publisher's format to another. It handles differences in document classes, margins, bibliography styles, and single-column or double-column structure through a staged extraction, injection, correction, and compilation workflow. Examples of source and destination formats include Springer, IPOL, MDPI, IEEE, and Nature.

The workflow begins by identifying the source LaTeX file and target template directory. It then assesses how the paper's layout maps to the destination, including column structure and bibliography requirements. A Python extraction script parses core text blocks with regular expressions, combines the target preamble with the extracted body and backmatter, and writes a new file into an output directory. The skill favors this repeatable script over manually copying large amounts of LaTeX.

Use it when a user wants to submit an existing paper in a different journal format, provides a .tex file and new template directory, or requests a named format conversion. Its scope is transferring an existing manuscript into the destination structure and checking that the converted document builds.

When the source and target differ substantially, structural choices need clarification. For example, the workflow should not silently decide how to combine abstract and keyword sections. It also cautions against assuming that mathematical packages present in the source are available in the new template. Missing required files, mapping decisions, or success criteria must be resolved before completing the conversion.

Inputs are the source .tex file, the target template, associated graphics, bibliography requirements, and any necessary structural mapping instructions. Outputs include the extraction script and converted LaTeX document in a new output location. Compilation and log inspection establish whether the resulting document is usable in the target environment.

Corrections cover capitalization of mathematical environment names, float placement options supported by the target template, and image paths relative to the converted file. Table handling may change tabular structures to tabularx or use resizing when column width changes. The workflow avoids forcing the H float option unless the float package is explicitly loaded.

The build cycle uses pdflatex, bibtex, and pdflatex again, followed by inspection of the log for package conflicts, undefined commands, and compilation halts. Overfull table boxes can require resizing to the destination column width or a layout change. Undefined control sequences trigger a search for the missing package or command rather than treating a generated file as a successful conversion.

The skill uses Python for extraction and transformation, LaTeX templates for document structure, pdflatex and bibtex for compilation, and grep or rg for log investigation. A source correction example changes a table environment to:

\begin{tabularx}{\textwidth}

The destination may require packages such as amsmath, float, or table-layout support. Overleaf LaTeX documentation is provided as a reference for resolving formatting questions.

It serves people preparing an existing academic manuscript for a different publisher or journal template. It is particularly relevant when layout and package differences make a straightforward change of document class insufficient.