Closed Bug 357682 Opened 19 years ago Closed 19 years ago

Nutch searching doesn't handle Japanese properly

Categories

(developer.mozilla.org Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: takenspc, Assigned: sancus)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061023 Minefield/3.0a1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061023 Minefield/3.0a1 Nutch searching doesn't handle Japanese properly. Reproducible: Always Steps to Reproduce: 1.Search Japanese words with Nutch. At this point , I use "正規表現"(means regular expression) http://developer.mozilla.org/ja/docs/%E7%89%B9%E5%88%A5:Nutch?query=%E6%AD%A3%E8%A6%8F%E8%A1%A8%E7%8F%BE&language=ja&start=0&hitsPerPage=10 Actual Results: * Nutch: url:developer.mozilla.org/ja/docs (search term) The search term should be "正規表現" but it's completely garbled. (Because above I guess) The search results don't contain "正規表現". You can confirm this by opening one of results, then searching "正規表現" in that page. Expected Results: Japanese should not be garbled. i.e. * Nutch: url:developer.mozilla.org/ja/docs 正規表現 should be shown. Search results should be pages contains "正規表現" e.g. http://developer.mozilla.org/ja/docs/Core_JavaScript_1.5_Guide:Regular_Expressions
Assignee: nobody → sancus
# taken... sorry that i forgot to report this.. it happens with some other words like DOM or so.. for me, it seems Nutch search's output contains only login request page. # but i cannot see actual page.
This should be fixed shortly with bug 360605, it is a tomcat configuration problem.
OK, tomcat is fixed. I'm going to mark this resolved, please feel free to verify that it's fixed or reopen if there's further problems.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
it seems fixed for me, too. thx.
Component: Deki Infrastructure → Other
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.