/usr/bin/skype needs different XMODIFIERS to allow Japanese input when cjk flag is set. Reproducible: Always
Maybe you could clarify this is a bit? Plus, this belongs upstream, not to Gentoo.
actually /usr/bin/skype is a script that appears to be added by Gentoo. For example if I download the static or generic package myself and untar it I don't have the /usr/bin/skype script instead if Just have skype binary. If I run the binary straight I can have Japanese input. the wrapper script /usr/bin/skype is not in the generic (shared) or static tar ball. I believe the issue is related to the /usr/bin/skype script (symlinked to /opt/skype/skype.sh script) particularly the XMODIFIERS. If I install the ebuild and just run the binary it also works fine for Japanese input. Only when I run the script which is not included in the tarball do I have an issue.
This is a p.masked alpha thing; if you have issues, take them upstream or don't use it. Thanks.
Again the issue is added by Gentoo not by Skype. This is not caused by Skype this is caused by a Gentoo provied skype.sh script. A temporary solution for any Japanese users would be to symlink /opt/skype/skype to /usr/bin/skype instead of to Gentoo provited /opt/skype/skype.sh
Another ebuild issue was already fixed why close this one repeatedly?
This cannot be sent upsteam as issue is caused by Gentoo provided script.
Either stick a patch here or don't use p.masked stuff; thanks.
In my case if I set XMODIFIERS in gentoo provided skype.sh script to kinput2 it works OK for Japanese input. I could add a sed line to change the script except it may interfere with scim or Chinese users. Another solution that works for me is to just remove the XMODIFIERS=@im=none bit from the gentoo provided script this should work for everyone (english, Japanese, Chinese etc.). The rest of the script can be left as is and it works. If there is no good reason to add the XMODIFIERS variable to the script I suggest simply removing it. I can reopen this when it's unmasked, I was just trying to inform of issues before it's unmasked as it seemed to make sense to me to fix it sooner rather than later. Thank you for the time, very sorry if I was troublesome! I appreciate the wonderful work you do and for providing an ebuild for alpha software at all.
*** Bug 177851 has been marked as a duplicate of this bug. ***
*** Bug 177853 has been marked as a duplicate of this bug. ***
I have found this applies to stable 1.3.053 as well: In skype ebuilds (1.3.0.53-r1 or 1.4.0.58_alpha but not 1.2.0.18) Gentoo provides a script called /opt/skype/skype.sh that it symlinks to /usr/bin/skype . This script is not included in the tarball from skype. In this script there is a line that says XMODIFIERS=@im=none if I change it to kinput2 (I use kinput2 with canna) I can input Japanese fine. If I remove XMODIFIERS from the script entirely I can input Japanese in both versions (1.3.0.53-r1 and 1.4.0.58_alpha). Is there a good reason for setting the XMODIFIERS variable that way, and if not can we just remove the XMODIFIERS from the script? Removing it should allow it not get in the way of input of any language. If I run the Skype provided binary without the Gentoo provided script that also allows Japanese input (in fact I have been using it without an ebuild). If I link /usr/bin/skype to /opt/skype/skype instead of the script that also works fine. I have tested removing XMODIFIERS from the Gentoo provided script in both those ebuilds for static and generic (shared) and I can input Japanese in both. Can we look at just removing the XMODIFIERS variable from /usr/bin/skype aka /opt/skype/skype.sh ?
That was added because of bug: https://bugs.gentoo.org/show_bug.cgi?id=149171 The existence of the script is the result of countless issues with skype that you are free to search the bugzilla or read the ebuld Changelog. The thing is I do not know much about SCIM and input on non Western languages. If you can try please do this: 1-Use the static and -static versions of 1.3 and 1.4. 2-Try with XMODIFIERS=@im=none QT_IM_MODULE=simple 3-Try removing XMODIFIERS=@im=none QT_IM_MODULE=simple 4-Try removing QT_IM_MODULE=simple And report back. Maybe then i can try to make some sence out of it all.
I have tried static and not static versions of both 1.3 and 1.4. I don't actually use scim but kinput2. BTW scim issues seem to be fixed in 1.4 (1.3 shared didn't work due to upstream issue). I find if I remove XMODIFIERS=@im=none they all work (static non static 1.3 and 1.4 with kinput2). Removing QT_IM_MODULE=simple makes no difference for me. I can leave it in and it works (with XMODIFIERS removed) or I can remove it and keep XMODIFIERS and it doesn't work. It's XMODIFIERS that makes the difference. It's exactly the same on shared and not shared and on 1.3 and 1.4. I can also set XMODIFIERS=kinput2 which is my input method and it works as well but that would interfere with scim and other input methods. QT_IM_MODULE=xim also makes no difference. It all comes back to XMODIFIERS. Seems a comment in the bug you reference mentions this script breaks Japanese input as well. I never experienced the issues referenced in that bug but I noticed that they were for an earlier version, do they occur on 1.3.0.53? As far as I'm concerned the script is just fine except for the XMODIFIERS setting which totally breaks Japanese input.
On 1.3 scim users, they would have better luck with static which would eliminate a lot of the script stuff for cjk users. 1.4 works either way from what I've read.
I propose that you could have those variables set for 1.3 shared only or at least the XINPUT variable, as even in the bug they mention a static works. Of course you'd want an echo message slightly different from the 1.3 you have now. It only effects scim not kinput2, so you break cjk for all skype uses when only scim with shared was broken. 1.4 should not need this variable at all as scim issues seem fixed. So basically my suggestion is go ahead and set that variable with shared Skype 1.3 with a warning (if cjk is set) (is there a way to check if scim is input method used if so it could be limited to that) and not set it on 1.3 static nor on 1.4 shared or static.
What portage would check for input method is the XMODIFIERS environment variable if that's possible. For example if I run set I find XMODIFIERS=@im=kinput2
Sorry to post again but I thought for completeness I should mention how to check for scim, as I'm sure you've guessed it's: XMODIFIERS="@im=SCIM" with our without the quotes.
*** Bug 149171 has been marked as a duplicate of this bug. ***
The new 1.4 script removed the incorrect declaration and allows Japanese input both with kinput2 and scim so good improvement there. So in 1.4 (only) this appears fixed.
If all is fixed in 1.4 I'm going to close this bug as fixed because versions < 1.4 will be removed in a few days: http://archives.gentoo.org/gentoo-dev/msg_146147.xml
