Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Babel » Using Babel to translate default dialogs in a e4 Application.
Using Babel to translate default dialogs in a e4 Application. [message #973388] Tue, 06 November 2012 09:40 Go to next message
Alex Kipling is currently offline Alex KiplingFriend
Messages: 257
Registered: July 2012
Senior Member
I am trying to import Babel Project bundles into my e4 application,

What i did was:

importing the babel german-package into my target platform:
<location includeAllPlatforms="false" includeConfigurePhase="false" includeMode="planner" includeSource="true" type="InstallableUnit">
<unit id="org.eclipse.babel.nls_datatools_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_eclipse_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_modeling.emf_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_modeling.emf.cdo_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_modeling.gmp.gmf-tooling_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_mylyn_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_technology.actf_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_technology.koneki_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_technology.packaging.mpc_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_technology.subversive_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_tools.cdt_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_tools.cdt.tcf_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_tools.gef_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_tools.pdt_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_tools.tm_de.feature.group" version="4.2.0.v20120721043402"/>
<unit id="org.eclipse.babel.nls_webtools_de.feature.group" version="4.2.0.v20120721043402"/>
<repository location="http://download.eclipse.org/technology/babel/update-site/R0.10.0/juno"/>


Unfortunately there are some plugins missing:
http://i.imgur.com/nX79I.png


Question:
Where can I find the missing plugins?
Is loading the language packages - all I need to use the translations from Babel project? is there some customization to do?
Re: Using Babel to translate default dialogs in a e4 Application. [message #974431 is a reply to message #973388] Wed, 07 November 2012 04:01 Go to previous messageGo to next message
Kit Lo is currently offline Kit LoFriend
Messages: 100
Registered: July 2009
Senior Member
"rt.equinox" and "rt.equinox.p2" did not provide the source locations to Babel in Juno (Eclipse 4.2/3.Cool. Therefore, Babel did not extract the Equinox files for translation in Juno. See the "Versions" pane for the Equinox project on the Babel translate page: http://babel.eclipse.org/babel/translate.php?project=rt.equinox&version=3.7&file=org.eclipse.equinox.jmx.client/org/eclipse/equinox/jmx/internal/client/ui/actions/ActionMessages.properties

On top of that, many Eclipse projects, including Equinox and Babel, migrated from CVS repository to Git repository. We are not sure about the Git repository location for Equinox 3.8 (or whether it was still available in the old CVS repository). And, Babel also has to enhance our process to support extracting files from Git repository. We will see if there is anything we can do to fix the problem in Babel R0.10.1 language packs.

Meanwhile, I noticed that the "rt.equinox" and "rt.equinox.p2" plugins were available at http://download.eclipse.org/technology/babel/update-site/R0.10.0/indigo. Babel language packs do not have the host fragment tolerance range to stop you from using Indigo language packs in Juno. If Equinox did not have too many string changes in 3.8, you probably could use the Equinox Indigo language packs in Juno. Hope that can help you work around the problem for now.
Re: Using Babel to translate default dialogs in a e4 Application. [message #974859 is a reply to message #974431] Wed, 07 November 2012 11:41 Go to previous messageGo to next message
Alex Kipling is currently offline Alex KiplingFriend
Messages: 257
Registered: July 2012
Senior Member
Thnx Kit, I could resolve the missing dependencies,
on "Add required Plugins" in Eclipse the following plugins where added: see [ ATTACHEMENT1 ]

The Problem is now, that when using tycho to build my application the following Error is thrown. see [ ATTACHEMENT2 ]
When building in Eclipse IDE - everything works fine.

Adding "org.eclipse.swt" or package "org.eclipse.swt.widgets" to my plugin's dependencies did not help.

As said here, the thrown Error is caused by the one of Babel's Plugins.

Question: do someone have expirience in compiling a e4 Application with tycho, wich Babel Plugin's loaded?




[ ATTACHEMENT1 ]:
org.eclipse.ant.core.nl_de@default:false
org.eclipse.core.commands.nl_de@default:false
org.eclipse.core.contenttype.nl_de@default:false
org.eclipse.core.databinding.beans.nl_de@default:false
org.eclipse.core.databinding.nl_de@default:false
org.eclipse.core.databinding.observable.nl_de@default:false
org.eclipse.core.databinding.property.nl_de@default:false
org.eclipse.core.expressions.nl_de@default:false
org.eclipse.core.filesystem.nl_de@default:false
org.eclipse.core.filesystem.win32.x86_64.nl_de@default:false
org.eclipse.core.jobs.nl_de@default:false
org.eclipse.core.resources.nl_de@default:false
org.eclipse.core.runtime.nl_de@default:false
org.eclipse.core.variables.nl_de@default:false
org.eclipse.e4.core.commands.nl_de@default:false
org.eclipse.e4.core.contexts.nl_de@default:false
org.eclipse.e4.core.di.extensions.nl_de@default:false
org.eclipse.e4.core.di.nl_de@default:false
org.eclipse.e4.core.services.nl_de@default:false
org.eclipse.e4.ui.bindings.nl_de@default:false
org.eclipse.e4.ui.css.core.nl_de@default:false
org.eclipse.e4.ui.css.swt.nl_de@default:false
org.eclipse.e4.ui.css.swt.theme.nl_de@default:false
org.eclipse.e4.ui.di.nl_de@default:false
org.eclipse.e4.ui.model.workbench.nl_de@default:false
org.eclipse.e4.ui.services.nl_de@default:false
org.eclipse.e4.ui.widgets.nl_de@default:false
org.eclipse.e4.ui.workbench.addons.swt.nl_de@default:false
org.eclipse.e4.ui.workbench.nl_de@default:false
org.eclipse.e4.ui.workbench.renderers.swt.nl_de@default:false
org.eclipse.e4.ui.workbench.swt.nl_de@default:false
org.eclipse.e4.ui.workbench3.nl_de@default:false
org.eclipse.equinox.app.nl_de@default:false
org.eclipse.equinox.common.nl_de@default:false
org.eclipse.equinox.ds.nl_de@default:false
org.eclipse.equinox.event.nl_de@default:false
org.eclipse.equinox.http.jetty.nl_de@default:false
org.eclipse.equinox.http.servlet.nl_de@default:false
org.eclipse.equinox.preferences.nl_de@default:false
org.eclipse.equinox.registry.nl_de@default:false
org.eclipse.equinox.util.nl_de@default:false
org.eclipse.help.base.nl_de@default:false
org.eclipse.help.nl_de@default:false
org.eclipse.jetty.http.nl_de@default:false
org.eclipse.jface.databinding.nl_de@default:false
org.eclipse.jface.nl_de@default:false
org.eclipse.osgi.nl_de@default:false
org.eclipse.osgi.services.nl_de@default:false
org.eclipse.swt.nl_de@default:false
org.eclipse.swt.win32.win32.x86_64.nl_de@default:false
org.eclipse.team.core.nl_de@default:false
org.eclipse.ui.forms.nl_de@default:false
org.eclipse.ui.intro.nl_de@default:false
org.eclipse.ui.nl_de@default:false
org.eclipse.ui.win32.nl_de@default:false
org.eclipse.ui.workbench.nl_de@default:false



[ ATTACHEMENT2 ]:
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.15.0:compile (default-compile) on project de.ivu.fare.rcp.plugin: Compilation failure: Compilation failure:
[ERROR] D:\1PROJEKTE\Neuentwicklung\de.ivu.fare.rcp\de.ivu.fare.rcp.plugin\src\main\java\de\ivu\fare\rcp\gui\preferences\PreferenceControl.java:[0,0]
[ERROR] package de.ivu.fare.rcp.gui.preferences;
[ERROR] ^
[ERROR] The type org.eclipse.swt.widgets.Button cannot be resolved. It is indirectly referenced from required .class files
[ERROR] 1 problem (1 error)
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.15.0:compile (default-compile) on project de.ivu.fare.rcp.plugin: Compilation failure
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: copied.org.apache.maven.plugin.CompilationFailureException: Compilation failure
	at copied.org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:418)
	at org.eclipse.tycho.compiler.AbstractOsgiCompilerMojo.execute(AbstractOsgiCompilerMojo.java:179)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
	... 19 more

Re: Using Babel to translate default dialogs in a e4 Application. [message #974924 is a reply to message #974859] Wed, 07 November 2012 12:49 Go to previous messageGo to next message
Kit Lo is currently offline Kit LoFriend
Messages: 100
Registered: July 2009
Senior Member
I don't have any experience with Tycho. The stack trace does not give us too much information. If you or the Tycho team can identify the problem with the Babel language packs, please open a Bugzilla report. We will try to fix that.
Re: Using Babel to translate default dialogs in a e4 Application. [message #977947 is a reply to message #974924] Fri, 09 November 2012 18:09 Go to previous message
Kit Lo is currently offline Kit LoFriend
Messages: 100
Registered: July 2009
Senior Member
Back to the original problem of missing Juno "rt.equinox" language packs, I've extracted the Equinox 3.8 files, sync'd up with existing translations.

The latest Babel update site containing the Equinox 3.8 language packs is available here:
http://build.eclipse.org/technology/babel/update-site/N20121109-0400/juno/
Previous Topic:Can I take latest mysqldump?
Next Topic:Babel Language Packs R0.10.1 are now available!
Goto Forum:
  


Current Time: Sun Nov 23 13:41:05 GMT 2014

Powered by FUDForum. Page generated in 0.06642 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software