Last modified: 2013-03-26 11:24:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T4413, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 2413 - Lucene search should use standard message
Lucene search should use standard message
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
lucene-search-2 (Other open bugs)
unspecified
All All
: Lowest normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-14 20:01 UTC by Guttorm Flatabø
Modified: 2013-03-26 11:24 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Guttorm Flatabø 2005-06-14 20:01:11 UTC
It seems lucene search is using the 'searchnoresults' string when there are no
results from a search.

'searchnoresults' is only translatable through the MediaWiki namespace and is
not a standard message. It should probably be replaced with the standard message
'notextmatches'
Comment 1 Ævar Arnfjörð Bjarmason 2005-06-16 17:36:57 UTC
Changed product to MediaWiki extensions and component to General/Unknown.
Comment 2 River Tarnell 2005-06-22 15:24:52 UTC
"notextmatches" says: "No page text matches" 
 
Lucene does not search in such a way that it would ever be correct to say that there 
were no "page text" matches.  either there are matches, or there aren't.   the split 
between title and text matches is an artifact of the MySQL search system. 
Comment 3 Andre Klapper 2013-03-26 11:24:15 UTC
[Merging "MediaWiki extensions/Lucene Search" into "Wikimedia/lucene-search2", see bug 46542. You can filter bugmail for: search-component-merge-20130326 ]

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links