-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 D'Arcy J.M. Cain a écrit : > So, what's happening. Is this discussion going into Limbo again for > six months. It feels like the latest round of messages just went > around the same circles as before. Let me summarize the different > possibilities as I see them. > > 0. Drop this patch > 1. Call it Rest and make it 100% compliant > 2. Call it Rest-like > 3. Call it simply border level 3 > > I don't think there are many supporting number 0 but... I think > everyone agrees that number 1 is difficult, perhaps impossible, to > achieve so its supporters probably drop into 0 or 2. > > Is there any chance we can narrow our choices here in order to focus > discussions? Is it fair to say that our real choices are 0 and 3? Is > there anyone who thinks that number 1 is achievable or that number 2 is > a good precedent for the project? >
I go for 3 (so whithout escaping) 1. Can be interesting *but* if all special char are escaped it will become useless : one good point with ReST is that you can read it like 'less README.rest' and it is readable like python code. If it is full of escaped characters it can turn unreadable by a human. (we, at dalibo, used to write our docs with ReST and most of the time we don't need to escape special char). I don't follow 0 or 2.. - -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAklrQNkACgkQo/dppWjpEvyKeACgsfHLQzrgvbi7unlV15mYushD YAAAoL1EYgz2bDLBdvEtfn+BlVBQhm/W =qQls -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
