- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 07 Feb 2009 00:09:11 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6469 --- Comment #8 from Christian Gruen <christian.gruen@gmail.com> 2009-02-07 00:09:11 --- Hi Jim, thanks again for the quick reply, and sorry for persisting on the tokenizer issue. Yes, I'll be interested what the other TF members say about this as I'm still not sure how to interpret the examples in 4.1.1. As stated before, using a Western tokenizer and assuming that commas and periods are treated the same way, I would expect all of the following queries to yield true (otherwise, the position information, which is shown in parentheses in this section, would not make much sense): "Ford Mustang 2000, 65K" ftcontains "2000 65K" "Ford Mustang 2000, 65K" ftcontains "2000.65K" "Ford Mustang 2000 65K" ftcontains "2000.65K" Concerning #10 and #11: > [10] FTWords/*.xml > I appreciate the comment, but it would be extremely helpful > if you could identify the specific locations. Hm, there might have been around 10 files with missing spaces. You could try search and replace in this directory for the following strings, I hope that the three replacements will cover all cases: "checked.<" -> "checked. <" "ue</nt>is" -> "ue</nt> is" "on</nt>produces" -> "on</nt> produces" > [11] FTPrimary-FTWords-phrase-q3a.xq - -q4a.xq > I agree. I've fixed the problems in each of the tests in > slightly different ways. > I also think that FTPrimary-FTWords-phrase-q4b.xq had the wrong result; > I believe that its result file should contain only an empty <paragraphs> > element. Do you agree? In my version from Jan 24, the result was already an empty <paragraphs> element; but I haven't checked the latest version. Christian, BaseX Team http://www.basex.org -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 7 February 2009 00:09:20 UTC