Yeah, probably for his case you're right, but the parser is given the innerHTML of the node and if you've got other html elements in the node you end up with a rather messy string to parse. If the parser was just passed the node itself or be able to set a flag for what form you want your argument to be I think it would be better.
On May 14, 11:13 am, tlphipps <[EMAIL PROTECTED]> wrote: > I'm pretty sure the recommended way to achieve this is to use the > "addParser" functionality. Then you can specify which fields should > use your custom parser using either metadata or options. > Overriding the textExtraction seems like using a sledgehammer to me > rather than a precision tool. > > On May 13, 1:16 pm, Seth - TA <[EMAIL PROTECTED]> wrote: > > > [Tried posting this, but never saw it go through. Sorry if it > > duplicates] > > > I am having a couple issues with how to sort a few of my fields. > > > The first, and I think most difficult is I have a field which holds > > the value of "Empty" or lists state abbreviations. What I'd like it to > > do is have "Empty" be grouped together and then sort the state > > abbreviations in alpha. I tried the grades demo, but with no success. > > > The second is I have an ID field which is constructed by the year and > > then a sequential number. > > Example - 2008 - 1, 2008 - 2, 2008 - 3, etc. > > The problem is that when sorted it sorts like this... > > 2008 - 90, 2008 - 9, 2008 - 89 > > > It does see the 9 as coming after 8 and before 10, but between 90 and > > 89. Help with either one is greatly appreciated. > > > Seth
