On 2004-11-04 12:29:21 -0500, Branden Robinson wrote: > Is this not a bug, then, but rather a misunderstanding of how > translation table resources work?
Well, this is a bug in the documentation, which doesn't provide enough information. It wasn't even clear that XtAugmentTranslations or XtOverrideTranslations was used. The behavior is explained by the XtParseTranslationTable(3Xt) man page: [...] The XtAugmentTranslations function nondestructively merges the new translations into the existing widget translations. If the new trans- lations contain an event or event sequence that already exists in the widget's translations, the new translation is ignored. The XtOverrideTranslations function destructively merges the new trans- lations into the existing widget translations. If the new translations contain an event or event sequence that already exists in the widget's translations, the new translation is merged in and override the wid- get's translation. [...] IMHO, there should be a man page for Xresources / app-defaults. "apropos" says: nothing appropriate. Shouldn't this documentation (at least for the translations) be provided by the libxt6 package? In this case, the bug should be reassigned to it. Note that the XtParseTranslationTable(3Xt) man page is provided by libxt-dev, though the end user who wants to modify X resources doesn't necessarily have this dev package. I haven't seen a libxt-doc package either. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / SPACES project at LORIA
