Bug 71014 - update iso8859-{1,15} composition rules to match en_US.UTF8 ones
update iso8859-{1,15} composition rules to match en_US.UTF8 ones
Product: Red Hat Public Beta
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
Blocks: 70995
  Show dependency treegraph
Reported: 2002-08-07 16:05 EDT by Alexandre Oliva
Modified: 2007-04-18 12:45 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-07 16:09:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch that fixes the problems in XFree86-4.2.0-56. (2.71 KB, patch)
2002-08-07 16:09 EDT, Alexandre Oliva
no flags Details | Diff

  None (edit)
Description Alexandre Oliva 2002-08-07 16:05:46 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020724

Description of problem:
Currently, iso8859-15 and iso8859-1 differ in handling of <dead_diaeresis>
<space>: the former generates quotedbl, and the letter produces diaeresis. 
Since <dead_diaeresis> <dead_diaeresis> already generates diaeresis and there's
no other easy way to generate quotedbl, the choice of en_US.UTF8 and iso8859-15
of generating quotedbl for the <dead_diaeresis> <space> composition looks sane,
so I'd like it to make it to iso8859-1 too.

Also, the iso8859-1 and iso8859-15 differ from en_US.UTF8 in a few double-accent
and accent-space pairs in that there are duplicates, sometimes conflicting ones,
in the iso8859 files.

The patch I'm attaching here, that I'm submitting to XFree86 too, should fix
these problems.
Comment 1 Alexandre Oliva 2002-08-07 16:09:03 EDT
Created attachment 69344 [details]
Patch that fixes the problems in XFree86-4.2.0-56.
Comment 2 Mike A. Harris 2002-08-07 18:16:07 EDT
Patch applied to XFree86 4.2.0-60.3

Note You need to log in before you can comment on or make changes to this bug.