Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j3RM6-0000ry-8E for pgsql-docs@arkaria.postgresql.org; Sun, 16 Feb 2020 21:21:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j3RM4-0008JT-Lb for pgsql-docs@arkaria.postgresql.org; Sun, 16 Feb 2020 21:21:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j3RM4-0008JL-Bd for pgsql-docs@lists.postgresql.org; Sun, 16 Feb 2020 21:21:32 +0000 Received: from mail-lf1-x131.google.com ([2a00:1450:4864:20::131]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1j3RM1-0004bb-B8 for pgsql-docs@lists.postgresql.org; Sun, 16 Feb 2020 21:21:31 +0000 Received: by mail-lf1-x131.google.com with SMTP id 203so10350917lfa.12 for ; Sun, 16 Feb 2020 13:21:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=5RHKJ6A1OA4vYYat7hxxPdjYfJOpGknVWRioGbtow8o=; b=ggQf0r1wW4T4/1ioZJLTYdnucpon1g1VSHRkHe85mUoVzPzI+ovzLE/G4bgd79YEyl EITf1fyK2Fqq+Uk1/8zFNzennwxOb2vpHHeIhVaVO81Yn0Rg0Hjlf/BbYGlfrB2NvC3H qLD0tgqmVZngenm4heKQJJeMOH9Trg6/A+3ZInNLscoAADZjf+IBhhP76bszQ+v3UN1I Lf2JfuPi1yNgxQxpOwRESd4K+GEj03q51IjvMqTc8ctc7iXWEhaspEIrEDTFOp4UtjQ6 qQuBhkx9SDW4NHwEHPjOPaDHcTHlXFaxhKXQqKG9ewb7Lq3k995F0gOw61Hq1BtW9szk 0EAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=5RHKJ6A1OA4vYYat7hxxPdjYfJOpGknVWRioGbtow8o=; b=FKMy8PchKimoliMKzdk0PMYd1mn6f7ifvpJFaPnpuVjPwxS8YjVlYTSI2Dwnf6wxB0 ZKH8m5yjM7QXPa0duRRtz0FPqy2t0XWLYsHP7BP6nTnQ99wLhcsHZxuDW4TBOoXtBD99 G3TM0hYEpDSHk+CEb4u2KHnCi2oryqJGurW0AvyjHfD5pF3IvedxUrk6dgkwH8JaNnDu 0AVttF47ZvSk/Uug0682JohI71hQ5QuIWqz8jV5CEW93hE4y+cPq7uh8bmW4gvpzlY+I NDgYkbsjgKp/TYcnz5J2KTdXzdGFdt2DQZyAb5EQP5X3XJY6SP8OIV0KSVvWeG35/iVm ntFw== X-Gm-Message-State: APjAAAX/KXukJqg6wDqe8MWWBDkzK3sC/odg22OFBWrhlfgt8Zv3nuei UCxCZkRGZvJ69HNFZCWBJZHjvizH X-Google-Smtp-Source: APXvYqwXkyV31pfK+7XHFAFN14yorHlKUeRgcGX6XLaQndDZMdV3H2Ipn9hglYgy6wCNugcghGtqRw== X-Received: by 2002:a19:f608:: with SMTP id x8mr6319820lfe.115.1581888087794; Sun, 16 Feb 2020 13:21:27 -0800 (PST) Received: from [1.0.0.7] ([178.155.4.59]) by smtp.gmail.com with ESMTPSA id u24sm7288912ljo.77.2020.02.16.13.21.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 16 Feb 2020 13:21:26 -0800 (PST) Subject: Re: Getting our tables to render better in PDF output To: Tom Lane , pgsql-docs@lists.postgresql.org References: <20200212221818.GA15503@alvherre.pgsql> <23574.1581555393@sss.pgh.pa.us> <10810.1581883655@sss.pgh.pa.us> From: Alexander Lakhin Message-ID: <5d1f5b72-1b4a-6e15-6730-d94e2252a073@gmail.com> Date: Mon, 17 Feb 2020 00:21:24 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <10810.1581883655@sss.pgh.pa.us> Content-Type: multipart/mixed; boundary="------------CE0EF25842A8E2B474A834DE" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------CE0EF25842A8E2B474A834DE Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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 > "→" 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 --------------CE0EF25842A8E2B474A834DE Content-Type: text/x-patch; charset=UTF-8; name="shift_arrow_up.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="shift_arrow_up.patch" diff --git a/doc/src/sgml/Makefile b/doc/src/sgml/Makefile index 0401a515df8..3be29dba9f1 100644 --- a/doc/src/sgml/Makefile +++ b/doc/src/sgml/Makefile @@ -169,10 +169,14 @@ XSLTPROC_FO_FLAGS += --stringparam img.src.path '$(srcdir)/' %-A4.fo: stylesheet-fo.xsl %.sgml $(ALLSGML) $(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^) $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) $(XSLTPROC_FO_FLAGS) --stringparam paper.type A4 -o $@ $(wordlist 1,2,$^) + $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) -o $@.tmp $(@D)/pg-customize-fo.xsl $@ + mv $@.tmp $@ %-US.fo: stylesheet-fo.xsl %.sgml $(ALLSGML) $(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^) $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) $(XSLTPROC_FO_FLAGS) --stringparam paper.type USletter -o $@ $(wordlist 1,2,$^) + $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) -o $@.tmp $(@D)/pg-customize-fo.xsl $@ + mv $@.tmp $@ %.pdf: %.fo $(ALL_IMAGES) $(FOP) -fo $< -pdf $@ diff --git a/doc/src/sgml/pg-customize-fo.xsl b/doc/src/sgml/pg-customize-fo.xsl new file mode 100644 index 00000000000..ba3138e2a3d --- /dev/null +++ b/doc/src/sgml/pg-customize-fo.xsl @@ -0,0 +1,42 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + → + + + + + + + + + + + --------------CE0EF25842A8E2B474A834DE--