The issue here is that all gtk+ applications have their own knowledge of dead keys (accents), so if an application is a gtk+ application, accents work just fine.
If an application is not a gtk+ application, then the app has to use the dead keys that are configured from the X server. It's normally the file
/usr/share/X11/locale/en_US.UTF-8/Compose
I did not try the specific app; if it's a gtk+ app, it should work just fine, perhaps some minor change
If it is not a gtk+ app, then you need to check the XOrg settings.
To figure out whether XOrg deadkeys work, start 'xterm' and try to type a compose sequence. If it does not work, then it's a XOrg problem. It it works on xterm, then it's a Unity app thing (so, it's easy to fix).
Last, if you have IBus activated and enabled, it may also mess up with all these.
The issue here is that all gtk+ applications have their own knowledge of dead keys (accents), so if an application is a gtk+ application, accents work just fine.
If an application is not a gtk+ application, then the app has to use the dead keys that are configured from the X server. It's normally the file X11/locale/ en_US.UTF- 8/Compose
/usr/share/
The above refer to
1. dead key Compose sequences (such as dead_acute + a = á)
2. general Compose sequences (such as Compose + o + c = ©)
I did not try the specific app; if it's a gtk+ app, it should work just fine, perhaps some minor change
If it is not a gtk+ app, then you need to check the XOrg settings.
To figure out whether XOrg deadkeys work, start 'xterm' and try to type a compose sequence. If it does not work, then it's a XOrg problem. It it works on xterm, then it's a Unity app thing (so, it's easy to fix).
Last, if you have IBus activated and enabled, it may also mess up with all these.