# Forum search does not recognize Japanese **URL:** \ **Category:** Bugs & Errors\ **Created:** [July 22, 2018, 6:31pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883 "2018-07-22T18:31:17Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Cychloryn](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/cychloryn/32/188167_2.png) [@Cychloryn](https://community.wanikani.com/u/Cychloryn)\ **Post date:** [July 22, 2018, 6:31pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/1 "2018-07-22T18:31:17Z")
This issue was apparently addressed in the past: > [@\[Forum\] 日本語 Search Issues](https://community.wanikani.com/t/forum-%E6%97%A5%E6%9C%AC%E8%AA%9E-search-issues/16510): > > I’ve been trying to search search on the forums in hiragana and kanji and it is not working. Has anyone else had this issue or am I doing something stoopid?? Can you guys reproduce the issue? Because this seems like it may be a major issue in a… Japanese learning forum. wink@Kumirei @AnimeCanuck@anon20839864 @viet But in that thread, WK staff said they fixed it, and that was over a year ago! However, I’ve been having issues now with searches in kana/kanji returning no results ![image](https://global.discourse-cdn.com/wanikanicommunity/original/3X/6/d/6d9185dab079b0fbb2b9b8da1d13ae898acbce7f.png) It’s made all the more painful, because the page hijacks the browser ctrl+f search (which _actually works_), and overrides it with the busted Discourse search. This must be a regression in the past year. Anyone else experience this? ---
**Author:** ![tombo](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/tombo/32/345347_2.png) [@tombo](https://community.wanikani.com/u/tombo)\ **Post date:** [July 22, 2018, 7:10pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/2 "2018-07-22T19:10:09Z")
I was able to search without those issues. The screenshot below is the results of using your example kana in the search. I clicked on one of the results and used find in page which implemented the native browser find and not a Discourse find. I’m running Chrome (latest) on Windows 10. I’m not sure why our experience differs, but it’s safe to say you’re not stupid 🙂 ![image](https://global.discourse-cdn.com/wanikanicommunity/original/3X/f/5/f55126143bb2b10e71545ab2347bd9a0ed30999e.png) ---
**Author:** ![Omun](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/omun/32/457654_2.png) [@Omun](https://community.wanikani.com/u/Omun)\ **Post date:** [July 22, 2018, 7:31pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/3 "2018-07-22T19:31:33Z")
In your example, you have the box “search this topic” checked. Could that possibly be the problem? I did a test. Searched for the Japanese title of a topic elsewhere on the forum while looking at your post with the checkbox checked. ![example](https://global.discourse-cdn.com/wanikanicommunity/original/3X/4/e/4e073f1f568262b7ec995f6571bfeada4b574611.JPG) Then without the checkbox. ![example%202](https://global.discourse-cdn.com/wanikanicommunity/original/3X/6/c/6c5aec12f357506903e3c2cfb2e05cd5f392453b.JPG) ---
**Author:** ![Cychloryn](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/cychloryn/32/188167_2.png) [@Cychloryn](https://community.wanikani.com/u/Cychloryn)\ **Post date:** [July 22, 2018, 7:38pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/4 "2018-07-22T19:38:53Z")
Yeah, it seems like search is maybe only broken when you do “search this topic”. But in my case, I was indeed trying to search for a word that I knew was in the topic I was looking at. ![image](https://global.discourse-cdn.com/wanikanicommunity/original/3X/a/d/ad7bf9b99f08d970610a46db686a07175f1c21d2.png) If you see this screenshot, 「あたし」 is right here in the topic, but wasn’t picked up in the search results. ---
**Author:** ![Omun](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/omun/32/457654_2.png) [@Omun](https://community.wanikani.com/u/Omun)\ **Post date:** [July 22, 2018, 7:42pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/6 "2018-07-22T19:42:57Z")
I see what you mean. I tried searching [あたし] in this topic. It first said no results found, and then gave a red warning box that search query was too short. This was on my Android phone. ---
**Author:** ![tombo](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/tombo/32/345347_2.png) [@tombo](https://community.wanikani.com/u/tombo)\ **Post date:** [July 22, 2018, 8:58pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/7 "2018-07-22T20:58:08Z")
Apparently Discourse behaves differently for posts with more than 20 replies. Whether or not a post is listed, may also be a factor. You should be able to override the search in page by pressing CTRL+F again. But on a \>20 reply post the actual results will still be influenced by which portions of the topic have been loaded (into the DOM). ---
**Author:** ![Radish8](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/radish8/32/206088_2.png) [@Radish8](https://community.wanikani.com/u/Radish8)\ **Post date:** [July 22, 2018, 9:01pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/8 "2018-07-22T21:01:43Z")
I find, in-thread, that it is incapable of picking up hiragana. It can pick up kanji fine, but as soon as you add any hiragana it becomes clueless. So ありがとう won’t work, 友達 will, but 来る won’t. The in-browser find function still highlights any instances it finds, so if you scroll down the page they’ll be picked out, but obviously that’s not particularly helpful. ---
**Author:** ![Kumirei](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/kumirei/32/480522_2.png) [@Kumirei](https://community.wanikani.com/u/Kumirei)\ **Post date:** [July 22, 2018, 9:03pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/9 "2018-07-22T21:03:21Z")
To be fair the search on Discourse is terrible in general. ---
**Author:** ![Cychloryn](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/cychloryn/32/188167_2.png) [@Cychloryn](https://community.wanikani.com/u/Cychloryn)\ **Post date:** [July 22, 2018, 9:15pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/10 "2018-07-22T21:15:05Z")
Right, the browser ctrl+f still works, but is useless in large threads where the post I’m searching for yet hasn’t been loaded. I’ll send an email to WK because this seems to be a real bug at this point. ---
**Author:** ![Belthazar](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/belthazar/32/4469_2.png) [@Belthazar](https://community.wanikani.com/u/Belthazar)\ **Post date:** [July 22, 2018, 11:42pm UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/11 "2018-07-22T23:42:06Z")
My browser ctrl-f just opens up Discord’s search box. I’ve been trying to work out how to make it not do that… ---
**Author:** ![Kumirei](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/kumirei/32/480522_2.png) [@Kumirei](https://community.wanikani.com/u/Kumirei)\ **Post date:** [July 23, 2018, 7:11am UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/12 "2018-07-23T07:11:20Z")
I just place my cursor in the URL first ---
**Author:** ![system](https://global.discourse-cdn.com/wanikanicommunity/original/4X/6/2/a/62a8b0f4c59ff2c5b6651ffcf43531480b3e5297.png) [@system](https://community.wanikani.com/u/system)\ **Post date:** [July 23, 2019, 7:11am UTC](https://community.wanikani.com/t/forum-search-does-not-recognize-japanese/31883/13 "2019-07-23T07:11:23Z")
Closed on July 23, 2019, 7:11am UTC This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.