| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
| Subject: | Broken linkparsing in archives |
| Date: | 2022-11-02 12:31:08 |
| Message-ID: | D0DB017E-F605-4158-BB12-6D5C20636DF8@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Looking at past announcements I noticed that Markdown links were parsed and/or
rendered incorrectly in the archives. The example email that I noticed it on
was this:
/message-id/163724833494.26187.1931723451787420391@wrigleys.postgresql.org
..but it happens on all it seems, a more recent example:
/message-id/166472941958.662.2706300812023074847%40wrigleys.postgresql.org
The rendered links follow the same pattern, the last word in the markdown text
block is prepended to the url block and all of it added as the href:
[call for papers](https://2022.nordicpgday.org/cfp/)
becomes:
[call for <a href="http://papers](https://2022.nordicpgday.org/cfp/)" rel="nofollow">papers](https://2022.nordicpgday.org/cfp/)</a>
Is this a known issue?
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2022-11-02 12:39:38 | Re: Broken linkparsing in archives |
| Previous Message | Christoph Berg | 2022-11-01 14:40:47 | Re: Debian releases |