From: Tom Lane on 16 Nov 2009 22:41 Alex Hunsaker <badalex(a)gmail.com> writes: > While looking over the writable cte patch I noticed queries.sgml has > lots of things in the form "<literal>FROM</>". I tried various > googles to see if </> is some kind of sgml/xml shorthand for close the > last opened tag. But alas, nothing found. Bad google foo? Apparently --- it's perfectly legal in SGML. (I think not in XML.) > Should we change those to be the right closing tag? aka </literal> You'd be wasting your time. I don't think it's good style to use </> when the opening tag is far away or there are other tags between. But for examples like the one you cite, it's perfectly reasonable. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Andrew Dunstan on 16 Nov 2009 22:44 Tom Lane wrote: > Alex Hunsaker <badalex(a)gmail.com> writes: > >> While looking over the writable cte patch I noticed queries.sgml has >> lots of things in the form "<literal>FROM</>". I tried various >> googles to see if </> is some kind of sgml/xml shorthand for close the >> last opened tag. But alas, nothing found. Bad google foo? >> > > Apparently --- it's perfectly legal in SGML. (I think not in XML.) > Correct on both counts. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Alex Hunsaker on 16 Nov 2009 22:54 On Mon, Nov 16, 2009 at 20:41, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: > Apparently --- it's perfectly legal in SGML. Â (I think not in XML.) Cool. Thanks! BTW anyone know how to escape < and > for google? I tried searching for it-- but ran into a chick and egg situation. So the I tried various forms of "google search left angle bracket", quotes, backslashes and "+". no luck -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Robert Haas on 16 Nov 2009 23:25 On Mon, Nov 16, 2009 at 10:54 PM, Alex Hunsaker <badalex(a)gmail.com> wrote: > On Mon, Nov 16, 2009 at 20:41, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: >> Apparently --- it's perfectly legal in SGML. (I think not in XML.) > > Cool. Thanks! > > BTW anyone know how to escape < and > for google? I tried searching > for it-- but ran into a chick and egg situation. So the I tried > various forms of "google search left angle bracket", quotes, > backslashes and "+". no luck I don't think you can. I gather that the Google text search algorithm is word-based. It seems like you can't search for things that it doesn't consider to be words. It has a pretty expansive notion of what a word is (like "2a43" is a word, for example) but any non-word characters are ignored (so, for example, "2a43$" returns the same hits as "2a43"). ....Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Peter Eisentraut on 17 Nov 2009 01:43 On mån, 2009-11-16 at 20:30 -0700, Alex Hunsaker wrote: > While looking over the writable cte patch I noticed queries.sgml has > lots of things in the form "<literal>FROM</>". I tried various > googles to see if </> is some kind of sgml/xml shorthand for close the > last opened tag. But alas, nothing found. Bad google foo? If you have DocBook installed locally, you should have a file called docbook.dcl, which contains the "SGML declaration" of DocBook, and somewhere down contains this: FEATURES MINIMIZE DATATAG NO OMITTAG NO RANK NO SHORTTAG YES So if you google for something like "markup minimization shorttag", you can find more information. For amusement, contrast this with the SGML declaration of HTML: FEATURES MINIMIZE DATATAG NO OMITTAG YES <-- This is why you can omit <body>, for example. RANK NO SHORTTAG YES -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
|
Next
|
Last
Pages: 1 2 Prev: [HACKERS] ORDER BY vs. volatile functions Next: plpythonu DO support (inline call handler) |