Login

LaTeX template & style

Style package

Manuscripts should be prepared in LaTeX preferably in one of the following ways:

Please note that the TeXLive version may not be in line with your preferred editor version. In order to know which TeX version is available in your system, you can type latex --version in your terminal.

Note: the legacy style class is derived from our other journal style packages, and is no longer mantained, it is provided only for compatibility reasons.

LaTeX engine and package settings

  • The default engine for a proper compilation is pdflatex.
  • In order to submit to JQuant please make sure that the journal setting is properly set: journal=jquant in the package options for the current package, see the documentation/examples.

Front page

Note on long author lists: If the front matter exceeds 2 pages, the complete author list will be moved to the end of the manuscript during production. This is meant to improve readability and facilitate metadata extraction by indexing services. Authors who require the full list on the first page for institutional or technical reasons should contact the Editorial Office via their manuscript web page.

  • Title, authors (first and family names), affiliations and e-mail addresses must be complete and clearly indicated. We recommend the use of the ASCII character set in order to improve compatibility with other systems.
  • Each author must be associated with at least one affiliation, which must contain: Department, University, Address, City (mandatory), Country (mandatory).
  • Each affiliation must be listed separately, i.e. affiliation clusters are not allowed and will be split before publication.
  • The abstract should briefly summarize the content of the contribution and must fit in the first page. Formulas and/or images should be avoided.

Text and style

  • The text should be organized into numbered sections using standard sectioning macros (e.g. \section, \subsection, \subsubsection, \paragraph). Non-numbered sections should be rendered as \paragraph.
  • Pages must be structured in single-column style.
  • Write your work in standard, comprehensible English. Conciseness is strongly encouraged, but clarity and consistency are more important. Short and simple words and sentences are helpful for readers. Please keep jargon and acronyms to a minimum. The editors will consider whether the content is of sufficient scientific interest compared to the overall length and may recommend shortening the text.
  • Do not modify template margins, font faces/sizes, or spacings: these will be restored to the publication defaults during typesetting. Mathematical font styles (e.g. \mathcal, \mathfrak) are also subject to this rule and must not be redefined.
  • All material (text, equations, figures, etc.) must fit within the text margins. Avoid overfull lines and boxes. Be aware that LaTeX flags these as warnings when content extends past the margin boundary.
  • Packages containing mathematical symbols can be added if they do not change the default mathematical font. However, they will be thoroughly checked after acceptance.
  • Please be aware that the journal publication style may require some graphical adaptation of the content during the typesetting phase (e.g. bold text, structured list).
  • Coloured text must be avoided, since it interferes with accessibility. In order to emphasize words or sentences please use italics (not boldface).
  • The source code should be cleaned before the manuscript's acceptance for publication (e.g. no \iffalse, coloured text, strikeout/underlined text, comment blocks). A new version may be required during typesetting in order to comply with this requirement.
  • Please note that any addition/modification which does not comply with the Journal's style will be restored to JQuant's default publication style.
  • Do not modify the provided sty or bst files in any way.

Front page

Note on long author lists: If the front matter exceeds 2 pages, the complete author list will be moved to the end of the manuscript during production. This is meant to improve readability and facilitate metadata extraction by indexing services. Authors who require the full list on the first page for institutional or technical reasons should contact the Editorial Office via their manuscript web page.

  • Title, authors (first and family names), affiliations and e-mail addresses must be complete and clearly indicated. We recommend the use of the ASCII character set in order to improve compatibility with other systems.
  • Each author must be associated with at least one affiliation, which must contain: Department, University, Address, City (mandatory), Country (mandatory).
  • Each affiliation must be listed separately, i.e. affiliation clusters are not allowed and will be split before publication.
  • The abstract should briefly summarize the content of the contribution and must fit in the first page. Formulas and/or images should be avoided.

