Samples of Problems
*******************

The email I sent to bug-texinfo described 7 problems.  Karl asked for a document to demonstrate the problems.  Here it is.

"Active" characters in PDF Bookmarks
************************************

When a PDF file is generated with pdftex, the bookmark for this chapter will show something ugly for the double quotes used in the title of this chapter.  I saw a GNU document with this problem, but I don't remember which one it was.  As described in a previous message, there are other characters with similar problems.  The plus character is especially important because it's used in the GNU binutils documentation.

Nested var and code formats
***************************

A lot of GNU manuals nest formats when describing things like command-line options with variables.  For example, --option=VALUE.  The default texinfo behavior is that var selects the same font regardless of whether it is nested inside a code format or not.  I think it looks much better to use the ttsl font when var is nested inside a code format.  (It isn't so bad using the default fonts, but I'm using Helvetica for the main font and Courier for the code font and the italic Helvetica used for the var format doesn't go well with Courier.  I can set the ttsl font to italic Courier but it doesn't get used without my patch.)

Spacing after a heading
***********************

My modified version of texinfo.tex changes the smallbook format to set parskip to 10pt plus 1pt instead of the default 2pt plus 1pt.  That should be OK, shouldn't it?  It exposes the problem illustrated below.

A Section heading
=================

     Here is an ``environment''.

The vertical spacing between the section heading and the preceding environment is too small.  This is due to the conditional that was added to aboveenvbreak.

Line Spacing in Small Examples
******************************

     The singlespace macro fixes the line spacing to 12.5 pts
     which is too big in a ``small'' environment.
     The smallerfonts macro sets the spacing to 9.5 pts but that gets
     overridden by the singlespace value.

     This ends up looking like it is double-spaced.

Definition types in the margin
******************************

The deftypemargin value is no longer used to control where the ``type'' is placed.  The smallbook format sets deftypemargin to zero but it has no effect.  For example:

 -- Variable: typename variablename
     Variablename is a sample variable.

The ``Variable'' text should not stick out into the right margin.

Need to allow page breaks in deffnx macro
*****************************************

The following is copied from the GNU BFD documentation.  It won't usually fit on one page and the deffnx macro doesn't allow a page break.

 -- BFD_RELOC_IA64_IMM14:
 -- BFD_RELOC_IA64_IMM22:
 -- BFD_RELOC_IA64_IMM64:
 -- BFD_RELOC_IA64_DIR32MSB:
 -- BFD_RELOC_IA64_DIR32LSB:
 -- BFD_RELOC_IA64_DIR64MSB:
 -- BFD_RELOC_IA64_DIR64LSB:
 -- BFD_RELOC_IA64_GPREL22:
 -- BFD_RELOC_IA64_GPREL64I:
 -- BFD_RELOC_IA64_GPREL32MSB:
 -- BFD_RELOC_IA64_GPREL32LSB:
 -- BFD_RELOC_IA64_GPREL64MSB:
 -- BFD_RELOC_IA64_GPREL64LSB:
 -- BFD_RELOC_IA64_LTOFF22:
 -- BFD_RELOC_IA64_LTOFF64I:
 -- BFD_RELOC_IA64_PLTOFF22:
 -- BFD_RELOC_IA64_PLTOFF64I:
 -- BFD_RELOC_IA64_PLTOFF64MSB:
 -- BFD_RELOC_IA64_PLTOFF64LSB:
 -- BFD_RELOC_IA64_FPTR64I:
 -- BFD_RELOC_IA64_FPTR32MSB:
 -- BFD_RELOC_IA64_FPTR32LSB:
 -- BFD_RELOC_IA64_FPTR64MSB:
 -- BFD_RELOC_IA64_FPTR64LSB:
 -- BFD_RELOC_IA64_PCREL21B:
 -- BFD_RELOC_IA64_PCREL21BI:
 -- BFD_RELOC_IA64_PCREL21M:
 -- BFD_RELOC_IA64_PCREL21F:
 -- BFD_RELOC_IA64_PCREL22:
 -- BFD_RELOC_IA64_PCREL60B:
 -- BFD_RELOC_IA64_PCREL64I:
 -- BFD_RELOC_IA64_PCREL32MSB:
 -- BFD_RELOC_IA64_PCREL32LSB:
 -- BFD_RELOC_IA64_PCREL64MSB:
 -- BFD_RELOC_IA64_PCREL64LSB:
 -- BFD_RELOC_IA64_LTOFF_FPTR22:
 -- BFD_RELOC_IA64_LTOFF_FPTR64I:
 -- BFD_RELOC_IA64_LTOFF_FPTR64MSB:
 -- BFD_RELOC_IA64_LTOFF_FPTR64LSB:
 -- BFD_RELOC_IA64_SEGREL32MSB:
 -- BFD_RELOC_IA64_SEGREL32LSB:
 -- BFD_RELOC_IA64_SEGREL64MSB:
 -- BFD_RELOC_IA64_SEGREL64LSB:
 -- BFD_RELOC_IA64_SECREL32MSB:
 -- BFD_RELOC_IA64_SECREL32LSB:
 -- BFD_RELOC_IA64_SECREL64MSB:
 -- BFD_RELOC_IA64_SECREL64LSB:
 -- BFD_RELOC_IA64_REL32MSB:
 -- BFD_RELOC_IA64_REL32LSB:
 -- BFD_RELOC_IA64_REL64MSB:
 -- BFD_RELOC_IA64_REL64LSB:
 -- BFD_RELOC_IA64_LTV32MSB:
 -- BFD_RELOC_IA64_LTV32LSB:
 -- BFD_RELOC_IA64_LTV64MSB:
 -- BFD_RELOC_IA64_LTV64LSB:
 -- BFD_RELOC_IA64_IPLTMSB:
 -- BFD_RELOC_IA64_IPLTLSB:
 -- BFD_RELOC_IA64_COPY:
 -- BFD_RELOC_IA64_TPREL22:
 -- BFD_RELOC_IA64_TPREL64MSB:
 -- BFD_RELOC_IA64_TPREL64LSB:
 -- BFD_RELOC_IA64_LTOFF_TP22:
 -- BFD_RELOC_IA64_LTOFF22X:
 -- BFD_RELOC_IA64_LDXMOV:
     Intel IA64 Relocations.

Unexpected cross reference behavior
***********************************

I think my problem with cross references was due to confusion on my part.  However, my comment about xref-automatic-section-title not being documented still applies.  Since I just discovered it in the source, I don't feel qualified to write a description of it, but it might be nice to document it.