Doc: fix remaining over-length entries in SQL keywords table.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 12 May 2020 00:03:55 +0000 (20:03 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 12 May 2020 00:03:55 +0000 (20:03 -0400)
commit4d1563717fb1860168a40b852e1d61a33ecdd62f
treed8058fb1b47fcd98b269f33ec939a946f64c9a0f
parent60c90c16c1885bb9aa2047b66f958b865c5d397e
Doc: fix remaining over-length entries in SQL keywords table.

Even after the tweaking I did in commit 5545b69ae, some of the
longer keywords mentioned in the SQL standard don't fit the
available space in PDF output.

I experimented with various solutions like putting such keywords
on their own table lines, but everything looked ugly or confusing
or both; worse, the weirdness also appeared in the HTML version,
which (normally) doesn't need it.

The best answer seems to be to insert &zwsp; into long keywords
so that they can be broken into two lines when, and only when,
needed.  It doesn't look too awful if the break happens after
an underscore --- and fortunately, all the problematic keywords
have underscores.

Discussion: https://postgr.es/m/6916.1589146280@sss.pgh.pa.us
doc/src/sgml/generate-keywords-table.pl