Doc: further fooling-about with rendering of tables in PDF output.
authorTom Lane <[email protected]>
Wed, 6 May 2020 16:23:43 +0000 (12:23 -0400)
committerTom Lane <[email protected]>
Wed, 6 May 2020 16:23:54 +0000 (12:23 -0400)
commitf21599311e50a43c90a3d33ef4f60193a774321a
tree088f02a41f84436b70930dadf232edd140a298b7
parentbeb2516e961490723fb1a2f193406afb3d71ea9c
Doc: further fooling-about with rendering of tables in PDF output.

I concluded that we really just ought to force all tables in PDF output
to default to "left" alignment (instead of "justify"); that is what the
HTML toolchain does and that's what most people have been designing the
tables to look good with.  There are few if any places where "justify"
produces better-looking output, and there are many where it looks
horrible.  So change stylesheet-fo.xsl to make that true.

Also tweak column widths in a few more tables to make them look better
and avoid "exceed the available area" warnings.  This commit fixes
basically everything that can be fixed through that approach.  The
remaining tables that give warnings either are scheduled for redesign
as per recent discussions, or need a fundamental rethink because they
Just Don't Work in a narrow view.
18 files changed:
doc/src/sgml/brin.sgml
doc/src/sgml/config.sgml
doc/src/sgml/datatype.sgml
doc/src/sgml/ddl.sgml
doc/src/sgml/event-trigger.sgml
doc/src/sgml/extend.sgml
doc/src/sgml/json.sgml
doc/src/sgml/libpq.sgml
doc/src/sgml/monitoring.sgml
doc/src/sgml/mvcc.sgml
doc/src/sgml/plpgsql.sgml
doc/src/sgml/runtime.sgml
doc/src/sgml/stylesheet-fo.xsl
doc/src/sgml/syntax.sgml
doc/src/sgml/textsearch.sgml
doc/src/sgml/user-manag.sgml
doc/src/sgml/xfunc.sgml
doc/src/sgml/xindex.sgml