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 1lRXT5-0005cs-OJ for pgsql-docs@arkaria.postgresql.org; Wed, 31 Mar 2021 09:48:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lRXT4-00071K-Ls for pgsql-docs@arkaria.postgresql.org; Wed, 31 Mar 2021 09:48:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lRXT4-00070X-GW for pgsql-docs@lists.postgresql.org; Wed, 31 Mar 2021 09:48:54 +0000 Received: from mail-ed1-x529.google.com ([2a00:1450:4864:20::529]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lRXT0-0005Ya-Ub for pgsql-docs@lists.postgresql.org; Wed, 31 Mar 2021 09:48:53 +0000 Received: by mail-ed1-x529.google.com with SMTP id x21so21541378eds.4 for ; Wed, 31 Mar 2021 02:48:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=fXNL+QoMinc82qzY8ZQNJpjIeexDaPjDD5Ij27UUKjs=; b=jznxhvJ0lDeE65Opb+DFuu9a8rDO3sBWxq0Vw1D77RX4StgTrt2ShSn7oMMVRdFHJN +MWm0rB4FYjQO2xLb3PSRlecWRqqBiRLFHR4hGR04mTwUnCCBz/S2PLFc/fnVU/7WcGg WCtK3pOiOEpmY6I0S77dSsjIvijDrRRgIA/2jqj/tzJR6yJtvITT2Jlvn3pqgub40BUV DoCHGhRtyVFxWUaGUVWe/wQIWw7Am5u6HBbENn0LzkucWkunhzaXphK+TCC7lS62E66H 3j/0Z+hT4umngyyTJzoEBNEolQKzsalCY7H0IxSdIDIOyc3j5NLRb6q22Ip4Z2Q2zdHw 3FYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=fXNL+QoMinc82qzY8ZQNJpjIeexDaPjDD5Ij27UUKjs=; b=Ka8sUArd19TSrgQOF6iVF1c+uLrupeMAd+eWiYz8D2sRcotpRUU0T8AWrOiKHb3AcR TBy7i5pqkdmsG2s+uVciMYVyvaLijUMErcO4LzOmmBmln/0nDhUOzj+7Al8p9SX57dKS qBBSsiL97S9QrCr0xr+Nz5nY1l9Hiy9+Va7wGWN/KYORaPy+5yz+kaYIHb85eyO9rqp7 RN/5T5W0EZd2jfSx/kzAj27g+f2tnIV1Ln+rz3BuSUhYWoXK/nwuyKF90blsFLZwTcto bZ/w2qSPvllarevq58d4shGAc87vOae6SB1SpgzsiWf7asUCErdeq0axVOS1urqjGopQ ERSA== X-Gm-Message-State: AOAM5321cFFg3IGFc3Lq9ebnEJqXtnEkACxu/QxtT8Ok9l0iTFgb7i64 Aj3WIOC8aCtMkPBalQzMTlaDGg== X-Google-Smtp-Source: ABdhPJwNrY6vUr4ohL16rGFjykbtPEc/zmzu1udbOMHuMCFLa/EONbNAw8/DfmJZI0mjPyagUNvQqA== X-Received: by 2002:aa7:d44a:: with SMTP id q10mr2577089edr.278.1617184129662; Wed, 31 Mar 2021 02:48:49 -0700 (PDT) Received: from localhost.localdomain (217-149-171-113.nat.highway.telekom.at. [217.149.171.113]) by smtp.gmail.com with ESMTPSA id r17sm1176457edx.1.2021.03.31.02.48.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 31 Mar 2021 02:48:49 -0700 (PDT) Message-ID: <938f4e7730a03c0214ec9e6dd87a9ce046cab6a4.camel@cybertec.at> Subject: Re: [PATCH] add link to domain data types section from locale documentation From: Laurenz Albe To: Anton Voloshin , pgsql-docs@lists.postgresql.org Date: Wed, 31 Mar 2021 11:48:48 +0200 In-Reply-To: <2ea65bdf-1380-f088-02bd-ff1a31ed265c@postgrespro.ru> References: <2ea65bdf-1380-f088-02bd-ff1a31ed265c@postgrespro.ru> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2021-03-30 at 22:46 +0300, Anton Voloshin wrote: > While browsing character set collation documentation [1] > I've found myself a bit puzzled by unfamiliar terminology: > > of course a domain over a collatable data type is collatable > > Of course, it only takes a search or two to find out the exact > meaning of "domain" in this context, but I think it would be useful > to make this word a link to the relevant section as a help for less > experienced users like myself. > > I've attached a patch that does that. Please let me know whether this > fix is desirable and correct (I'm new to Postgres) and if there is a > better way of suggesting an improvement for the documentation. > > [1] https://www.postgresql.org/docs/current/collation.html +1 Yours, Laurenz Albe