A short introduction to writing EOATeX

The core of our publishing strategy is a canonical format with a restricted number of LaTeX commands covering all the necessary features of scientific texts. To fulfill these requirements, it is imperative that certain basic rules are followed so that the authors' texts can easily be converted into the various publishing formats: HTML, epub for ebook readers, and PDF for the free download of texts.

Prerequisites & Typesetting

In general, the implemented procedure is independent of any computer platform, editor and program. The only prerequisite is that the authors dispose of a basic LaTeX environment, as is available for all commonly used operating systems. We use XeLaTeX (which is part of the standard distribution of TeX) instead of pdflatex or latex. This enables us to type Unicode (UTF-8) and avoid the coding of non-ASCII-characters. This applies in particular to non-Latin scripts such as Classical Greek or Chinese. Furthermore, we use BibLaTeX and Biber instead of BibTeX. This enables us to accurately typeset bibliographies that include non-Latin scripts.

Please note: This procedure requires the configuration of most editors (such as TeXShop, TeXWorks, BibDesk and JabRef). In general, you must use the command xelatex rather than pdflatex or latex. In addition, the command biber has to be used instead of bibtex. Typesetting the publication therefore requires the following commands:

  1. xelatex Main_TeX_File
  2. biber Main_TeX_File
  3. xelatex Main_TeX_File

The command makeindex is not used. The index is generated using the package 'imakeidx' which is included in the preamble.

The current distribution of TeX (2013) is used for the time being. For Mac and Windows users, this is combined with a convenient working environment that runs on Mac systems OS X 10.6 or higher, or Windows Vista and later.

Setting up a project

All TeX files (including BibTeX files) should be placed in one single folder. Illustrations and graphics are best stored jointly in a subfolder labeled 'Images.' If illustrations and graphics are placed in a subfolder, the path has to be made explicit in the TeX file:


File and directory names must begin with a letter and not include blanks, umlauts or other special characters (except hyphens and underscores).

The character encoding of the LaTeX file should always be UTF-8. Line breaks should be simple line feeds (LF) as is customary in Unix. This may necessitate a change in the standard settings of the editor.

The cited literature must be entered into a bibliographic database (e.g. BibDesk).

Each project consists of at least three files:

  1. The pre_eoa.tex file contains the preferences, macros and packages defined for the purpose of the project and the text file. Generally, the preamble does not need to be changed by the authors. Individual requirements should be discussed with the Development Team.

  2. The biblio.bib file exported from the bibliographic database.

  3. The main file containing the text written by the author. In the case of edited books, this file may be divided into individual chapters. In order to generate a complete table of contents, the chapter titles and the names of the authors should be kept in the main file. The chapter files are inserted into the main file with the \input{…} command.

Each main file begins with the commands


The purpose of the first line is to embed the macros and commands that are defined in the preamble. The command \EOAbibliographytype in the second line defines what kind of bibliography is being created. Use {monograph} for one large bibliography at the end of the publication or {anthology} for one bibliography at the end of each chapter. The command \EOAseries may contain one keyword (Studies, Sources, Proceedings or Textbooks). It defines the dimensions of the book and may alter various options. The command \EOAbibliographydatabase refers to the file containing the bibliographic database. In the example above, the command refers to the file biblio.bib.

The main text ends with the command


Rules for authors

Please note that self-defined LaTeX-Macros are not supported. The special LaTeX commands defined for this system ensure maximum consistency and convertibility. Without this restriction, it would be impossible to convert the publications into ePub and HTML. The list of authorized commands is available in a separate document.