Merge lp:~jincreator/ubuntu/precise/language-selector/korean into lp:ubuntu/precise/language-selector
Proposed by
Jinkyu Yi
on 2012-02-17
| Status: | Merged |
|---|---|
| Merged at revision: | 184 |
| Proposed branch: | lp:~jincreator/ubuntu/precise/language-selector/korean |
| Merge into: | lp:ubuntu/precise/language-selector |
| Diff against target: |
21 lines (+1/-3) 1 file modified
data/pkg_depends (+1/-3) |
| To merge this branch: | bzr merge lp:~jincreator/ubuntu/precise/language-selector/korean |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Martin Pitt | 2012-03-15 | Approve on 2012-03-16 | |
| Gunnar Hjalmarsson (community) | 2012-03-15 | Approve on 2012-03-16 | |
| Sebastien Bacher | Needs Information on 2012-03-05 | ||
| Ubuntu branches | 2012-02-17 | Pending | |
|
Review via email:
|
|||
To post a comment you must log in.
lp:~jincreator/ubuntu/precise/language-selector/korean
updated
on 2012-03-02
| Jinkyu Yi (jincreator) wrote : | # |
As far as I know, Unity get Korean strings correctly from only IBus at now.
In latest Unity, it works as client of IBus(as result of fix bug ##880876).
So Unity depends on IBus and as result, Unity can't support nabi(which use XIM).
For now there is no bug report about using nabi at Unity, but I test it and notice this problem.
One more thing, does my patch need freeze exception to ship in precise?
| Gunnar Hjalmarsson (gunnarhj) wrote : | # |
As far as I can tell, the proposed changes make sense.
Jinkyu Yi: If Unity's inability to support nabi is of significance to Korean users, it would be great if you could file a bug about it.
review:
Approve


Thank you for your work, what do you mean "Unity can't support it"? do you have a bug reference?