Bug 59529 - us_intl xkb symbols file with syntax problems
Summary: us_intl xkb symbols file with syntax problems
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: XFree86   
(Show other bugs)
Version: 1.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-09 17:57 UTC by Flavio Ribeiro
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-02-09 17:57:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Flavio Ribeiro 2002-02-09 17:57:36 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204

Description of problem:
/usr/X11R6/lib/X11/xkb/symbols/us_intl lacks some commas after certain ']'
characters, making it unreadable. Just add the commas and you'll fix it.

this file holds dead key support for people who want to write latin characters
with standard 101 key US keyboards.

Note that this particular problem may be present in other symbol files (I
haven't checked). I haven't checked any other architectures either, but they
should also have the bug.

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

How reproducible:
Always

Steps to Reproduce:
use Option "XkbLayout"  "us_intl" in your XF86Config file or run
setxkbmap -symbols "us(pc101)+us_intl"

Actual Results:  dead key support doesn't exist, because us_intl is ignored

Additional info: I've submitted this bug to XFree86.org, so we should expect it
to be fixed on their next minor release.
Comment 1 Mike A. Harris 2002-02-09 19:46:10 UTC 
Commas added to XFree86-4.2.0-6.31 in rawhide.

Thanks very much for the report and info.
Note You need to log in before you can comment on or make changes to this bug.