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 1ghpER-0000Wd-D7 for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Jan 2019 05:19:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ghpEP-0007fE-9q for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Jan 2019 05:19:45 +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 1ghpEO-0007f7-VS for pgsql-hackers@lists.postgresql.org; Fri, 11 Jan 2019 05:19:45 +0000 Received: from bay.acenet.us ([173.230.252.50]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ghpEI-0004Vw-Dn for pgsql-hackers@postgresql.org; Fri, 11 Jan 2019 05:19:43 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anastigmatix.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=i0Ll7ayO92b6VJrpOxjWpWgQ6rF1ZXaFpno4PX8daK8=; b=H68kYEZRnbm+yLzlgf+bKUYIQ7 gQw1eXlSh3Pk2jE9SqZX605vJC489h8+GoQYXUnjrC77bwKE5cm3Ow4olL3ae0Qd+D0AVfZz9qlZP PnimEBh2weAKxmbaJb1CeESAToFqC4AqoZOVC3QQSg5pDTzzSO/n85ZpqiUdBZL9QvSFecTBKyUwb wr2JpE0CJC7n5MDB1K+VJCbdQ+j9H9L5DmutMkFO6fvz/2cL1/ahDBpMyeAqXZngh38J2GRH9cPFf e8MGuijmbj7dkLb6y0SBPzgwALNO4KIfBZKSvDFzty1hCfGw/pVsvNcgzcIRcP+oKjYcHZwcfASLF aIXqp5qg==; Received: from [192.182.57.242] (port=58836) by bay.acenet.us with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1ghpEF-001egb-Hf; Fri, 11 Jan 2019 00:19:36 -0500 Subject: Re: doc: where best to add ~ 400 words to the manual? To: Pavel Stehule References: <20181025194720.ylmw64xqlnjr5wja@alvherre.pgsql> <45C74339-3531-46BD-A595-37183C6730A1@winand.at> <5C283168.8060001@anastigmatix.net> <5C291741.9060506@anastigmatix.net> <5C298BCB.4060704@anastigmatix.net> <5C382028.8020704@anastigmatix.net> Cc: Markus Winand , Alvaro Herrera , Tom Lane , PostgreSQL Hackers From: Chapman Flack X-Enigmail-Draft-Status: N1110 Message-ID: <5C382766.2080409@anastigmatix.net> Date: Fri, 11 Jan 2019 00:19:34 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <5C382028.8020704@anastigmatix.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-96.8 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bay.acenet.us X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anastigmatix.net X-Get-Message-Sender-Via: bay.acenet.us: authenticated_id: chap@anastigmatix.net X-Authenticated-Sender: bay.acenet.us: chap@anastigmatix.net X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 01/10/19 23:48, Chapman Flack wrote: > On 12/30/18 22:23, Chapman Flack wrote: > (3) seems to be supported by (the only) precedent, the "Limits and > Compatibility" sect3 within functions-posix-regexp. > > So, absent objection, I'll work on a Limits and Compatibility sect2 > within functions-xml. One fly in the ointment: tables of contents seem to list sect1 and sect2 elements, but not sect3. So the "Limits and Compatibility" sect3 under functions-posix-regexp does not clutter the overall "Functions and Operators" ToC, but a "Limits and Compatibility" sect2 under functions-xml would be visible there. Tucking it as a sect3 within an existing sect2 would prevent that, but it is common information that pertains to more than one of them, so that doesn't seem quite right. Or is it ok to have a "Limits and Compatibility" visible in the ToC under XML Functions? -Chap