Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [babel-dev] Trying out the runtime plug-in

Title: Message
Thanks for the feedback.  Yes, of course the plug-in should interface directly with the translation server.  It was always my assumption that there would be a relatively easy way of doing that.  We will need to agree on the API to be used.  Presumably we would not be able to access the database directly as there would be no way of providing proper security, validating the bugzilla account etc. So we would need some other API such as web services.  Note also that the URL should be as stable as possible because, like update sites, the location of the appropriate translation server for each plug-in would be embedded in the plug-in.
 
I was hoping to have a version that worked with Java 5 by now.  However, quite a substantial re-working of the resource bundles took place between Java 5 and Java 6.  These changes basically made possible the design taken by the runtime plug-in when creating the updatable resource bundles.  To get the plug-in to work with Java 5 I believe we have to give up the use of a lot of Sun's code.  This is not so bad because a lot of the stuff we need was independently implemented in the NLS class, which we can re-use.  Clearly we do need this to work with versions of Java prior to Java 6.  Anyway, I will let you all know when I have this done.
 
Nigel 
-----Original Message-----
From: babel-dev-bounces@xxxxxxxxxxx [mailto:babel-dev-bounces@xxxxxxxxxxx] On Behalf Of Kit Lo
Sent: Tuesday, January 22, 2008 8:50 AM
To: Babel committers mailing list
Subject: Re: [babel-dev] Trying out the runtime plug-in


Nigel,

I tried the runtime plugin with Sun Jave 6 Update 4. I got it to come up, and was able to exercise a few functions. But, I received a few exceptions in a few areas. See the log file for more info.


This runtime tool is very useful! That's basically my vision of one of the Babel tools we should provide to Eclipse developers and users - while using Eclipse, any user may improve the translation if he sees any problem with any translation, and then contribute back to Babel.

Just one thing I want to improve on the design - currently, the new translations we made during runtime will stay in the runtime environment. We should somehow tie the new changes back to the translation server, so that the changes will be available to other users.

Kit Lo
IBM Eclipse SDK Globalization Technical Lead

Back to the top