About
Console app and Python API for automated preparation of your LaTeX paper for submission in PLOS journals.
Please cite this project in your papers:
@misc{latex2plos,
title={{latex2plos public code repository}},
author={Mari{\'c}, Petar},
year={2019},
url={https://github.com/petarmaric/latex2plos},
}
Major features
Multiple LaTeX files workflow
If your paper is organized into multiple .tex files, latex2plos will combine them into a single, cohesive .tex file.
\verbatiminput
Transforms a \verbatiminput file inclusion into its equivalent \begin{verbatim}...\end{verbatim} call.
\bibliography
Transforms a \bibliography file inclusion into its equivalent \begin{thebibliography}...\end{thebibliography} call.
This is done as PLOS does not allow submission of BiBTeX databases, and instead requires the reference information to be embedded in the paper directly, as per PLOS LaTeX guidelines.
\lstinputlisting
Copies over the files referenced by \lstinputlisting into the papers export directory.
\includegraphics
Copies over the figures referenced by \includegraphics into the papers export directory. It will also transform all figures into the TIFF image format (LZW compression, at 300 dpi) and remove/comment-out them from the papers exported PDF, as per PLOS LaTeX guidelines and figures guidelines.
Examples
An example paper, based on the PLOS LaTeX template, has been provided in the template4plos repository to verify the latex2plos features listed above.
Installation
To install latex2plos run:
$ pip install latex2plos
Console app usage
Quick start:
$ latex2plos <filename>
Show help:
$ latex2plos --help
Python API usage
Quick start:
>>> import logging
>>> logging.basicConfig(level=logging.DEBUG, format="[%(levelname)s] %(message)s")
>>> from latex2plos.main import latex2plos
>>> latex2plos('paper.tex')
Contribute
If you find any bugs, or wish to propose new features please let us know.
If you’d like to contribute, simply fork the repository, commit your changes and send a pull request. Make sure you add yourself to AUTHORS.
Metadata
Release files for latex2plos 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| latex2plos-1.0.2.tar.gz | 7.3 kB | Without provenance | Details for latex2plos-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| latex2plos-1.0.2-py2-none-any.whl | Python 2 | none | any | Details for latex2plos-1.0.2-py2-none-any.whl |
Total release size: 17.4 kB
Release files / latex2plos-1.0.2.tar.gz
| Download URL | latex2plos-1.0.2.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d95d54db434799e7397ef4025768e42379eeedfba2b8fd237b42b032f845690
|
|
BLAKE2b-256 checksum How to use checksums |
3791841e632599da46300f7502c040d291ca2c5c7a03b5edb39390de30a1dd21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Release files / latex2plos-1.0.2-py2-none-any.whl
| Download URL | latex2plos-1.0.2-py2-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
0ebac1b6001dd88ebcd921a88ed4c4798db823f8a1598bcda4a7ca862339dae3
|
|
BLAKE2b-256 checksum How to use checksums |
a79c8779e513963c9c1ed2f687f48fcfc35d9bfab3885878c3e503b0225e0bde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Security for latex2plos 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.