Subject: Re: PDF building with FOP
To: Alvaro Herrera <alvherre@2ndquadrant.com>,
 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
References: <20170311031945.dwj5w7lai26lvf4z@alvherre.pgsql>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
From: Alexander Law <exclusion@gmail.com>
Message-ID: <a0523587-2f01-4e16-4ef7-9fd7a475d3d5@gmail.com>
Date: Sat, 11 Mar 2017 10:22:51 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <20170311031945.dwj5w7lai26lvf4z@alvherre.pgsql>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

Hello Alvaro,

11.03.2017 06:19, Alvaro Herrera wrote:
> - Does the output look OK?
> It looks generally sane in a very quick skim, modulo the problems we've
> always had with PDFs, such as tables 9-44 and 9-45 being completely
> unusable.
We at postgrespro added custom XSL (see pg-customize-fo.xsl in 
patches/xml in pg-doc.check.tar.bz2 attached to 
https://www.postgresql.org/message-id/449e34c4-9cc8-d17d-5ebe-be92b4c0a87a%40gmail.com) 
to get long text wrapped in the table cells.
Look at http://repo.postgrespro.ru/doc/pgpro/9.6/en/postgres-A4-fop.pdf 
(pages 224-228)
There are a few places where long strings still should be broken 
manually (with &zwsp;) but the majority of the long string issues fixed 
automatically with this xsl.

Best regards,
Alexander


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs