[jira] Commented: (NUTCH-358) Language Switching PROBLEM FIXED

[ http://issues.apache.org/jira/browse/NUTCH-358?page=comments#action_1270 ] KuroSaka TeruHiko commented on NUTCH-358: - I am afraid: + java.util.Locale selectedLocale = new java.util.Locale(queryLang, queryLang.toUpperCase()); only

[jira] Updated: (NUTCH-162) country code jp is used instead of language code ja for Japanese

[ http://issues.apache.org/jira/browse/NUTCH-162?page=all ] KuroSaka TeruHiko updated NUTCH-162: It seems many .html files are actually generated by ant target generate-docs in build.xml, and only these four changes are needed to fix this bug: mv

[jira] Commented: (NUTCH-224) Nutch doesn't handle Korean text at all

[ http://issues.apache.org/jira/browse/NUTCH-224?page=comments#action_12442140 ] KuroSaka TeruHiko commented on NUTCH-224: - [[ Old comment, sent by email on Tue, 13 Jun 2006 18:17:48 -0700 ]] Thank you for taking care of this bug.

[jira] Commented: (NUTCH-266) hadoop bug when doing updatedb

[ http://issues.apache.org/jira/browse/NUTCH-266?page=comments#action_12426377 ] KuroSaka TeruHiko commented on NUTCH-266: - Renaud, thank you for posting the patch. Is there a patched version of hadoop jar file (precompiled) that I can

[jira] Commented: (NUTCH-313) moreFrom property in search.properties cannot be translated into Japanese. Compound text issue.

[ http://issues.apache.org/jira/browse/NUTCH-313?page=comments#action_12418731 ] KuroSaka TeruHiko commented on NUTCH-313: - Perhaps this might fixe the issue, besides the fix to the moreForm line in each of the search*.properties. $ diff -bw -c

[jira] Created: (NUTCH-316) Confusion about query languages

Confusion about query languages --- Key: NUTCH-316 URL: http://issues.apache.org/jira/browse/NUTCH-316 Project: Nutch Type: Bug Components: web gui Versions: 0.8-dev Environment: n/a Reporter: KuroSaka TeruHiko In

[jira] Created: (NUTCH-317) Clarify what the queryLanguage argument of Query.parse(...) means

Clarify what the queryLanguage argument of Query.parse(...) means - Key: NUTCH-317 URL: http://issues.apache.org/jira/browse/NUTCH-317 Project: Nutch Type: Bug Components: searcher Versions:

[jira] Commented: (NUTCH-266) hadoop bug when doing updatedb

[ http://issues.apache.org/jira/browse/NUTCH-266?page=comments#action_12417922 ] KuroSaka TeruHiko commented on NUTCH-266: - I opened a Hadoop bug as this is more likely a bug in Hadoop: http://issues.apache.org/jira/browse/HADOOP-323 Close this bug

[jira] Commented: (NUTCH-266) hadoop bug when doing updatedb

[ http://issues.apache.org/jira/browse/NUTCH-266?page=comments#action_12417387 ] KuroSaka TeruHiko commented on NUTCH-266: - Both Eugine's case and my case are failing in the call chain started at line 101 of LocalJobRunner.java, which reads:

[jira] Commented: (NUTCH-266) hadoop bug when doing updatedb

[ http://issues.apache.org/jira/browse/NUTCH-266?page=comments#action_12417391 ] KuroSaka TeruHiko commented on NUTCH-266: - I'm sorry for adding many comment. This would be the last for today. As an experiment, I replaced hadoop-0.2-dev.jar that

[jira] Commented: (NUTCH-266) hadoop bug when doing updatedb

[ http://issues.apache.org/jira/browse/NUTCH-266?page=comments#action_12416945 ] KuroSaka TeruHiko commented on NUTCH-266: - I am experiencing pretty much the same symptom with the nighly builds of 5/31/2006 up to 6/14/2006, which I tested the last

[jira] Commented: (NUTCH-266) hadoop bug when doing updatedb

[ http://issues.apache.org/jira/browse/NUTCH-266?page=comments#action_12416958 ] KuroSaka TeruHiko commented on NUTCH-266: - I noticed that there is no drive letter C: in the path quoted in the exception messages in both cases. Since both cases are

[jira] Commented: (NUTCH-266) hadoop bug when doing updatedb

[ http://issues.apache.org/jira/browse/NUTCH-266?page=comments#action_12416971 ] KuroSaka TeruHiko commented on NUTCH-266: - The Nutch binary (w/ Adming GUI) downloadable from: http://68.178.249.66/nutch-admin/nutch-0.8-dev_guiBundle_05_02_06.tar.gz

[jira] Created: (NUTCH-224) Nutch doesn't handle Korean text at all

Nutch doesn't handle Korean text at all --- Key: NUTCH-224 URL: http://issues.apache.org/jira/browse/NUTCH-224 Project: Nutch Type: Bug Components: indexer Versions: 0.7.1 Reporter: KuroSaka TeruHiko I was

[jira] Commented: (NUTCH-153) TextParser is only supposed to parse plain text, but if given postscript, it can take hours and then fail

[ http://issues.apache.org/jira/browse/NUTCH-153?page=comments#action_12361995 ] KuroSaka TeruHiko commented on NUTCH-153: - The strings command would work with mostly ASCII text content. It is highly doubtful if we can have a universal strings

[jira] Commented: (NUTCH-153) TextParser is only supposed to parse plain text, but if given postscript, it can take hours and then fail

[ http://issues.apache.org/jira/browse/NUTCH-153?page=comments#action_12361997 ] KuroSaka TeruHiko commented on NUTCH-153: - Actually, shouldn't turning on the mime.type.magic property do the job that the patch is trying to address? TextParser

[jira] Commented: (NUTCH-164) Locale (language) choice by first session has global effect to all sessions

[ http://issues.apache.org/jira/browse/NUTCH-164?page=comments#action_12361782 ] KuroSaka TeruHiko commented on NUTCH-164: - Actually, the current language selection scheme needs an overhaul. The locale for the message bundle is determined only by

[jira] Created: (NUTCH-162) country code jp is used instead of language code ja for Japanese

country code jp is used instead of language code ja for Japanese Key: NUTCH-162 URL: http://issues.apache.org/jira/browse/NUTCH-162 Project: Nutch Type: Bug Components: web gui Versions:

[jira] Commented: (NUTCH-162) country code jp is used instead of language code ja for Japanese

[ http://issues.apache.org/jira/browse/NUTCH-162?page=comments#action_12361683 ] KuroSaka TeruHiko commented on NUTCH-162: - This is causing an undesired behavior for Japanese users. If the Nutch main index.jsp is visited from the browser of which

[jira] Commented: (NUTCH-138) non-Latin-1 characters cannot be submitted for search

[ http://issues.apache.org/jira/browse/NUTCH-138?page=comments#action_12361546 ] KuroSaka TeruHiko commented on NUTCH-138: - You are right. WIth this Tomcat config, UTF-8 characters can be passed. Also works is having: useBodyEncodingForURI=true

[jira] Created: (NUTCH-161) Plain text parser should use parser.character.encoding.default property for fall back encoding

Plain text parser should use parser.character.encoding.default property for fall back encoding -- Key: NUTCH-161 URL: http://issues.apache.org/jira/browse/NUTCH-161 Project: Nutch

[jira] Created: (NUTCH-137) footer is not displayed in search result page

footer is not displayed in search result page - Key: NUTCH-137 URL: http://issues.apache.org/jira/browse/NUTCH-137 Project: Nutch Type: Bug Components: web gui Versions: 0.7.1 Environment: Windows XP, Japanese

[jira] Created: (NUTCH-138) non-Latin-1 characters cannot be submitted for search

non-Latin-1 characters cannot be submitted for search - Key: NUTCH-138 URL: http://issues.apache.org/jira/browse/NUTCH-138 Project: Nutch Type: Bug Components: web gui Versions: 0.7.1 Environment: