[Gutsy 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

[Loïc Martin]

Although language-support-"any CJK language" installs scim and scim-"any CJK input", it doesn't configure the system to allow using scim in applications others than the ones using the gnome input method selector if your session isn't a CJK session.

If we don't want to set scim as an input method for all locales, there should be a central place to allow users to set scim as the default input method for the locale they are using.

It could be an application, or better a button added in System>Preferences>Scim Input Method Configuration (best solution since it's available for any user on a per-user basis).

For Dapper, if time is to short for that before the release, any icon lauching a script that detects the locale used and then launch

im-switch -z "LOCALE used" -s scim

in a terminal would be enough (alternatively it could run im-switch -s scim_xim -z default).

Only need to be checked the possibility to reverse the situation (using the same script that would detect if scim is exported for the locale used in the session, then if not set it, if it is it would unset it) and the fact that it shouldn't affect other users with the same locales (idealy, only the user that has chosen to use scim should be affected)

[Ming Hua (minghua)]

I agree that the docs in /usr/share/doc/scim requires a little too much of the understanding of the whole system and skills to change configurations for the users.

The reason is those docs are mainly for Debian users. Debian systems usually have much more diversities, and the doc would be wrong if it just specify one method that only works for GNOME, for example. Therefore the doc has to cover all possible system configurations and can't avoid being a little vague (at least with my understanding and writing skills, I can't make it more clear).

I agree "working out of the box" experience is a goal worth persuing for scim in ubuntu, of course. We just need more people working on this.

[zero0w (zero0w)]

If you use the OpenOffice.org 2.0.2 m156 packages built for Dapper
Drake, shouldn't SCIM run fine 'out of the box' ?

Now, if you are trying to run the OpenOffice.org 2.0.2 built by the
official OOo homepage, then please check out this SCIM entry in the
Wiki:

https://wiki.ubuntu.com/SCIM

Yes, it is not working out of the box.
But the gcc C++ ABI compatibility issue is not going away for a while
I am afraid.

Also, is this guide by Mr. Bass for Ubuntu Hoary still useful for Dapper Drake?

Ubuntu CJK Chinese Japanese Korean Input Guide
http://www.mrbass.org/linux/ubuntu/scim/

Regards,
-zero0w

On 3/11/06, Ming Hua <email address hidden> wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/34282
>
> Comment:
> I agree that the docs in /usr/share/doc/scim requires a little too much
> of the understanding of the whole system and skills to change
> configurations for the users.
>
> The reason is those docs are mainly for Debian users. Debian systems
> usually have much more diversities, and the doc would be wrong if it
> just specify one method that only works for GNOME, for example.
> Therefore the doc has to cover all possible system configurations and
> can't avoid being a little vague (at least with my understanding and
> writing skills, I can't make it more clear).
>
> I agree "working out of the box" experience is a goal worth persuing for
> scim in ubuntu, of course. We just need more people working on this.

[Ming Hua (minghua)]

On Sat, Mar 11, 2006 at 07:51:04AM -0000, zero0w wrote:
> Comment:
> If you use the OpenOffice.org 2.0.2 m156 packages built for Dapper
> Drake, shouldn't SCIM run fine 'out of the box' ?

Only recently im-switch is added to some of the SCIM module packages,
there are still modules without im-switch support, and can't
automatically start scim when user logs in.

P.S.: Please don't quote my mail if you are not refering to me in
reply, thanks.

Ming
2006.03.11

[zero0w (zero0w)]

So it is a problem of some im-switch modules not added to SCIM,
not because SCIM cannot be configured to work with OpenOffice.org.

Ok, so this is a packaging issue now I suppose.
-zero0w

On 3/11/06, Ming Hua <email address hidden> wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/34282
>
> Comment:
> On Sat, Mar 11, 2006 at 07:51:04AM -0000, zero0w wrote:
> > Comment:
> > If you use the OpenOffice.org 2.0.2 m156 packages built for Dapper
> > Drake, shouldn't SCIM run fine 'out of the box' ?
>
> Only recently im-switch is added to some of the SCIM module packages,
> there are still modules without im-switch support, and can't
> automatically start scim when user logs in.
>
> P.S.: Please don't quote my mail if you are not refering to me in
> reply, thanks.
>
> Ming
> 2006.03.11

[Loïc Martin (loic-martin3)]

I did a clean install of Dapper Flight cd 5 and there's some improvements.
Using a Chinese session makes scim the default input for Open Office.

Using another language (English or French) now allows to select scim as an input in gnome applications (Gedit, gnome-terminal and Nautilus have been tested).
However, still now way to input Chinese in Open Office or Firefox, which are default applications in Ubuntu.

A good number of people prefer to use English (or the language of the country they live in) as their session language, even when they are Chinese. Others, like me, aren't native Chinese speakers but still need to be able to produce documents in Chinese. As for now in Dapper, until that bug is solved, there's no way for an user using a different language than Chinese to input Chinese in the most usefull applications.

One temporary solution would be to be kind enough to tell us how to set scim as default input in Dapper, as a per user basis (be it creating a configuration file or using the command line if necessary). Or letting us now how to start scim along with OO from the command line. Even in Dapper F5, the line
 GTK_IM_MODULE="scim"; oowriter

doesn't work.

A more long-term solution would be to create a button in scim-setup that would create the relevant configuration file for any user that wants to use scim whatever his session language. Or if it's too difficult, just create another menu entry in System>Preferences with a dialog box asking if the user wants to set scim as the default input method. Then the user can uncheck it if he no longer wants to use scim, and the configuration file is erased (or the lines commented).

[Ming Hua (minghua)]

On Fri, Mar 24, 2006 at 11:06:52PM -0000, Loïc wrote:
> One temporary solution would be to be kind enough to tell us how to
> set scim as default input in Dapper, as a per user basis (be it
> creating a configuration file or using the command line if necessary).

These information has been in the scim(1) man page, as well as the
/usr/share/doc/scim/README.Debian.gz file for quite some time.

Ming
2006.03.24

[Loïc Martin (loic-martin3)]

This documentation is nice for *nixes gurus, but not really for mere mortals. What I still don't understand is (quoting scim man page):
>To avoid the inconvenience of having to start the program from X >terminal, make sure you set XMODIFIERS and GTK_IM_MODULE >before starting your X session."
What is the official recommended method to set this in Ubuntu (or, at least, in Debian) so we won't have 10 differents methods advised in the forums or on ubuntu-users ?

Second thing that a Joe user like me doesn't understand is that if I follow (scim man page again):
>To use scim in XIM mode, execute the following commands in an X >terminal (assuming Bourne style shell):
> XMODIFIERS="@im=SCIM"
> export XMODIFIERS
> GTK_IM_MODULE="xim"
> export GTK_IM_MODULE
> scim -d
> <program>
Then start oowriter from the same terminal, I still can't use scim as an input (session is not in Chinese, because when session is in Chinese there's no need for these tricks). What did I miss when I've just been following the instructions?

