| From: | Brar Piening <brar(at)gmx(dot)de> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add id's to various elements in protocol.sgml |
| Date: | 2022-03-01 17:27:38 |
| Message-ID: | 767059d5-ed1f-3d16-cada-24175461f3db@gmx.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 28, 2022 at 21:06, Chapman Flack wrote:
> I think that in other recent examples I've seen, there might be
> (something like a) consensus forming around the Unicode LINK SYMBOL
> 🔗 rather than # as the symbol for such things.
I intentionally opted for an ASCII character as that definitely won't
cause any display/font/portability issues but changing that is no problem.
> ... and now that the concept is proven, how hard would it be to broaden
> that template's pattern to apply to all the other DocBook constructs
> (such as section headings) that emit anchors?
As long as we stick to manually assigned ids in the same way my patch
does it, it shouldn't be too hard. Speaking of autogenerated ids, I
failed to make use of them since I wasn't able to reproduce the same
autogenerated id twice in order to use it for the link.
Also I'm not sure how well the autogenerated ids are reproducible over
time/versions/builds, and if it is wise to use them as targets to link
to from somewhere else.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2022-03-01 17:32:08 | Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file |
| Previous Message | Nathan Bossart | 2022-03-01 17:05:37 | Re: Allow async standbys wait for sync replication |