blog/content/posts/2012-06-11-hardcoded-gnomeish-composition.md

title, author, type, date, url, aktt_notify_twitter, al2fb_facebook_link_id, al2fb_facebook_link_time, al2fb_facebook_link_picture, aktt_tweeted, dsq_thread_id, categories

title	author	type	date	url	aktt_notify_twitter	al2fb_facebook_link_id	al2fb_facebook_link_time	al2fb_facebook_link_picture	aktt_tweeted	dsq_thread_id	categories
Hardcoded GNOMEish composition	james	post	2012-06-11T16:42:20+00:00	/2012/06/hardcoded-gnomeish-composition/	yes	658281334_10151014685521335	2012-06-11T16:42:24+00:00	post=https://jamesmcdonald.com/?al2fb_image=1	1	3804739886	Tech

From Ubuntu docs about the Compose key at https://help.ubuntu.com/community/ComposeKey:

The compose key sequences used by Gnome are derived from the X compose tables of XFree86 version 4.0 with further modifications to provide a Gnome standard for all locales. They are hard coded into the program in source file gtk+-2.10.7/gtk/gtkimcontextsimple.c

Digging into the current Debian gtk+ source verifies this:

`
/* This file contains the table of the compose sequences,

• static const guint16 gtk_compose_seqs_compact[] = {}
  
• IT is generated from the compose-parse.py script.
  */
  #include "gtkimcontextsimpleseqs.h"
  `

So they start with the X Input Method layer which has nice unixy text config files (check out /usr/share/X11/locale) and they want to extend it with some extra sequences. What’s the best way to do that? Clearly snarf what’s already there, bolt on your own bits and hardcode the lot into your binary.

Well done, chaps.