menu framework shortcuts -- collisions and standards

> Hi Albert,
>
> I think you make a very good suggestion. I suggest you submit a rosetta
> bug (https://launchpad.net/products/rosetta/+filebug) with a "Wishlist"
> severity.
>
> Claude

I made an effort to fix this problem programmatically for my own
application (Gourmet). My application notices conflicts as they occur
and adjusts mnemonics accordingly. Of course, this can mean breaking
consistency for the sake of conflict resolution... on the other hand,
if there are no conflicts, my program won't touch the defaults, so
everything will be alright. I also set up the system to allow
parameters for making mnemonics un-modifyable in cases where
consistency is more important than lack-of-conflict (such as _File
always being _File).

I can't imagine I'm the only person to do this -- have others made
programmatic attempts to resolve mnemonics at the application level?
Is that fundamentally the wrong place for the fix (i.e. am I insane)?

For the curious (i.e. anyone else as crazy as me), the library I wrote
is here: http://cvs.sourceforge.net/viewcvs.py/grecipe-manager/grm/src/lib/mnemonic_manager.py?rev=1.1.4.8&view=markup

Tom