Bug 32656

Summary:	fcitx can't input in libreoffice
Product:	LibreOffice	Reporter:	ZH <zhanghan2001>
Component:	Linguistic	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	LibreOffice
Priority:	medium
Version:	Inherited From OOo
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description ZH 2010-12-25 23:18:51 UTC

Fcitx is a very popular Chinese input method commonly used in china.

a week ago i downloaded LibreOffice from opensuse's repo but i find it impossible to input any character in LO. However  before switching to LO, fcitx works fine in oo.o.

a workaround available.that is set OOO_FORCE_DESKTOP to "gnome".
that is to say without KDE integration libreoffice and fcitx works fine. 

so it is possible LO's kde integration has some problem with fcitx, more precisely,which probably be a regression.

Fcitx's project page: http://code.google.com/p/fcitx/
translated version of this problem discussed in Fcitx's issue list: 
http://translate.google.com/translate?js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&sl=auto&tl=en&u=http%3A%2F%2Fcode.google.com%2Fp%2Ffcitx%2Fissues%2Fdetail%3Fid%3D355

Comment 1 Jan Holesovsky 2010-12-28 05:38:59 UTC

ZH: Which KDE version, please?

Comment 2 ZH 2010-12-28 18:18:19 UTC

Currently KDE 4.5.4 openSUSE rpm.:)

Comment 3 ZH 2011-02-24 04:54:02 UTC

Up to KDE 4.6.00 with LibreOffice 3.3.0 this problem still persists.

Comment 4 Rainer Bielefeld Retired 2011-10-13 08:59:50 UTC

That will never be fixed if we have no description how to reproduce without any Chinese knowledge.

Very old bug ...

@reporter:
Still a problem for you wiht 3.4.3? If yes, please read  hints on
<http://wiki.documentfoundation.org/BugReport> carefully!

Then please:
- Write a meaningful Summary
- Attach a sample document (not only screenshot)
- Attach screenshots with comments if you believe that that might explain the 
  problem better than a text comment. Best way is to insert your screenshots
  into a DRAW document and to add comments that explain what you want to show
- Contribute a step by step instruction containing every key press and every 
  mouse click how to reproduce your problem. Descriptions like "impossible to 
  input ..." are completely usesless, there are lots of
  ways to proceed for such actions, and every little detail might be 
  important.
  -- (and if possible how to created a sample document from the scratch)
- add information 
  -- what exactly is unexpected (as Tor said, all effects very carefully and 
     complete)
  -- and why do you believe it's unexpected (cite Help or Documentation!)
  -- concerning your PC 
  -- concerning your OS (Version, Distribution, Language)
  -- concerning your LibO version and localization (UI language)
  –- Libo settings that might be related to your problems 
  -- how you launch LibO and how you opened the sample document
  –- If you can contribute an OOo Issue that might be useful
  -- everything else crossing your mind after you read a.m. URL
May be you can test <http://wiki.documentfoundation.org/BugReport_Details> for
submitting bug reports?

Please file Bug reports with status UNCONFIRMED if your are not absolutely sure
that you contributed all required background information, that the problem will
be reproducible with information you can provide or that your enhancement
request will be accepted! Thank you!

Comment 5 ZH 2011-10-14 19:26:55 UTC

The problem is resolved due to the fix to Fcitx.
This bug can be closed now.
Thanks.

Comment 6 Björn Michaelsen 2011-12-22 05:36:51 UTC

Remove infoprovider from closed and resolved bugs.

Comment 7 Björn Michaelsen 2011-12-22 05:53:15 UTC

RESOLVED, FIXED or CLOSED bugs cant be KEYWORD NEEDINFO.