25.3.9 Translation Tables
The UIL translation_table type corresponds to the XtTranslations type. A translation table maps events
to action procedures. The format of a UIL translation table looks like an asciz_table in that it contains a list of
strings, but the individual entries in the table must contain valid translations. (See Volume Four, X Toolkit Intrinsics
Programming Manual, for a description of the Xt translation table syntax.) The following fragment shows the
definition of a translation_table value:
value
actions : translation_table ('#override',
'Ctrl<Key>A: beginning−of−line()',
'Ctrl<Key>E: end−of−line()',
'Ctrl<Key>space: set−anchor()');
The first entry of a translation_table can be used to control how the table affects the existing translations of a
widget. If the first entry is not a translation, the string must be one of #augment, #override, or #replace. Each
of the remaining entries in the table must be a NULL−terminated string containing a single translation. If you specify a
translation in a UIL module, a user cannot override it from a resource file. You should consider placing translations in
an app−defaults file so that users can customize them if they wish.
25.4 Working With Callbacks
Setting up a callback with UIL and Mrm involves four steps: writing the callback in application code, registering the
callback with Mrm, declaring the callback in the UIL module, and setting the callback in a UIL widget definition. A
callback that you write for use in an Mrm application ...