=E2=80=9D= tag, which causes browsers to interpret each space literally. For the case of the =E2=80=9Cdigest=E2=80=9D function, the outputted = HTML shows the first digest function indented, the second one at the start of the new line. Jonathan --Apple-Mail=_15BD341A-83CA-4CD6-82B7-B0CC17D8B0E6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On Mar 28, 2018, at 9:32 PM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:

On = 3/28/18 21:30, Peter Eisentraut wrote:
On 3/23/18 08:56, Daniel Westermann wrote:
is it only me who sees = blanks before the first word in the first line of
the code = boxes, e.g. here:

https://www.postgresql.org/docs/9.6/static/sql-createtable.html=
https://www.postgresql.org/docs/10/static/sql-createtable.html<= br class=3D"">
For the devel documentation it is fine:
https://www.postgresql.org/docs/devel/static/sql-createtable.ht= ml

Tested in Firefox and Chrome.

Yeah, that looks weird. = I'll look into it.

Just = looking at a nearby thread ... something is quite whacky with the
web site stylesheet. It didn't use to look like this. = Check this out:
https://www.postgresql.org/docs/10/static/pgcrypto.html#id-1.11= .7.35.5
Something = is adding spaces - it=E2=80=99s within the =E2=80=9C<pre>=E2=80=9D = tag, which causes browsers
to interpret each space = literally.
For the case of the = =E2=80=9Cdigest=E2=80=9D function, the outputted HTML shows the first = digest
function indented, the second one at the start of the = new line.
Jonathan
= --Apple-Mail=_15BD341A-83CA-4CD6-82B7-B0CC17D8B0E6-- From peter.eisentraut@2ndquadrant.com Fri May 22 02:06:21 2026 Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1MiN-00077o-4R for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 01:50:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f1MiM-0007jp-4C for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 01:50:54 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1MfH-0005sV-3U for pgsql-docs@lists.postgresql.org; Thu, 29 Mar 2018 01:47:43 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1MfD-0006Kb-Cr; Thu, 29 Mar 2018 01:47:41 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 86FE721910; Wed, 28 Mar 2018 21:47:38 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 28 Mar 2018 21:47:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=y3cIdL r7ewBJFpAWNHGveGjLlcP6gwA0755qrvLPfy4=; b=BHjqytfWBOopVXLSLZRZtd xXjVHWZ2bP35cyd3WJMBLh2Oj0hS0tfTcpaIH7oU1CwnESt8pgUZ77h0AE6S5rox FR5UjugAgdiGOorHYy7bXHBRI9SOfYvipu/Vnkn0LzTXeRFkDXNTrxgmkFBOFs6I dikbsiR5eTaLihP2SgTxT/sv8JJk4auCtBHvTsqPpoZ3Gq6ABVaDmwJKuZfmKbXu bmkL0RJtKOa41y9tt/NiqSwkQK9KQ0Me5VyJKe9VbN0F8d2WAFt1z5RFJ+f4jp7Z AN6LeUGAOKpPJtcKTErGILBEzyK/IExYoNu+gBOzOBh20FjBaLkH4v6WfifoLFuA == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 4CD7510339; Wed, 28 Mar 2018 21:47:38 -0400 (EDT) Subject: Re: Blanks in the first line before the first word in the code boxes To: "Jonathan S. Katz" References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
<5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org> Cc: Daniel Westermann , pgsql-docs@postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 28 Mar 2018 21:47:38 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 3/28/18 21:36, Jonathan S. Katz wrote: > >> On Mar 28, 2018, at 9:32 PM, Peter Eisentraut >> > > wrote: >>> Yeah, that looks weird. I'll look into it. >> >> Just looking at a nearby thread ... something is quite whacky with the >> web site stylesheet. It didn't use to look like this. Check this out: >> https://www.postgresql.org/docs/10/static/pgcrypto.html#id-1.11.7.35.5 > > Something is adding spaces - it’s within the “
” tag, which causes
> browsers
> to interpret each space literally.
> 
> For the case of the “digest” function, the outputted HTML shows the
> first digest
> function indented, the second one at the start of the new line.

Yeah, the spaces are in the source, so it's not a CSS issue.  But it
doesn't come out like that if you build the docs locally.  So it's
something in the web site code.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




From jkatz@postgresql.org Fri May  22 02:06:21 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Mtv-0007uQ-69
	for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 02:02:51 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f1Mtt-0002vF-H0
	for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 02:02:49 +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_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Mtt-0002v5-Ay
	for pgsql-docs@lists.postgresql.org; Thu, 29 Mar 2018 02:02:49 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Mtp-0006CW-T8
	for pgsql-docs@postgresql.org; Thu, 29 Mar 2018 02:02:48 +0000
Received: from pool-98-116-99-252.nycmny.fios.verizon.net ([98.116.99.252]
 helo=ph33r-retina.home)
	by meldrar.postgresql.org with esmtpsa
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Mtl-0008F0-Q2; Thu, 29 Mar 2018 02:02:44 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Blanks in the first line before the first word in the code boxes
From: "Jonathan S. Katz" 
In-Reply-To: 
Date: Wed, 28 Mar 2018 22:02:38 -0400
Cc: Daniel Westermann ,
 pgsql-docs@postgresql.org,
 Magnus Hagander 
Content-Transfer-Encoding: quoted-printable
Message-Id: <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
To: Peter Eisentraut 
X-Mailer: Apple Mail (2.3273)
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk


> On Mar 28, 2018, at 9:47 PM, Peter Eisentraut =
 wrote:
>=20
> On 3/28/18 21:36, Jonathan S. Katz wrote:
>>=20
>>> On Mar 28, 2018, at 9:32 PM, Peter Eisentraut
>>> >> > wrote:
>>>> Yeah, that looks weird.  I'll look into it.
>>>=20
>>> Just looking at a nearby thread ... something is quite whacky with =
the
>>> web site stylesheet.  It didn't use to look like this.  Check this =
out:
>>> =
https://www.postgresql.org/docs/10/static/pgcrypto.html#id-1.11.7.35.5
>>=20
>> Something is adding spaces - it=E2=80=99s within the =E2=80=9C=E2=80=
=9D tag, which causes
>> browsers
>> to interpret each space literally.
>>=20
>> For the case of the =E2=80=9Cdigest=E2=80=9D function, the outputted =
HTML shows the
>> first digest
>> function indented, the second one at the start of the new line.
>=20
> Yeah, the spaces are in the source, so it's not a CSS issue.  But it
> doesn't come out like that if you build the docs locally.  So it's
> something in the web site code.

If I traced the code correctly, the line I suspect is such:

	s =3D tidy.parseString(contents.encode('utf-8'), **tidyopts)

I know that the web infrastructure recently updated to the Django 1.11
series, I=E2=80=99m not sure if libtidy or the like were also updated =
with that. I=E2=80=99ll
defer to Magnus on that.

Jonathan





From magnus@hagander.net Fri May  22 02:06:21 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Ua6-0003OT-9N
	for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 10:14:54 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f1Ua4-0003ze-Bm
	for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 10:14:52 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Ua4-0003zU-2M
	for pgsql-docs@lists.postgresql.org; Thu, 29 Mar 2018 10:14:52 +0000
Received: from mail-lf0-x243.google.com ([2a00:1450:4010:c07::243])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1UZz-00012H-Vr
	for pgsql-docs@postgresql.org; Thu, 29 Mar 2018 10:14:50 +0000
