<refentry xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:src="http://nwalsh.com/xmlns/litprog/fragment" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="5.0" xml:id="tex.math.in.alt"> <refmeta> <refentrytitle>tex.math.in.alt</refentrytitle> <refmiscinfo class="other" otherclass="datatype">list</refmiscinfo> <refmiscinfo class="other" otherclass="value">plain</refmiscinfo> <refmiscinfo class="other" otherclass="value">latex</refmiscinfo> </refmeta> <refnamediv> <refname>tex.math.in.alt</refname> <refpurpose>TeX notation used for equations</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="tex.math.in.alt.frag"> <xsl:param name="tex.math.in.alt"></xsl:param> </src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>If you want type math directly in TeX notation in equations, this parameter specifies notation used. Currently are supported two values -- <literal>plain</literal> and <literal>latex</literal>. Empty value means that you are not using TeX math at all.</para> <para>Preferred way for including TeX alternative of math is inside of <tag>textobject</tag> element. Eg.:</para> <programlisting><inlineequation> <inlinemediaobject> <imageobject> <imagedata fileref="eq1.gif"/> </imageobject> <textobject><phrase>E=mc squared</phrase></textobject> <textobject role="tex"><phrase>E=mc^2</phrase></textobject> </inlinemediaobject> </inlineequation></programlisting> <para>If you are using <tag>graphic</tag> element, you can store TeX inside <tag>alt</tag> element:</para> <programlisting><inlineequation> <alt role="tex">a^2+b^2=c^2</alt> <graphic fileref="a2b2c2.gif"/> </inlineequation></programlisting> <para>If you want use this feature, you should process your FO with PassiveTeX, which only supports TeX math notation. When calling stylsheet, don't forget to specify also passivetex.extensions=1.</para> <para>If you want equations in HTML, just process generated file <filename>tex-math-equations.tex</filename> by TeX or LaTeX. Then run dvi2bitmap program on result DVI file. You will get images for equations in your document.</para> <warning> <para>This feature is useful for print/PDF output only if you use the obsolete and now unsupported PassiveTeX XSL-FO engine.</para> </warning> </refsection> <refsection><info><title>Related Parameters</title></info> <para><parameter>tex.math.delims</parameter>, <parameter>passivetex.extensions</parameter>, <parameter>tex.math.file</parameter></para> </refsection> </refentry>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 12728 | eedwards |
Upgrade ANT doc build infrastructure to assemble PDFs: - remove non-namespaced DocBook source and add namespaced DocBook source. - add Apache FOP 1.1 - copy fonts, images, XSL into _build, establishing new asset structure. The original structure remains until all guides using it can be upgraded, and several other issues can be resolved. - updated build.xml to allow for per-target build properties. - upgraded the P4SAG to use the new infrastructure. - tweaked admonition presentation in PDFs to remove admonition graphics, and resemble closely the presentation used in the new HTML layout, including the same colors. With these changes, building PDFs involves using a shell, navigating into the guide's directory (just P4SAG for now), and executing "ant pdf". Issues still to be resolved: - PDF generation encounters several warnings about missing fonts (bold versions of Symbol and ZapfDingbats), and a couple of locations where the page content exceeds the defined content area. - Due to issues within Apache FOP, PDF generation emits a substantial amount of output that is not easily suppressed without losing important warning information. - Apache FOP's interface to ANT does not expose a way to set the font base directory. The current configuration does work under Mac OSX, but further testing on Windows will need to be done to determine if the relative paths defined continue to work. The workaround is for Windows users to customize the fop-config.xml to provide absolute system paths to the required fonts. - HTML generation needs further browser testing, and exhibits broken navigation on iOS browsers within the TOC sidebar. - A number of PDF and HTML presentation tweaks still need to be made, for example: sidebars, gui* DocBook tags, whitespace, section separation, etc. |