The basic problem is that UIManager.get(someKey, someLocale) is not served
correctly, see XLocalizeIssues.testGetLocaleUIDefaults - I think it's related to
the first shot for fixing Issue 159: when copying the key/value pairs the
hierarchical lookup of localized resources is lost, only the values for the
default Locales are copied. As copying was a quick hack anyway, we probably
should give it another try to solve.
this blocks Issue 459 (localized resources in JXTable not updated in setLocale),
there's the same problem for all SwingX components which have localized resources.