Received: by mail-lf0-x243.google.com with SMTP id j68-v6so7601793lfg.13
        for ; Thu, 29 Mar 2018 03:14:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=hagander-net.20150623.gappssmtp.com; s=20150623;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=lZiecZ+35MINGx498+lkARbpRZ8Qt70b1bnH7CwV/A0=;
        b=dC20XtzhfO1uuZ0oDuwL01eqBo34OYrYXsRWbA2z9BTRPhkwvZbD+n0T7pYQb+p+K0
         NXxJNHD0ZLs1MvTWthPo0Z8zxubBJLClYU67y2Bd1Pw9De8SIwQsIwg7EVqXFb8UOrzC
         C7X47fmCdZnIRpylhC6VNLdjJs0Abq44+RfSaSFuspzMaagmvEo/tR5QF1yEGmKTf4lt
         Yrk6s8xb2EyPyqvF4uhy2A6N5uSXYMa2FNkhQpd0PtO52BgMbK+rgqO+f8ZGKKuRaMQH
         1gFiKDG70M+qjNOeImxy8pKSEv3XUPwJ6eB4qsVLWxJ0vrY4EfXDpbhF5OG5mCvTYxUf
         xVoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=lZiecZ+35MINGx498+lkARbpRZ8Qt70b1bnH7CwV/A0=;
        b=MwD68jVOO2S7crhx3zPEvoROGTC9k6E7MqyF94KgjFNjmL7Rf8j6TLPdCvRZygbMsz
         M57A1cK72QyXudbgYy+4f8l3fjkYOB0X21mcgFy9EQsefXGu9sdNIOyKR3VRuwigJQU7
         QbBzfbbxOL3TMaJn/+O71BZ28tbmT7V0nCR3UcaYd071BNIniYl0IqysXaqAdIzNwwkr
         qhuebm4LsiaFq0WCwwCKdGJPhxNmHhp7GXFoJNasvmjBae4XAylM8hkoQ+s4TY+UCFrd
         vbmm8X8qUCA6iU8gCv3Gj29D+f0io3Yh34CPs6zCfwU0KuN88NHrH6UCttxCigvgP+pb
         PSmQ==
X-Gm-Message-State: AElRT7EzXdXmGuv64kuTYEBkmwPTnxAH28/+MKMF7YfiskN+lr8pSgDd
	RaTQlJhv1hmP+PVEGlKTFCkr1a+e5baLYKiqJwIKvHuC
X-Google-Smtp-Source: 
 AIpwx48dHoO2XSuCPYWKan42s+18MUje+o/4AaopLWAGc7GOvtamjr+1gzJtmCwBFRPgMP3O4z7asT7CwisX/wco/Y8=
X-Received: by 10.46.144.13 with SMTP id h13mr4210296ljg.115.1522318485995;
 Thu, 29 Mar 2018 03:14:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:9748:0:0:0:0:0 with HTTP; Thu, 29 Mar 2018 03:14:45
 -0700 (PDT)
In-Reply-To: <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
From: Magnus Hagander 
Date: Thu, 29 Mar 2018 12:14:45 +0200
Message-ID: 
 
Subject: Re: Blanks in the first line before the first word in the code boxes
To: "Jonathan S. Katz" 
Cc: Peter Eisentraut ,
	Daniel Westermann ,
 pgsql-docs 
Content-Type: multipart/alternative; boundary="089e0823b26c97ce4005688a64b0"
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

--089e0823b26c97ce4005688a64b0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 29, 2018 at 4:02 AM, Jonathan S. Katz 
wrote:

>
> > On Mar 28, 2018, at 9:47 PM, Peter Eisentraut <
> peter.eisentraut@2ndquadrant.com> wrote:
> >
> > On 3/28/18 21:36, Jonathan S. Katz wrote:
> >>
> >>> On Mar 28, 2018, at 9:32 PM, Peter Eisentraut
> >>>  >>> > wrote:
> >>>> Yeah, that looks weird.  I'll look into it.
> >>>
> >>> Just looking at a nearby thread ... something is quite whacky with th=
e
> >>> web site stylesheet.  It didn't use to look like this.  Check this ou=
t:
> >>> https://www.postgresql.org/docs/10/static/pgcrypto.html#id-1.11.7.35.=
5
> >>
> >> Something is adding spaces - it=E2=80=99s within the =E2=80=9C=E2=
=80=9D tag, which causes
> >> browsers
> >> to interpret each space literally.
> >>
> >> For the case of the =E2=80=9Cdigest=E2=80=9D function, the outputted H=
TML shows the
> >> first digest
> >> function indented, the second one at the start of the new line.
> >
> > Yeah, the spaces are in the source, so it's not a CSS issue.  But it
> > doesn't come out like that if you build the docs locally.  So it's
> > something in the web site code.
>
> If I traced the code correctly, the line I suspect is such:
>
>         s =3D tidy.parseString(contents.encode('utf-8'), **tidyopts)
>
> I know that the web infrastructure recently updated to the Django 1.11
> series, I=E2=80=99m not sure if libtidy or the like were also updated wit=
h that.
> I=E2=80=99ll
> defer to Magnus on that.
>

This would not change with the change to Django 1.11 -- the actual script
that loads the docs runs outside of Django.

Now, the entire machine was upgraded to a new Debian meaning new python,
new tidy etc some time ago. But this was done the first week of February.

Is it possible that this issue actually showed up around 4-5 February, but
just has gone unnoticed since?

--=20
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/ 

--089e0823b26c97ce4005688a64b0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable



On Thu, Mar 29, 2018 at 4:02 AM, Jonathan S. Katz <=
;jkatz@postgresql=
.org> wrote:


> On Mar 28, 2018, at 9:47 PM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com&g=
t; wrote:

>

> On 3/28/18 21:36, Jonathan S. Katz wrote:

>>

>>> On Mar 28, 2018, at 9:32 PM, Peter Eisentraut

>>> <peter.=
eisentraut@2ndquadrant.com

>>> <mailto:peter.eisentraut@2ndquadrant.com>> wrote:

>>>> Yeah, that looks weird.=C2=A0 I'll look into it.

>>>

>>> Just looking at a nearby thread ... something is quite whacky =
with the

>>> web site stylesheet.=C2=A0 It didn't use to look like this=
.=C2=A0 Check this out:

>>> https://www.postg=
resql.org/docs/10/static/pgcrypto.html#id-1.11.7.35.5

>>

>> Something is adding spaces - it=E2=80=99s within the =E2=80=9C<=
pre>=E2=80=9D tag, which causes

>> browsers

>> to interpret each space literally.

>>

>> For the case of the =E2=80=9Cdigest=E2=80=9D function, the outputt=
ed HTML shows the

>> first digest

>> function indented, the second one at the start of the new line.
>

> Yeah, the spaces are in the source, so it's not a CSS issue.=C2=A0=
 But it

> doesn't come out like that if you build the docs locally.=C2=A0 So=
 it's

> something in the web site code.



If I traced the code correctly, the line I suspect is such:



