QuickSearch eXtended

[Samuel]

I also considered to implement these 3 rules. (perhaps I will in beta 2)
4) a vowel in the search string should match all combinations of this vowel with any lead consonants.
5) a vowel in the search string should match all combinations of this vowel with any lead consonants and trail consonants.
6) a trail consonant in the search string should match all combinations with any lead consonants and vowels.

I still need feedback about 4, 5, 6. What do you think?

[sheppaul]

Could you try if this "ᄑᄋ" filters the file "평양" correct? (instead of "ㅍㅇ")

Yes, I can confirm by 'copy and paste' into search dialog.
The first two consonants "ᄑᄋ" filter correctly "평양" but "ㅍㅇ" is what I really typed in a dialog box.

Could you also try if this "펴야" filters files like this "평양"?

It worked and this "펴야" is same one typed in dialog.

This is something my plugin cannot handle. TC calls it with search string and file name. I have nothing to do with opening the quicksearch window.

I see.

Thank you for your effort.
z

[sheppaul]

4) a vowel in the search string should match all combinations of this vowel with any lead consonants.
5) a vowel in the search string should match all combinations of this vowel with any lead consonants and trail consonants.
6) a trail consonant in the search string should match all combinations with any lead consonants and vowels.

I think it's rather meaningless to implement this.
A vowel itself could have a meaningful part of a word but it's not necessary in case of searching a word.
A trail consonant is only meaningful as a completion of syllable. It does not affect much, thinking of quick search.

Thank you,
z

[infimum]

I can't find "migemo-dict". Do you mean "zen2han.dat"? If not where do I find it?

Are you sure it's not in the "dict" folder? Just in case, here's another link to migemo.
http://www1.kaoriya.net/dist/cmigemo-1.2-dll.tar.bz2

Could you give an example how to use the "migemo-dict"?

As you figured out a couple of responses above that it goes Roman -> hiragana -> katakana, "migemo-dict" changes the last step to (mostly) hiragana -> (mostly) Chinese characters. This is how Roman letters ("kyu" in your example) are connected to Chinese characters.

Did the "Volk" part confuse you? See, the Japanese characters for it don't come out "Volk" in the Romanization system migemo uses. Think of the Chinese word for the electronics company "Sony". If it is phonetically transcribed in PinYin, I'm sure it will not come out as "Sony". But many people just want to type "Sony", and wouldn't it be great that the corresponding Chinese word gets picked up? "migemo-dict" has those conversions. (Of course, migemo only covers Japanese.)

[sheppaul]

7) According to my source there are different chars for lead consonants, vowels and trail consonants. (like Jamo ᄀ [U4352] and Compatibility Jamo ㄱ [U12593]) So far I only implemented the normal Jamo's. Anyone thinks the Compatibility Jamo's are needed too?

In my opinion, normal jamo is enough if there is no problem with quick search.

[Samuel]

I have a new korean beta ready:
QuickSearch eXtended Korean (x32) beta 2

Please install the regular version first and overwrite the "tcmatch.dll" with the packed file. You need "use_pinyin=1" in your "tcmatch.ini" to make it work.

Could you try if this "ᄑᄋ" filters the file "평양" correct? (instead of "ㅍㅇ")

Yes, I can confirm by 'copy and paste' into search dialog.
The first two consonants "ᄑᄋ" filter correctly "평양" but "ㅍㅇ" is what I really typed in a dialog box.

I made this compatibility jamos "ㅍㅇ" work in the new beta. Thanks for the feedback about 4, 5 and 6.
IMO it should just work now. Any fixes or improvements needed?

I can't find "migemo-dict". Do you mean "zen2han.dat"? If not where do I find it?

Are you sure it's not in the "dict" folder? Just in case, here's another link to migemo.
http://www1.kaoriya.net/dist/cmigemo-1.2-dll.tar.bz2

Thank you, I found the file now. I used this before: (the file is missing there)
http://code.google.com/p/cmigemo/

I'm not convinced to extend my QuickSearch to Japanese. There seem to be too much possibilities. Especially with the dict there are some entries that are translated to different words (also back to roman).

Example:
I search for "Hypericales" and there is a file "おとぎりそうもくぐん.txt".
Dict. rule entry: "おとぎりそうもくぐん" translates to "オトギリソウ目群" or "Hypericales"
roma2hira rule entry: "a" translates to "あ".

What rule to apply first? Dict or roma2hira? In this case it is easy for us, but I need an algorithm. I consider to use the "migemo.dll" (it seems to include all the logic needed), but I didn't find an English documentation.

[sheppaul]

I made this compatibility jamos "ㅍㅇ" work in the new beta. Thanks for the feedback about 4, 5 and 6.
IMO it should just work now. Any fixes or improvements needed?

Wow, it works now. I'll report back if there are any problems.

Thank you very much!
z

[Samuel]

I made this compatibility jamos "ㅍㅇ" work in the new beta. Thanks for the feedback about 4, 5 and 6.
IMO it should just work now. Any fixes or improvements needed?

Wow, it works now. I'll report back if there are any problems.

Thank you very much!
z

Nice to hear that.

[xbeta]

Hi Samuel, if there is no Chinese version of "QuickSearch eXtended readme" -- I have not read all this 30+ pages thread -- you can send the origin file (MS office doc?) to me, I can translate it.

[Samuel]

Hi Samuel, if there is no Chinese version of "QuickSearch eXtended readme" -- I have not read all this 30+ pages thread -- you can send the origin file (MS office doc?) to me, I can translate it.

Hi xbeta,
nice to hear you want to contribute.
Here is the file:
tcmatch translate

2infimum:
Do you have an idea, how it may work?
Perhaps I could omit the dict part?

[infimum]

2infimum:
Do you have an idea, how it may work?
Perhaps I could omit the dict part?

If that would make it considerably easier, please go ahead. At least that's something.

[sheppaul]

Hello, again.

This is a readme file translated into Korean.
http://www.mediafire.com/?iodmv04adlscblo

Thank you for an excellent plugin!

[sheppaul]

64bit version of QSx is not working with Korean.

I'm not sure it's because of QSx 64 itself as TC 8.0b8-64 version seems like working with korean while performing a quick search.

Can you confirm it?

Could you run some tests?
- TCs internal QS 32 & 64
- QSx 32 & 64 without option "allow input leading to an empty list"
- QSx 32 & 64 with option "allow input leading to an empty list"

TCs internal QS 32: works
TCs internal QS 64: seems like working
QSx 32: works regardless of the option, "allow input leading to an empty list".
QSx 64: don't work regardless of the option, "allow input leading to an empty list".

When the option is disabled, QSx 64 shows a somewhat weird action: impossilbe to input lead consonants sequentially (PinYin Search).

--------------------------------------------------------------------------------
1. Make folders named as "노트북(sh-xm-qnq), 모니터(ah-sl-xj), 컴퓨터(zja-vb-xj)".
노트북|모니터|컴퓨터

2. Change a keyboard to Korean (microsoft IME).

3. Cannot input lead consonants sequentally.
- try to input the lead consonants "ㄴㅌㅂ(sxq)"



Separation of syllables by hypen.
노트북 (sh-xm-qnq) : Notebook
모니터 (ah-sl-xj) : Monitor
컴퓨터 (zja-vb-xj) : Computer


-------
When the option is enabled, "allow input leading to an empty list".
--> It's possible to input lead consonants sequentally. However, the search doesn't return any result.



Thanks,

[Samuel]

This is a known "bug".

[sheppaul]

It's a bug of QSx itself?