| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Getting our tables to render better in PDF output |
| Date: | 2020-02-16 21:21:24 |
| Message-ID: | 5d1f5b72-1b4a-6e15-6730-d94e2252a073@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Hello Tom,
> 16.02.2020 23:07, Tom Lane wrote:
>
>
> I poked at this a little bit, and found that I could get a pretty
> decent-looking result if I hacked the .fo file to contain
> "<fo:inline baseline-shift="10%">→</fo:inline>" rather than a bare
> right arrow. (See attached screenshot, wherein the last rightarrow
> was fixed this way but the others weren't.) However, I do not
> have much of a clue as to how such a fix might be injected into
> our stylesheets --- anybody have a suggestion?
Please look at the XSLT template for processing .fo before calling fop.
Maybe this can be done with just the existing stylesheet-fo.xsl, I'll
try to research this later.
Best regards,
Alexander
| Attachment | Content-Type | Size |
|---|---|---|
| shift_arrow_up.patch | text/x-patch | 2.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2020-02-17 06:37:11 | REGEXP_REPLACE : How to use a column value in the regex |
| Previous Message | Tom Lane | 2020-02-16 20:07:35 | Re: Getting our tables to render better in PDF output |