Re: fulltext parser strange behave - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: fulltext parser strange behave
Date
Msg-id 47326E15.8000702@dunslane.net
Whole thread Raw
In response to Re: fulltext parser strange behave  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: fulltext parser strange behave  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>   
>> Tom Lane wrote:
>>     
>>> Well, the state machine definitely thinks that tag names should contain
>>> only ASCII letters (with possibly a leading or trailing '/').  Given the
>>> HTML examples I suppose we should allow non-first digits too.  Is there
>>> anything else that should be considered a tag?  What about dash and
>>> underscore for instance?
>>>       
>
>   
>> The docs say we specifically accept HTML tags. Are we really just 
>> accepting anything that is a string of ASCII letters as the tag name? 
>> Then we should adjust the docs. <foo> and <foo1234> are not HTML tags.
>>     
>
> I don't think I want to try to maintain a list of exactly which
> identifiers are considered valid tag names ... and if I did, I wouldn't
> put it into the parser.  It would be a dictionary's job to tell valid
> from invalid tag names, no?
>
>             
>   

I don't have a quarrel with that. But then we should be more clear about 
what we are recognizing. We could describe the thing as an HTML-like 
tag, possibly. I think the same probably goes for entities too.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Throw error and ErrorContext question.
Next
From: Josh Berkus
Date:
Subject: Re: Bug: --with-libxml does not take a location