=C2=A0 =C2=A0 =C2=A0 =C2=A0 s =3D tidy.parseString(contents.encode(=
9;utf-8'), **tidyopts)



I know that the web infrastructure recently updated to the Django 1.11

series, I=E2=80=99m not sure if libtidy or the like were also updated with =
that. I=E2=80=99ll

defer to Magnus on that.

This would not=
 change with the change to Django 1.11 -- the actual script that loads the =
docs runs outside of Django.

Now, the entire machi=
ne was upgraded to a new Debian meaning new python, new tidy etc some time =
ago. But this was done the first week of February.

Is it possible that this issue actually showed up around 4-5 February, but=
 just has gone unnoticed since?=C2=A0

-- 
=C2=A0Magnus Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-=
linpro.com/


--089e0823b26c97ce4005688a64b0--




From tgl@sss.pgh.pa.us Fri May  22 02:06:21 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Xo2-0007PB-W4
	for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 13:41:31 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f1Xo1-000339-ER
	for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 13:41:29 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Xo1-00032y-5F
	for pgsql-docs@lists.postgresql.org; Thu, 29 Mar 2018 13:41:29 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Xny-0005vj-NO; Thu, 29 Mar 2018 13:41:27 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w2TDewJw013426;
	Thu, 29 Mar 2018 09:40:58 -0400
From: Tom Lane 
To: Magnus Hagander 
cc: "Jonathan S. Katz" ,
        Peter Eisentraut ,
        Daniel Westermann ,
        pgsql-docs 
Subject: Re: Blanks in the first line before the first word in the code boxes
In-reply-to: 
 
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
Comments: In-reply-to Magnus Hagander 
	message dated "Thu, 29 Mar 2018 12:14:45 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <13424.1522330858.1@sss.pgh.pa.us>
Date: Thu, 29 Mar 2018 09:40:58 -0400
Message-ID: <13425.1522330858@sss.pgh.pa.us>
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

Magnus Hagander  writes:
> Is it possible that this issue actually showed up around 4-5 February, but
> just has gone unnoticed since?

It's been there a few weeks, anyway --- I remember somebody complaining
before this particular thread started.  I wouldn't be a bit surprised
if it broke then.

			regards, tom lane




From david.g.johnston@gmail.com Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Y7o-0000N6-GB
	for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 14:01:56 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f1Y7m-0002NX-Mm
	for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 14:01:54 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Y7m-0002NN-AP
	for pgsql-docs@lists.postgresql.org; Thu, 29 Mar 2018 14:01:54 +0000
Received: from mail-qt0-x242.google.com ([2607:f8b0:400d:c0d::242])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from )
	id 1f1Y7j-0006QV-8W; Thu, 29 Mar 2018 14:01:53 +0000
Received: by mail-qt0-x242.google.com with SMTP id h4so6286453qtn.13;
        Thu, 29 Mar 2018 07:01:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=lX5YHB83leUX+P22DPIEhhyt5ShanGKjlUDoKhA9yuU=;
        b=FSWtmY9b7mJUcmvE7PjIQZGZCNIcZtqFhBNkN9u5T7LAMdlepAtqR7lX+Ou+8qPrJW
         HbruZZ495xE00LXRfDEAzFIGJbChUG2ZOXeO+xka3eKVgK7OFWWGNta+50LHLv0Ao8OK
         g9wum0REXfyGg10zRQnm7DELAaBq8W0JWeUAfPfQA17ZnwOtCU77C88lIWnOZDpw41Fi
         yieWnrfGiO9tcU1ZE8JB7uWgAQV1OIqoMhrFOI/AkHZlPVNqij5Zp+BrtbBW4+T2IzlP
         k3iT+LR3VHUkMEflpal8tL0OY9Zu4Z4HAcKab0wa1tMRxekRYI/78ryWxBxHbnsKICdf
         1/zw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=lX5YHB83leUX+P22DPIEhhyt5ShanGKjlUDoKhA9yuU=;
        b=i7bx+QeRjAfuG2fM568wDZ7CmDpYmC74t796DMeaMrUqZV81RbHjNLdb67zW1g963J
         VWOW+Zp1djXOc6O3RZBTWVk8B542F+2D4KYzjuoDjr1/OwpPlcNby+MAL7z6A6hCNAz1
         bumIHj8YPF68AJbAoxLJzjYzmEdqcHb0gT5nJMvGXWyFj/9a5bbHKpE7JFA8nPsmuGpC
         oojzTYgjCObJhvM1Vs+P4PiQddEuE9BdI9eBoSYcBL+7cSfDD+z4SKPp24x7olqmShrJ
         QAY/W4A9uY55f9kfrmHiWKTZ1y2zG1jD9W1l8K54mX74vxJkNexGtVNw0uySkHtufbS6
         7u6g==
X-Gm-Message-State: ALQs6tBbtsU5Dv+e6551+6m5c3XOKUfvYfLCPGtqyfGDq6sovXcy+dez
	Vrq2mSNXdANKqsfjlcYD5gtMD8ReSpWtIP77ouw=
X-Google-Smtp-Source: 
 AIpwx48KRBytFVYVXJ+9NLf4pl03qqgbEGie5GimkNiGWqd5AW9JlHXOwk1gidh3SAlhPPti17jXtuFwlsD3nwV4NIE=
X-Received: by 10.200.46.139 with SMTP id h11mr11671876qta.253.1522332110180;
 Thu, 29 Mar 2018 07:01:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.157.78 with HTTP; Thu, 29 Mar 2018 07:01:49 -0700 (PDT)
In-Reply-To: <13425.1522330858@sss.pgh.pa.us>
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
From: "David G. Johnston" 
Date: Thu, 29 Mar 2018 07:01:49 -0700
Message-ID: 
 
Subject: Re: Blanks in the first line before the first word in the code boxes
To: Tom Lane 
Cc: Magnus Hagander ,
 "Jonathan S. Katz" ,
	Peter Eisentraut ,
	Daniel Westermann ,
 pgsql-docs 
Content-Type: multipart/alternative; boundary="001a11c10f90a8588105688d90aa"
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

--001a11c10f90a8588105688d90aa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 29, 2018 at 6:40 AM, Tom Lane  wrote:

> Magnus Hagander  writes:
> > Is it possible that this issue actually showed up around 4-5 February,
> but
> > just has gone unnoticed since?
>
> It's been there a few weeks, anyway --- I remember somebody complaining
> before this particular thread started.  I wouldn't be a bit surprised
> if it broke then.
>

=E2=80=8BFirst report that both Tom and I responded to, Tom by cc'ing www, =
was on
the Feb 26th,

https://www.postgresql.org/message-id/151965261562.21248.680702308554136126=
4%40wrigleys.postgresql.org

David J.

--001a11c10f90a8588105688d90aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Ma=
r 29, 2018 at 6:40 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@h=
agander.net> writes:

> Is it possible that this issue actually showed up around 4-5 February,=
 but

> just has gone unnoticed since?



It's been there a few weeks, anyway --- I remember somebody comp=
laining

before this particular thread started.=C2=A0 I wouldn't be a bit surpri=
sed

if it broke then.

=E2=80=8BFirst report t=
hat both Tom and I responded to, Tom by cc'ing www, was on the Feb 26th=
,

https://www.=
postgresql.org/message-id/151965261562.21248.6807023085541361264%40wrigleys=
.postgresql.org

David J.

<=
/div>

--001a11c10f90a8588105688d90aa--




From magnus@hagander.net Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f2fKP-0006Xb-CI
	for pgsql-docs@arkaria.postgresql.org; Sun, 01 Apr 2018 15:55:33 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f2fKM-0000zG-HE
	for pgsql-docs@arkaria.postgresql.org; Sun, 01 Apr 2018 15:55:30 +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_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f2fKM-0000z6-BT
	for pgsql-docs@lists.postgresql.org; Sun, 01 Apr 2018 15:55:30 +0000
Received: from mail-lf0-x22b.google.com ([2a00:1450:4010:c07::22b])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from )
	id 1f2fKH-0005aX-SM
	for pgsql-docs@postgresql.org; Sun, 01 Apr 2018 15:55:29 +0000
