Eclipse Community Forums: Eclipse Platform » API for programmtically creating Plugins+features

Home » Eclipse Projects » Eclipse Platform » API for programmtically creating Plugins+features

API for programmtically creating Plugins+features [message #481695]

Sun, 23 August 2009 13:34

Eclipse User

Hello group,

for making translations easier especially allowing translations in a
more community like approach .
I came up with the idea for my project to put all Translations into one
big xml file
and automatically generate the properties files from that XML file ...
(specially to create fragments + features so one could put them in the
dropins folder and test immediately)
like that it should be more easily manageable to do translations for
that project without an IDE and the sourcecode of the project ...
Another benefit would be the better unicode support in XML files...
doing unicode escaped with cp12x properties files seems to be not that
nice..

First is this a totally flawed idea in a way I have not jet seen?
Are there already any projects doing sth likewise or have a solution to
the same problem (allowing translation and testing without IDE +
optionally not dozens of properties files to manage)?

Is there some API for simpler creation of fragments/features
programmtically than just packing them up creating manifest and
fragment.xml by hand (or rather writing them without any api) ?

Christian

Re: API for programmtically creating Plugins+features [message #481711 is a reply to message #481695]

Sun, 23 August 2009 19:13

Eclipse User

Christian wrote:
> Hello group,
>
> for making translations easier especially allowing translations in a
> more community like approach .
> I came up with the idea for my project to put all Translations into one
> big xml file
> and automatically generate the properties files from that XML file ...
> (specially to create fragments + features so one could put them in the
> dropins folder and test immediately)
> like that it should be more easily manageable to do translations for
> that project without an IDE and the sourcecode of the project ...
> Another benefit would be the better unicode support in XML files...
> doing unicode escaped with cp12x properties files seems to be not that
> nice..
>
> First is this a totally flawed idea in a way I have not jet seen?
> Are there already any projects doing sth likewise or have a solution to
> the same problem (allowing translation and testing without IDE +
> optionally not dozens of properties files to manage)?
>
> Is there some API for simpler creation of fragments/features
> programmtically than just packing them up creating manifest and
> fragment.xml by hand (or rather writing them without any api) ?

At Eclipse, we have the Babel project to do translations via a community
approach, have you seen it?
http://babel.eclipse.org/babel/

Eclipse PDE has an "Internationalize" action which you may find useful.
This essentially generates the necessary fragments for you. Here's a
blog post that goes over it quickly:

http://eclipsesource.com/blogs/2008/12/11/tip-generate-nls-f ragments-in-eclipse/

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Re: API for programmtically creating Plugins+features [message #481713 is a reply to message #481711]

Sun, 23 August 2009 20:39

Eclipse User

Chris Aniszczyk schrieb:
>
> At Eclipse, we have the Babel project to do translations via a community
> approach, have you seen it?
> http://babel.eclipse.org/babel/

I have seem the babel Project though I am coding on a rcp application
so I doubt adding such a non-eclipse project there is possible.

>
> Eclipse PDE has an "Internationalize" action which you may find useful.
> This essentially generates the necessary fragments for you. Here's a
> blog post that goes over it quickly:
>
> http://eclipsesource.com/blogs/2008/12/11/tip-generate-nls-f ragments-in-eclipse/
>
Thank you. That looks like a good starting point.

regards
Christian

Previous Topic:	Suppress general views in dialog "Window->Show View"?
Next Topic:	Preventing ErrorEditorInput from Showing

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 06:49:54 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter