• Content of the Manuscript
• LaTeX Class and Files
• Images
• Style
• Layout
• Links
• References
• Abstract
• Capitalization

Quick link: IPOL LaTeX style, example and manual are at
https://tools.ipol.im/wiki/ref/manuscript_guidelines/ipol_latex_class_v0.4.2.zip.

Content of the Manuscript

The submission process is detailed in the IPOL Author Manual. The manuscript of an IPOL article submitted for peer-review should include:

• the list of authors with e-mail address, institution and web page;
• an overview of the algorithm;
• the theoretical background;
• a detailed and accurate description of the algorithm, with pseudo-code and/or block diagram and a short complexity analysis;
• commented examples and counter-examples of resulgts;
• references of printed publications or preprints explaining the algorithm in detail.

This content must be adapted when the article is not about an algorithm (like dataset articles).

The manuscript of an IPOL article accepted by the peer-review and submitted for edition before final publication must be provided as a single archive file (zip, tar/gzip) containing the complete source (LaTeX, BibTeX, and figures) needed to recreate the PDF file accepted in peer-review.

LaTeX Class and Files

Manuscripts submitted for review in IPOL must be provided as PDF files using the IPOL LaTeX style. At this step of the process, only the PDF file is needed, and it can be produced as the authors wish, as long as it conforms to the IPOL layout rules as defined in the IPOL class.

After review and during the editing process at the step 3, the authors must provide the complete LaTeX source, including the LaTeX source (.tex), BibTeX references (.bib), LaTeX class (.cls) and style (.sty) and all the embedded figures. This source will be used to produce the final published PDF version, and must compile with pdfLaTeX.

Images

This LaTeX source will be compiled with pdfLaTex, so EPS files can not be included in the document. Instead, you must use PDF files for vector images (graphs and figures) and PNG or JPEG files for the bitmap images.

• You can convert EPS vector images files to PDF files with the epstopdf tool.
• JPEG is for natural images obtained from digital photography, when visually identical data is sufficient. PNG is for artificial images and when exact pixel values are important.
• If your bitmap images are not in JPEG or PNG format, you can convert them into these file formats with the ImageMagick convert tool.
• If your images are already in JPEG or PNG, do not change their file format.
• Use the highest resolution available for these images; the PDF files distributed as the final published articles will be filtered and downsampled to screen resolution, and the full-resolution data will be available too.

Style

• The manuscript must use correct English and punctuation. Please refer to to manuals of style, grammar and punctuation.
• Every author must provide their first name, last name, email address (a professional address, not gmail/yahoo/etc) and affiliation.
• Do not use sentences like “Try the demo! Try the code!”; this is an academic article, not a commercial.
• If an additional or binary version of the software is provided, it must be clearly mentioned that this is not the reviewed version.
• The origin of any element (image, figure, citation) reused in the article from other sources must mentioned in a “Credits” section at the end of the manuscript, with explicit license information.
• The article title and section titles must use headline-style capitalization (cf. details in the ‘Capitalization’ chapter).
• Do not insert spaces before typographic signs (:;,.). Do insert non-breaking spaces (~ in LaTeX) before references and citations (\ref and \cite).
• Capitalize brand names (Intel Xeon), do not insert the (R) or TM symbols. Write file names in monospace (\texttt{program.c}). Write foreign words in italic, but not common terms (like “de facto” or “vis-à-vis”). Do not italicize latin abbreviations (“i.e.”, “et al.”, …).
• Avoid unnecessary abbreviations (like “Fig.”) in the text. Do not capitalize “Figure”, “Table”, “Equation”, “Algorithm” unless at thebeginning of a sentence.
• Group references together: \cite{foo,bar} instead of \cite{foo}, \cite{bar}.
• Grammatically, reference numbers are treated like footnote numbers: “as shown by Brown [4], [5]; as mentioned earlier [2, 4–7, 9]; Smith [4] and Brown and Jones [5]; Wood et al. [7]”.

Layout

• Do not modify the margins, fonts and page headers defined in the LaTeX class.
• Only keep the standard LaTeX header provided with the ipol LaTeX class. Additional LaTeX packages, if needed, must be distributed with the source of the article (package.sty files).
• Avoid inline tables and images when they are large, use floating environments, with !htbp positioning options (\begin{table}[!htbp], \begin{figure}[!htbp]). Every floating figure and table must have a caption and must also be referenced in the text, independently of their legend, and redundancy of both texts is allowed.
• Avoid internal grids (horizontal and vertical lines) in tables. Generally lines should be only used to separate different parts of a table, to direct the reader’s eye in one direction, or to organize an unusually complex table¹.
• Do not use \include{} statements to split your article into different files, because they insert a page break; use \input{} instead.
• Do not insert manual page breaks (\\, \newline) or vertical space (\vspace{1cm}). The document layout should still be correct with a different page size or font size.
• Do not insert empty lines between text and math if they are in the same paragraph; empty lines may result in misplaced page breaks.
• Do not use absolute dimensions (cm, mm) to resize an image. Instead, express their width and height relatively to the dimensions of a text line: width=0.45\linewidth, height=5em.

Links

Manuscripts must not include direct links to the demo or to the source code files, because these addresses may change. The only link to be used is the LaTeX \ipolLink macro, which will be replaced by the DOI address upon publication. This DOI address will refer to the main web page of the article, where every other component of the article (demo, source code, data) will be available. The \ipolLink macro must not be concatenated with a file name because the link will be invalid once the DOI is used. The only correct way to use it is \url{\ipolLink} or \href{\ipolLink}{the article page}.

References

The articles references must follow the standard rules, with at least: author(s), title, journal/series/volume/editor, and year. Do not use shortened journal titles in the references. These rules also apply to website references, including personal home pages, Wikipedia, etc. Reference presentation rules are complex, see The Chicago Manual of Style or online extracts for details:

• http://www.chicagomanualofstyle.org/tools_citationguide.html
• http://www.lib.sfu.ca/help/writing/chicago-turabian

Journal articles references must mention the DOI if it exists, presented as “http://dx.doi.org/AA.BBBB/CCCCCCC” according to the Crossref DOI Display Guidelines. DOIs provides reliable and permanent links to the officially published version of articles, and they are used by reference management tools and indexing services to automatically collect reference citations from a document. You can search for DOIs using the Crossref Guest Query tool.

Book references must mention the ISBN, presented as “ISBN XXXXXXXXXX”. You can search for ISBNs in ISBNdb or the WorldCat catalog.

Grammatically, reference numbers are treated like footnote numbers: “as shown by Brown [4, 5]; as mentioned earlier [2, 4–7, 9]; Smith [4] and Brown and Jones [5]; Wood et al. [7]”, not like nouns (“we see in [42] that…”, “[23] contains a discussion”). Reference numbers are links to additional information at the end of the document, sentences must still make sense without these links. To help readers recognize references, the first author name should appear in the text. For example,

• “we see in [23] that these parameters…” becomes
  “we see in the original work by Smith et al. [23] that these parameters…”
• “in a recent paper [42] the authors showed that…” becomes
  “Jones and Kato showed in a recent paper [42] that…”
• “[99] has a complete description of this method.” becomes
  “Martin [99] provides a complete descrioption of this method.”

Abstract

The abstract will be reused out of the PDF document: HTML page, article metadata, bibliographic databases. Typography (italic, line breaks, …) will be lost in these contexts, si its use should be minimal in the abstract. Avoid mathematical notations in the abstract, and do not insert references numbers there.

Capitalization

from Turabian, A Manual for Writers, p 314

Headline-style capitalization is intended to distinguish clearly titles from surrounding text. In this style, capitalize the first letter of the first and last words of the title and subtitle and all other words, except as follows:

• Do not capitalize articles (‘a’, ‘an’, ‘the’), coordinating conjunctions (‘and’, ‘but’, ‘or’, ‘nor’, ‘for’, ‘so’, ‘yet’), or the words ‘to’ and ‘as’ unless such a word is the first or last word in the title or subtitle.
• Do not capitalize prepositions (‘of’, ‘in’, ‘at’, ‘above’, ‘under’, and so forth) unless they are emphasized (‘through’ in ‘A River Runs Through It’) or used as adverbs (‘up’ in ‘Look Up’), adjectives (‘on’ in ‘The On Button’), or conjunctions (‘before’ in ‘Look Before You Leap’).
• Do not capitalize the second part (or subsequent parts) of an hyphenated compound unlesss it is a proper noun or adjective.
• Do not capitalize parts of proper nouns that are normally in lowercase (‘van’ in ‘Ludwig van Beethoven’).