Received: by mail-lf0-x22b.google.com with SMTP id j68-v6so17818500lfg.13
        for ; Sun, 01 Apr 2018 08:55:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=hagander-net.20150623.gappssmtp.com; s=20150623;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=dVoUVuxnspf7FsseYf0FF+n7tPflIISKVdfmgjHJfBQ=;
        b=in3uv4FPWziq0FthcUcNyO2hrtFqbA5nFRNHUOLOQwqN9H7xeQC6VrgWqDOjtxcqkK
         3+QtNMnxG8pX0ZmpnGS2cXPco/x5IqB+vKikMbyFB5qO1chVqJb1nRXvNRf/ygBYyJ9u
         +D1JtXbL8fkbhxYScq2G+h7mcNpwLKkMB5M+0BopcFewrsXvV/ZKxwMcYa22nrec/QOr
         rQ4PSfMF6/cAD5jK6Z0NnXuZjEsgAtnVgm8e9x3cUV4reSZKee4FI7hu1AyhMBbk0tsI
         UV2aYpjQzXnVC84aTDkzc1lwECqn/1gsKl55I49K4IUHOZ3SA1sLtlH2WCfdsdgtmP0f
         IE6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=dVoUVuxnspf7FsseYf0FF+n7tPflIISKVdfmgjHJfBQ=;
        b=l9pVZn1pZCzrNV2fjQLEWcJF4govD6/UvCpPiE9dzFKhC7+DIz5Z5ail9SKrXcts4g
         /B7DhvM/Wzfm+/TYsxPvJJt3Mll9usAj9JCCgt5acOoiM2VXWo0hN5LQyaO6bIZxxHD0
         MyD3X5fHyDBzmQe7m7bQbpUVY/km9vQQ3scO+MdWA7TP355Ylajxt6i+hom6cuNY0Iat
         2eWwrGnNMi3S7C2911Ua1O2AnFDW0gSjENi9MlE3aZKCnx2TWho981Fx0erHw9J2Fa06
         FhXwdA3BnosL6mDy7JSzn7uNn8SzOSFy2atTBw7HmkYno2YYI//bIXahlj1Dq0tjx+rw
         iS2g==
X-Gm-Message-State: ALQs6tDf922CCLey5hB1XFiNSH/uNQWxLrXzRXEKs2kpiAlbPDbAeN1l
	x/k65lR1nLXkQKJMB3eyBJtmBYjeYP4y+PovvkUZMg==
X-Google-Smtp-Source: 
 AIpwx4/xSnu7uFevMQCKKBKpfYmjn+vqRiP9UV6mSVBj6WSrsVB0xXzFexluYNQP11DoPUnG22MQrkYK4JRi6Lb2QGM=
X-Received: by 10.46.1.213 with SMTP id f82mr3931632lji.35.1522598122164; Sun,
 01 Apr 2018 08:55:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:9748:0:0:0:0:0 with HTTP;
 Sun, 1 Apr 2018 08:55:21 -0700 (PDT)
In-Reply-To: <13425.1522330858@sss.pgh.pa.us>
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
From: Magnus Hagander 
Date: Sun, 1 Apr 2018 17:55:21 +0200
Message-ID: 
 
Subject: Re: Blanks in the first line before the first word in the code boxes
To: Tom Lane 
Cc: "Jonathan S. Katz" ,
	Peter Eisentraut ,
	Daniel Westermann ,
 pgsql-docs 
Content-Type: multipart/alternative; boundary="001a1142acdc3528ab0568cb809e"
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

--001a1142acdc3528ab0568cb809e
Content-Type: text/plain; charset="UTF-8"

On Thu, Mar 29, 2018 at 3:40 PM, Tom Lane  wrote:

> Magnus Hagander  writes:
> > Is it possible that this issue actually showed up around 4-5 February,
> but
> > just has gone unnoticed since?
>
> It's been there a few weeks, anyway --- I remember somebody complaining
> before this particular thread started.  I wouldn't be a bit surprised
> if it broke then.
>

Yeah, it's quite likely that it got broken by the OS upgrade and nobody
picked up on it before then. This can probably be because the backbranch
documentation is only updated when we make actual releases.

However, why does devel work fine when the others are broken. It's the
exact same code that's run to load the docs. The *input* to the loader must
also be different at some point.

-- 
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/ 

--001a1142acdc3528ab0568cb809e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On T=
hu, Mar 29, 2018 at 3:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wr=
ote:
Magnus Hagander <=
;magnus@hagander.net> writes:=


> Is it possible that this issue actually showed up around 4-5 February,=
 but

> just has gone unnoticed since?



It's been there a few weeks, anyway --- I remember somebody comp=
laining

before this particular thread started.=C2=A0 I wouldn't be a bit surpri=
sed

if it broke then.

Yeah, it's quite =
likely that it got broken by the OS upgrade and nobody picked up on it befo=
re then. This can probably be because the backbranch documentation is only =
updated when we make actual releases.

However, why=
 does devel work fine when the others are broken. It's the exact same c=
ode that's run to load the docs. The *input* to the loader must also be=
 different at some point.

-- 
=C2=
=A0Magnus Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-linpro.com/<=
/a>



--001a1142acdc3528ab0568cb809e--




From tgl@sss.pgh.pa.us Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f2fS1-00070U-P9
	for pgsql-docs@arkaria.postgresql.org; Sun, 01 Apr 2018 16:03:25 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f2fS0-0005BY-R0
	for pgsql-docs@arkaria.postgresql.org; Sun, 01 Apr 2018 16:03:24 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f2fS0-0005BN-HU
	for pgsql-docs@lists.postgresql.org; Sun, 01 Apr 2018 16:03:24 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f2fRy-0006px-7p; Sun, 01 Apr 2018 16:03:23 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w31G2tfn019321;
	Sun, 1 Apr 2018 12:02:55 -0400
From: Tom Lane 
To: Magnus Hagander 
cc: "Jonathan S. Katz" ,
        Peter Eisentraut ,
        Daniel Westermann ,
        pgsql-docs 
Subject: Re: Blanks in the first line before the first word in the code boxes
In-reply-to: 
 
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
 
Comments: In-reply-to Magnus Hagander 
	message dated "Sun, 01 Apr 2018 17:55:21 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <19319.1522598575.1@sss.pgh.pa.us>
Date: Sun, 01 Apr 2018 12:02:55 -0400
Message-ID: <19320.1522598575@sss.pgh.pa.us>
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

Magnus Hagander  writes:
> However, why does devel work fine when the others are broken. It's the
> exact same code that's run to load the docs. The *input* to the loader must
> also be different at some point.

HEAD is the only branch building the docs via XML, so it's hardly
unlikely that the input is different.

			regards, tom lane




From peter.eisentraut@2ndquadrant.com Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f31rp-0000Lm-No
	for pgsql-docs@arkaria.postgresql.org; Mon, 02 Apr 2018 15:59:33 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f31ro-0001aL-26
	for pgsql-docs@arkaria.postgresql.org; Mon, 02 Apr 2018 15:59: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_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f31rn-0001aB-Rs
	for pgsql-docs@lists.postgresql.org; Mon, 02 Apr 2018 15:59:31 +0000
