LaTeX
Explanation
The LaTeX Syntax 1.0 renderer produces its LaTeX through a system of templates, and every one of those templates can be overridden. Changing what an export looks like is therefore a matter of supplying your own template, not of patching the renderer.
You rarely drive the renderer yourself: it runs behind the LaTeX Exporter, and what you customize is what comes out of it.
The Template System
Template Mechanism explains how a Block becomes LaTeX: which template is looked up for it, in what order, and how a Block can ask for one by name. Template Script Bindings is the reference for what a template can call once it runs.
Override a Template is the procedure, in a form that survives an upgrade of the extension. Three worked examples sit below it: Customize the Preamble, Render Table Cells in Italic and Wrap Long Table Cells.
Add Support for a Macro gives a macro a LaTeX form of its own.
Extending Without Owning a Template
Extension Points lists the UI extension points the templates expose. They let an extension add to the generated document, a \usepackage line for instance, without taking over the template it adds to.
Export Part of a Page goes the other way: keeping a piece of a page out of the export, decided in the page itself.
The Export Package
An export produces more than one rendered page. Export Package describes what the output filter assembles and how its pieces relate. Customize the Index Template changes the index.tex that ties them together, and Output Filter Parameters is what you need to drive the filter from code rather than from the export form.
Calling the Renderer Directly
Renderer API is the exception: rendering an XDOM as LaTeX yourself, from Java or from Velocity, as a whole document or as a fragment of one.
More
To find more about the current topic, you can search or use the table below and filter the columns to narrow your choices.
