The PDF toolchain defaults to laying out all columns of a table with
equal widths, in contrast to the HTML rendering which automatically
varies the column widths to fit the data. In many places, this
results in very badly laid-out tables, with lots of useless whitespace
in some places and text that overruns its cell in other places.
For tables that have reasonably static content, we can improve
matters by adding entries to hand-assign the column widths.
This commit does that for a few of the tables that were worst off;
it eliminates close to 200 "contents ... exceed the available area"
warnings in an A4 PDF build.
I also forced align="left" in these tables, overriding the PDF
toolchain's default which is evidently "justify". (The HTML toolchain
seems to default to that already.) Anyplace where things are tight
enough that we need to worry about this, forced justification tends to
look truly awful.
+
+
|
LC_COLLATE
PostgreSQL Character Sets
+
+
+
+
+
+
+
|
Name
The Bytes/Char field is populated by looking at the values returned
by pg_wchar_table.mblen function for each encoding.
-->
- Bytes/Char
+ Bytes/&zwsp;Char
Aliases
Built-in Client/Server Character Set Conversions
+
+
|
Server Character Set
All Built-in Character Set Conversions
+
+
+
|
Conversion Name
-
-
+ align="left" colwidth="1*"/>
+ align="left" colwidth="8*"/>