Last, where is the user supposed to add the line :
scim -c simple -e pinyin -f x11 --no-socket -d
(I assume we don't expect Joe user to type that each time he has logged in :) )

I don't want to sound harsh, the documentation is really nice. But Joe users like me still need a clear explanation of what to do and where in the system to do it.

[Ming Hua (minghua)]

On Sat, Mar 25, 2006 at 01:23:23AM -0000, Loïc wrote:
>
> Second thing that a Joe user like me doesn't understand is that if I
> follow (scim man page again):
> >To use scim in XIM mode, execute the following commands in an X >terminal
> >(assuming Bourne style shell):
> > XMODIFIERS="@im=SCIM"
> > export XMODIFIERS
> > GTK_IM_MODULE="xim"
> > export GTK_IM_MODULE
> > scim -d
> > <program>
> Then start oowriter from the same terminal, I still can't use scim as
> an input (session is not in Chinese, because when session is in
> Chinese there's no need for these tricks). What did I miss when I've
> just been following the instructions?

You missed the following part in /usr/share/doc/scim/README.Debian.gz:

<quote>
There is one limitation in SCIM, that you must tell SCIM the UTF-8 locale you
want to use SCIM in. This is recorded in the user's configuration file
~/.scim/global. You need to add a line of the format
    /SupportedUnicodeLocales = <your_locale>
to your ~/.scim/global file unless you use en_US.UTF-8 locale (which is
supported by default). The <your_locale> string should be in ll_CC.UTF-8
form, where ll being the language, and CC being the country. You can always
use the "locale" command to check your locale setting. You can also add
mutiple locales there, just separate them by comma without space, like
    /SupportedUnicodeLocales = en_US.UTF-8,en_GB.UTF_8,fr_FR.UTF-8
</quote>

Ming
2006.03.24

[Greg Aumann (greg-aumann)]

I'm having this problem on Dapper Beta. Chinese input works fine in a Chinese session. Doesn't work at all in an English session.

If you search the forums using "dapper scim" you will see lots of people having problems with this and few clear solutions.

There are a lot of people that want to use Asian languages but not in an Asian language session and Dapper should have a simpler way to address this need.

[Loïc Martin (loic-martin3)]

For anyone having to use scim in a non-CJK session, there's an interting bug opened here :
https://launchpad.net/distros/ubuntu/+source/scim/+bug/36628

Mainly:
>I tested it again from a fresh Dapper Flight 6 install.
>
>Installing libapt-pkg-perl through Synaptic
>and runing "im-switch -z fr_FR -s scim" from the console
>allowed me to use SCIM by default on a french language session (after restarting the session).

Not tested, because it's not an Ubuntu default and I wouldn't be qualified enough to revert my Dapper intall to default in order to test the (hopefully) fixes that would be released.

However, that's still doesn't solve the bug - the fact is language-support-"CJK language" doesn't set up a way to input the language (unless you choe a session in that language, which is not really a multi-lingual environment).

[Loïc Martin (loic-martin3)]

Confirmed using Dapper 05/23 Daily Build

[Michael Vogt (mvo)]

The current solution is certainly not optimal. It works very welll if you run a native session but not that well otherwise (without going to the commandline).

I would like to propose a spec for edgy that adds a "advanced" button to language-selector. It should contain: "Input method default" (im-switch) and "Optimize display for language" (fontconfig-voodoo).

I'm afraid for dapper all we can do is setup (or improve) the wiki to explain what commands must be entered to get scim for non-CJK sessions.

What do you think?

Cheers,
 Michael

[Loïc Martin (loic-martin3)]

The idea for edgy sounds very good, I've proposed it for Dapper a few month ago with no result, and I'm not a programmer to know if it was feasible. If it comes from a programmer, there's more chances it can work.

Improving the documentation for Dapper might be the only solution left now,however a wiki has nothing official and we'll be facing the same problem as for Breezy : people will get many differents hacks when they'll be asking in the forum, and no way to tell which wiki/forum thread has the answer. Worse, they'll google it and from experience, I can tell they'll only find the good web page after having messed up their system a few times. Having new bugs open for nothing is not the main problem, more the fact that for each bug openned there's a hundred (or more) users that will have the same problem and won't be technical enough (or english fluent enough) to use launchpad.

There's already a lot of threads open about scim for Hoary/Breezy/DapperBetas, and any wiki is going to be lost in the noise.

Would it be possible to get the documentation on how to use scim (which is in main) in a more official way (like included in the packages, or in Dapper's installed documentation) then could be translated?

At the moment, when I look for scim in Yelp, I get the scim man page, which is way too confusing for users, and don't even advertise the im-swich method (you can check yourself, it's provided on any Dapper install, even without CJK support).

It should instead point me to a simple paragraph explaining how to use im-switch to set up scim (explaining how to check user's locale), then how to revert it easily (also with im-swich?)

Could we get some input from CJK testers/users about the easiest and best way for a user to set up scim input in a non-CJK session? Once we get an official method for Dapper, it might be possible as a quick hack to edit the man page, or better to create a small help page and include it in the doc so it's the first thing that appears in Yelp.

Thanks

[Loïc Martin (loic-martin3)]

Sorry for the triple post.

[hendry (hendry-webc)]

It would be best if Ubuntu set SCIM as the default input method for
every install.

I've done a bunch of testing on Dapper and I must say SCIM is a
nightmare. There are lots of issues that need to be ironed out.

Especially in regards to English installations switching over to Korean.
Korean language support also often requires Chinese support too as some
Chinese characters can be used.

[Loïc Martin (loic-martin3)]

Here is an attempt at an easy guide to set up scim input in Dapper.
https://wiki.ubuntu.com/InputMethods/SCIM/CJK_Chinese_Japanese_Korean_Input_Method_configuration_using_SCIM_in_Ubuntu_6%2e06_Dapper_Drake

I'd like as much review as possible, please try to follow the method and email me (or use the wiki, but remember the shorter the better) the points thats need to be ironed out. I especially need advices on a way to easily revert the changes.

[Walter Cheuk (wwycheuk)]

When boot with Chinese (Traditional) language, Chinese input works out of the box in flight 6 (both in Firefox in Ubuntu and Konquerer in Kubuntu), but this is gone in later releases.

[Loïc Martin (loic-martin3)]

Walter, I think you should open a new bug report for this case, especially because it's a regression and should be treated as a high priority. Then you can describe it enough to give the devs enough clues about what went wrong.

[Walter Cheuk (wwycheuk)]

Hi, the bug ID is #47411

[Jan Ask (janaskhoej)]

This problem still exists in Edgy (final). If you do an English install, you will be unable to input CJK in applications.

Using the steps in this guide, I can always get it to work.
http://www.ubuntuforums.org/archive/index.php/t-27811.html

[Michael Vogt (mvo)]

Thanks for the additional information and sorry that this feature did not made it into edgy.

My bzr branch at http://bazaar.launchpad.net/~ubuntu-core-dev/language-selector/ubuntu/ has a new checkbox "Enable input methods" that can be used to globally enable scim input even for non-CJK languages. When feisty opens I will immediately upload it.

If people are interessted in testing this new feature I can build debs for edgy (maybe dapper too) fromthe repository.

Cheers,
 Michael

[Loïc Martin (loic-martin3)]

I'll be pleased to test it. I'll keep Dapper for about a month or so, so I'll be able to test Dapper packages too during that timeframe.

Edgy debs would indeed be welcome and tested :)

Thanks a lot for these good news,
Loïc

[Jan Ask (janaskhoej-gmail)]

This problem still exists in Feisty Herd 3 (kubuntu). Using the following workaround, I can get it to work in all applications except Open Office:

sudo touch /etc/X11/Xsession.d/74custom-scim_startup
sudo chmod 646 /etc/X11/Xsession.d/74custom-scim_startup
echo 'export XMODIFIERS="@im=SCIM"' >> /etc/X11/Xsession.d/74custom-scim_startup
echo 'export GTK_IM_MODULE="scim"' >> /etc/X11/Xsession.d/74custom-scim_startup
echo 'export XIM_PROGRAM="scim -d"' >> /etc/X11/Xsession.d/74custom-scim_startup
echo 'export QT_IM_MODULE="scim"' >> /etc/X11/Xsession.d/74custom-scim_startup
sudo chmod 644 /etc/X11/Xsession.d/74custom-scim_startup

For some reason, only OpenOffice doesn't even allow me to change to Japanese input. Copy/Pasting Japanese characters works though.

[Loïc Martin (loic-martin3)]

This problem is solved here on Feisty Herd 4 (+ all updates). I can input with scim in Open Office using a default French session (+Beryl).

Jan Ask, can you confirm?

Thanks

[Jan Ask (janaskhoej-gmail)]

Hi Loic

Sorry, this problem still exists in a fresh install of Herd CD 5.

Steps taken:
After installation, under System Settings -> Regional and Language, install New Language"Japanese"
Add Japanese to "Languages"
(adept batch completes successfully)
Set keyboard to Japanese and logout
Login and setup Scim to use Japanese
Logout and relogin
Fire up Kate and Openoffice.
Try to switch to Japanese input... unfortunately I cannot switch.

I dont know if this is any help, but I played around with scim for a while, and found out that using the command "sudo im-switch -z en_US -s scim", Japanese input becomes possible.

[Loïc Martin (loic-martin3)]

You're right. Since Herd 4, Chinese input has been playing tricks : two times, after some updates, scim IM has been enabled by default (without having done anything) then gone away.

In Feisty Beta, the bug is still there and an user has no way to input any CJK language in Open Office or Firefox, even though these apps are Core apps.

Michael Vogt, what's happening with your branch?

[Jan Ask (janaskhoej-gmail)]

Sorry to do a follow up, but it seems this bug isn't moving forward. I just did a fresh install of Feisty with all the updates. The bug is still present.

It would be great for all the users that need CJK language support to have this fixed for Feisty Final.

Let me know if you need help with testing

[Loïc Martin (loic-martin3)]

Jan, you're right and moreover there's a new problem (regression) which makes the situation in Feisty worse than it was already in Edgy/Dapper: see bug #93221 which doesn't seem to be taken care atm (and that one doesn't have any manual fix).

I think what might be needed would be an external developer willing to fix the bugs, even though the problem arise in core packages.

Even a small reply informing us that nothing will be done and that we shouldn't bother doing any testing and filling bug reports would be nice. Maybe the only way to get an answer would be to ask Mark if there's any plans to support CJK languages in a future version of Ubuntu.

[Jan Ask (janaskhoej-gmail)]

Hmm. Doesn't sound good.

In my opinion, this is more than a Medium Importance bug, as it affects all users in China, Korea and Japan who use (K)Ubuntu in English. Potentially a lot of people.

Since nobody seems to be involved in fixing this bug (CJK input has been broken since Hoary!), I think we do need to escalate it somewhere -Though going to Mark might be a bit too much. Do you know how to get the attention of the developers?

I even considered putting up a Bounty, just to get this fixed :)

[Loïc Martin (loic-martin3)]

I think best is to write a specification for next milestone (contributors welcomed) AND email Mark so there's a slight chance it could be considered as a targeted feature (hopefully with high priority) for Feisty+1, and that has to be done before next summit.

I don't think emailing Mark once we have a good-looking specification is over the top - we had main (core) developers looking this bug once and a while, but without a clear understanding of priorities, I guess other bug work takes precedence - at least a release critical bug is going to attract more attention.

If anybody here has some experience about specifications and more important about the schedule to get the specification discussed at next summit, I'll be happy to have some help.

[Martin Pitt (pitti)]

What we would need for bugs like this is a developer who actually speaks and uses these languages. I do agree that it is very important to have a good CJK support out of the box, but we simply do not have anyone who cares for it at the moment.

[ZhengPeng Hou (zhengpeng-hou)]

because scim it self provide a configure file for im-switch, but it
use xim for qt application, but xim can not beed used with qt now, so
you'd so switch to use the configure file provided by scim-pinyin
scim-anthy, etc. it's a bug of qt that can not use xim now.

[Jan Ask (janaskhoej-gmail)]

That is too bad. I (and many others) have hoped to have this fixed for a
long time.

But if it really is the case that nobody cares for support for Asian
languages, I think we should make this clear to our users. It would be more
honest to say that Asian languages are not supported in Ubuntu if this
really is the case.

Anyway, thanks for your honest answer.

[ZhengPeng Hou (zhengpeng-hou)]

Sorry for my previous comment, qt now can use xim.
I can do about 3-4 times fresh install with kubuntu, using alternate cd, IM can be used after I configured it using language-selctor.

[ZhengPeng Hou (zhengpeng-hou)]

2007/4/9, Jan Ask <email address hidden>:
> That is too bad. I (and many others) have hoped to have this fixed for a
> long time.
>
> But if it really is the case that nobody cares for support for Asian
> languages, I think we should make this clear to our users. It would be more
> honest to say that Asian languages are not supported in Ubuntu if this
> really is the case.
>
> Anyway, thanks for your honest answer.
would you like come to irc and talk me directly? I care it. :)

