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 1ptnBL-0003Ml-RH for pgsql-docs@arkaria.postgresql.org; Tue, 02 May 2023 10:24:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ptnBK-0000nw-Bo for pgsql-docs@arkaria.postgresql.org; Tue, 02 May 2023 10:24:26 +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 1ptnBJ-0000nn-Dx for pgsql-docs@lists.postgresql.org; Tue, 02 May 2023 10:24:26 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ptnBF-00079C-2y for pgsql-docs@postgresql.org; Tue, 02 May 2023 10:24:24 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 69D425C00BA; Tue, 2 May 2023 06:24:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 02 May 2023 06:24:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1683023058; x= 1683109458; bh=wndf+ilu+ETYNt9y2L4uEW5TXv1rAk6KEQtZf4Tyh0c=; b=g VrTmguGaXKyDrcJRjw4CJWLQJ6eE/c135ARs0UoNgEV8yifGLE+gS0EQFmgQwaSt ZlkvfYH8mE/1HudaIfbh4s4eLK/sVSC70MaZZ73ADJA3yQA5GS0/y9nccUNZPny/ bafBCJbUdGPxHnoQU0PmHEEy9uE5CkVLOPZ7PXAJ2uuMG6cTD+y0GbZD9SeldXkH hZ9CfXLxTHo1AlvuK/7Bn9KZ4ZdIqAikIR5cciyG5gLGrsPb9c9vYRTGZktKJJPw L3lDdAzWyYMCycAexTEks2J8P2vHEACsol6/iHJFFMcH7toyPmBXk0Z02s0WiYS8 jVzie9dHosQ8hADaeu7lw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfedviedgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepteffudekjedtudfggeetgeelgedvgefhgffhveduieel gffhfedviedthffhhfdunecuffhomhgrihhnpehsthgrtghkohhvvghrfhhlohifrdgtoh hmpdgvnhhtvghrphhrihhsvggusgdrtghomhdpkhgvrhhnvghlrdhorhhgnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvse grlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 2 May 2023 06:24:17 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 41A58A0; Tue, 2 May 2023 12:24:15 +0200 (CEST) Date: Tue, 2 May 2023 12:24:15 +0200 From: Alvaro Herrera To: Daniel Gustafsson Cc: Peter Eisentraut , pgsql-docs Subject: Re: some new glossary entries Message-ID: <20230502102415.pjgo4yhwjmdhe4mc@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <6C5CF872-8B69-4E13-9D0D-40094378F156@yesql.se> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-May-02, Daniel Gustafsson wrote: > + > + LSN > + > + > > The other entries doesn't have a glossentry id > attribute set, is the use here related to the glossentry.show.acronym param? I debated with myself for 347d2b07fcc2 on whether to add id attribs to entries. The only saving grace for doing that is that you can link to such entries; but if you do that, you're only causing the user one more click in order to see the definition they want to see. So in the end I decided not make the glosssee's directly referenceable. And I think this new entry shouldn't have an id either. I think that what glossentry.show.acronym allows is to show the text that's part of the main entry: https://stackoverflow.com/questions/28869578/docbook-5-rendering-without-abbrev-tag/28879785#28879785 so the fact that there's an id in the other entry doesn't change anything. If we do turn glossentry.show.acronym on (and I don't see any reason not to), we can follow up later to add and tags to other entries, too. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "I'm always right, but sometimes I'm more right than other times." (Linus Torvalds) https://lore.kernel.org/git/Pine.LNX.4.58.0504150753440.7211@ppc970.osdl.org/