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 1inN6v-0001HH-68 for pgsql-docs@arkaria.postgresql.org; Fri, 03 Jan 2020 13:35:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1inN6t-0008Nm-PP for pgsql-docs@arkaria.postgresql.org; Fri, 03 Jan 2020 13:35:27 +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 1inN6t-0008Nd-Hx for pgsql-docs@lists.postgresql.org; Fri, 03 Jan 2020 13:35:27 +0000 Received: from mail-qt1-x844.google.com ([2607:f8b0:4864:20::844]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1inN6q-0001sr-RX for pgsql-docs@lists.postgresql.org; Fri, 03 Jan 2020 13:35:27 +0000 Received: by mail-qt1-x844.google.com with SMTP id d18so34148260qtj.10 for ; Fri, 03 Jan 2020 05:35:24 -0800 (PST) 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=oLzhlNdEolO4Z/TgMMdkP7EsMrtr+zNHB7m6Fndo9us=; b=xzDdRyWf1lNHTkKyRi1D4u+J9ud0HbZq2QclU/9PSDmDgVpaWA8TtjiHwkytVX0rhQ AEqkU1tSW/1yzNc9GZ+X3iFI7981IzW/Pwf/KsIO8jV/sEspywCbVnwDlE3MMecSH1na faF851GBYJG9XCv7vPmX0JRY0hbS/UhHmTKiTfI1hFFKaL+tTDhyaPmTzpiTo0ICuddm 8GTUmEmxMO/J0VACgbaWUNd7D8OGV5uL86MIIkJ0TeE8k3pbGHiCShkJu7RfrX6g/aXB sbOuaDBTzqA3xAIXYa3182i89nW5rt+d/JGyFEGEyifcFO8YfDLqk7c/I//qyrBQhYsV QaPA== 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=oLzhlNdEolO4Z/TgMMdkP7EsMrtr+zNHB7m6Fndo9us=; b=ZTTMkVvSVwmVJmWPKmI1LSk0uwtt/T7h/PFtzs+2keavzsd0WB3bVvYZhk702F/Mi7 Nd1zY9Qwp7mm+ajQMbBMoDUgBvN37nDQvrjxy7S72UEdqivLeZb08Jx3YSJWiQmkozuD 6z7Tz8c1p8alRJwnrpsRZrH/kH+R8sUXUKFk6lPuI4nz1lEpGC9yXsmhxVl0Gca9utmy 7tzwOT2e20jaqMSSyF6WQy0uz/YHTJCbaHdelaeelsMXmFJHMWXHApvz5E4S0k+z4fy4 DBA+6t3IdWS41TELNwwwPQ8ywe8hNzYV01AYjDu1MEidZ/LbGwc4MLNGRDw29AEkeRGi zkRw== X-Gm-Message-State: APjAAAV0cdLnnBXbuvlH8RNEEhBxS5MTWZBNVjD2C0ucMRGkpsa1ac7d m61h9Wo/RdqDdqyTsTUrZL5+Hw== X-Google-Smtp-Source: APXvYqzGwUbln2zzTDw41hMn5JUSZDs465ilZN6t1T0iP5l5ZmKsBuUnRpxaJEOHGUSMnvDWUNtpyw== X-Received: by 2002:aed:3287:: with SMTP id z7mr62732373qtd.103.1578058523029; Fri, 03 Jan 2020 05:35:23 -0800 (PST) Received: from nimloth.alvh.no-ip.org ([190.95.19.128]) by smtp.gmail.com with ESMTPSA id z8sm18362255qth.16.2020.01.03.05.35.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 03 Jan 2020 05:35:22 -0800 (PST) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id A6B0430153D; Fri, 3 Jan 2020 10:35:20 -0300 (-03) Date: Fri, 3 Jan 2020 10:35:20 -0300 From: Alvaro Herrera To: helix84 Cc: pgsql-docs@lists.postgresql.org Subject: Re: doc: Add anchors in create_table.sgml Message-ID: <20200103133520.GA29959@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 Hi, On 2020-Jan-02, helix84 wrote: > Hi, I prefer to bookmark docs pointing to the exact term I need and > with pg docs it's often been the case that the exact term doesn't have > an anchor or only has unstable, generated anchors. So I would very > much like to add stable anchors in many more places. I haven't > contributed to pg before, so this patch is me testing the waters. If > there is interest, I'd like to add stable anchors to wherever we'll > agree it makes sense - preferably in an automated or semi-automated > way. > > I read an older thread on this topic [1] which links to a custom SGML > parser in Python for this specific task [2]. I have experience with > XSLT, but not so much with SGML processing, so I would appreciate if > you could point me whether a custom parser is the way to go for this > task or I should look into a more generic SGML processing tool. Ah, https://www.postgresql.org/message-id/AANLkTikAgIyYfwy_2Zj8GafoC7ZFlGv5iCdab1l7VuDp@mail.gmail.com (We prefer our own archive to GMane's.) That thread is so old that Peter feels the need to point out that the Git mirror was out of date with CVS ... I can no longer even remember the commit process for CVS anymore. We also converted from SGML to XML in the meantime, so you can probably make do with a standard XML parser without having to write a custom SGML one. (Daniele Varrazzo's patch ended up as 477319829c2e.) TBH I've felt the need for anchors for tags in the past also (IIRC the runtime-config page would be improved by them), but I'm not sure about adding them to every single keyword of every single reference page. Is that really useful? > Thanks in advance and let me take this opportunity to thank you all > for this wonderful piece of software. You're welcome. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services