Where is Korean keyboard source code?

[Inki Yoo]

There are some bug in Korean keyboard. I want to fix it.
I think Korean keyboard relates to ibus-mozc-hangul. Right?
"ibus-mozc-hangul" is in "third_party/chromiumos-overlay/app-i18n/" but there is no source code, there are only patch files.

Where is "ibus-mozc-hangul" full source code? and Can I change source code and test in ChromeOS ?

[Mike Frysinger]

in the ebuild it lists a SRC_URI which points to the full tarball:

http://commondatastorage.googleapis.com/chromeos-localmirror/distfiles/mozc-${PV}.tar.bz2

where PV corresponds to the version in the ebuild name:

ibus-mozc-hangul-1.4.1033.102-r4.ebuild

which is:

http://commondatastorage.googleapis.com/chromeos-localmirror/distfiles/mozc-1.4.1033.102.tar.bz2

all this source comes from:

http://code.google.com/p/mozc

-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Seigo Nonaka]

+shuchen@

I'm sorry, ibus-mozc-hangul is no longer used. I should remove these obsolete packages.

The new hangul IME is named chromeos-hangul which is written by Google i18n team and IIRC it was open sourced.

Thanks.

Seigo

[Shu Chen]

Yes, the source code for Korean IME is located at https://code.google.com/p/google-input-tools/source/browse/#git%2Fsrc%2Fchrome%2Fos%2Fnacl-hangul.

[Shu Chen]

Btw, if the bug is related to decoding, the source code you may want to look into is at:

https://code.google.com/p/libhangul/

--

Shu Chen |

Software Engineer |

shu...@google.com |

+86 (10) 6250-3615

[Inki Yoo]

Thank you.
I made success to download chromeos-hangul source. I have one more question.
What is a package name for chromeos-hangul ? I think I should run "cros_workon" but I can not find a package name.

[Inki Yoo]

I have answer for my question.
I made 999.ebuild file and local_source. and I could build it with emerge in chroot.

[Mike Frysinger]

unfortunately, cros_workon only works for cros-workon packages atm.  other packages (like this one) you'll have to manually unpack and manage the patches yourself.

even then, chromeos-hangul ships a precompiled NaCl extension.  so your best bet is to go to the upstream project, get the source from there, and then build it however they build it.
-mike

--