| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
In PDF, DVI, and PostScript files, the contents of the @top
node were being printed. These are intended only for info
and html output formats.
|
| |
|
| |
|
|
|
|
|
| |
See http://www.rtems.org/pipermail/rtems-devel/2013-February/002466.html
for instructions on how to do this.
|
|
|
|
|
|
|
|
|
| |
The 16 bit Object Id image was incorrectly rotated in the manual.
Both the 16 and 32 Object Id bit images had thin borders on the table
and the bottom line was not visible in the PDF. I tinkered with the
original drawings to add a bit more space around the tables and
manually converted the PNG to EPS using Gimp to ensure a controlled
and high quality conversion.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Per a discussion with the GNU Texinfo maintainer Patrice Dumas,
change to generating HTML files per a standard for stable URL
names and easier cross manual referencing.
http://lists.gnu.org/archive/html/help-texinfo/2013-02/msg00002.html
|
|
|
|
|
|
|
|
|
|
|
| |
This was tested with texi2html-1.82-5.1.el6.noarch and
a locally built texinfo 5.0. These are completely different
implementations and require different invocations.
The Makefile dependencies appear to work but are likely not
perfect at this point. The key point is that the autoconf
probe detects which to use and responds accordingly with
preference given to texi2any.
|
|
|
|
|
| |
Texinfo 5.0 is a complete reimplementation and has stricter
interpretations of the texinfo language.
|
| |
|
|
|