Created attachment 118157 [details] New definitions of IPA symbols / African Reference Alphabet I work to make a new keyboard for Togo. It is based on French keyboard, but it should also include symbols for local languages used in Togo. This patch contains the symbols that we're missing inside keysymdef.h and they are needed to be able to create compose keys ("multi keys") to combine symbols and tones. Some questions: - Should we only add the IPA symbols actually needed for the composer or is it better to add all IPA symbols missing inside keysymdef.h ? - Should I create separate issues for the composer and the new keyboard or add them to this issue? This is my first patch, please explain me if I've misunderstood anything. Thanks in advance.
> - Should I create separate issues for the composer and the new keyboard or add > them to this issue? Both for the composer and the keyboard layout (XKB), you can use keysyms like "U0190", you do not need to introduce keysyms such as "Open_E". While using the former hexadecimal form is less memorable, it avoids coordination concerns. Therefore, in my opinion, it is best to forget about the patch and directly move on to XKB, and then to the compose sequences. But it is really just a personal opinion.
Created attachment 118749 [details] [review] French azerty symbols - version 2 I've corrected the dead grave in new patch and added: include "level3(ralt_switch)" The benefit is to be able to use a strict subset of the "basic" French layout, and also to easily include it in new keyboard layouts (that I was recommended to do on xkb email list.
Sorry, commenting on wrong issue
Thanks for checking the patch and giving feedback. Okay, I agree, better to just use the hexadecimal forms directly inside XKB.
I opened a new issue to add several unicode keysyms needed for local languages in Togo here: https://bugs.freedesktop.org/show_bug.cgi?id=93660
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.