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 1j2mcT-0003Ia-8m for pgsql-docs@arkaria.postgresql.org; Sat, 15 Feb 2020 01:51:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j2mcR-0002d9-RU for pgsql-docs@arkaria.postgresql.org; Sat, 15 Feb 2020 01:51:43 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j2mcR-0002ZG-GA for pgsql-docs@lists.postgresql.org; Sat, 15 Feb 2020 01:51:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j2mcP-0003Li-4H; Sat, 15 Feb 2020 01:51:42 +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 01F1pdpp017446; Fri, 14 Feb 2020 20:51:39 -0500 From: Tom Lane To: "Jonathan S. Katz" cc: Peter Geoghegan , Pg Docs Subject: Re: Duplicating website's formatting in local doc builds In-reply-to: <8d663c68-3df0-bf3f-8c2e-e6897a55394a@postgresql.org> References: <1375.1581446233@sss.pgh.pa.us> <3873.1581449531@sss.pgh.pa.us> <4b44c4ec-a678-6586-fbb0-efc3299af203@postgresql.org> <86f03290-e60c-855e-786a-d1b75c254811@postgresql.org> <716a39ec-6f56-0280-8d4b-b246176c6a3d@postgresql.org> <11007.1581721578@sss.pgh.pa.us> <8d663c68-3df0-bf3f-8c2e-e6897a55394a@postgresql.org> Comments: In-reply-to "Jonathan S. Katz" message dated "Fri, 14 Feb 2020 20:21:23 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17444.1581731499.1@sss.pgh.pa.us> Date: Fri, 14 Feb 2020 20:51:39 -0500 Message-ID: <17445.1581731499@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "Jonathan S. Katz" writes: > A potential solution is that we drop the use of "monospace" in relying > on the OS default and just pick a font. I would say that this is outside > the scope of the patch that's being proposed, but certainly something to > look into on the pgweb side given we're creating an inconsistent > cross-browser experience. Agreed, not in-scope for this patch. >> The point about network access seems to me to be sufficient reason not >> to make it the default. I'd actually say that we ought to annotate >> section J.3.1 to point out that "make STYLE=website" will result in >> that. However, I'm not quite clear on whether that means external >> access during viewing, or during build, or both? The note should say. > It would only be during viewing -- the build just puts the URL into the > HTML file. OK. > But don't take my word for it, please see the attached patch ;) Hm, I wouldn't go into that much detail; it'd likely soon be out of date anyway. I had in mind something more like "If the STYLE=website option is used, the generated HTML files will include references to stylesheets hosted at www.postgresql.org, so that viewing them will require network access." regards, tom lane