It appears that the score for the second document (āUK_Wedderburnā¦ā ā the one with the āfalseā result") is higher than the score for the first (āUS_Gouldā¦ā). Those scores would be an additional error, it seems.
I located a copy of the āUK_Wedderburnā¦ā document here. With these settings, I am unable to reproduce the false result reported in the OP:
My copy had 14 instances of āfarā and none of āevolvingā. If you grab that other copy I mentioned, put it alongside the two you already have, and continue to get the false results, then perhaps sending both documents to Support would give staff an opportunity to test the situation.
Iāve just ran the search again.
Wedderburn is still there, only highlighting the āfarā - I hadnāt even noticed its āscoreā was higher, which is obviously problematic.
Iām going to re-download a fresh copy of Wedderburn, and run it againā¦
[EDIT]
As an aside - āfarā appears on pages 4, 5, 9, 12, 13 & 20. āEvolvingā appears on pages 13 & 18.
The āfarā picked up in the screengrab above, was on page 4.
Granted - it was precisely the same article - but obtained through āofficialā channels, off the LexisNexis database. Itās a word doc converted to PDF, and is fully searchable in preview.
Is this a possible bug? Should I send it through to someone at DTP?
With all the above being said - could this mean I would have problems doing similar NEAR searches with other terms? Think Iāll pull a Windows trick, and reboot - maybe that might make a differenceā¦
I got the same results as korm, using the document that he linked to.
A document should only appear in the results list if there is a match for āFarā NEAR/20 āevolvingā, however all instances of āfarā and āevolvingā will be highlighted in the document.
I assumed that the search function would ONLY highlight the actual instance(s) where āFarā appeared 20 words or less NEAR to āEvolvingāā¦
It never occurred to me that it would also highlight all the appearances of words being searched for. I will do a few more tests, and see if my understanding as above holds true!
Thanks for the help - played around with a few searches, and now it makes sense.
I consider myself as someone who knows their way around a computer - but goodness me, DTP as had me feeling idiotic on more than one occasion over the past few months!
I will need to tweak my searches to minimise the likelihood of needing to skip through dozens of individual search-hits in the identified documents, before getting to the Term1 NEAR Term2 jackpot. But thatās a small price to pay.
Whilst it would obviously be super useful if the Search function was able to exclude highlighting the individual terms, and thereby - only present the Term1 NEAR/20 Term2 hit - it is what it is. I cannot begin to fathom some of the answers by the likes of Bill, explaining why it does that - Iāll happily leave that to the people who actually know something about programming. Iām not one of those people!
Armed with the above, I will be able to narrow down future searches, to get to what I need.
I hope this might save someone else some time in the future, too!
), or am I missing something obvious?