Received: from out5-smtp.messagingengine.com ([66.111.4.29])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f31rj-0003UJ-Vj; Mon, 02 Apr 2018 15:59:30 +0000
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47])
	by mailout.nyi.internal (Postfix) with ESMTP id 861D42133A;
	Mon,  2 Apr 2018 11:59:25 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
  by compute7.internal (MEProxy); Mon, 02 Apr 2018 11:59:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=cc:content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=zz7rDF
	x1Ztl1usEq3gK6ajSkt85Xzjq7P77lm8Rvthg=; b=Qql1sR/GZOgWs9sLWp7hHB
	KfHxw5wsBpA2bbBURBtKUBi2uuRTIpv5OP4qe6W47His+RWITzVunjHoHbRHCbVB
	yoDAQ2g0Xh/3P7LJk+PpHKBKeXHGNz2d5JeKzrJGYPPKS9iSyd6vqE8PlQ+3NpS4
	+uXA3D5GShpqGyQ79n5nIi8kpktkloG+XmitMtsYdrp4zTKfQNJwSKmBEGA5PBlN
	3S9HJ4eyi6QZAJqeHq6JoXt9KTjisbvL50cZT8wzbFkXhw1ScTYV3rH/PbvtGA3x
	v2maQ6252Yw7jMqfRoJwakXaSUVhw8P59KCPkp5XibjvPF75pOtZtngckF/D0OHw
	==
X-ME-Sender: 
Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39])
	by mail.messagingengine.com (Postfix) with ESMTPA id 3D28010263;
	Mon,  2 Apr 2018 11:59:25 -0400 (EDT)
Subject: Re: Blanks in the first line before the first word in the code boxes
To: Magnus Hagander , Tom Lane 
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
 
Cc: "Jonathan S. Katz" ,
 Daniel Westermann ,
 pgsql-docs 
From: Peter Eisentraut 
Organization: 2ndQuadrant
Message-ID: <60a39b28-485e-1621-79af-fa01cf43b3c6@2ndquadrant.com>
Date: Mon, 2 Apr 2018 11:59:24 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: 
 
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

On 4/1/18 11:55, Magnus Hagander wrote:
> However, why does devel work fine when the others are broken. It's the
> exact same code that's run to load the docs. The *input* to the loader
> must also be different at some point.

In devel, the raw HTML output looks like

... ALTER FOREIGN TABLE [ IF EXISTS ] [ ONLY ] ...

(with a line break)

but before it looks like

... ALTER FOREIGN TABLE [ IF EXISTS ] [ ONLY ] ...

(without a line break).

So maybe some part of the processing code thinks it should do some kind
of "indentation" here.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




From magnus@hagander.net Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3Lmm-0001MM-79
	for pgsql-docs@arkaria.postgresql.org; Tue, 03 Apr 2018 13:15:40 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f3Lml-0008Ok-3o
	for pgsql-docs@arkaria.postgresql.org; Tue, 03 Apr 2018 13:15:39 +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_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3LjZ-0006Ha-Ar
	for pgsql-docs@lists.postgresql.org; Tue, 03 Apr 2018 13:12:21 +0000
Received: from mail-lf0-x22a.google.com ([2a00:1450:4010:c07::22a])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3LjR-0007Ay-R8
	for pgsql-docs@postgresql.org; Tue, 03 Apr 2018 13:12:20 +0000
Received: by mail-lf0-x22a.google.com with SMTP id o102-v6so20101147lfg.8
        for ; Tue, 03 Apr 2018 06:12:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=hagander-net.20150623.gappssmtp.com; s=20150623;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=iCfHbtZru9+KDHjuby/1mz/ES6n5TGgSl5iI+nTahNs=;
        b=BRFzavrMNzrW+79Hra3nG+RkwTaSde6nXIUioixM6govu+eqT6SAY7xVw91XkVznno
         92rwTpKmoGBU4tqxLqiF3SeOmJ4KhF3oPsF3A+paLSbIs06nr8bDMDbLXjzL5uKDy6BN
         pSnqtrkSVP0BIfdTTbw+4/6YcdTqakMD4PCU50LbkdX87Ybn9IcCjAteBzeVrK4S5gbC
         0gRcC0FGQYpVU5xV/KZFXMbRp9Ano+yvCVpsYtS6IRAxdPq6WsghdKo7aiWBRzihAoCw
         OsxA/tMSR+d2RqNVM2fRTV5xhZxkYGysmpXFWUADglkixPFw9xok5fehXVmE9mW9cg7b
         ecnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=iCfHbtZru9+KDHjuby/1mz/ES6n5TGgSl5iI+nTahNs=;
        b=QvSr+J7PcFn97hwKdpZP04qe55ikm3WqEktX6eV7NtwCq9mzjbN7xIJCzvWG0rRBEJ
         Yj5r6Lz44TsKKn7avipkH/cEYM9kvYipLBsoJ5mfKP9GE6AjnBuvCqQxb407LYgmoSv8
         81hEaVYl4OmhrF2flTx7dCQHnOC9Ya9yzNdeDJdudDNE3J8YLK/WrJtT0Bs/SCHxc2j4
         SaBstUalboEDh6pB3eT48xUctTr5hGez5hE6smzmkM3u6ziuWDh8rZIpN4PRnDPMkRuU
         j48LOjP7KzZNK8NJ6+PDHT4lzZDTT1AOmIAQ8cZtQjvdRx5fP5xMnvtcFv7PSigmMO+5
         1qgQ==
X-Gm-Message-State: ALQs6tDxKvP4kRStBdi98iTdg/jZ/IP9ZDylkX75Zb+EFxBPhDVh/yNf
	cGN06gqQnC/FpzAg3DphLEr542+hmoD9HOLaBibKFhaA
X-Google-Smtp-Source: 
 AIpwx4+BuWY1IuiHIPPD+nM54Vf8av0l3cMogOZ+tUL+w7KN2uaYDkybMShWHVrkNxo8ISgLvWwJhmel735rOx8okqU=
X-Received: by 10.46.146.87 with SMTP id v23mr8844021ljg.147.1522761132902;
 Tue, 03 Apr 2018 06:12:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:9748:0:0:0:0:0 with HTTP;
 Tue, 3 Apr 2018 06:12:12 -0700 (PDT)
In-Reply-To: <60a39b28-485e-1621-79af-fa01cf43b3c6@2ndquadrant.com>
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
 
 <60a39b28-485e-1621-79af-fa01cf43b3c6@2ndquadrant.com>
From: Magnus Hagander 
Date: Tue, 3 Apr 2018 15:12:12 +0200
Message-ID: 
 
Subject: Re: Blanks in the first line before the first word in the code boxes
To: Peter Eisentraut 
Cc: Tom Lane , "Jonathan S. Katz" ,
	Daniel Westermann ,
 pgsql-docs 
Content-Type: multipart/alternative; boundary="089e0823b0d4679ce60568f17473"
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

--089e0823b0d4679ce60568f17473
Content-Type: text/plain; charset="UTF-8"

On Mon, Apr 2, 2018 at 5:59 PM, Peter Eisentraut <
peter.eisentraut@2ndquadrant.com> wrote:

> On 4/1/18 11:55, Magnus Hagander wrote:
> > However, why does devel work fine when the others are broken. It's the
> > exact same code that's run to load the docs. The *input* to the loader
> > must also be different at some point.
>
> In devel, the raw HTML output looks like
>
> ... > ALTER FOREIGN TABLE [ IF EXISTS ] [ ONLY ] ...
>
> (with a line break)
>
> but before it looks like
>
> ... ALTER FOREIGN TABLE [ IF EXISTS ] [ ONLY ] ...
>
> (without a line break).
>
> So maybe some part of the processing code thinks it should do some kind
> of "indentation" here.
>
>
I think I found the problem, and pushed a fix for it. Basically it turns
off indentation completely on pre-11 versions., I elected to keep indention
on dev because it works there, and it makes debugging any of the formatting
a lot easier.

I've pushed the fix and reloaded the 10 docs. I have not reloaded earlier
branches yet, but I'd be interested in some people reviewing a bunch of
pages in the 10 docs mainly to see if (1) it fixes all the cases, and (2)
it actually breaks some *other* cases.


-- 
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/ 

--089e0823b0d4679ce60568f17473
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On M=
on, Apr 2, 2018 at 5:59 PM, Peter Eisentraut <peter.eisent=
raut@2ndquadrant.com> wrote:
On 4/1/18 11:55, Magnus Hagander wrote:

> However, why does devel work fine when the others are broken. It's=
 the

> exact same code that's run to load the docs. The *input* to the lo=
ader

> must also be different at some point.



In devel, the raw HTML output looks like



... <pre class=3D"synopsis">

ALTER FOREIGN TABLE [ IF EXISTS ] [ ONLY ] ...



(with a line break)



but before it looks like



... <pre class=3D"synopsis">ALTER FOREIGN TABLE [ IF EXISTS=
 ] [ ONLY ] ...



(without a line break).



So maybe some part of the processing code thinks it should do some kind

of "indentation" here.


<=
br>
I think I found the problem, and pushed a fix for it. Basical=
ly it turns off indentation completely on pre-11 versions., I elected to ke=
ep indention on dev because it works there, and it makes debugging any of t=
he formatting a lot easier.

I've pushed the fi=
x and reloaded the 10 docs. I have not reloaded earlier branches yet, but I=
'd be interested in some people reviewing a bunch of pages in the 10 do=
cs mainly to see if (1) it fixes all the cases, and (2) it actually breaks =
some *other* cases.=C2=A0


-- =C2=A0Magnus Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: =
https://www.re=
dpill-linpro.com/


--089e0823b0d4679ce60568f17473--




From peter.eisentraut@2ndquadrant.com Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3NLA-0000Fh-1E
	for pgsql-docs@arkaria.postgresql.org; Tue, 03 Apr 2018 14:55:16 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f3NL9-0003qu-1D
	for pgsql-docs@arkaria.postgresql.org; Tue, 03 Apr 2018 14:55:15 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3NL8-0003qP-O5
	for pgsql-docs@lists.postgresql.org; Tue, 03 Apr 2018 14:55:14 +0000
Received: from out5-smtp.messagingengine.com ([66.111.4.29])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3NL1-0001bp-Dz; Tue, 03 Apr 2018 14:55:13 +0000
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47])
	by mailout.nyi.internal (Postfix) with ESMTP id 9982820D87;
	Tue,  3 Apr 2018 10:55:04 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
  by compute7.internal (MEProxy); Tue, 03 Apr 2018 10:55:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=cc:content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=UrEk7C
	fe0GYWJ5+oo1LaKVtMw1lG4f0YLXW7IBOjL7w=; b=KKpcDUDmUB2ktuhquCAWDr
	EpxbRolSsIsi0/l+RLhFOO0YBkGQHHiE24yH80oyrgQdv+H4Hsjoe10Xa03qflgo
	2JHHN0xKb//qhFjhVojNPmhCRdfxCuGaRc3XApKxZOxF7Zi0k8Vj1qhWdBm5vlcB
	fw6gHyF3DQnlfd4TC1J7OmY4P+3bOmecfN/em5rpd2gEzGHJ9ZPj+cq5qYZHhBVL
	yrRDFbl5jT4HivK77NWLQ5I6gsG51GzsMSEY4F+tngRHVhqQqABjkYrVemuYjINz
	+BOeKFeE5puFiC77gnbDcd/rX6Dj05uIVXhBfoe5stq1/6iWxSFHsovp+i+p7qxw
	==
X-ME-Sender: 
Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39])
	by mail.messagingengine.com (Postfix) with ESMTPA id 47942E5096;
	Tue,  3 Apr 2018 10:55:04 -0400 (EDT)
Subject: Re: Blanks in the first line before the first word in the code boxes
To: Magnus Hagander 
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
 
 <60a39b28-485e-1621-79af-fa01cf43b3c6@2ndquadrant.com>
 
Cc: Tom Lane , "Jonathan S. Katz" ,
 Daniel Westermann ,
 pgsql-docs 
From: Peter Eisentraut 
Organization: 2ndQuadrant
Message-ID: <3f249760-fdf7-edb5-d927-6d5a4a1754d0@2ndquadrant.com>
Date: Tue, 3 Apr 2018 10:55:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: 
 
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

On 4/3/18 09:12, Magnus Hagander wrote:
> I've pushed the fix and reloaded the 10 docs. I have not reloaded
> earlier branches yet, but I'd be interested in some people reviewing a
> bunch of pages in the 10 docs mainly to see if (1) it fixes all the
> cases, and (2) it actually breaks some *other* cases. 

It looks correct now.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




From jkatz@postgresql.org Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3iML-0000JJ-BT
	for pgsql-docs@arkaria.postgresql.org; Wed, 04 Apr 2018 13:21:53 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f3iMK-0002qR-89
	for pgsql-docs@arkaria.postgresql.org; Wed, 04 Apr 2018 13:21:52 +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_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3iMK-0002qG-24
	for pgsql-docs@lists.postgresql.org; Wed, 04 Apr 2018 13:21:52 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3iMC-0006Fu-HU
	for pgsql-docs@postgresql.org; Wed, 04 Apr 2018 13:21:51 +0000
Received: from pool-98-116-99-252.nycmny.fios.verizon.net ([98.116.99.252]
 helo=ph33r-retina.home)
	by meldrar.postgresql.org with esmtpsa
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3iM7-0006EA-Fi; Wed, 04 Apr 2018 13:21:42 +0000
From: "Jonathan S. Katz" 
Message-Id: 
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_1070809B-3A47-4978-98BD-1F26B9065329"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Blanks in the first line before the first word in the code boxes
Date: Wed, 4 Apr 2018 09:21:32 -0400
In-Reply-To: <3f249760-fdf7-edb5-d927-6d5a4a1754d0@2ndquadrant.com>
Cc: Magnus Hagander ,
 Tom Lane ,
 Daniel Westermann ,
 pgsql-docs 
To: Peter Eisentraut 
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
 
 <60a39b28-485e-1621-79af-fa01cf43b3c6@2ndquadrant.com>
 
 <3f249760-fdf7-edb5-d927-6d5a4a1754d0@2ndquadrant.com>
X-Mailer: Apple Mail (2.3273)
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk


--Apple-Mail=_1070809B-3A47-4978-98BD-1F26B9065329
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Apr 3, 2018, at 10:55 AM, Peter Eisentraut =
 wrote:
>=20
> On 4/3/18 09:12, Magnus Hagander wrote:
>> I've pushed the fix and reloaded the 10 docs. I have not reloaded
>> earlier branches yet, but I'd be interested in some people reviewing =
a
>> bunch of pages in the 10 docs mainly to see if (1) it fixes all the
>> cases, and (2) it actually breaks some *other* cases.=20
>=20
> It looks correct now.

+1

Did a spot check on known broken pages and chose some others at
random. Viewed the 9.6, 10, and devel versions.  10 and devel both
looked correct, and the 9.6 was broken where expected.

The only thing I saw (and this may be something to look at the SGML
source) was some blocks that looked overly indented, but it was =
consistent
across all versions.  On

https://www.postgresql.org/docs/current/static/queries-with.html =


If you search for "WITH RECURSIVE search_graph(id, link, data, depth)=E2=80=
=9D
the expression in the CTE is much more indented than similar CTEs above
it.

IMV I would not let this stop us from reloading the earlier versions as =
that
indentation is consistent across all versions (including 9.6, where it =
has the
initial indentation as well).

