Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1joY4o-0007G4-0j for pgsql-docs@arkaria.postgresql.org; Thu, 25 Jun 2020 20:02:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1joY4m-0008O5-LX for pgsql-docs@arkaria.postgresql.org; Thu, 25 Jun 2020 20:02:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1joY4m-0008Ny-Af for pgsql-docs@lists.postgresql.org; Thu, 25 Jun 2020 20:02:24 +0000 Received: from mail-qk1-x735.google.com ([2607:f8b0:4864:20::735]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1joY4f-0006WA-1y for pgsql-docs@lists.postgresql.org; Thu, 25 Jun 2020 20:02:23 +0000 Received: by mail-qk1-x735.google.com with SMTP id l6so6657700qkc.6 for ; Thu, 25 Jun 2020 13:02:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=XU9xuTr4fit7MUM30jEchLD40NAMFUJINDaCry17r5s=; b=kNnKeDlgXgL46cCdzsuZ3FoxbK6E8vBEGFOc0UReBmhCR2BhaEttNpKFrtAQLKOxUG qVTN9KnK+gePXB2yUiY+iasp0yOpQdmgOaW4M49ZkW5VUHvnIbBPFk+SRga53O1n4RTe B6IsB4TvQkCH4KpMtQg3Xl1BQdBjuVrTJlLjTVuMqRjorsgfvbk77x4bwiwSWhrQ2euJ 0DynLga27w/1dNzg5kesBjvDK5f7ZfZcQZRZ5sYa3VfdvxFSeyUkHO/3jnNHB0qOkXmT g+tsN+gssrGm6aimhdus3y/KbCQ5VFNYkD7eOLW4UJ4XLPI8K3kQYwdIVaaKPby86AFI XvEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=XU9xuTr4fit7MUM30jEchLD40NAMFUJINDaCry17r5s=; b=CANps1NEppsLdkQqyNESk8oLb9BRWUOT7AbaSB96trZk+PpEfGdYLOAj0M3AVVIiPj 09YHpGZeVv8HVuxRbXmqYLp3oi8clytCN940gpDuzqVNM/cGPDwjq6t0CbEBIvIZ4l/+ LjYqnl6HlluDmUb9SAHVetUpqaGTRrZJEY0TjGcqlNaM4TbYxEkX54viep167Wb4gEqz avYsv9BsMhawSr3AEYFTCDuaepI1cb6XMhIZKGv1y8aqX8FxpQVW25J8Juja6V8Xmlh0 6m0cbHmj50k96Rjb1DmvA6q/Sp5rUdjUgua5umsAG06BUKiuv7mR2PLVYAVnO0RT1NY2 Pc4g== X-Gm-Message-State: AOAM530tMX/UlKp7ZuSU4I+TnBBRYcWPd0OfvPO73aK4d/okxqq3b2iK RbSsBn++79kH7m+82Uy4izZEPQ== X-Google-Smtp-Source: ABdhPJzJHdlVcczm5JBKSv7dayST+lCErcYpzxEW0L8xHh68oh34fdjygukVRrVVwU5pwXGvW/i2Xw== X-Received: by 2002:a37:6295:: with SMTP id w143mr21935844qkb.486.1593115335274; Thu, 25 Jun 2020 13:02:15 -0700 (PDT) Received: from perhan.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id x57sm2468882qtk.19.2020.06.25.13.02.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 25 Jun 2020 13:02:14 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id CD3B42A3AC7; Thu, 25 Jun 2020 16:02:12 -0400 (-04) Date: Thu, 25 Jun 2020 16:02:12 -0400 From: Alvaro Herrera To: Steven Pousty Cc: Bruce Momjian , pgsql-docs@lists.postgresql.org Subject: Re: Please add a link to [BRIN] physical block ranges of a table Message-ID: <20200625200212.GA1570@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Jun-25, Steven Pousty wrote: > I like the direction as well as long as each of the items in the glossary > has an anchor and you can link to it from the rest of the documents. It has. > The reader, if they are confused by the term, should be able to go get > a quick definition without having to remember there is a glossary and > then search for the term. I cannot help people with incurable ADHD, so I hope your readers can achieve clicking a page, reading the definition they're interested in, and going back to whatever page they were reading originally. If they're too easily distracted reading the rest of the glossary, they may never return to the original page anyway. > I think you actually said that but I want to confirm. If so then you would > like me to: > 1. Add the text " physical block range " to acronym page Yes. > 2. Make it anchor so I can link to it directly If you follow the neighboring terms layout, this should be painless. > 3. Add the definition, which can include links to external sites Yes. What external sites are you thinking of, particularly to define the BRIN terms? > 4. Then turn the link on the original page to the anchor I created for > Physical block range. Yes. > Is that the correct flow? Will this require me building all the docs on my > machine? I think the chances of people editing the DocBook sources with zero mistakes without a way to compile them is very close to zero, so yes. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services