Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.4) Gecko/20091028 Ubuntu/9.10 (karmic) Firefox/3.5.4 Build Identifier: 3.5.0.v20090620043401 It would help with exporting and building RCP applications if the Babel software site would provide _separate_ Babel features for these platform features: - org.eclipse.rcp - org.eclipse.help - org.eclipse.equinox.p2.user.ui If you use org.eclipse.babel.nls_eclipse as provided today: - you clutter your target platform with lots of unnecessary fragments - you can't refer that feature when exporting because then you have fragments that are missing their host -> gives an error when exporting So you have to create nl features yourself grouping the translation fragments. Which is a tedious task which maybe could be automated with the existing Babel package tooling? Reproducible: Always
Created attachment 151639 [details] Features for Eclipse RCP, Help based on BabelLanguagePack-eclipse-de_3.5.0.v20090620043401.zip Built them manually for now using feature projects + PDE feature export.
Hi Ralf, thanks for the contribution! The attached language pack will be useful to German RCP users. I'm trying to think of a solution for all languages. The "org.eclipse.rcp" feature belongs to the Eclipse RCP sub-project, and the "org.eclipse.help" and "org.eclipse.equinox.p2.user.ui" features belong to the Eclipse Platform sub-project. What if we provide language packs for the Eclipse RCP and Eclipse Platform sub-projects. Will that help?
As host bundles and available bundles have to match, it is important to have separate language features for every original feature, like org.eclipse.rcp.nl_de for org.eclipse.rcp org.eclipse.help.nl_de for org.eclipse.help We currently have a "Platform Runtime" and "Platform SDK" which contain rcp, help, user.ui + other features. I think providing a "Platform Language Pack" containing a nl feature for every platform feature would be a good solution. Especially if it's provided in a p2 site that also can be downloaded as zip.
Is there anything I can do to help with resolving this bug? Are the instructions for building the Babel sets somewhere so I can try it out and try to add a RCP feature? Are Babel features already generated according to the contents of Eclipse release features?
Hi Ralf, we discussed this problem in a Babel status meeting. We think that this is an isolated request and is not very common. Modifying the build process to generate the RCP language packs for all languages will add significant amount of time to the build process. Many duplicating plugins will be generated and take up necessary storage. The requested feature can be created manually easily. We are resolving this as WONTFIX. You probably can create the lanugage pack you want by downloading the German Eclipse language pack (http://www.eclipse.org/downloads/download.php?file=/technology/babel/babel_language_packs/BabelLanguagePack-eclipse-de_3.5.0.v20091121043401.zip) and remove the unwanted plugins from the feature.xml.
Kit, would it be an option to generate a NL feature for the Eclipse RCP SDK only? There are already, like, 30 different kinds of language packs on http://download.eclipse.org/technology/babel/babel_language_packs/galileo.php , (some clearly less important than the RCP feature). Can you please give me some arguments why building RCP applications in German or French is "uncommon"? I'm very sure that it is not. I know I can do it manually, that's how I created the attachment. But is not easy, it takes around one hour and is a very tedious talk.
Also, the resulting feature is 113kB big if you build it manually, which is 3,8 Mb for all 34 languages per release. Is such an amount really relevant regarding storage space?
As an alternative, saving build time and storage, maybe BabelLanguagePack-eclipse could be provided as p2 site containing one nl feature per original feature so one can pick the translation features one actually needs?
Ralf, we are not saying that building RCP applications is uncommon. But, so far, for each Eclipse project (for example, BIRT, Datatools, GEF, etc), we just provide one language pack that contains all translations. It's satisfying most users. With just about an hour's work one time when you need to pull the language packs, it will save a lot of the build time for all 34 languages, and avoid the unnecessary extra storage for the duplicating plugins. It's true that the size of this RCP language pack you are looking for is not very big. But, if there is another request for... just the BIRT Runtime language pack..., or just the GEF doc plugin language packs, with the very limited resource we currently have for our small team, we cannot satisfy the requests at the moment. This is a very good opportunity for the community to help! If someone can come up with some tools to help pick and choose the features in the language packs that you want, it will be very helpful to the community!
Kit, as I understand it, the issue here is the general feasibility of more fine-granular babel features / downloads, not the utility of a separate RCP download? Would providing the eclipse language pack as p2 software site containing a separate nl features per orginal feature be a sound technical solution for this issue in your opinion?
The Eclipse update site mechanism allows 2 levels of categories. Babel uses the first level category for languages and second level category for different projects. We will investigate more to see if there is any way to provide more fine-granular Babel features. We may have to open an enhancement bug against Eclipse update site mechanism to ask for supports for more levels of categories first before we can do anything.
btw, I created a p2 site containing the German Eclipse RCP translations at the following URL: http://github.com/ralfebert/rcp_babel.git/site/ Any new ideas regarding to this problem? What came to my mind, is that for p2, adding separate "Eclipse RCP" features to the build would not require extra storage as all the fragments are already in the p2 site - this would only add additional features that provide a different grouping.
Sorry, github changed the http urls, this broke the org.eclipse.rcp.nl_de site. Repository for the German RCP fragments is available here: http://www.ralfebert.de/projects/releases/ Source project for building yourself is here: http://github.com/ralfebert/rcp_babel
I have the same problem. I need to assemble language pack which contains six languages for rcp platform, emf and gef. I also need to update it in the future. So some kind of tooling or p2-based solution can be very helpful.
I have the same problem. Is it maybe possible to use Ralf's solution as a p2 repository as a base and update it to Babel 0.8.0 for Eclipse 3.6 Helios? If not is there any instruction available about how to achieve a translation of the rcp bundles (select only required Babel bundles) and how to keep this up to date? Maybe Ralf has written something about it in his blog, but in this case I did cope with finding it.
