Re: Getting our tables to render better in PDF output
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Lakhin <exclusion@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Date: 2020-04-12T17:33:11Z
Lists: pgsql-docs
Attachments
- markup-for-returnvalue.patch (text/x-diff) patch
I wrote:
> So if we can get <returnvalue> to both insert a right arrow and switch the
> font to match <type>'s choice, this would work more or less decently, and
> it's probably cleaner than the bare-entity-reference approach I posted
> before. I don't have the XSL skills to get that to work though.
> Anyone want to help out?
I educated myself a teensy bit about XSL, and unless I'm missing
something, this is really pretty darn trivial; the attached seems
to do the trick.
I experimented with the markup from <guimenuitem> and decided that
I didn't like their choice of a smaller font size in this context;
it looks better to me to leave the arrow full-size. The important
thing to learn from that precedent seems to be that we have to
specify the font correctly, as indeed is mentioned in the docbook
documentation. So it seems to work well to just use
<fo:inline font-family="{$symbol.font.family}">→ </fo:inline>
(The extra space seems to be necessary, else the arrow ends up
adjacent to the type name.)
So I'm pretty happy with this implementation and will push forward.
regards, tom lane
Commits
-
Doc: introduce new layout for tables of functions and operators.
- e894c61836e4 13.0 landed
-
Doc: introduce and document "&zwsp;" for allowing optional line breaks.
- 88d934f0387a 13.0 landed