I agree about having no hard code defines/const like that. That was really only part of the demo. As, for an actual implementation, there should be an action map file format (either binary or text, but probably not XML... as I do not want to add an XML parser to this lib). As far as localisaztion.. well, Action Map really (from my current thought) doesn't really need to much localisation (that really only comes into play when entering strings - text into GUI for example)...
As, ActionMap only cares about KeyScan Codes, and not really on the basis of what exact character that is. And, if you find that in <enter country here> the key combination is awkward, or extremely unusable.. you can remap the keys to whatever you want. And/Or, the client app can load different ActionMap.CFG files based on local too.
And, while I said it is not core right now, I do plan to add it to core when it is more complete (method binding, etc). But, there will be a config flag (via ./configure on linux or OISConfig.h on windows) that disables it's inclusion.