Ubuntu
language-support-zh package

  1. Bug #34282
  2. Comment #38

Comment 38 for bug 34282

Revision history for this message
Loïc Martin (loic-martin3) wrote : Re: [Feisty Edgy Dapper] language-support-"any CJK language" doesn't set up a way to input this language with scim if the session doesn't correspond to this particular CJK (Chinese, Japanese or Korean) language

As far as I understand, a developer speaking Chinese could be handy to backport any changes done by by a CJK-oriented specific distribution of Ubuntu. However, I'm not aware there's any yet (and the RPC already have these kind of distributions, but not Ubuntu-based), nor am I aware that they wouldn't use English as the development language.

For example, scim developers use English as their main language. Using another language would require either Korean and Chinese to learn Japanese, or Chinese and Japanese to learn Korean, or ... :)

Martin, if you look at the step needed to solve this bug, any English speaking developer can handle it. We already provide you with the steps required to make it work (see https://help.ubuntu.com/community/SCIM).

To summarize, a python script could query the user's locale, then run "im-switch -z “your locale” -s scim". To revert the changes : "im-switch -z “your locale” -s default"
Then, using gtk/qt/whatever_is_best to create a front-end to the script - either incorporate a check box "Do you want to enable SCIM in your locale?" in SCIM control panel, or create a application whose simple purpose would be to ask that.

And, to solve bug #93221, no need to speak or understand Chinese either. One doesn't even have to be in a Chinese session to squat the bug, and booting a live cd in Chinese keep the menus in English while still showing the bug (all OO menus are in English till the user install full Chinese support from the Internet).

On the other hand, we acknowledge the fact that "we simply do not have anyone who cares for it at the moment". The amount of high importance bugs that main developers have to fix before each release is daunting enough, and we all appreciate the amount of efforts everyone is making.

Thus the idea to have this bug set as a specification (and hopefully feature critical) for Feisty+1. The problem is well documented and ,as it is, we only need an English speaking developer to take the task. Apparently, Michael Vogt has made some work on it (sadly we don't have access to it, nor do we know what's happening) so the developer could start with some already existing code.