When using Libreoffice KDE integration on Arch (other distributions have the same problem), Fcitx (an input method for East Asian scripts) only displays over-the-top input. This makes it very hard to write longer sentences because the pre-commit string does not fit into the actual written text. Especially in a word processor this is extremely hard to use.
Here is a OpenSUSE forum entry which describes the problem with screenshots:
A workaround is to use libreoffice-gnome integration, but this does not integrate so well into KDE.
Is there any hope that this will be fixed? From what I understand from the OpenSUSE thread, Libreoffice should use QT_IM_MODULE when using the KDE integration. Or at least GTK_IM_MODULE, even if KDE integration is used. But _not_ XIM. Maybe Libreoffice should even use that without the gnome/kde integration.
I think this problem is also apparant with Ibus, Scim and other frameworks, because the problem does not seem to lie with Fcitx.
cc'lubos for KDE advice.
Firstly I'd like to apologize myself because it's my first time working with different input methods :-)
What I guess is what the original poster detected. LibO KDE integration is not fully working with "fcitx" and "mozc" while KDE apps like "kwriter" is working fine.
Steps to reproduce on Debian 8 (jessie):
1.- Install "fcitx-mozc fcitx-ui-classic" and its dependencies.
2.- Create a file named ~/.kde/env/fcitx.sh with this content:
3.- Restart KDE session
4.- You'll see an icon on panel for Input Method selection
5.- Start "kwriter" and press Ctrl+Space and you'll get into MOZC Input Method typing asian characters and representing what the original poster says.
6.- Trying the same on LibO does not work.
7.- As a workaround you can change the ~/.kde/env/fcitx.sh file and replace the lines with:
8.- Now you can get the MOZC Input Method but as mention in SuSE (I can't confirm) this is not the best option.
To the original poster: Can you verify if the Comment #2 is what you get?
Migrating Whiteboard tags to Keywords: (needAdvice)
this issue continues to drag on
currently in Libreoffice 184.108.40.206 and fcitx 4.2.9-8.1(with mozc) openSUSE leap 42.1
Not sure if the issue is with libreoffice or KDE
suggestion in comment #2 doesn't seem to work in plasma 5 (or at least I can't work out how to get it to work).
removing libreoffice-kde4 and replacing it with libreoffice-gnome & libreoffice-gtk3 and over the top input becomes available.
Plasma 5 still seems to be using libreoffice-kde4 for KDE integration.
(In reply to farcus from comment #6)
> removing libreoffice-kde4 and replacing it with libreoffice-gnome &
> libreoffice-gtk3 and over the top input becomes available.
> Plasma 5 still seems to be using libreoffice-kde4 for KDE integration.
Yes, there is nothing newer. Hopefully this GSoC task will get done: https://wiki.documentfoundation.org/Development/GSoC/Ideas#KDE5:_port_KDE4_plugin_to_KF5
is this bug still present with LibO 220.127.116.11
if yes set status to UNCONFIRMED or NEW (if it's an independent confirmation) or RESOLVED WORKSFORME if bug is gone
This problem is still present in app-office/libreoffice-18.104.22.168-r1
USE flag: bluetooth branding cups dbus gtk gtk3 kde Python 3.4
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Dear Hans Schmidt,
KDE4 support has been dropped in LibreOffice 6.3.
Could you please try to reproduce it with LibreOffice 6.3 Beta1 from https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'NEW' if the bug is still present in the master build
I just became aware of this bug report, so I'm not entirely sure how the situation used to be when the OP first reported the bug or how it has evolved since then. But as far as I can tell almost everything works perfectly at the moment, and the only thing that doesn't (pre-edit text not being underlined) is not a LO-specific issue because I can reproduce it in other Qt or KDE apps (and is also not really relevant because it's an entirely different issue than this one).
I will set this to UNCONFIRMED, but seeing as the original bug report is very old and the last user comment is from 3 years old, and since I can be sure from personal experience that there are no real problems with fcitx input in LO, I think this could be marked as fixed.
Versions tested: current 6.2.x and 6.3.rc1
Thanks, let's set to WFM