[Loïc Martin (loic-martin3)]

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.

[Jan Ask (janaskhoej-gmail)]

I would love to help on irc if I can! Let me know what to do.

On 4/9/07, ZhengPeng Hou <email address hidden> wrote:
>
> 2007/4/9, Jan Ask <email address hidden>:
> > That is too bad. I (and many others) have hoped to have this fixed for a
> > long time.
> >
> > But if it really is the case that nobody cares for support for Asian
> > languages, I think we should make this clear to our users. It would be
> more
> > honest to say that Asian languages are not supported in Ubuntu if this
> > really is the case.
> >
> > Anyway, thanks for your honest answer.
> would you like come to irc and talk me directly? I care it. :)
>
>

[Loïc Martin (loic-martin3)]

To Martin and ZhengPeng Hou
ZhengPeng Hou said
"Sorry for my previous comment, qt now can use xim.
I can do about 3-4 times fresh install with kubuntu, using alternate cd, IM can be used after I configured it using language-selector."

We did have scim input working in Feisty, but it was kind of a yoyo thing - here one day, gone the other. And once scim input is enabled (I'm talking OO here, so if qt wasn't using scim, nor did OO), the user must be able to deactivate it if he changes his mind.

I'll check with the RC - daily builds haven't been up-to-date recently OO wise - to see if the bug is solved. However, I can't remember any changelogs that were addressing this bug or bug #93221, and I think I've really checked thoroughly before installing each update.

