I wrote:
>> Table 27.4 is annoying: it could be made to work, just barely, with some
>> hacking of the column widths and a or two. But it's not stable
>> text so I have little faith in the longevity of such a solution,
>> especially if people keep on inventing long wait event names. I also
>>
I wrote:
> Table 27.4 is annoying: it could be made to work, just barely, with some
> hacking of the column widths and a or two. But it's not stable
> text so I have little faith in the longevity of such a solution,
> especially if people keep on inventing long wait event names. I also
> find
There are something like 140 "exceeds the available area" PDF build
warnings that will remain after the catalog-table reformatting I've
proposed nearby. I've looked through these and they fall into
two groups:
1. We have lots of overwidth examples. Using our standard monospaced
font, A4-size
