BuildPDFs
Build PDFs
You can build:
- non-localized pdf
- localized pdfs (if certain conditions are met)
Note: Localization is a moving target. The instructions are for trunk branch 59 (or thereabouts). Localization does not include images (screenshots and etc.) (yet).
What is a Localized PDF?
At this time, it is a pdf built from:
The source tex file (main.tex)
- With translations from the target lingua's po file (if any -- that is, the lingua-specific po file can contain zero or more translated messages, and whatever is present and matches the source file string ("message") is used).
Note: Updating the pot file and po files from main.tex is done manually on an as needed basis by maintainers.
What is a non-Localized PDF?
It is a pdf built from the the source tex file with no translations applied.
Caveat
The toolchain does not presently support all linguas (also called "locales"), notably (some) non-Latin ones such as Chinese.
Build Non-Localized PDF
Just run make in the root directory, as in:
make
This produces main.pdf.
Build Localized PDF(s)
Requirements
LINGUAS file in root directory must contain the target locale code.
Note: For clarity, let's keep this with one locale per line and in alphabetical order.
po/ must contain a po file for the target locale code.
Build All Target Lingua PDFs
Build PDFs for all configured target locales as follows.
- Be in trunk's root directory
- Create all PDFs:
./lang_pdfs
This generates pdf files for each (valid and configured) lingua in LINGUAS file, named as follows: main-<lingua>.pdf
For example, the generated French pdf filename is: main-fr.pdf (because the LINGUAS file contians "fr" and the po/fr.po exists).
And the generated Spanish pdf filename is: main-es.pdf.
Build A Single Lingua PDF
In this case, we execute make and also specify the make target (langpdf). We also must pass a LANG=<lingua> argument to specify the language we want.
For example, to build a Spanish pdf:
make langpdf LANG=es
This generates: main-es.pdf