Nevertheless, since we got no information during the whole Feisty development cycle, we can only assume it's not been worked on.

[ZhengPeng Hou (zhengpeng-hou)]

To:Loïc
At least it can work using Chinese. I will have a test for other CJK
languages later.

[Loïc Martin (loic-martin3)]

ZhengPeng, I'm not sure I understand your comment.

Chinese input under a Chinese session has been working for quite a while (worked in Dapper/Edgy). Now, does it work under a different locale (neither CJK nor the default en_US - even though the locale can be English :) but not US) in Open Office/Firefox? If it works in Open Office/Firefox after installing the support for Chinese with Administration>Language Support, does uninstalling this support remove scim input (i.e. CTRL-Space won't start scim) which would be the required behavior?

Thanks

[ZhengPeng Hou (zhengpeng-hou)]

have you noticed that there have a option in language-selector: enable
input( I don't remember it exactly), if you choose it, you can use
scim under any locales

[Loïc Martin (loic-martin3)]

Yes, I did notice :)

However, during Feisty's development cycle, this has been more like a yo-yo thing : sometimes it works, sometimes it doesn't, sometimes it only works for a few days :)

OTOH, I do notice that once it works, unchecking the option usually doesn't work (that habit being more stable than the other way around).

However, we had no input regarding the fact that this option was there to solve the bug or not :) and I don't really think just hope does the trick. That said, I'll be happy if the 2 bugs are solved in RC, because there could then be a possibility the bug aren't reintroduced before the final release comes out.

[Jan Ask (janaskhoej-gmail)]

Just a final confirmation that this bug is still present in the final Feisty.

Whats more, im-switch -z "LOCALE used" -s scim doesn't seem to work anymore.

Lets see if we can get this fixed for Gutsty

[Ming Hua (minghua)]

Jan Ask wrote:
> Whats more, im-switch -z "LOCALE used" -s scim doesn't seem to work anymore.

I wonder why that is the case. If a UTF-8 locale is used, scim should work just fine if you set "/SupportedUnicodeLocales" properly. Read /usr/share/doc/scim/README.Debian.gz for details about setting "/SupportedUnicodeLocales".

[Emmet Hikory (persia)]

On 4/23/07, Ming Hua <email address hidden> wrote:
> I wonder why that is the case. If a UTF-8 locale is used, scim should
> work just fine if you set "/SupportedUnicodeLocales" properly. Read
> /usr/share/doc/scim/README.Debian.gz for details about setting
> "/SupportedUnicodeLocales".

    Perhaps this could be configured automatically when configuring
language support? Many users do not use the en_US locale.

[Ming Hua (minghua)]

On Mon, Apr 23, 2007 at 02:07:34AM -0000, Emmet Hikory wrote:
> On 4/23/07, Ming Hua <email address hidden> wrote:
> > I wonder why that is the case. If a UTF-8 locale is used, scim should
> > work just fine if you set "/SupportedUnicodeLocales" properly. Read
> > /usr/share/doc/scim/README.Debian.gz for details about setting
> > "/SupportedUnicodeLocales".
>
> Perhaps this could be configured automatically when configuring
> language support? Many users do not use the en_US locale.

Yes, it would be nice if non-en_US UTF-8 locales can be supported out of
box. However I have no idea how to do that, patches are always welcome.

Ming
2007.04.23

[Emmet Hikory (persia)]

    I see three ways to address this:

