Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e7bqY-0005CO-Ob for pgsql-docs@arkaria.postgresql.org; Thu, 26 Oct 2017 06:40:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e7bqX-00041G-AW for pgsql-docs@arkaria.postgresql.org; Thu, 26 Oct 2017 06:40:53 +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.84_2) (envelope-from ) id 1e7bq7-0003Mr-7S for pgsql-docs@postgresql.org; Thu, 26 Oct 2017 06:40:27 +0000 Received: from mail-lf0-x22f.google.com ([2a00:1450:4010:c07::22f]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1e7bpx-0002kO-HF for pgsql-docs@postgresql.org; Thu, 26 Oct 2017 06:40:25 +0000 Received: by mail-lf0-x22f.google.com with SMTP id b190so2488949lfg.9 for ; Wed, 25 Oct 2017 23:40:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=VwxLiePrgCSHWWeC+50QakpVcf5reVMVd4nUq4WPQvY=; b=qOPNly1qN2WliDAz4wQGup3gIM7wY2mR8PgF8Y5lR46oDw2aC0KgFjd6bhN2fh47Gm 5imhaoktDbx11AsGQpvgvZ3hWHnCQiiEufA4AJfOBm7Y7JYyD3Jmf9t0/MK+Uh9w9y6n h43ZClqqShri/aeaZuc5PaFZXdGCy9k5DHI4uhO1/lLGot0NXcyeWakFkatf8TdKwPJ2 P3tiolyYfoOpo9JddHBH+XeAFLyLG66yO0QC/TQfpp/WZtIsTK3QxCj5cO/H20hP42qV XNaFsbUUnv76n7QZIJZtwytmhzte5hnAH//eCk1vEenY26+ek4FiB9aaXOz8m7amTROd yE/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=VwxLiePrgCSHWWeC+50QakpVcf5reVMVd4nUq4WPQvY=; b=eskdufSbj3c4HEUwuSriLKjLE0VUhRefJOJKxSQhZ4eQrutECESYKafjW1/b+lyS+j wrmFqGeQArnsH4MJqSqA+d2APcEyBnYzOcOumAXwV48vCgPPrwzpuSdl2IASoJOsLt/e X1ErgS9i7POJZTqpVjWkhEzU1zbYjW+V8Frjc87ib9FxVTJmMOl6WfbmvYSZuOk1gzJZ 0mqHzVuKa3uLf4hwyAwksvDQsWCC5ZZ29o+hVObuUmH1St9EwhBIIyDgnw+v9XSgn04H tsNqSFj3gGs3XvGrJjwlEqGqICBtyImtgl/lBgpoqHfJ2venGVFwvu6w0PTUERIPv1Sw wIrw== X-Gm-Message-State: AMCzsaUmmRdyEuE/UPeGRRN7YWSTnzVQJxFnEGhWwzsDwZf7TE2mv45Y NzvCizaPTquZPsbdfVg7NPL05Q== X-Google-Smtp-Source: ABhQp+QzzAhZB6xzSTRPKYnyhNrtznt5xvdW9XcVSOAlzjGKabFQEuzW6ZKB4KoildPjbYR2enK9jQ== X-Received: by 10.25.168.2 with SMTP id r2mr7288542lfe.103.1509000013721; Wed, 25 Oct 2017 23:40:13 -0700 (PDT) Received: from [1.0.0.7] ([178.155.4.15]) by smtp.gmail.com with ESMTPSA id a73sm1225240ljf.6.2017.10.25.23.40.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Oct 2017 23:40:12 -0700 (PDT) Subject: Re: with To: Tom Lane Cc: Alvaro Herrera , Pg Docs References: <20170315160525.42x4wxtdhk3sa522@alvherre.pgsql> <6f1a6a95-d36e-8c9e-e0d1-3e273793ad9a@gmail.com> <23010.1508963000@sss.pgh.pa.us> From: Alexander Lakhin Message-ID: <54391dfd-7f17-ead6-76be-0957ec2e67cb@gmail.com> Date: Thu, 26 Oct 2017 09:40:11 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <23010.1508963000@sss.pgh.pa.us> Content-Type: multipart/mixed; boundary="------------8467B41A4AA7E08FC0638484" Content-Language: en-US List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org This is a multi-part message in MIME format. --------------8467B41A4AA7E08FC0638484 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello Tom, 25.10.2017 23:23, Tom Lane writes: > >> 2. To remove @zone specification from indexterm's. >> Are there any reasons to specify it explicitly? > According to my understanding, the use of "zone" means that the > indexterm entry refers to the whole section named by the "zone" label, > not only the physical point the entry is at. So I think our usage > is correct in principle; for example, this would allow an index entry > to say something like "Section 4.2" not just "page 435". In practice, > though, the distinction seems merely pedantic: AFAICS it does not > affect either HTML output (which always gives you a hyperlink to the > containing section) or PDF output (which always gives you a page number). There is also the Docbook parameter "index.links.to.section" ( http://docbook.sourceforge.net/release/xsl/1.79.1/doc/html/index.links.to.section.html ) which affects the pedanticism of the distinction. > So we could run around and remove the zone tags, but that still seems > like rather a grotty answer --- maybe someday we'd want them back, > if the doc toolchain were ever improved to make effective use of them. > > How complicated is the "customize the xsl template" solution? > > (BTW, I do not see the extra-entries bug at all in PDF output.) Yes, the issue is with html/autoidx.xsl only. I would choose to customize xsl for now, though the corresponding docbook templates are not very human-friendly (for xhtml/autoidx.xsl they are autogenerated from html/autoidx). See the patch attached. (May be we might reformat it slightly.) The commands used to generate the patch are more simpler: wget http://docbook.sourceforge.net/release/xsl/1.79.1/xhtml/autoidx.xsl -O - | grep -Pzo '(?s)(.*?)\s' | sed -e "s/\x0//" -e "s/\$refs\[@zone != '' or generate-id()/\$refs[generate-id()/" >> stylesheet-html-common.xsl perl -0777 -i -pe 's#\n##' stylesheet-html-common.xsl; echo -e '\n' >>stylesheet-html-common.xsl Nonertheless, it might be better solution as we can leave all the zone references intact and preserve the freedom to change our mind later. Best regards, ------ Alexander Lakhin Postgres Professional: http://www.postgrespro.com The Russian Postgres Company --------------8467B41A4AA7E08FC0638484 Content-Type: text/x-patch; name="fix-html-autoidx.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="fix-html-autoidx.patch" diff --git a/doc/src/sgml/stylesheet-html-common.xsl b/doc/src/sgml/stylesh= eet-html-common.xsl index 72fac1e..af22f43 100644 --- a/doc/src/sgml/stylesheet-html-common.xsl +++ b/doc/src/sgml/stylesheet-html-common.xsl @@ -263,4 +263,253 @@ set toc,title =20 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ + + + + + + + + + + + + + +
+
+
+ + +
+ + + + + + + + + + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+
+ + + + + + + + + + + + + + +
+
+
+ + +
+ + + + + + + + + + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+
+ + + + + + + +
+
+
+ + +
+ + + + --------------8467B41A4AA7E08FC0638484 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs --------------8467B41A4AA7E08FC0638484--