Excerpts from Tom Lane's message of mié nov 03 00:15:26 -0300 2010:
> Josh Kupershmidt writes:
> > This HTML fails validation, as one isn't supposed to be stuffing
> > tables inside nodes. The attached patch fixes all the instances of
> > this I could find, by closing out nodes before beginning
Josh Kupershmidt writes:
> This HTML fails validation, as one isn't supposed to be stuffing
> tables inside nodes. The attached patch fixes all the instances of
> this I could find, by closing out nodes before beginning lists
> and tables.
I think this isn't even worth thinking about applying,
[Resending without large attachment, looks like the previous attempt
isn't going to make it]
Hi all,
I've gone through the SGML documentation, trying to push the output
HTML towards HTML 4.01 compliance. By far the most common problem I
found was incorrect nesting of nodes, which results in inva
Thank you Kevin!
I'll look at the contrib/test_parser directory.
Any way, I agree with you. I actually made a pl/pgsql function for
pre-parsing documents
based on my own needs, and cast the results to a tsvector normally. It works
fine enough!
Katharina
On Tue, Nov 2, 2010 at 2:58 PM, Kevin Grittn
Katharina kuhn wrote:
> I'd like to build a custom text search parser and then use it
> within a custom text search configuration.
> It would be great if you could give us an example showing how to
> build a custom parser, including examples of start, gettoken and
> end functions.
You might wa