1) im-switch is add the current (or requested) locale to /SupportedUnicodeLocales
2) /etc/scim/global to include all locales by default (my least favorite)
3) scim itself to ignore /SupportedUnicodeLocales always attempt to support the current locale

    I'm not very familiar with the architecture of im-switch and scim, and so am unsure of the ancillary effects that might develop as a result of any of these choices. From my quick review, I would suspect that the first is the least intrusive (although not necessarily correct), and would involve parsing (or creating) ~/.scim/global to include the appropriate locale.

    For which of these (if any) should a patch be generated? Alternately, is this more complicated than it looks, and does the patch need to be somewhere else?

[Ming Hua (minghua)]

On Mon, Apr 23, 2007 at 11:43:38PM -0000, Emmet Hikory wrote:
> I see three ways to address this:
>
> 1) im-switch is add the current (or requested) locale to
> /SupportedUnicodeLocales

This is a very fragile solution. The file /etc/scim/global which
contains the "/SupportedUnicodeLocales" configuration is a conffile of
package scim. In principle im-switch shouldn't touch other package's
conffile.

Also locales can be generated by user actions, whether installing
language support packages, or explictily run "dpkg-reconfigure locales"
(or something similar in Ubuntu). The only "current" situation
im-switch can know is when it is installed, which can be very different
from the situation when scim is run.

> 2) /etc/scim/global to include all locales by default (my least favorite)

I don't like it either. There are just too many UTF-8 locales. And
keeping a duplicate list which may get updated from time to time is
never a good idea.

> 3) scim itself to ignore /SupportedUnicodeLocales always attempt to
> support the current locale

Some non-UTF-8 locales just can't be supported, such as en_US
(ISO-8859-1 encoding). Even if we only consider UTF-8 locales, this
still needs knowledge about both the scim code and locale handling.
This is close to what I have in mind when I say "patches are always
welcome", changing the way scim handles locales.

> I'm not very familiar with the architecture of im-switch and scim,
> and so am unsure of the ancillary effects that might develop as a result
> of any of these choices. From my quick review, I would suspect that the
> first is the least intrusive (although not necessarily correct), and
> would involve parsing (or creating) ~/.scim/global to include the
> appropriate locale.

If you want to modify ~/.scim/global instead of /etc/scim/global, you
have the problem of only being able to change setting on a user-by-user
basis, but not system-wide.

Also, if scim is already running, it will ignore changes to
~/.scim/global and rewrite its internal settings back when it exits.
That's another issue that needs consideration.

Ming
2007.04.26