Tables, figures, code listings

  • Tables and figures should be on top of the page. They must always be referenced in the text and must have a caption describing their contents.
  • Do not use wrapped figures and tables (i.e. wrapfig).
  • For figures or tables that have already been published elsewhere, a permission from the copyright owner(s) must be obtained before incorporating in your article.
  • For figures: the minimum resolution requested for figures is at least 300dpi, meanwhile vector images containing fonts must have the fonts embedded in the files. Accepted formats are pdf, png and eps, other formats should be avoided and may result in a loss of quality during typesetting. If the provided images do not meet QA standard (e.g. bad scans, hand-drawn figure, fonts not embedded, low quality) a new image meeting specific requirements may be requested.
  • Color accessibility: authors are strongly encouraged to use color-blind-safe palettes in figures. Where possible, supplement color with additional visual cues such as different line styles or markers. Tools such as ColorBrewer (colorbrewer2.org) can assist in selecting accessible color schemes.
  • For tables: each table should have a top and bottom border, and a heading row describing each column.
  • Our preferred way to include code chunks is listings package (https://ctan.org/pkg/listings).
  • We suggest to provide very large tables and long code listings (spanning more than one page) as Supplementary Material, since this improves readability and accessibility.

Internal referencing

  • When referring to internal material (e.g. figures, tables), please use the expanded name in lowercase form, such as "figure" instead of "fig." or "Figure". The only exception are equations and references, for which the abbreviations "eq./ref." and "eqs./refs." are preferred.
  • Please use dynamic referencing rather than the static one, i.e. "figure~\ref{fig:2}" instead of "figure~2". This improves accessibility and facilitates consultation.
  • Please use numbered sections and ensure that every equation has at least one equation number, as this may be useful for future cross-referencing in subsequent papers.
  • Every figure, table, citation must be referenced in the text.

Math

  • Equations must fit within text margins and their content must be readable.
  • Avoid uncommon symbols, since they may interfere with readers and webpage rendering.
  • Use align instead of eqnarray. Do not use $$...$$ or gather.
  • Equations should be centered and numbered.
  • Equations spanning multiple lines should be aligned on the binary relations (e.g. =, >, <). When an expression breaks across lines, place the binary operator (+, −, =, etc.) at the beginning of the continuation line, not at the end of the preceding line.
  • Superscript and subscripts should be in roman whenever they contain a word or an abbreviation.

Bibliography

  • JQuant uses the sequential numerical system for references in the text. The sequential numbers occur within square brackets, and the reference list at the end of the manuscript lists the references in numerical order (usually in order of first appearance), not alphabetical.
  • Each item of the bibliography must cite one work only, without any extra text (e.g. "See for example"); articles on the same topic or different volumes of one book, should be referenced by separate bibliography items. If you need to refer to a part of one reference (e.g. "See chapter 5 of..."), please do it inside the text, not in the bibliography ("See chapter 5 of [1]").
  • Each bibliographical item must be properly referenced in the text.
  • References should contain only the data required to clearly identify the cited work ("authors, title, journal data, arXiv, doi" or "webpage"), all provided links and webpages must be publicly accessible.
  • References with "Private communication" and similar ones are discouraged and will be likely removed before publication.
  • References cannot refer to other references in the paper, i.e. no \cite in references.
  • Please note that the bibliography will be processed and formatted again before publication in order to carefully check its contents and apply the publication standard style.
  • The information provided for each reference should be as complete as possible, some examples:
    • Article: author(s), title, journal name, volume, year, page number, arxiv-number. Additional information (erratum, addendum) can be specified too. "M. Anselmino, A. Efremov and E. Leader, The theory and phenomenology of polarized deep inelastic scattering, Phys. Rept. 261 (1995) 1 doi:10.1016/0370-1573/95-900011-5 [Erratum ibid 281 (1997) 399] [hep-ph/9501369]."
    • Book: author(s), title, publisher and year. "R. Penrose and W. Rindler, Spinors and Space-time, Vol. 2: Spinor and twistor methods in space-time geometry, Cambridge University Press, Cambridge U.K. (1986)."
    • Technical report/note: author(s), title, report number. "CMS collaboration, Technical Design Report Vol. 1, CERN-LHCC-2006-001 (2006)."
    • Webpage: title (if any), link, optional date. "JQuant webpage, https://jquant.sissa.it, accessed May 1 (2026)."
    • Proceeding/talk: author(s), title, conference information, year. "HERMES collaboration, F.~Ellinghaus, DVCS at HERMES: Recent Results, in Proceedings of the Workshop on Exclusive Reactions at High Momentum Transfer, Jefferson Lab, Newport News, U.S.A., May (2007)."
    • Software: author, name, link, doi (or similar). “Astropy Collaboration, Astropy: A community Python package for astronomy, v5.3, doi:10.5281/zenodo.XXXXXXX (2023).”
  • JQuant strongly encourages citations to data files and similar supplementary material available in external repositories. Citations should follow the repository style (i.e., the “cite as” notice) and should include persistent identifiers such as DOIs wherever possible.
  • Software and computational tools used in the research should also be cited. A software citation should include the software name, version, author(s), and a persistent identifier such as a DOI (e.g. obtained via Zenodo or the Astrophysics Source Code Library, ASCL).
  • References should be provided in the bibliography environment or in a separate .bbl file; a .bib file is also welcome for cross-checking. See the TeX and LaTeX section for submission requirements regarding these files.
  • Use the jsty3-author.bst style to compile .bib into .bbl files. If you use instead use biber, note that its output can lead to errors during internal checks, bibTeX is strongly preferred. Please note that the output given by the bst file is designed to be processed by our biblbiographical tool and may differ from the style intended for the final publication.
  • The bbl file can be edited manually, if on-point modifications are required. 

TeX and LaTeX

  • Your contribution can be one of the following:
    • a single .tex file
    • a file archive (.zip or .tar.gz)
      If your manuscript includes more than one file, the files will have to be archived. In this case it is essential for the master file to be saved in the root (main) directory, while the other files may be included in subdirectories. Please note that if two or more source files have the same extension (i.e. "abc.tex" and "def.tex"), in making the submission you must specify the master file name together with the extension in the appropriate field, otherwise the submission will fail. The archive should contain only the files necessary for the compilation and the production of the pdf. Other files (cover letters, reply to referee reports, etc.) must not be included since the system would simply ignore them.
  • Manuscripts should be prepared in LaTeX using one of the templates listed at the top of the page, different styles are also accepted, but are inevitably processed more slowly after acceptance.
  • Please use standard packages, the use of legacy/outdated or niche packages is discouraged since it may severely interfere with the publication phase, if this is the case a new version of the paper can be requested in order to safely remove these packages without changing the paper contents.
  • Only the packages needed for an error free compilation should be included, since unnecessary packages can lead to unexpected results.
  • A full TeXLive is instantiated for the JQuant site, so if you are using an unrecognized package, please include it in making the submission.
  • Always consider that the submission can be completed only if the submitted file compiles successfully on the JQuant server.
  • Please include the .bbl file in the submission (or insert it in the main tex file). The .bib file should be also included if available, since it may be useful for double checking references during typesetting.
  • Use of biber bibliographical tool is discouraged, since some data may be tangled up during typesetting.
  • If the document consists of a stand-alone (La)TeX file this can be submitted as is, without compressing it.

Archive preparation (.tar.gz/zip)

  • Put all the files required for a tex compilation (as explained above, please do not include any cover letter or unnecessary/unused files) in a folder.
  • As a best practice, file names should contain only ASCII characters without spaces, dashes or unnecessary dots like (e.g. prefer figure_alpha1_0_value.pdf instead of figure_alpha1.0-value.pdf).
  • Please note that the file names are case sensitive (especially for figures).
  • The main tex file should be in the root directory of the archive.
  • Works can be uploaded as: a single tex file, as a tar.gz, or as a zip file.
  • Some LaTeX packages refer to the main file name explicitly (e.g. tikz with externalize option), please check that all the configurations are not linked to the main file name (bbl excluded), since the main file may be renamed during the process.
  • If you use packages like feynmf that require the use of metafont please include the .pk, .tfm and .t1, .t2, ... files in your archive.
  • If a glossary is required, please also include the .gls file in the archive.

Quick check summary

Front matter

  • Title, all authors, affiliations (with City and Country), and email addresses are complete.
  • Each affiliation is listed separately; affiliation clusters are not allowed.
  • Abstract fits on the first page and contains no formulas or images.

Style

  • Template margins, fonts, and spacings are unmodified.
  • No colored text; emphasis uses italics only.
  • Source code is clean: no \iffalse blocks, no commented-out text, no strikethrough or underlined text.

Figures and tables

  • All figures are vector (with embedded fonts) or raster at ≥ 300 dpi; accepted formats are pdf, png, and eps.
  • All figures and tables have captions and are referenced in the text.
  • Figures use color-blind-safe palettes and/or supplementary visual cues (line styles, markers, hatching).

Equations

  • Use align, not eqnarray, $$...$$, or gather.
  • All displayed equations are numbered and centered.
  • Multi-line equations are aligned on binary relations, with operators at the start of continuation lines.

Bibliography

  • Bibliography is complete; each item cites one work only and is referenced in the text.
  • Software and computational tools are cited with name, version, author(s), and a persistent identifier (DOI).
  • All links are publicly accessible.
  • The .bbl file is included in the submission.

Archive

  • Main .tex file is in the root directory.
  • File names use ASCII characters only, no spaces; names are case-sensitive.
  • Only files required for compilation are included (e.g. images, bib, bbl), i.e. no cover letters, no unused files.
  • Submission compiles successfully with pdflatex.