Nicolas Richeton

Localization in RCP plugins is usually done by including translations in a property file and using their id in plugin.xml.

I spend some time lately trying to understand why some translations were not used in my application although they were correctly displayed in PDE.

Answer : when using plugin.properties, you MUST include the following line in the plugin manifest :

Bundle-Localization: plugin

Otherwise, PDE will show the translated text, but your app won’t.

Strangely, I had to edit the manifest manually because I couldn’t find a way to enable plugin localization in PDE. Some other plugins of my application already had this line, but I don’t remember adding it. Maybe Eclipse templates have changed since I created my first plugins (using Eclipse 3.1).

See this post on the rcp newsgroup

Yet another bug on which I spent several days. Bundle-NativeCode directive works on windows but not on MacOS. I tried almost all possible workarounds, the only thing that worked was to add the java.library.path property to the VM, but things should not be done this way with OSGI.

I ended up with a new bug report : https://bugs.eclipse.org/bugs/show_bug.cgi?id=186373

Wait and See.

UPDATE: A fix was released for Eclipse 3.3RC1. The workaround is to use “Mac OS X” as the osname. The right Bundle-NaticeCode directive on MAC is :

Bundle-NativeCode: libjinput-osx.jnilib;liblwjgl.jnilib;openal.dylib;osname=”mac os x”;processor=x86;libjinput-osx.jnilib;liblwjgl.jnilib;openal.dylib;osname=”mac os x”;processor=ppc

Now Sharemedia 0.1.34 can be released