ACTION_SEARCH_JMDICT API: Option to include reference to matched section of query

[timrae]

When an inexact / compound query is searched, it would be useful to be able to match the result back to the query.

Example:
If I search for 寿司が食べたい then I'd want to get back 寿司、が、食べたい together with the search results 寿司、が、食べる. The start and stop indices of the match would work as well.

[timrae]

Another option could be to just include the verb inflections separately like kuromoji does. For example 寿司が食べたい。 returns:

Surface form Part-of-Speech Base form Reading Pronunciation
寿司 名詞,一般,, 寿司 スシ スシ
が 助詞,格助詞,一般,* が ガ ガ
食べ 動詞,自立,, 食べる タベ タベ
たい 助動詞,,,* たい タイ タイ
。 記号,句点,, 。 。 。

[timrae]

After actually spending quite a bit of time working with kuromoji and furigana, I've found that with the way they do it, it's a bit of a pain reassembling the words, so please just ignore my last comment. Finally I think giving two indices (start, stop) for each entry will be the most convenient for me:

e.g. the following sentence 寿司が食べたい。 should return:
寿司 (0, 2)
が (2, 3)
食べる (3, 7)

Do you think this is something which you could add to the API relatively quickly? It's kind of crucial for me to proceed with my application

[mvysny]

Hi Tim, thanks for the feature request. I will revisit the API and I will let you know. Don't hold your breath though, this will be done next week soonest... sorry.

[mvysny]

Just to confirm: you use the ACTION_SEARCH_JMDICT api with "kanjis" set to "寿司が食べたい" and "return_results" set to true. Is it okay if in the resulting list of maps, each map would contain e.g. "origin_range" with the format of 0,2 (that is, start index, end index, no braces)?

[timrae]

Yes, great!
On 14/05/2015 11:22 pm, "Martin Vysny" notifications@github.com wrote:

Just to confirm: you use the ACTION_SEARCH_JMDICT api with "kanjis" set to
"寿司が食べたい" and "return_results" set to true. Is it okay if in the resulting
list of maps, each map would contain e.g. "origin_range" with the format of
0,2 (start index, end index)

—
Reply to this email directly or view it on GitHub
#497 (comment).

[mvysny]

Fixed in Aedict 3.19

[mvysny]

The key will be called "position_in_sentence".

[mvysny]

Tim, can you please share a link to your application if it is on the Google Play? I'm quite interested.

[timrae]

@mvysny
It's not on Google Play yet, I mainly just made it for myself to be honest, but OK I'll try and upload it sometime this week.

[mvysny]

If you do not wish to go public, no problem. In such case if this is okay with you, you can just send me the APK via e-mail. Thanks!

[timrae]

Probably I'll make it available via the beta testing facilities on Google Play, just give me a few days.

[timrae]

This doesn't appear to be working (I'm currently using a different analysis engine because I required this PR to proceed with Aedict)... I just sent the following query taken from Wikipedia:

漢字（かんじ）は、古代中国に発祥を持つ文字。古代において中国から日本、朝鮮、ベトナムなど周辺諸国にも伝わり、その形態・機能を利用して日本語など各地の言語の表記にも使われている（ただし、現在は漢字表記を廃している言語もある。日本の漢字については日本における漢字を参照）。

The first hit has "position_in_sentence" -> "127,2" which is obviously wrong... others were wrong as well

I also tried a simpler search: 漢字難しいよ and got back:
("kanji" -> "漢字", "position_in_sentence" -> "0,2")
("kanji" -> "難しい, 六借しい, 六ヶ敷い", "position_in_sentence" -> "2,3")
("kanji" -> "よ", "position_in_sentence" -> "5,1")

Whereas I'd expect to get back:
"0,2"
"2,5"
"5,6"