Jonathan



--Apple-Mail=_1070809B-3A47-4978-98BD-1F26B9065329
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8


On Apr 3, 2018, at 10:55 AM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:

On =
4/3/18 09:12, Magnus Hagander wrote:
I've pushed the fix and reloaded the 10 docs. I =
have not reloaded
earlier branches yet, but I'd be =
interested in some people reviewing a
bunch of pages in =
the 10 docs mainly to see if (1) it fixes all the
cases, =
and (2) it actually breaks some *other* cases. 

It looks correct =
now.

+1

Did a spot check on known broken pages and chose =
some others at
random. Viewed the 9.6, 10, and devel versions. =
 10 and devel both
looked correct, and the 9.6 was broken =
where expected.

The only thing I saw =
(and this may be something to look at the SGML
source) was =
some blocks that looked overly indented, but it was =
consistent
across all versions.  On

https://www.postgresql.org/docs/current/static/queries-with.htm=
l

If you search for "WITH =
RECURSIVE search_graph(id, link, data, depth)=E2=80=9D
the =
expression in the CTE is much more indented than similar CTEs =
above
it.

IMV I would not =
let this stop us from reloading the earlier versions as =
that
indentation is consistent across all versions (including =
9.6, where it has the
initial indentation as =
well).

Jonathan


=

--Apple-Mail=_1070809B-3A47-4978-98BD-1F26B9065329--




From magnus@hagander.net Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3p2i-00056S-Tn
	for pgsql-docs@arkaria.postgresql.org; Wed, 04 Apr 2018 20:30:05 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f3p2h-00046U-Gs
	for pgsql-docs@arkaria.postgresql.org; Wed, 04 Apr 2018 20:30:03 +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_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3p2h-00046I-Ak
	for pgsql-docs@lists.postgresql.org; Wed, 04 Apr 2018 20:30:03 +0000
Received: from mail-wr0-x241.google.com ([2a00:1450:400c:c0c::241])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3p2d-0000cD-R3
	for pgsql-docs@postgresql.org; Wed, 04 Apr 2018 20:30:02 +0000
Received: by mail-wr0-x241.google.com with SMTP id l49so24795664wrl.4
        for ; Wed, 04 Apr 2018 13:29:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=hagander-net.20150623.gappssmtp.com; s=20150623;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=xKNMJuB32M+kFfN+LgFS9/TiC1A8EcVkttdpKTq4Hwg=;
        b=irOWQIyIu2z4qs0w3LtMbC305okQsPEKkvZNZf4KcRxyDJD8pYUYErAGOwTBcK49js
         9yoAdCK9ytjz26RsRJ7QVpILNo7u7OZnDRrGnF02GBiFV1lGNwZ9ywXLu61dLgw1fEgj
         AoLYztmm7PtDZey85+DmnqKhO5gnpycAKHGXCZHtyi5nUErkjenF94Lqw3DTfCnJ1sFB
         WALEU1VaP2q9OVZyno5A+I/gFqNNk1RkxV4GjLhOXfFaT680ht/ip9hfngnsRrTPwxFR
         fakdfgIrt4C7De2kUBjIGOFaMbdP1j8iYbMbZJXC6ObcWFQDbxlGWgQ9gaQ0VB/lmJgo
         Y5dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=xKNMJuB32M+kFfN+LgFS9/TiC1A8EcVkttdpKTq4Hwg=;
        b=g5wdtschY9crgqqBiMvFHCyLYhPnZGsautL2PX+dxSipt5MFLzm/n+fMhxAjthcUym
         HR+6t7d8yXDpcxsRSh7n6OUThNxc5+eweGNVruPS/K25eRRpHjCaA0Ns9hxHducN50Gw
         pP4ANPym5YdsEL6l6c3F3ar+LT5xdyN1cBXw68H4Yr5OjRL0ckzSGWC7TlnNB4IUGC23
         jJArk+ZVMKji5eh4nQLaeAQMjSbBq47v9My2tpNWQKomx+uOveApsQbEEXbZkrRwaJHw
         vv/NId89FQNqR7KQTYEktEIGg3AD9VYDTWgjzKznEUXPtUwH+E8hK7yWzmN+WaSG+QmC
         vQgA==
X-Gm-Message-State: ALQs6tBMaBn1ypJGdwFRhWv45JEHi6MT8zxyRMS/rrPJrrLjVOHr6tkO
	UZvSVFJ/oOFAkdRtAWYw5CdeearYziH5AQiVi4cpbA==
X-Google-Smtp-Source: 
 AIpwx4+BUcOeURpYl1B6ymW+ld4EwpBuPbYBmX/wV+yq0DXBYjEVNwZGmr+qsHeisOSgkyfZFt0aoqDI3wTkWJO/LA0=
X-Received: by 2002:a19:6919:: with SMTP id
 e25-v6mr11733336lfc.52.1522873798397;
 Wed, 04 Apr 2018 13:29:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:9748:0:0:0:0:0 with HTTP;
 Wed, 4 Apr 2018 13:29:57 -0700 (PDT)
In-Reply-To: 
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
 
 <60a39b28-485e-1621-79af-fa01cf43b3c6@2ndquadrant.com>
 
 <3f249760-fdf7-edb5-d927-6d5a4a1754d0@2ndquadrant.com>
 
From: Magnus Hagander 
Date: Wed, 4 Apr 2018 22:29:57 +0200
Message-ID: 
 
Subject: Re: Blanks in the first line before the first word in the code boxes
To: "Jonathan S. Katz" 
Cc: Peter Eisentraut ,
 Tom Lane ,
	Daniel Westermann ,
 pgsql-docs 
Content-Type: multipart/alternative; boundary="000000000000caa90105690baf5c"
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

--000000000000caa90105690baf5c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 4, 2018 at 3:21 PM, Jonathan S. Katz 
wrote:

>
> On Apr 3, 2018, at 10:55 AM, Peter Eisentraut <
> peter.eisentraut@2ndquadrant.com> wrote:
>
> On 4/3/18 09:12, Magnus Hagander wrote:
>
> I've pushed the fix and reloaded the 10 docs. I have not reloaded
> earlier branches yet, but I'd be interested in some people reviewing a
> bunch of pages in the 10 docs mainly to see if (1) it fixes all the
> cases, and (2) it actually breaks some *other* cases.
>
>
> It looks correct now.
>
>
> +1
>
> Did a spot check on known broken pages and chose some others at
> random. Viewed the 9.6, 10, and devel versions.  10 and devel both
> looked correct, and the 9.6 was broken where expected.
>
> The only thing I saw (and this may be something to look at the SGML
> source) was some blocks that looked overly indented, but it was consisten=
t
> across all versions.  On
>
> https://www.postgresql.org/docs/current/static/queries-with.html
>
> If you search for "WITH RECURSIVE search_graph(id, link, data, depth)=E2=
=80=9D
> the expression in the CTE is much more indented than similar CTEs above
> it.
>
> IMV I would not let this stop us from reloading the earlier versions as
> that
> indentation is consistent across all versions (including 9.6, where it ha=
s
> the
> initial indentation as well).
>
>
I've reloaded docs back to 9.3.


--=20
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/ 

--000000000000caa90105690baf5c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable



On Wed, Apr 4, 2018 at 3:21 PM, Jonathan S. Katz <=
jkatz@postgresql.=
org> wrote:

On Apr 3, 2018, at 10:55 AM, Peter Eisentraut <peter.eisentraut@2ndquadran=
t.com> wrote:

