Updates:
Labels: Mstone-4
Blockedon: -14756
Comment #7 on issue 8803 by [email protected]: add Korean spell checking
support
http://code.google.com/p/chromium/issues/detail?id=8803
Thank you for the reply and starting the project (Korean hunspell
dictionary) !
When calculating the edit distance, it might work better to go beyond the
NFD.
Perhaps, whether and how far depend on a few factors including IME/kbd
layouts (and
what's proposed in UTR 47 is not necessarily the best for spell checking).
Well, I'm
digressing here.
Getting back to this bug: Due to a lot of valgrind warnings, hunspell was
reverted
back to 1.1.5. So, we can't support Korean.
Actually, we can (as Changwoo suggested) because we can easily do NFD/NFC
ourselves
before/after calling hunspell functions. Even if we upgrade to 1.2.8, we'd
better
remove ICONV/OCONV entries (11,172 each) in the Korean dictionary and do
NFD/NFC
ourselves to save the memory consumption and improve the performance (ICU's
NFD/NFC
would be much faster than what's done inside Hunspell with 11,172
ICONV/OCONV
entries). So, I'm removing 'blocked on 14756'.
Nonetheless, it's too late for 3.0.
And, another potential blocker is that we don't have a word breaker for
Korean. Our
copy of ICU has a 'rudimentary' implementation for Korean word breaking,
but it's
disabled because we don't have an open-sourceable Korean word frequency
list, yet.
That's another reason I was excited to find the Korean hunspell dictionary.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
