Bug 107034 - [PATCH] Add compose sequence for U+0149
Summary: [PATCH] Add compose sequence for U+0149
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/Xlib (data) (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
Depends on:
Reported: 2018-06-25 17:09 UTC by Marko Myllynen
Modified: 2019-03-10 23:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Add compose sequence for U+0149 (1.52 KB, patch)
2018-06-25 17:09 UTC, Marko Myllynen
no flags Details | Splinter Review

Description Marko Myllynen 2018-06-25 17:09:57 UTC
Created attachment 140334 [details] [review]
Add compose sequence for U+0149

There is currently no compose sequence available for ʼn (U+0149), this
looks to be the only letter with no compose sequence from the Latin
Extended-A block.

The below Wikipedia page indicates that while deprecated it is still
in quite general use in Afrikaans. This patch is for consideration to
add a new compose sequence for the letter ʼn.

Comment 1 GitLab Migration User 2018-08-10 20:12:40 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/71.
Comment 2 Alan Coopersmith 2019-03-10 23:59:18 UTC
Attempting to apply this patch resulted in a "make check" failure, since
there's an existing Compose sequence defined for that sequence of keys:

FAIL: compose-check.pl

Clash with existing sequence in en_US.UTF-8/Compose on line 763: <Multi_key> <apostrophe> <space> <n>
  line #763: <Multi_key> <apostrophe> <space> <n>       : "ʼn"   U0149  # LATIN SMALL LETTER N PRECEDED BY APOSTROPHE
  line #52: <Multi_key> <apostrophe> <space>    : "'"   apostrophe # APOSTROPHE
FAIL compose-check.pl (exit status: 1)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.