[Fedora-i18n-bugs] [Bug 734076] New: gcin cannot be started via Ctrl+Space within Firefox and libreoffice
bugzilla at redhat.com
bugzilla at redhat.com
Mon Aug 29 11:51:20 UTC 2011
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: gcin cannot be started via Ctrl+Space within Firefox and libreoffice
https://bugzilla.redhat.com/show_bug.cgi?id=734076
Summary: gcin cannot be started via Ctrl+Space within Firefox
and libreoffice
Product: Fedora
Version: 16
Platform: All
OS/Version: Linux
Status: NEW
Severity: high
Priority: unspecified
Component: gcin
AssignedTo: candyz0416 at gmail.com
ReportedBy: pswo10680 at gmail.com
QAContact: extras-qa at fedoraproject.org
CC: candyz0416 at gmail.com,
i18n-bugs at lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: ---
Description of problem:
gcin is used by many Chinese (Traditional) users, because ibus-chewing has many
critical bugs not fixed yet.
gcin uses Ctrl+Space to start to input Chinese characters. I installed gcin,
gcin-gtk2, gcin-gtk3 and gcin-qt4.
gcin works well within gtk3 programs such as gedit, and it works well with qt4
programs like Amarok too.
Version-Release number of selected component (if applicable): 1.6.1
How reproducible:
Steps to Reproduce:
1. install gicn gcin-gtk2 gcin-gtk3 gcin-qt4 libreoffice amarok gimp first
2. siwtich im into gcin via im-chooser
3. log in again
4. use Ctrl+Space within gedit, firefox, libreoffice (e.g. Writer) and gimp
Actual results:
Only gedit, a gtk3 program, and amarok, a qt4 program can use Ctrl+Space to
input Chinese characters.
Expected results:
firefox, libreoffice and gimp can use Ctrl+Space to input Chinese characters.
Additional info: the test build of gcin-1.6.1.pre13-1 works well with all the
programs described above (
http://koji.fedoraproject.org/koji/taskinfo?taskID=3023647), I have kept the
rpm.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the i18n-bugs
mailing list