From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL www <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Wiki problem with URLs |
Date: | 2013-02-01 17:42:07 |
Message-ID: | 20130201174207.GA2357@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Fri, Feb 1, 2013 at 12:39:42AM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > So the only known fix is to hand-edit URLs to use %3D? That doesn't
> > seem very good. Do we need to move the TODO list somewhere else?
>
> There are several reasons why the wiki is not a perfect fit for the
> TODO; for instance, taking out the items done as each major version gets
> released is always problematic. Are you proposing to write a Django app
> to host the TODO? That, I think, would be best.
Well, I guess all I am saying is that now that there are no archive URLs
being generated, e.g.
http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php
everything is a message-id, and many message ids (e.g. Google) have
characters that cause problems for the wiki, e.g. '='.
I can encode '=', but there might be other characters, and other people
might not know to do that. Also, when you don't encode '=', you don't
get any feedback that there is a problem --- that link URL just
disappears from the wiki, and not just the URL disappears but all links
and any secondary text for the item.
What I can do it cleanup what is there and try to encode '=', but I
hardly see that as a long-term solution.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-02-01 18:21:11 | Re: Wiki problem with URLs |
Previous Message | Alvaro Herrera | 2013-02-01 03:39:42 | Re: Wiki problem with URLs |