Max Rydahl Andersen wrote: My mistake was trying to use eclipse-jee as a shortcut, when I should have used eclipse-SDK and all the other M7 build drivers. eclipse-jee doesn't even come with a dropins directory by default (!?), but mainly I think P2 was disabling everything that didn't have its dependencies available. In other words, pretty much everything in JBoss Tools. But now that I have all the dependencies, I can definitely run in Japanese with "eclipse -nl ja". There's less Japanese showing than I had hoped, but some of the Seam preferences pages (for instance) have good coverage. On the other hand, getting Eclipse itself (JDT, WTP, etc) to come up in Japanese is pretty difficult right now. I think it's because Babel's langpack generator isn't currently generating P2 metadata, due to a scalability bug in the p2 generator: https://bugs.eclipse.org/bugs/show_bug.cgi?id=274025 Using the Babel update site, at present, takes ages to display an empty list. http://download.eclipse.org/technology/babel/update-site/galileo I have modified the p2 generator, and it is working for me (Japanese eclipse + Japanese JBT), but I had to change some API, so whether it will be accepted as a patch I'm not sure. It might be a while until Babel langpacks work in Eclipse 3.5. Sigh. -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat