Bug 93660

Summary:

New composer keys for local languages in Togo

Product:

xorg

Reporter:

Mats Blakstad <mats.gbproject>

Component:

Lib/Xlib (data)

Assignee:

James Cloos <cloos>

Status:

RESOLVED MOVED

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

CC:

cloos, mats.gbproject

Version:

unspecified

Hardware:

Other

OS:

All

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
New composers local languages Togo	none
Patch to add composer symbols with diacritics used in Togo/African languages	none
Cleanup of attachment 121796	none

Description Mats Blakstad 2016-01-11 04:45:28 UTC

Created attachment 120944 [details]
New composers local languages Togo

Check attached file, it is temporary work, but I need some feedback. I want to add them inside this file:
http://cgit.freedesktop.org/xorg/lib/libX11/plain/nls/en_US.UTF-8/Compose.pre

- Are the rules fine?

- Should I create a new section for these composers? Or just add them all at the bottom? Or find similar rules and add them nearby?

- I also didn't add any # yet, several of the composer uses several unicode symbols, like:
<dead_acute> <dead_tilde> <U0190>       : "Ɛ̃́"   LATIN CAPITAL LETTER EPSILON WITH TILDE AND ACUTE
Can I add like this:
<dead_acute> <dead_tilde> <U0190>       : "Ɛ̃́"   U+0190U0303U0301 # LATIN CAPITAL LETTER EPSILON WITH TILDE AND ACUTE
?

- What is the function of <Multi_key>? Should I also use it?

Thanks in advance for your feedback!

Comment 1 James Cloos 2016-01-11 11:17:53 UTC

> What is the function of <Multi_key>? Should I also use it?

Some older keyboard had a key called Compose.  On modern keyboards it is common to map things like the menu key to compose.

Sequences starting with <Multi_key> allow those of us who have a compose key but do not have the dead keys to enter the target characters.

Presuming that all of the target strings are multi-character composed sequences I'd add them at the end of the file.

Be sure to include a comment block (use XCOMM to start each comment line) introducing them.

OTOH, if any of the targets are single characters I'd put those in code point order with their compatriots.

Comment 2 Mats Blakstad 2016-01-12 12:15:49 UTC

Thanks for feedback!

I'm not sure if I really understand the <Multi_key>, but you say I should just replicate all the new composer rules and add <Multi_key> in front of them? To me it sounds like this is something that should have been solved in another way.. I can do it if you're sure we should add it, but not very comfortable to add something that I kind of don't understand. As example: Should they still use <dead_tilde> or do those keyboard use another tilde?

Still need to clear up if I need to add the unicode behind the quotemarks (in front of hash) and how I should add symbols consisting of several unicodes.

Comment 3 Mats Blakstad 2016-02-16 23:20:05 UTC

Created attachment 121796 [details] [review]
Patch to add composer symbols with diacritics used in Togo/African languages

Here is the pacth.

I've checked over carefully, however I have problems to manage to test on my system.

Can anyone give me a short guide for how to test it on Ubuntu 14.04? Or help me test?

Comment 4 James Cloos 2016-02-28 18:30:22 UTC

Created attachment 122017 [details] [review]
Cleanup of attachment 121796 [details] [review]

Added hashes before the comments.
Removed trailing whitespace.

<Multi_key> sequences can come in a followup patch.

I'll get this pushed out as soon as I can test it.

Comment 5 Mats Blakstad 2016-03-07 03:42:25 UTC

Thanks

I can also help test if I just get some hints about how to set up locally on ubuntu.

Comment 6 GitLab Migration User 2018-08-10 20:12:26 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/64.

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.