Re: sgml and "empty" closing tags

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alex Hunsaker <badalex(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: sgml and "empty" closing tags
Date: 2009-11-17 04:25:11
Message-ID: 603c8f070911162025q5fdf51b5w8a331a37653efbf2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 16, 2009 at 10:54 PM, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
> On Mon, Nov 16, 2009 at 20:41, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Itagaki Takahiro 2009-11-17 05:19:58 Re: UTF8 with BOM support in psql
Previous Message Robert Haas 2009-11-17 04:21:21 Re: Raising the geqo_threshold default