Hello hackers,
30.04.2020 00:23, Alvaro Herrera wrote:
> But apparently it's not sufficient -- the new font is not used
> everywhere. For example footnotes seem to use a different font than the
> main body of text. (I altered the fontname to Gentium, which I like
> better, and uses a different g
ElasticSearch also uses AsciiDoc with the "edit_me" module that generates
those. Code -
https://github.com/elastic/docs/blob/master/resources/asciidoctor/lib/edit_me/extension.rb
It results in a semi-transparent "edit me" button at the top to the right
of the page title, e.g.
https://www.elastic.
On 2020-Apr-29, Peter Eisentraut wrote:
> To use a different font, you have to (a) pick one, and (b) install it
> locally when you build the PDFs.
>
> My proposal is to use the DejaVu fonts, which are open source and easily
> available for common operating systems. (Arguably, they also give the
Peter Eisentraut writes:
> On 2020-04-29 21:58, Tom Lane wrote:
>> I think making the built documentation depend on nonstandard fonts
>> is a truly awful idea. It'd be okay perhaps if the requirement only
>> applied to people building the docs, but won't the requirement also
>> flow through to en
On 2020-04-29 21:58, Tom Lane wrote:
I think making the built documentation depend on nonstandard fonts
is a truly awful idea. It'd be okay perhaps if the requirement only
applied to people building the docs, but won't the requirement also
flow through to end users?
No, the font is embedded in
Peter Eisentraut writes:
> On 2020-04-26 21:13, Tom Lane wrote:
>> "π" renders poorly in our PDF docs: as shown in the attached
>> screenshot, it doesn't line up on the baseline.
> The real problem here is that the default font (Times or Times New
> Roman) embedded in PDF readers doesn't have th
On 2020-04-29 16:13, Jürgen Purtz wrote:
On 20.04.20 10:30, Jürgen Purtz wrote:
On 17.04.20 20:40, Erik Rijkers wrote:
Very good stuff, and useful. I think.
I mean that but nevertheless here is a lot of comment :)
(I didn't fully compile as docs, just read the 'text' from the patch
file)
Th
On 2020-04-10 05:45, Bruce Momjian wrote:
On Thu, Apr 9, 2020 at 08:47:56PM -0400, Jonathan Katz wrote:
On 4/9/20 4:57 PM, Bruce Momjian wrote:
Jonathan, Stephen, with the minor release done, can we focus on adding
the URL redirect and completing the patch to rename this feature in the
docs?
On 2020-04-26 21:13, Tom Lane wrote:
"π" renders poorly in our PDF docs: as shown in the attached
screenshot, it doesn't line up on the baseline. I realized that
this is the same problem I'd run into recently with right-arrow,
and it can be solved in the same way, namely we have to specify
use o
PG Doc comments form writes:
> "-C
> --create
> ...
> When this option is used, the database named with -d is used only to
> issue the initial DROP DATABASE and CREATE DATABASE commands. All data is
> restored into the database name that appears in the archive."
> I am finding the opposite ha
On Wed, Apr 29, 2020 at 04:36:37PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/runtime-config-wal.html
> Description:
>
> Would it be possible to add "edit this page" links to every PostgreSQ
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/runtime-config-wal.html
Description:
Would it be possible to add "edit this page" links to every PostgreSQL doc
page, pointing to the docs git repo, ideally on a site that allows
on-the-si
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/app-pgrestore.html
Description:
"-C
--create
Create the database before restoring into it. If --clean is also
specified, drop and recreate the target database before connecting to it.
On Wed, Apr 29, 2020 at 8:32 AM PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/protocol-flow.html
> Description:
>
> In "52.2.2.1. Multiple Statements in a Simple Query" there is supposed to
> be
> a t
On 2020-04-29 16:13, Jürgen Purtz wrote:
On 20.04.20 10:30, Jürgen Purtz wrote:
On 17.04.20 20:40, Erik Rijkers wrote:
Very good stuff, and useful. I think.
I mean that but nevertheless here is a lot of comment :)
(I didn't fully compile as docs, just read the 'text' from the patch
file)
T
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/protocol-flow.html
Description:
In "52.2.2.1. Multiple Statements in a Simple Query" there is supposed to be
a typo in the last example.
I cannot find it, even having diffed the two exampl
16 matches
Mail list logo
