Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Babel » Re: how to internationalize a product-file
Re: how to internationalize a product-file [message #22315] Thu, 23 October 2008 16:35 Go to next message
Ed Merks is currently offline Ed Merks
Messages: 26141
Registered: July 2009
Senior Member
Matthias,

I'm not sure, but maybe folks on the Babel newsgroup will know the
answer if no one here does. I've added it to the "to" list of the reply.


Matthias Droste wrote:
> Hi,
> I'm just trying to internationalize an RCP-App. I'm using the approach
> to put all the properties-files into a fragment and for java-Files,
> XML-Files and the plug-in/manifest-file everything has worked fine.
>
> But how can I adapt the .product-file to multiple languages?
> Especially items like the Launcher Name and the About Dialog's text
> should be translatable.
>
> I've tried something like this:
> bla.product: <launcher name="%product.LauncherName">
> bla.properties: product.LauncherName = bla Product
>
> But Eclipse just shows the key instead of the value.
>
> Do I have to create a product for each language or is there some
> better way?
>
> Thanks,
> Matthias
Re: how to internationalize a product-file [message #22456 is a reply to message #22315] Fri, 24 October 2008 22:51 Go to previous messageGo to next message
Eclipse User
Originally posted by: atoulme.intalio.com

Matthias I think there is another way for those files.

Look up that article:
http://www.eclipse.org/articles/Article-Speak-The-Local-Lang uage/article.html

Look at the picture:

You can place your files like this:

com.matthias.nl1.fragment
nl
fr
CA
something.product

Let me know if it works.

Thanks,

Antoine

Ed Merks wrote:
> Matthias,
>
> I'm not sure, but maybe folks on the Babel newsgroup will know the
> answer if no one here does. I've added it to the "to" list of the reply.
>
>
> Matthias Droste wrote:
>> Hi,
>> I'm just trying to internationalize an RCP-App. I'm using the approach
>> to put all the properties-files into a fragment and for java-Files,
>> XML-Files and the plug-in/manifest-file everything has worked fine.
>>
>> But how can I adapt the .product-file to multiple languages?
>> Especially items like the Launcher Name and the About Dialog's text
>> should be translatable.
>>
>> I've tried something like this:
>> bla.product: <launcher name="%product.LauncherName">
>> bla.properties: product.LauncherName = bla Product
>>
>> But Eclipse just shows the key instead of the value.
>>
>> Do I have to create a product for each language or is there some
>> better way?
>>
>> Thanks,
>> Matthias
Re: how to internationalize a product-file [message #22587 is a reply to message #22456] Mon, 03 November 2008 07:57 Go to previous messageGo to next message
Eclipse User
Originally posted by: matthias-droste.gmx.net

Hi,

yes, thank, it works.
But the drawback is that this actually means that you have to copy the
product and don't (automatically) have the nice properties-file that you
can give to an external translator.
But at least the product's clean and tidy in the respective nl-folder.

Antoine Toulme schrieb:
> Matthias I think there is another way for those files.
>
> Look up that article:
> http://www.eclipse.org/articles/Article-Speak-The-Local-Lang uage/article.html
>
>
> Look at the picture:
>
> You can place your files like this:
>
> com.matthias.nl1.fragment
> nl
> fr
> CA
> something.product
>
> Let me know if it works.
>
> Thanks,
>
> Antoine
>
> Ed Merks wrote:
>> Matthias,
>>
>> I'm not sure, but maybe folks on the Babel newsgroup will know the
>> answer if no one here does. I've added it to the "to" list of the reply.
>>
>>
>> Matthias Droste wrote:
>>> Hi,
>>> I'm just trying to internationalize an RCP-App. I'm using the
>>> approach to put all the properties-files into a fragment and for
>>> java-Files, XML-Files and the plug-in/manifest-file everything has
>>> worked fine.
>>>
>>> But how can I adapt the .product-file to multiple languages?
>>> Especially items like the Launcher Name and the About Dialog's text
>>> should be translatable.
>>>
>>> I've tried something like this:
>>> bla.product: <launcher name="%product.LauncherName">
>>> bla.properties: product.LauncherName = bla Product
>>>
>>> But Eclipse just shows the key instead of the value.
>>>
>>> Do I have to create a product for each language or is there some
>>> better way?
>>>
>>> Thanks,
>>> Matthias
Re: how to internationalize a product-file [message #22631 is a reply to message #22587] Mon, 03 November 2008 20:27 Go to previous messageGo to next message
Eclipse User
Originally posted by: atoulme.intalio.com

Not sure that will be ever possible, but if you think that's important,
please file a bug to PDE and see if they like the idea.

Thanks,

Antoine

Matthias Droste wrote:
> Hi,
>
> yes, thank, it works.
> But the drawback is that this actually means that you have to copy the
> product and don't (automatically) have the nice properties-file that you
> can give to an external translator.
> But at least the product's clean and tidy in the respective nl-folder.
>
> Antoine Toulme schrieb:
>> Matthias I think there is another way for those files.
>>
>> Look up that article:
>> http://www.eclipse.org/articles/Article-Speak-The-Local-Lang uage/article.html
>>
>>
>> Look at the picture:
>>
>> You can place your files like this:
>>
>> com.matthias.nl1.fragment
>> nl
>> fr
>> CA
>> something.product
>>
>> Let me know if it works.
>>
>> Thanks,
>>
>> Antoine
>>
>> Ed Merks wrote:
>>> Matthias,
>>>
>>> I'm not sure, but maybe folks on the Babel newsgroup will know the
>>> answer if no one here does. I've added it to the "to" list of the reply.
>>>
>>>
>>> Matthias Droste wrote:
>>>> Hi,
>>>> I'm just trying to internationalize an RCP-App. I'm using the
>>>> approach to put all the properties-files into a fragment and for
>>>> java-Files, XML-Files and the plug-in/manifest-file everything has
>>>> worked fine.
>>>>
>>>> But how can I adapt the .product-file to multiple languages?
>>>> Especially items like the Launcher Name and the About Dialog's text
>>>> should be translatable.
>>>>
>>>> I've tried something like this:
>>>> bla.product: <launcher name="%product.LauncherName">
>>>> bla.properties: product.LauncherName = bla Product
>>>>
>>>> But Eclipse just shows the key instead of the value.
>>>>
>>>> Do I have to create a product for each language or is there some
>>>> better way?
>>>>
>>>> Thanks,
>>>> Matthias
Re: how to internationalize a product-file [message #22674 is a reply to message #22587] Wed, 05 November 2008 12:45 Go to previous message
Eclipse User
Originally posted by: matthias-droste.gmx.net

Just for future use a better solution to the problem:

By pressing Synchronize in the product-UI some of the product's entries
(e.g. the about-text) end up in the application's plugin.xml. These
entries can be translated using properties.

Example:
file my.product:
<aboutInfo>
<text>
%product.branding.text
</text>
</aboutInfo>

file plugin.xml:
<extension
id="product"
point="org.eclipse.core.runtime.products">
<product...>
<property
name="aboutText"
value="%product.branding.text1">
</property>

file: plugin.properties:
product.branding.text1 = some about text


Matthias Droste schrieb:
> Hi,
>
> yes, thank, it works.
> But the drawback is that this actually means that you have to copy the
> product and don't (automatically) have the nice properties-file that you
> can give to an external translator.
> But at least the product's clean and tidy in the respective nl-folder.
>
> Antoine Toulme schrieb:
>> Matthias I think there is another way for those files.
>>
>> Look up that article:
>> http://www.eclipse.org/articles/Article-Speak-The-Local-Lang uage/article.html
>>
>>
>> Look at the picture:
>>
>> You can place your files like this:
>>
>> com.matthias.nl1.fragment
>> nl
>> fr
>> CA
>> something.product
>>
>> Let me know if it works.
>>
>> Thanks,
>>
>> Antoine
>>
>> Ed Merks wrote:
>>> Matthias,
>>>
>>> I'm not sure, but maybe folks on the Babel newsgroup will know the
>>> answer if no one here does. I've added it to the "to" list of the
>>> reply.
>>>
>>>
>>> Matthias Droste wrote:
>>>> Hi,
>>>> I'm just trying to internationalize an RCP-App. I'm using the
>>>> approach to put all the properties-files into a fragment and for
>>>> java-Files, XML-Files and the plug-in/manifest-file everything has
>>>> worked fine.
>>>>
>>>> But how can I adapt the .product-file to multiple languages?
>>>> Especially items like the Launcher Name and the About Dialog's text
>>>> should be translatable.
>>>>
>>>> I've tried something like this:
>>>> bla.product: <launcher name="%product.LauncherName">
>>>> bla.properties: product.LauncherName = bla Product
>>>>
>>>> But Eclipse just shows the key instead of the value.
>>>>
>>>> Do I have to create a product for each language or is there some
>>>> better way?
>>>>
>>>> Thanks,
>>>> Matthias
Re: how to internationalize a product-file [message #575380 is a reply to message #22315] Fri, 24 October 2008 22:51 Go to previous message
Eclipse User
Originally posted by: atoulme.intalio.com

Matthias I think there is another way for those files.

Look up that article:
http://www.eclipse.org/articles/Article-Speak-The-Local-Lang uage/article.html

Look at the picture:

You can place your files like this:

com.matthias.nl1.fragment
nl
fr
CA
something.product

Let me know if it works.

Thanks,

Antoine

Ed Merks wrote:
> Matthias,
>
> I'm not sure, but maybe folks on the Babel newsgroup will know the
> answer if no one here does. I've added it to the "to" list of the reply.
>
>
> Matthias Droste wrote:
>> Hi,
>> I'm just trying to internationalize an RCP-App. I'm using the approach
>> to put all the properties-files into a fragment and for java-Files,
>> XML-Files and the plug-in/manifest-file everything has worked fine.
>>
>> But how can I adapt the .product-file to multiple languages?
>> Especially items like the Launcher Name and the About Dialog's text
>> should be translatable.
>>
>> I've tried something like this:
>> bla.product: <launcher name="%product.LauncherName">
>> bla.properties: product.LauncherName = bla Product
>>
>> But Eclipse just shows the key instead of the value.
>>
>> Do I have to create a product for each language or is there some
>> better way?
>>
>> Thanks,
>> Matthias
Re: how to internationalize a product-file [message #575461 is a reply to message #22456] Mon, 03 November 2008 07:57 Go to previous message
Matthias Droste is currently offline Matthias Droste
Messages: 2
Registered: July 2009
Junior Member
Hi,

yes, thank, it works.
But the drawback is that this actually means that you have to copy the
product and don't (automatically) have the nice properties-file that you
can give to an external translator.
But at least the product's clean and tidy in the respective nl-folder.

Antoine Toulme schrieb:
> Matthias I think there is another way for those files.
>
> Look up that article:
> http://www.eclipse.org/articles/Article-Speak-The-Local-Lang uage/article.html
>
>
> Look at the picture:
>
> You can place your files like this:
>
> com.matthias.nl1.fragment
> nl
> fr
> CA
> something.product
>
> Let me know if it works.
>
> Thanks,
>
> Antoine
>
> Ed Merks wrote:
>> Matthias,
>>
>> I'm not sure, but maybe folks on the Babel newsgroup will know the
>> answer if no one here does. I've added it to the "to" list of the reply.
>>
>>
>> Matthias Droste wrote:
>>> Hi,
>>> I'm just trying to internationalize an RCP-App. I'm using the
>>> approach to put all the properties-files into a fragment and for
>>> java-Files, XML-Files and the plug-in/manifest-file everything has
>>> worked fine.
>>>
>>> But how can I adapt the .product-file to multiple languages?
>>> Especially items like the Launcher Name and the About Dialog's text
>>> should be translatable.
>>>
>>> I've tried something like this:
>>> bla.product: <launcher name="%product.LauncherName">
>>> bla.properties: product.LauncherName = bla Product
>>>
>>> But Eclipse just shows the key instead of the value.
>>>
>>> Do I have to create a product for each language or is there some
>>> better way?
>>>
>>> Thanks,
>>> Matthias
Re: how to internationalize a product-file [message #575503 is a reply to message #22587] Mon, 03 November 2008 20:27 Go to previous message
Eclipse User
Originally posted by: atoulme.intalio.com

Not sure that will be ever possible, but if you think that's important,
please file a bug to PDE and see if they like the idea.

Thanks,

Antoine

Matthias Droste wrote:
> Hi,
>
> yes, thank, it works.
> But the drawback is that this actually means that you have to copy the
> product and don't (automatically) have the nice properties-file that you
> can give to an external translator.
> But at least the product's clean and tidy in the respective nl-folder.
>
> Antoine Toulme schrieb:
>> Matthias I think there is another way for those files.
>>
>> Look up that article:
>> http://www.eclipse.org/articles/Article-Speak-The-Local-Lang uage/article.html
>>
>>
>> Look at the picture:
>>
>> You can place your files like this:
>>
>> com.matthias.nl1.fragment
>> nl
>> fr
>> CA
>> something.product
>>
>> Let me know if it works.
>>
>> Thanks,
>>
>> Antoine
>>
>> Ed Merks wrote:
>>> Matthias,
>>>
>>> I'm not sure, but maybe folks on the Babel newsgroup will know the
>>> answer if no one here does. I've added it to the "to" list of the reply.
>>>
>>>
>>> Matthias Droste wrote:
>>>> Hi,
>>>> I'm just trying to internationalize an RCP-App. I'm using the
>>>> approach to put all the properties-files into a fragment and for
>>>> java-Files, XML-Files and the plug-in/manifest-file everything has
>>>> worked fine.
>>>>
>>>> But how can I adapt the .product-file to multiple languages?
>>>> Especially items like the Launcher Name and the About Dialog's text
>>>> should be translatable.
>>>>
>>>> I've tried something like this:
>>>> bla.product: <launcher name="%product.LauncherName">
>>>> bla.properties: product.LauncherName = bla Product
>>>>
>>>> But Eclipse just shows the key instead of the value.
>>>>
>>>> Do I have to create a product for each language or is there some
>>>> better way?
>>>>
>>>> Thanks,
>>>> Matthias
Re: how to internationalize a product-file [message #575535 is a reply to message #22587] Wed, 05 November 2008 12:45 Go to previous message
Matthias Droste is currently offline Matthias Droste
Messages: 2
Registered: July 2009
Junior Member
Just for future use a better solution to the problem:

By pressing Synchronize in the product-UI some of the product's entries
(e.g. the about-text) end up in the application's plugin.xml. These
entries can be translated using properties.

Example:
file my.product:
<aboutInfo>
<text>
%product.branding.text
</text>
</aboutInfo>

file plugin.xml:
<extension
id="product"
point="org.eclipse.core.runtime.products">
<product...>
<property
name="aboutText"
value="%product.branding.text1">
</property>

file: plugin.properties:
product.branding.text1 = some about text


Matthias Droste schrieb:
> Hi,
>
> yes, thank, it works.
> But the drawback is that this actually means that you have to copy the
> product and don't (automatically) have the nice properties-file that you
> can give to an external translator.
> But at least the product's clean and tidy in the respective nl-folder.
>
> Antoine Toulme schrieb:
>> Matthias I think there is another way for those files.
>>
>> Look up that article:
>> http://www.eclipse.org/articles/Article-Speak-The-Local-Lang uage/article.html
>>
>>
>> Look at the picture:
>>
>> You can place your files like this:
>>
>> com.matthias.nl1.fragment
>> nl
>> fr
>> CA
>> something.product
>>
>> Let me know if it works.
>>
>> Thanks,
>>
>> Antoine
>>
>> Ed Merks wrote:
>>> Matthias,
>>>
>>> I'm not sure, but maybe folks on the Babel newsgroup will know the
>>> answer if no one here does. I've added it to the "to" list of the
>>> reply.
>>>
>>>
>>> Matthias Droste wrote:
>>>> Hi,
>>>> I'm just trying to internationalize an RCP-App. I'm using the
>>>> approach to put all the properties-files into a fragment and for
>>>> java-Files, XML-Files and the plug-in/manifest-file everything has
>>>> worked fine.
>>>>
>>>> But how can I adapt the .product-file to multiple languages?
>>>> Especially items like the Launcher Name and the About Dialog's text
>>>> should be translatable.
>>>>
>>>> I've tried something like this:
>>>> bla.product: <launcher name="%product.LauncherName">
>>>> bla.properties: product.LauncherName = bla Product
>>>>
>>>> But Eclipse just shows the key instead of the value.
>>>>
>>>> Do I have to create a product for each language or is there some
>>>> better way?
>>>>
>>>> Thanks,
>>>> Matthias
Previous Topic:Illegal token characters in babel fragment names
Next Topic:recent development updates
Goto Forum:
  


Current Time: Fri Oct 24 18:08:14 GMT 2014

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

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