Home » Eclipse Projects » Babel » Non-translatable Strings and properties files in fragment
| |
| Re: Non-translatable Strings and properties files in fragment [message #28322 is a reply to message #28284] |
Wed, 13 May 2009 17:36   |
 Eclipse Webmaster
Messages: 607343
Registered: July 2009 |
Senior Member |
|
|
Eclipse Webmaster (Denis Roy) wrote:
> Hi,
>
> Can you please file a bug against Babel Server for #1? I wasn't even
> aware that we had to support that :)
As a follow-up, I just noticed that the Guidelines document is a working
draft, so I believe none of those guidelines have been formally accepted
.... yet.
Denis
>
> As for #2, I believe Kit (our fearless leader) can answer that. Kit?
>
> Thanks!
>
>
> Kentarou Fukuda wrote:
>> Hi Babel team,
>>
>> I'm now working for PTT, and I found 2 issues below. Would you please
>> help us to solve these issues?
>>
>> 1. Non-translatable Strings
>>
>> We followed the guidelines below to exclude Non-translatable Strings.
>> http://wiki.eclipse.org/Eclipse_Globalization_Guidelines#Non -translatable_Message_Strings
>>
>>
>> However, some Strings between "# START NON-TRANSLATABLE" and "# END
>> NON-TRANSLATABLE"
>> are included in Pseudo translation.
>>
>> Is it OK? If it means that these Strings are handled as translatable
>> Strings,
>> would you please check our properties file and let me know how to fix it?
>>
>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.common/plugins/org.eclipse.actf.model.dom.htm l/src/org/eclipse/actf/model/internal/dom/html/parser/public _entities.properties?root=Technology_Project&view=co
>>
>>
>>
>> 2. Properties files in Fragment
>>
>> I found that properties files in Fragment are not included in Pseudo
>> translation.
>>
>> Is there any way to include properties files in Fragment into
>> translation target?
>> We have 3 fragment.properties files in our project.
>>
>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.blind.html/fragment.properties?root=Technology_Proje ct&view=co
>>
>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.blind.odfbyhtml/fragmentodf.properties?root=Technolo gy_Project&view=co
>>
>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.flash/fragment.properties?root=Technology_Project&am p;view=co
>>
>>
>>
>> Thank you in advance for your support.
>>
>> Best regards,
>> Kentarou
>>
>>
|
|
|
| Re: Non-translatable Strings and properties files in fragment [message #28435 is a reply to message #28322] |
Tue, 19 May 2009 05:10 |
Kentarou Fukuda
Messages: 46
Registered: July 2009 |
Member |
|
|
Hi Denis,
Thank you for your reply.
I submitted the bug for #1 (for future enhancement).
Shall I need to submit a bug for #2?
#2:
>>>Is there any way to include properties files in Fragment into
>>> translation target?
>>> We have 3 fragment.properties files in our project.
Thanks,
Kentarou
---
> Eclipse Webmaster (Denis Roy) wrote:
>> Hi,
>>
>> Can you please file a bug against Babel Server for #1? I wasn't even
>> aware that we had to support that :)
> As a follow-up, I just noticed that the Guidelines document is a working
> draft, so I believe none of those guidelines have been formally accepted
> .... yet.
> Denis
>>
>> As for #2, I believe Kit (our fearless leader) can answer that. Kit?
>>
>> Thanks!
>>
>>
>> Kentarou Fukuda wrote:
>>> Hi Babel team,
>>>
>>> I'm now working for PTT, and I found 2 issues below. Would you please
>>> help us to solve these issues?
>>>
>>> 1. Non-translatable Strings
>>>
>>> We followed the guidelines below to exclude Non-translatable Strings.
>>>
http://wiki.eclipse.org/Eclipse_Globalization_Guidelines#Non -translatable_Message_Strings
>>>
>>>
>>> However, some Strings between "# START NON-TRANSLATABLE" and "# END
>>> NON-TRANSLATABLE"
>>> are included in Pseudo translation.
>>>
>>> Is it OK? If it means that these Strings are handled as translatable
>>> Strings,
>>> would you please check our properties file and let me know how to fix it?
>>>
>>>
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.common/plugins/org.eclipse.actf.model.dom.htm l/src/org/eclipse/actf/model/internal/dom/html/parser/public _entities.properties?root=Technology_Project&view=co
>>>
>>>
>>>
>>> 2. Properties files in Fragment
>>>
>>> I found that properties files in Fragment are not included in Pseudo
>>> translation.
>>>
>>> Is there any way to include properties files in Fragment into
>>> translation target?
>>> We have 3 fragment.properties files in our project.
>>>
>>>
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.blind.html/fragment.properties?root=Technology_Proje ct&view=co
>>>
>>>
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.blind.odfbyhtml/fragmentodf.properties?root=Technolo gy_Project&view=co
>>>
>>>
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.flash/fragment.properties?root=Technology_Project&am p;view=co
>>>
>>>
>>>
>>> Thank you in advance for your support.
>>>
>>> Best regards,
>>> Kentarou
>>>
>>>
Best regards,
Kentarou
|
|
| |
| Re: Non-translatable Strings and properties files in fragment [message #28938 is a reply to message #28901] |
Wed, 20 May 2009 13:52 |
Kentarou Fukuda
Messages: 46
Registered: July 2009 |
Member |
|
|
Hi Kit,
Thank you for your reply.
I forgot that translations are provided as a fragment...
I'll move properties files into the parent plugin or somewhere in next
release.
> As far as I know, we cannot create a fragment for a fragment. Have you
> seen that done somewhere? If you can provide an example, I will
> investigate. Otherwise, the answer is that we do not support creating a
> fragment for a fragment.
Thanks,
Kentarou
Best regards,
Kentarou
|
|
| |
| Re: Non-translatable Strings and properties files in fragment [message #578754 is a reply to message #28284] |
Wed, 13 May 2009 17:36 |
Eclipse Webmaster
Messages: 607343
Registered: July 2009 |
Senior Member |
|
|
Eclipse Webmaster (Denis Roy) wrote:
> Hi,
>
> Can you please file a bug against Babel Server for #1? I wasn't even
> aware that we had to support that :)
As a follow-up, I just noticed that the Guidelines document is a working
draft, so I believe none of those guidelines have been formally accepted
.... yet.
Denis
>
> As for #2, I believe Kit (our fearless leader) can answer that. Kit?
>
> Thanks!
>
>
> Kentarou Fukuda wrote:
>> Hi Babel team,
>>
>> I'm now working for PTT, and I found 2 issues below. Would you please
>> help us to solve these issues?
>>
>> 1. Non-translatable Strings
>>
>> We followed the guidelines below to exclude Non-translatable Strings.
>> http://wiki.eclipse.org/Eclipse_Globalization_Guidelines#Non -translatable_Message_Strings
>>
>>
>> However, some Strings between "# START NON-TRANSLATABLE" and "# END
>> NON-TRANSLATABLE"
>> are included in Pseudo translation.
>>
>> Is it OK? If it means that these Strings are handled as translatable
>> Strings,
>> would you please check our properties file and let me know how to fix it?
>>
>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.common/plugins/org.eclipse.actf.model.dom.htm l/src/org/eclipse/actf/model/internal/dom/html/parser/public _entities.properties?root=Technology_Project&view=co
>>
>>
>>
>> 2. Properties files in Fragment
>>
>> I found that properties files in Fragment are not included in Pseudo
>> translation.
>>
>> Is there any way to include properties files in Fragment into
>> translation target?
>> We have 3 fragment.properties files in our project.
>>
>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.blind.html/fragment.properties?root=Technology_Proje ct&view=co
>>
>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.blind.odfbyhtml/fragmentodf.properties?root=Technolo gy_Project&view=co
>>
>> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.flash/fragment.properties?root=Technology_Project&am p;view=co
>>
>>
>>
>> Thank you in advance for your support.
>>
>> Best regards,
>> Kentarou
>>
>>
|
|
|
| Re: Non-translatable Strings and properties files in fragment [message #578802 is a reply to message #28322] |
Tue, 19 May 2009 05:10 |
Kentarou Fukuda
Messages: 46
Registered: July 2009 |
Member |
|
|
Hi Denis,
Thank you for your reply.
I submitted the bug for #1 (for future enhancement).
Shall I need to submit a bug for #2?
#2:
>>>Is there any way to include properties files in Fragment into
>>> translation target?
>>> We have 3 fragment.properties files in our project.
Thanks,
Kentarou
---
> Eclipse Webmaster (Denis Roy) wrote:
>> Hi,
>>
>> Can you please file a bug against Babel Server for #1? I wasn't even
>> aware that we had to support that :)
> As a follow-up, I just noticed that the Guidelines document is a working
> draft, so I believe none of those guidelines have been formally accepted
> .... yet.
> Denis
>>
>> As for #2, I believe Kit (our fearless leader) can answer that. Kit?
>>
>> Thanks!
>>
>>
>> Kentarou Fukuda wrote:
>>> Hi Babel team,
>>>
>>> I'm now working for PTT, and I found 2 issues below. Would you please
>>> help us to solve these issues?
>>>
>>> 1. Non-translatable Strings
>>>
>>> We followed the guidelines below to exclude Non-translatable Strings.
>>>
http://wiki.eclipse.org/Eclipse_Globalization_Guidelines#Non -translatable_Message_Strings
>>>
>>>
>>> However, some Strings between "# START NON-TRANSLATABLE" and "# END
>>> NON-TRANSLATABLE"
>>> are included in Pseudo translation.
>>>
>>> Is it OK? If it means that these Strings are handled as translatable
>>> Strings,
>>> would you please check our properties file and let me know how to fix it?
>>>
>>>
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.common/plugins/org.eclipse.actf.model.dom.htm l/src/org/eclipse/actf/model/internal/dom/html/parser/public _entities.properties?root=Technology_Project&view=co
>>>
>>>
>>>
>>> 2. Properties files in Fragment
>>>
>>> I found that properties files in Fragment are not included in Pseudo
>>> translation.
>>>
>>> Is there any way to include properties files in Fragment into
>>> translation target?
>>> We have 3 fragment.properties files in our project.
>>>
>>>
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.blind.html/fragment.properties?root=Technology_Proje ct&view=co
>>>
>>>
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.blind.odfbyhtml/fragmentodf.properties?root=Technolo gy_Project&view=co
>>>
>>>
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.actf/or g.eclipse.actf.visualization/plugins/org.eclipse.actf.visual ization.flash/fragment.properties?root=Technology_Project&am p;view=co
>>>
>>>
>>>
>>> Thank you in advance for your support.
>>>
>>> Best regards,
>>> Kentarou
>>>
>>>
Best regards,
Kentarou
|
|
| |
| Re: Non-translatable Strings and properties files in fragment [message #578843 is a reply to message #28901] |
Wed, 20 May 2009 13:52 |
Kentarou Fukuda
Messages: 46
Registered: July 2009 |
Member |
|
|
Hi Kit,
Thank you for your reply.
I forgot that translations are provided as a fragment...
I'll move properties files into the parent plugin or somewhere in next
release.
> As far as I know, we cannot create a fragment for a fragment. Have you
> seen that done somewhere? If you can provide an example, I will
> investigate. Otherwise, the answer is that we do not support creating a
> fragment for a fragment.
Thanks,
Kentarou
Best regards,
Kentarou
|
|
|
Goto Forum:
Current Time: Tue Apr 16 19:14:12 GMT 2024
Powered by FUDForum. Page generated in 5.22125 seconds |
] 
Search
Help
Register
Login
Home
