Documentation compiler: Difference between revisions
Jump to navigation
Jump to search
(initial page) |
m (→Features: fixed dead link) |
||
| Line 21: | Line 21: | ||
The Documentation compiler takes Flightgear data and render a pdf file. It currently handles only aircraft data, but different other things have been suggested. | The Documentation compiler takes Flightgear data and render a pdf file. It currently handles only aircraft data, but different other things have been suggested. | ||
* It takes the [[ | * It takes the aircrafts [[Aircraft Checklists|checklists]] and outputs them to LaTeX | ||
* It takes the extra LaTeX data in the Docs/ subdirectory of the aircraft and puts it before the checklists. | * It takes the extra LaTeX data in the Docs/ subdirectory of the aircraft and puts it before the checklists. | ||
* It takes the thumbnail of the aircraft for using it on the titlepage of the documentation. | * It takes the thumbnail of the aircraft for using it on the titlepage of the documentation. | ||
Revision as of 17:31, 16 January 2015
| Developed by | Ruben De Smet (rubdos) |
|---|---|
| Written in | Python2, pdfLaTeX |
| Development status | Active |
| Type | Documentation generator |
| License | GNU GPL v2 |
| Website | |
The Documentation compiler is a script that reads FlightGear data such as Aircraft checklists and writes out pdf files using pdfLaTeX. It was first announced on the forum.
Features
The Documentation compiler takes Flightgear data and render a pdf file. It currently handles only aircraft data, but different other things have been suggested.
- It takes the aircrafts checklists and outputs them to LaTeX
- It takes the extra LaTeX data in the Docs/ subdirectory of the aircraft and puts it before the checklists.
- It takes the thumbnail of the aircraft for using it on the titlepage of the documentation.
Usage
stub