Bug 918747

Summary:	Jabref does not recognize dead keys
Product:	[Fedora] Fedora	Reporter:	Gustavo Maciel Dias Vieira <gustavo>
Component:	ibus	Assignee:	fujiwara <tfujiwar>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	i18n-bugs, shawn.p.huang, tfujiwar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-08 03:27:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gustavo Maciel Dias Vieira 2013-03-06 19:31:42 UTC

Description of problem:

My system uses GNOME 3.6, pt_BR.utf8 locale and Portuguese (Brasil) keyboard layout. The locale and keyboard settings were made using the gnome control center. With this setup Jabref ignores dead keys, while they worked in F16. Jabref is a Java (Swing) application, I suspect this problem affects other Java programs as well.

I'm assuming this is related to the GNOME and ibus integration.


Version-Release number of selected component (if applicable):

jabref-2.8-4.fc18.noarch
java-1.7.0-openjdk-1.7.0.9-2.3.7.0.fc18.x86_64
ibus-1.5.1-2.fc18.x86_64

How reproducible:

Deterministic

Comment 1 fujiwara 2013-03-07 07:12:40 UTC

I don't know how to open a input text with jabref.
I chose [File] -> [New database].

Comment 2 Gustavo Maciel Dias Vieira 2013-03-07 12:55:37 UTC

Sorry, after choosing [File] -> [New database], select [BibTeX] -> [New entry], pick [Article]. After that you can type.

If you want to reproduce this bug but and don't have a Brazilian keyboard lying around, try the "English (US, international with dead keys)" layout.

Comment 3 fujiwara 2013-03-08 03:27:11 UTC

I can show acute e with jabref.

*** This bug has been marked as a duplicate of bug 918740 ***