MIME-Version: 1.0
References: <11c93b2a-2445-148b-30a9-35fb9eee82d7@purtz.de>
 <20200402000925.GA7329@alvherre.pgsql>
In-Reply-To: <20200402000925.GA7329@alvherre.pgsql>
From: Corey Huinker <corey.huinker@gmail.com>
Date: Wed, 1 Apr 2020 23:34:31 -0400
Message-ID: 
 <CADkLM=fW_CUBFFJrBfQB1-jcjDBrFhG7-TDjA+N56z_3kxUh0g@mail.gmail.com>
Subject: Re: Add A Glossary
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: =?UTF-8?Q?J=C3=BCrgen_Purtz?= <juergen@purtz.de>,
	Justin Pryzby <pryzby@telsasoft.com>, Roger Harkavy <rogerharkavy@gmail.com>,
	pgsql-hackers@postgresql.org, Fabien COELHO <coelho@cri.ensmp.fr>,
	Michael Paquier <michael@paquier.xyz>
Content-Type: multipart/alternative; boundary="0000000000004c6ee305a2467b4a"
Precedence: bulk

--0000000000004c6ee305a2467b4a
Content-Type: text/plain; charset="UTF-8"

>
> 2. I found out that "see xyz" and "see also" have bespoke markup in
> Docbook -- <glosssee> and <glossseealso>.  I changed some glossentries
> to use those, removing some glossdefs and changing a couple of paras to
> glossseealsos.  I also removed all "id" properties from glossentries
> that are just <glosssee>, because I think it's a mistake to have
> references to entries that will make the reader look up a different
> term; for me as a reader that's annoying, and I don't like to annoy
> people.
>

+1 These structural enhancements are great. I'm fine with removing the id
from just-glossee, and glad that we're keeping the entry to aid discovery.


> I rewrote the definition for "atomic" once again.  Made it two
> glossdefs, because I can.  If you don't like this, I can undo.
>

+1 Splitting this into two definitions, one for each context, is the most
sensible thing and I don't know why I didn't do that in the first place.

--0000000000004c6ee305a2467b4a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">2. I found out that &quot;see xyz&quot; and &quot;see al=
so&quot; have bespoke markup in<br>
Docbook -- &lt;glosssee&gt; and &lt;glossseealso&gt;.=C2=A0 I changed some =
glossentries<br>
to use those, removing some glossdefs and changing a couple of paras to<br>
glossseealsos.=C2=A0 I also removed all &quot;id&quot; properties from glos=
sentries<br>
that are just &lt;glosssee&gt;, because I think it&#39;s a mistake to have<=
br>
references to entries that will make the reader look up a different<br>
term; for me as a reader that&#39;s annoying, and I don&#39;t like to annoy=
<br>
people.<br></blockquote><div><br></div><div>+1 These structural enhancement=
s are great. I&#39;m fine with removing the id from just-glossee, and glad =
that we&#39;re keeping the entry to aid discovery.<br></div><div>=C2=A0<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">I rewrote the defin=
ition for &quot;atomic&quot; once again.=C2=A0 Made it two<br>
glossdefs, because I can.=C2=A0 If you don&#39;t like this, I can undo.<br>=
</blockquote><div><br></div><div>+1 Splitting this into two definitions, on=
e for each context, is the most sensible thing and I don&#39;t know why I d=
idn&#39;t do that in the first place.<br></div><div><br></div></div></div>

--0000000000004c6ee305a2467b4a--