On 4/3/18 09:12, Magnus Hagander wrote:
I've pushed the fix and reloaded the 10 docs. I h=
ave not reloaded
earlier branches yet, but I'd be interested in some=
 people reviewing a
bunch of pages in the 10 docs mainly to see if (1) i=
t fixes all the
cases, and (2) it actually breaks some *other* cases.=C2=
=A0

It looks correct now.

<=
/div>+1

Did a spot check on known brok=
en pages and chose some others at
random. Viewed the 9.6, 10, and=
 devel versions. =C2=A010 and devel both
looked correct, and the =
9.6 was broken where expected.

The only thing I sa=
w (and this may be something to look at the SGML
source) was some=
 blocks that looked overly indented, but it was consistent
across=
 all versions.=C2=A0 On

https:=
//www.postgresql.org/docs/current/static/queries-with.html
If you search for "WITH RECURSIVE search_graph(=
id, link, data, depth)=E2=80=9D
the expression in the CTE is much=
 more indented than similar CTEs above
it.

IMV I would not let this stop us from reloading the earlier versions as =
that
indentation is consistent across all versions (including 9.6=
, where it has the
initial indentation as well).


I've reloaded docs back to 9.3.=C2=A0


-- 
=C2=A0Magnus Ha=
gander
=C2=A0Me: =
https://www.hagander.net/
=C2=A0Work: https://www.redpill-linpro.com/


--000000000000caa90105690baf5c--




From peter.eisentraut@2ndquadrant.com Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3tFJ-0007bg-3a
	for pgsql-docs@arkaria.postgresql.org; Thu, 05 Apr 2018 00:59:21 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f3tFI-0001xF-1Z
	for pgsql-docs@arkaria.postgresql.org; Thu, 05 Apr 2018 00:59:20 +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_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3tFH-0001x5-1k
	for pgsql-docs@lists.postgresql.org; Thu, 05 Apr 2018 00:59:19 +0000
Received: from out5-smtp.messagingengine.com ([66.111.4.29])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3tFD-0006wV-7h; Thu, 05 Apr 2018 00:59:18 +0000
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47])
	by mailout.nyi.internal (Postfix) with ESMTP id 85ACF21ECA;
	Wed,  4 Apr 2018 20:59:13 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
  by compute7.internal (MEProxy); Wed, 04 Apr 2018 20:59:13 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=cc:content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Cud8Ff
	c35wj9XbfeT2h/f7xf8/ReovNdO+rhWl70g7U=; b=mt2/1dAEKMR9kQQLwRdxku
	F3DhVQbQhOxrN/rKTpwChP4qLQW910BTqFOOQy2IT3FaW1NIhvJPy7lusnTIOC2u
	rxFMQmB2ipYIf8FHAb1BPv4wO7N/UNtoy4+YNK7LMGKeu74pZ9LkAk7fmAqoo9KV
	Snmf2jQKJaAb6a8MqXITVURapm7RZh+tD8sXPpiS2FUmndiKU+4/0Fyxy5dsHBzh
	3SVhQIMNQLrhz/A4qtLTeoVLbdcYxCbPBdlcLsz9zW9tU5q8bmWUDOEBPCT9//Hk
	CrBWdgmhBzKhSWBJHw3kwXM2nGsuyfsSAG7WBGB9BsgSCAOqEK+XRzvyAvxX5mDw
	==
X-ME-Sender: 
Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39])
	by mail.messagingengine.com (Postfix) with ESMTPA id 2CA7510260;
	Wed,  4 Apr 2018 20:59:13 -0400 (EDT)
Subject: Re: Blanks in the first line before the first word in the code boxes
To: "Jonathan S. Katz" 
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
 
 <60a39b28-485e-1621-79af-fa01cf43b3c6@2ndquadrant.com>
 
 <3f249760-fdf7-edb5-d927-6d5a4a1754d0@2ndquadrant.com>
 
Cc: Magnus Hagander , Tom Lane ,
 Daniel Westermann ,
 pgsql-docs 
From: Peter Eisentraut 
Organization: 2ndQuadrant
Message-ID: <8168ffec-3a23-af64-f9a2-6d8c8b1f2358@2ndquadrant.com>
Date: Wed, 4 Apr 2018 20:59:12 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: 
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk

On 4/4/18 09:21, Jonathan S. Katz wrote:
> The only thing I saw (and this may be something to look at the SGML
> source) was some blocks that looked overly indented, but it was consistent
> across all versions.  On
> 
> https://www.postgresql.org/docs/current/static/queries-with.html
> 
> If you search for "WITH RECURSIVE search_graph(id, link, data, depth)”
> the expression in the CTE is much more indented than similar CTEs above
> it.

This was that way in the source.  Probably originally 8-space tabs.
I've fixed it now.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




From jkatz@postgresql.org Fri May  22 02:06:22 2026
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3tPw-0008M3-DB
	for pgsql-docs@arkaria.postgresql.org; Thu, 05 Apr 2018 01:10:20 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from )
	id 1f3tPv-0007cl-A6
	for pgsql-docs@arkaria.postgresql.org; Thu, 05 Apr 2018 01:10:19 +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_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3tPv-0007bm-3s
	for pgsql-docs@lists.postgresql.org; Thu, 05 Apr 2018 01:10:19 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3tPr-0007DG-Sk
	for pgsql-docs@postgresql.org; Thu, 05 Apr 2018 01:10:18 +0000
Received: from pool-98-116-99-252.nycmny.fios.verizon.net ([98.116.99.252]
 helo=ph33r-retina.home)
	by meldrar.postgresql.org with esmtpsa
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from )
	id 1f3tPm-0002sq-H2; Thu, 05 Apr 2018 01:10:13 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Blanks in the first line before the first word in the code boxes
From: "Jonathan S. Katz" 
In-Reply-To: <8168ffec-3a23-af64-f9a2-6d8c8b1f2358@2ndquadrant.com>
Date: Wed, 4 Apr 2018 21:10:06 -0400
Cc: Magnus Hagander ,
 Tom Lane ,
 Daniel Westermann ,
 pgsql-docs 
Content-Transfer-Encoding: quoted-printable
Message-Id: <5CB17727-5BFE-4455-930A-89882B2432BE@postgresql.org>
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 
 
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 
 <13425.1522330858@sss.pgh.pa.us>
 
 <60a39b28-485e-1621-79af-fa01cf43b3c6@2ndquadrant.com>
 
 <3f249760-fdf7-edb5-d927-6d5a4a1754d0@2ndquadrant.com>
 
 <8168ffec-3a23-af64-f9a2-6d8c8b1f2358@2ndquadrant.com>
To: Peter Eisentraut 
X-Mailer: Apple Mail (2.3273)
List-Id: 
List-Help: 
List-Subscribe: 
List-Post: 
List-Owner: 
List-Archive: 
Precedence: bulk


> On Apr 4, 2018, at 8:59 PM, Peter Eisentraut =
 wrote:
>=20
> On 4/4/18 09:21, Jonathan S. Katz wrote:
>> The only thing I saw (and this may be something to look at the SGML
>> source) was some blocks that looked overly indented, but it was =
consistent
>> across all versions.  On
>>=20
>> https://www.postgresql.org/docs/current/static/queries-with.html
>>=20
>> If you search for "WITH RECURSIVE search_graph(id, link, data, =
depth)=E2=80=9D
>> the expression in the CTE is much more indented than similar CTEs =
above
>> it.
>=20
> This was that way in the source.  Probably originally 8-space tabs.

That was my hunch, but wanted to be triple-sure.

> I've fixed it now.

Awesome. Thanks!

Jonathan