>>> This appears to me as an additional issue instead a *must do*.
>>> Formatting as pdf (or plain text) an API doc with an OO paradygm
>>> and plenty of links is IMHO meaningless. I give you a personal
>>> advice: don't spend your time in the creation of this kind of
>>> document; what now seems good to you, in the future will show many
>>> unwanted side effects.
>>
>> It's not that I personally like or use documentation in PDF or info
>> format; the choice is not mine. We already build all manuals in
>> all three formats, and some users are accustomed to them. If we
>> change the formatting of the IR, formats other than HTML must be
>> accounted for, either by choosing a presentation scheme that is
>> readable in those formats or by generating conditional Texinfo
>> markup (@ifpdf and similar) so that they will use their own scheme
>> entirely.
>
> If it helps to have a data point, I exclusively use the PDF manuals
> for my reference (apart from searching the code base directly).
And I use almost exclusively the info files with the standard terminal
`info` browser for looking up the Internals Reference.
Werner