[Emmet Hikory (persia)]

    Thanks for the detailed review. How about supporting all UTF8 locales by default? This avoids the non-UTF-8 problem, and should work for the standard default installation. Of course, it will cause additional issues for scim users in non-UTF-8 locales :(

[Loïc Martin (loic-martin3)]

This problem seems to have been fixed for me in Feisty final release. However, it could be only in my locale (fr_FR).

Steps to do after a clean install to verify:

- System>Administration>Language support
Check "Chinese" then Apply
UNCHECK "Activate ... complex characters" (the box below "Input Method" then Apply
Check it again (the box should be in a checked state) then Apply

-Reboot the computer

You should now be able to use the shortcut CTRL-Space to activate scim input in Open Office and Firefox

Can you please tell us if it doesn't work for your locale (please also indicate what your locale is)?

[Jan Ask (janaskhoej-gmail)]

Thank Loic! I think I got it now. It does work... to a degree.

I just did a new install of Feisty, and did - System>Administration>Language support Check "Japanese". The script starts, and the packages are downloaded successfully. After making sure that "complex characters" is checked, I click OK. Now here comes the funny part, if you open Language support again, "complex characters" is now unchecked. Not until you click APPLY instead of OK, does the "complex characters" stay checked.

After doing this and logging out and in, I can use Japanese. Looks like we are getting closer to a solution. Can you confirm?

I am using en_US as my locale

(By the way, after the Language support script has run, from a usability standpoint, there should be a "You may need to login again for the changes to take effect" message, but that is a different story)

[Ming Hua (minghua)]

Recent discussions start to make me think this is actually a problem with the installer or the language-support-* packages, instead of a problem with scim. Maybe this bug should be reassigned to appropriate package?

[Michal Suchanek (hramrach)]

Note that you can have im-switch set up scim as the default method for all_ALL - any locale. It would still need some way to make scim try to support any UTF-8 locale without modyfing config files, though. Perhaps adding the current locale on session start? Or add locales to the global file when locales are added?

[Loïc Martin (loic-martin3)]

Just an update on current situation (Feisty) when using only the Language Support tool in Administration :

I noticed that if you remove Open Office, then reinstall it without the Open Office Gnome package, you can't input with scim in OO (it still works for Firefox and other apps where it worked before). Once you install the package, it works again.

So it seems some apps needs their own settings (I didn't test, but I'm under the impression that the brute force im-switch manual configuration would still work whan OO Gnome support package isn't installed.

I don't know what to make out of it, though :)

[Jan Ask (janaskhoej-gmail)]

Hi all,

This bug is still present in Gutsy Tribe 3. Tested on Kubuntu.

Steps taken:
After installation, under System Settings -> Regional and Language, install New Language"Japanese"
Add Japanese to "Languages"
(adept batch completes successfully)
Set keyboard to Japanese and logout
Login and setup Skim to use Japanese
Logout and relogin
Fire up Kate and Openoffice.
Try to switch to Japanese input... unfortunately I cannot switch.

[Jan Ask (janaskhoej-gmail)]

Hi all,

It _finally_ seems like we can close this one. In the newest Gutsy tribe, CJK installation works as it is supposed to.

Tested using Ubuntu gutsy-desktop amd64 on a vmware machine.

Could someone else test this (preferably on a Kubuntu setup)?

Thanks

[Jan Ask (janaskhoej-gmail)]

Bump :)

[Loïc Martin (loic-martin3)]

Hi,
Is anybody having scim problems in Ubuntu Gutsy?

Even in gedit, selecting scim input from the contextual menu doesn't
work (even though scim is sitting idle in the taskbar), not to talk
about the Ctrl+Space method in other applications.

I installed support for Chinese, English and French and am under a
French session, and I also checked the "Enable support to enter complex
characters" (I unchecked and checked it a few times, restarting X in the process to be sure).

Since then, it borked my keyboard, but didn't give me any access to scim
input,
Thanks,
Loic (yes, the ¨on the i doesn't work anymore, unless I copy/paste it)

[Loïc Martin (loic-martin3)]

For the keyboard problem, I did a few tests and filled Bug #155780

[Water Liu (water)]

I have experienced Opera Browser shortcut key conflit with SCIM
and quite often my IM (gaim) crashes because of SCIM. Have to
manually kill process and restart it for X11. Pain...

On 10/22/07, Loïc Martin <email address hidden> wrote:
> For the keyboard problem, I did a few tests and filled Bug #155780
>
> --
> [Gutsy 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
> https://bugs.launchpad.net/bugs/34282
> You received this bug notification because you are a member of Ubuntu
> Simplified Chinese Translators, which is a bug contact for language-
> support-zh in ubuntu.
>

--
This e-mail, any attachments and the information contained therein
("this message") are confidential and intended solely for the use of
the addressee(s). If you have received this message in error please
send it back to the sender and delete it. Unauthorized publication,
use, dissemination or disclosure of this message, either in whole or
in part is strictly prohibited.
**********************************************************************
Ce message electronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci apres "le message" ), sont
confidentiels et destines exclusivement a l'usage de la personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur,
merci de le renvoyer a son emetteur et de le detruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous
quelque forme que se soit non expressement autorisees de ce message,
sont interdites.
**********************************************************************

[robinl (robinl-cfso1751)]

I have the exact same problem with Gutsy. Both SCIM and dead keys work back in Feisty and then I dist-upgraded to Gutsy back in beta and both broke.

[Ming Hua (minghua)]

On Tue, Oct 23, 2007 at 04:23:21AM -0000, robinl wrote:
> I have the exact same problem with Gutsy. Both SCIM and dead keys work
> back in Feisty and then I dist-upgraded to Gutsy back in beta and both
> broke.

Please follow up deadkey issues in bug #155780, thanks.

Ming
2007.10.23

[Loïc Martin (loic-martin3)]

Just to update the situation, after a few searches :

- after scim install, a normal input has borked dead keys even though /FrontEnd/X11/Dynamic is set to false ;
- after scim install, one can use scim in gedit by selecting it as Input Method in the contextual menu ;
- checking the "Enable support to enter complex characters" box doesn't enable scim input for all applications anymore, which is a big regression from Feisty.

I'm using a french keyboard under a fr_FR locale, but it's the same under an en_GB locale.

[robinl (robinl-cfso1751)]

I've found the solution on Chinese Ubuntu forums on http://forum.ubuntu.org.cn/viewtopic.php?p=479741&sid=c37de1d11989db6ebe95227b35efa770#479818 ,
which say
sudo apt-get install scim-bridge
sudo gedit /etc/X11/xinit/xinput.d/scim
change GTK_IM_MODULE=xim into GTK_IM_MODULE="scim-bridge"
and restart X.
This fixed the problem (both deadkey and SCIM) for me.

[robinl (robinl-cfso1751)]

Sorry wrong place...

[Loïc Martin (loic-martin3)]

No, it's the right place too, since we were also puzzled by Gutsy's changes. I can confirm your method works for me, and I've edited https://help.ubuntu.com/community/SCIM accordingly.

Thanks a lot, robinl.

[Ming Hua (minghua)]

On Wed, Oct 24, 2007 at 09:48:29AM -0000, robinl wrote:
> sudo apt-get install scim-bridge
> sudo gedit /etc/X11/xinit/xinput.d/scim
> change GTK_IM_MODULE=xim into GTK_IM_MODULE="scim-bridge"
> and restart X.
> This fixed the problem (both deadkey and SCIM) for me.

On Wed, Oct 24, 2007 at 01:45:57PM -0000, Loïc Martin wrote:
> I can confirm your method works for me, and I've edited
> https://help.ubuntu.com/community/SCIM accordingly.

Personally I think it's a very bad idea to encourage users to manually
change system conffiles (/etc/X11/xinit/xinput.d/scim is one of them)
when there is an alternative.

The alternative, and the proper way to use scim-bridge IMO, is to copy
/etc/X11/xinit/xinput.d/scim to /etc/X11/xinit/xinput.d/scim-bridge,
then modify the new scim-bridge configuration file, and run "im-switch
-s scim-bridge".

But since I have never worked on the help.ubuntu.com documentation, I
won't change it myself, and leave the decision to someone who can make
better judgement.

Ming
2007.10.26

[Loïc Martin (loic-martin3)]

Ming, if someone would have been so kind as to explain to Gusty users how they could eventually solve their deadkeys problem and get scim to work (I'm sorry, but
>Please follow up deadkey issues in bug #155780, thanks.
didn't solve anything, neither for scim nor for the deadkeys issue), we wouldn't have to maintain the SCIM page ourselves.

I'm far from being able to make a better judgement than you - but I know only robinl came with a method that worked, and that after one week of big regression, when we couldn't use our computer for the productivity tasks we were taking for granted.

We all know it's not your fault, and it's quite saddening to see the good work you do in Debian messed up by some anonymous Ubuntu main developer.

The documentation at https://help.ubuntu.com/community/SCIM is open to anyone to edit - and different inputs have already made the page more helpful. Anybody able to understand the method you just suggested and check it works in Gutsy will be able to edit that page accordingly - the only important thing is that the explanation is easily understandable by a newbie, with screenshots and such.

>Personally I think it's a very bad idea to encourage users to manually
>change system conffiles (/etc/X11/xinit/xinput.d/scim is one of them)
>when there is an alternative

There was no alternative till you explained it to us, and during that time we need to get our job done. I know you're on Debian, but for the other subscribers, if this was a so well-known method, how come none of the Gusty developers answered our difficulties in this thread, or, better, advertise us that a major breakage would occur with scim in Gutsy (release highlights are for that, not just for show)?

Anyway, thanks again Ming for spending time for us even though you're on Debian. If none edits the documentation, I might do it again if I can test that on another computer. For the moment, I'd rather keep things as they are on mine, because one week of mess is more than enough.

[Jan Ask (janaskhoej-gmail)]

CJK language support tested on Ubuntu Gutsy daily build 30 Dec 2007.

CJK import works, but after logging in, I get an error saying something like "Language en_US doesn't exist, using default". If this can be removed, it looks like we are finally getting there.

[Ming Hua (minghua)]

Jan Ask wrote:
> CJK language support tested on Ubuntu Gutsy daily build 30 Dec 2007.

What does "Gutsy daily build" mean? Did you mean hardy? Or gutsy release (7.10)?

[Jan Ask (janaskhoej-gmail)]

Sorry, I was too fast on the trigger.

Of course I meant Hardy (8.04).

[Jan Ask (janaskhoej-gmail)]

Another update. Japanese language Installation on Hardy, Alpha 5 - Released Feb 22nd, 2008

There are two problems still remaining:

1. When Selecting "Enable support to enter complex charactes", user has to click "Apply" and then "OK". If user just selects "OK", the window quits without remembering selection.

2. After successfully installing Japanese language, the user is presented with a prompt saying "The selected language en_US does not exist, using system default" - This can be remedied by manually selecting default session language once.

I have not yet encountered the deadkeys problem yet, but I have only tested for a day. Can someone else confirm?

[robinl (robin4home)]

I can confirm no.1, I was wondering why SCIM didn't show up on my fresh Gutsy install. Never seen no.2 though.

[Boning Chen (neodarksaver)]

no 1 is confirmed here.

On Sun, Feb 24, 2008 at 11:21 PM, robinl <email address hidden> wrote:

> I can confirm no.1, I was wondering why SCIM didn't show up on my fresh
> Gutsy install. Never seen no.2 though.
>
> --
> [Gutsy 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
> https://bugs.launchpad.net/bugs/34282
> You received this bug notification because you are a member of Ubuntu
> Simplified Chinese Translators, which is subscribed to language-support-
> zh in ubuntu.
>

[Emix (liuying)]

Thank you for your help。

2008/2/25, NeoDarkSaver <email address hidden>:
>
> no 1 is confirmed here.
>
>
> On Sun, Feb 24, 2008 at 11:21 PM, robinl <email address hidden> wrote:
>
> > I can confirm no.1, I was wondering why SCIM didn't show up on my fresh
> > Gutsy install. Never seen no.2 though.
> >
> > --
> > [Gutsy 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
> > https://bugs.launchpad.net/bugs/34282
> > You received this bug notification because you are a member of Ubuntu
> > Simplified Chinese Translators, which is subscribed to language-support-
> > zh in ubuntu.
> >
>
> --
> [Gutsy 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
> https://bugs.launchpad.net/bugs/34282
> You received this bug notification because you are a member of Ubuntu
> Simplified Chinese Translators, which is subscribed to language-support-
> zh in ubuntu.
>

[Jan Ask (janaskhoej-gmail)]

I tried a new install of Hardy Alpha 5 just to test this. The error
where the user is presented with a prompt saying "The selected
language en_US does not exist" is real, and should be easy to
reproduce for others with a fresh install as well.

On Tue, Feb 26, 2008 at 1:07 PM, liuyingxianglan
<email address hidden> wrote:
> Thank you for your help。
>
> 2008/2/25, NeoDarkSaver <email address hidden>:
>
>
> >
> > no 1 is confirmed here.
> >
> >
> > On Sun, Feb 24, 2008 at 11:21 PM, robinl <email address hidden> wrote:
> >
> > > I can confirm no.1, I was wondering why SCIM didn't show up on my fresh
> > > Gutsy install. Never seen no.2 though.
> > >
> > > --
> > > [Gutsy 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
> > > https://bugs.launchpad.net/bugs/34282
> > > You received this bug notification because you are a member of Ubuntu
> > > Simplified Chinese Translators, which is subscribed to language-support-
> > > zh in ubuntu.
> > >
> >
> > --
> > [Gutsy 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
> > https://bugs.launchpad.net/bugs/34282
> > You received this bug notification because you are a member of Ubuntu
> > Simplified Chinese Translators, which is subscribed to language-support-
> > zh in ubuntu.
> >
>
> --
> [Gutsy 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
> https://bugs.launchpad.net/bugs/34282
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
305-0821 Ibaraki-ken
Tsukuba-shi, Kasuga 2 Choume 3-5-103
Japan

([phone]
<email address hidden>

[Emix (liuying)]

That problem come out in Hardy Alpha 4，Hardy Alpha 5 already solved。I
mean。。。
あの��はHardy Alpha 4の�合がありますが、Hardy Alpha 5はもう解�しました。言�の�入法ソフトと言�不��化で起こしました。

2008/2/26, Jan Ask <email address hidden>:
>
> I tried a new install of Hardy Alpha 5 just to test this. The error
> where the user is presented with a prompt saying "The selected
> language en_US does not exist" is real, and should be easy to
> reproduce for others with a fresh install as well.
>
>
> On Tue, Feb 26, 2008 at 1:07 PM, liuyingxianglan
> <email address hidden> wrote:
> > Thank you for your help。
> >
> > 2008/2/25, NeoDarkSaver <email address hidden>:
> >
> >
> > >
> > > no 1 is confirmed here.
> > >
> > >
> > > On Sun, Feb 24, 2008 at 11:21 PM, robinl <email address hidden>
> wrote:
> > >
> > > > I can confirm no.1, I was wondering why SCIM didn't show up on my
> fresh
> > > > Gutsy install. Never seen no.2 though.
> > > >
> > > > --
> > > > [Gutsy 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
> > > > https://bugs.launchpad.net/bugs/34282
> > > > You received this bug notification because you are a member of
> Ubuntu
> > > > Simplified Chinese Translators, which is subscribed to
> language-support-
> > > > zh in ubuntu.
> > > >
> > >
> > > --
> > > [Gutsy 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
> > > https://bugs.launchpad.net/bugs/34282
> > > You received this bug notification because you are a member of Ubuntu
> > > Simplified Chinese Translators, which is subscribed to
> language-support-
> > > zh in ubuntu.
> > >
> >
> > --
> > [Gutsy 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
> > https://bugs.launchpad.net/bugs/34282
>
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> 305-0821 Ibaraki-ken
> Tsukuba-shi, Kasuga 2 Choume 3-5-103
> Japan
>
> ([phone]
> <email address hidden>
>
>
> --
>
> [Gutsy 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
> https://bugs.launchpad.net/bugs/34282
> You received this bug notification because you are a member of Ubuntu
> Simplified Chinese Translators, which is subscribed to language-support-
> zh in ubuntu.
>

[Jan Ask (janaskhoej-gmail)]

Hi liuyingxianglan,

I am not sure what you mean. While it is true that you can install
asian languages, the following three problems still remain in Hardy
Alpha 5:

1. When Selecting "Enable support to enter complex charactes", user
has to click "Apply" and then "OK". If user just selects "OK", the
window quits without remembering selection.
2. After successfully installing Japanese language, the user is
presented with a prompt saying "The selected language en_US does not
exist, using system default" - This can be remedied by manually
selecting default session language once.
3. Deadkeys problem using SCIM

[Yiding He (yiding-he)]

Hi everyone,

When I upgraded from 7.10 to 8.04 Alpha 5, I got "The selected language
zh_CN does not exist, using system default" too. I changed the language
settings on logon screen to Chinese and this message never showed again.

Deadkeys problem is still there, too.

Jan Ask 写道:
> Hi liuyingxianglan,
>
> I am not sure what you mean. While it is true that you can install
> asian languages, the following three problems still remain in Hardy
> Alpha 5:
>
> 1. When Selecting "Enable support to enter complex charactes", user
> has to click "Apply" and then "OK". If user just selects "OK", the
> window quits without remembering selection.
> 2. After successfully installing Japanese language, the user is
> presented with a prompt saying "The selected language en_US does not
> exist, using system default" - This can be remedied by manually
> selecting default session language once.
> 3. Deadkeys problem using SCIM
>
>

[Emix (liuying)]

Thank you for your help.before this It is so hard that i can not resolved
that problem

2008/2/27, Yiding He <email address hidden>:
>
> Hi everyone,
>
> When I upgraded from 7.10 to 8.04 Alpha 5, I got "The selected language
> zh_CN does not exist, using system default" too. I changed the language
> settings on logon screen to Chinese and this message never showed again.
>
> Deadkeys problem is still there, too.
>
>
>
> Jan Ask 写道:
>
> > Hi liuyingxianglan,
> >
> > I am not sure what you mean. While it is true that you can install
> > asian languages, the following three problems still remain in Hardy
> > Alpha 5:
> >
> > 1. When Selecting "Enable support to enter complex charactes", user
> > has to click "Apply" and then "OK". If user just selects "OK", the
> > window quits without remembering selection.
> > 2. After successfully installing Japanese language, the user is
> > presented with a prompt saying "The selected language en_US does not
> > exist, using system default" - This can be remedied by manually
> > selecting default session language once.
> > 3. Deadkeys problem using SCIM
> >
> >
>
> --
> [Gutsy 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
> https://bugs.launchpad.net/bugs/34282
> You received this bug notification because you are a member of Ubuntu
> Simplified Chinese Translators, which is subscribed to language-support-
> zh in ubuntu.
>

[Loïc Martin (loic-martin3)]

I opened a Ubuntu Brainstorm idea at http://brainstorm.ubuntu.com/idea/2203/ (there was another idea about CJK, but focusing on other problems, like fonts. I restricted mine to just allowing CJK input on a Latin locale).

Feel free to vote on it, hopefully it might attract Canonical's attention.

(For records, in each release development cycle we had days where scim input seemed to work under a Latin locale - however it was never linked to anyone working on the bug, and eventually all support for allowing users to use scim under a Latin locale disappeared on release day, so as long as no developer with main - main as in main repository - rights is working on this bug, there's sadly no reason to expect it to be different this time).

[Loïc Martin (loic-martin3)]

Somebody put it as a duplicate of http://brainstorm.ubuntu.com/idea/285/ so go there instead if you want to vote. I can't edit the description or title of this bug, though, so if any moderatoer could add the words Chinese Japanese Korean and CJK to the title or description, it will give more visibility, since normal users wouldn't know the name of the input method (scim) just that they want to input one of these languages (I know they're not the only ones, but the most common on launchpad).

[Loïc Martin (loic-martin3)]

Somebody put it as a duplicate of http://brainstorm.ubuntu.com/idea/285/ so go there instead if you want to vote. I can't edit the description or title of this bug, though, so if any moderater could add the words Chinese Japanese Korean and CJK to the title or description, it will give more visibility, since normal users wouldn't know the name of the input method (scim) just that they want to input one of these languages (I know they're not the only ones, but the most common on launchpad).

[Jan Ask (janaskhoej-gmail)]

After a period using fedora, I just tested this again using a fresh install of ubuntu 8.04.1, and both installation and input works flawlessly. I also have no problems with deadkeys.

Can we *finally* close this bug?

[Michael Vogt (mvo)]

@Jan Ask:
Thanks for confirming that it is fixed for you.

The hardy (8.04) version of language-selector should finally get this right now, please reopen if there are still issues.

[xteejx (xteejx-deactivatedaccount)]

Marking language-support-zh as Invalid, believe this may have been missed, if this is in error, please reset this to New under Status.

[Michal Suchanek (hramrach)]

2009/5/20 Teej <email address hidden>:
> Marking language-support-zh as Invalid, believe this may have been
> missed, if this is in error, please reset this to New under Status.
>
> ** Changed in: language-support-zh (Ubuntu)
>       Status: New => Invalid

On a fresh installation of Jaunty scim is installed even for English
but it does not seem active. Pressing Ctrl+Space does nothing and I
did not notice any scim panel either.

Neither do I see any tool for switching it on.

[xteejx (xteejx-deactivatedaccount)]

Isn't everything under System>Administration>Language Support now?

[xiebin (3183669-163)]

my ubuntu updata from 8.10,my scim is nearly ok, but when I input
Chinese in pidgin 2.5.5 ,the scim will die,when after I kill the
scim-panel-gtk process ,every thing will be ok.
在 2009-05-20三的 08:40 +0000，Teej写道：
> Isn't everything under System>Administration>Language Support now?
>

[xteejx (xteejx-deactivatedaccount)]

I think this other problem you're having is not related to the original issue. Can you file another bug report against this please? Thank you. :)