.tex<\/code>). For books in Microsoft Word (.doc<\/code>) or Libre Office (.odt<\/code>) format, we offer a webservice<\/a> to generate an initial LaTeX version. After the final editing and polishing steps, the heavy lifting to produce a PDF document from the LaTeX source is done by xelatex<\/code>. So if we include the optional preprocessing stages in the picture, the current production pipeline can be represented as follows:<\/p>\n![\"Current](\"https:\/\/userblogs.fu-berlin.de\/langsci-press\/files\/2015\/03\/conversion-current-300x121.png\")
<\/a><\/p>\nWe are currently working on substituting that with the following conversion network:<\/p>\n
![\"Planned](\"https:\/\/userblogs.fu-berlin.de\/langsci-press\/files\/2015\/03\/conversion-planned-300x112.png\")
<\/a><\/p>\nOnce this is in place, Language Science Press will be able to offer every book in three main output formats:<\/p>\n
\n- PDF: for a classic page-based presentation of the content that matches the printed book<\/li>\n
- HTML: for reading in a webbrowser and for linkable content (making it easy to refer to a specific paragraph or example sentence in a LangSci book with a link)<\/li>\n
- EPUB: for reading on an e-book reader<\/a> or on other devices with appropriate apps (like iBooks, FBReader, etc.)<\/li>\n<\/ul>\n
Additionally, there will be a structured representation of the book content in XML format. This can be used to access pieces of information in a standardized machine-readable format, e.g. to extract linguistic example sentences or syntactic tree structures. The XML format also plays an important role as an intermediate step for producing HTML and EPUB versions of the book.<\/p>\n
We are also planning to use the HTML version of books in a pre-publication stage with Annotator<\/a> as an easy way for reviewers and proofreaders to provide feedback or add comments at specific positions in the document.<\/p>\nWhile there are many existing tools to convert LaTeX documents into other formats (e.g. pandoc<\/a>, plasTeX<\/a>, HeVeA<\/a>, tex4ht<\/a>), none of them is capable of handling documents with typical linguistic content in an entirely satisfactory way. In particular, we want to make sure that glossed example sentences, syntax trees, attribute-value matrices and other data types commonly found in linguistic writing are automatically handled correctly. That’s why we are developing additional conversion tools, specifically designed to handle these cases. In particular, in the past few months we have been working on a LaTeX parser<\/a> that will serve as the basis for extracting custom data structures from LangSci books, like glossed example sentences or syntactic trees. Since the parser is written in Haskell<\/a>, it is easy to interface with the universal markup converter pandoc<\/a>, which already provides excellent conversion routines to HTML and EPUB, among many other formats.<\/p>\nIn principle, it would be desirable to integrate our parsing extensions directly into pandoc, but since pandoc aims to support an impressive list of input and output formats and is designed for a wide range of use cases, its internal data structures are less flexible than those of our LangSci-specific LaTeX-only reader. However, we already started to contribute code to pandoc and are planning to keep a close relationship to its development. The exact document representation for LangSci books is still in the design process, but we intend to provide a direct interface to pandoc’s internal types which would massively increase the list of input and output formats that Language Science Press could support. Still, our main focus for the next months is on a proper mapping of linguistic data structures to HTML and EPUB. As our toolchain becomes ready for general use, we will announce its availability under an open license in a future blogpost.<\/p>\n
Some parts of this conversion pipeline are already working. For example, we have used an early version of the converter to extract XML representations of linguistic example sentences from the LangSci books published so far. These files can be accessed here<\/a>.<\/p>\n