Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EPF » Again to translation topic
Again to translation topic [message #11406] Mon, 29 May 2006 13:36 Go to next message
jan masaryk is currently offline jan masaryk
Messages: 50
Registered: July 2009
Member
Hi all,

I'm reading conversation concerning translation of OpenUP and I would to
expand question to this topic ...

Some ways we can translate "core" content which I mean concrete method
content (for example OpenUP). However when I translate whole OpenUP inside
EPF tool and publish it, this export still contains english parts.
Just look at published content, visit one of task-type page and look at
words
- Task : ..
- Discipline
- Relationships
- and so on.

My questions:
1. How can we translate these non-core parts of published content?
2. How can we translate EPF composer enviroment to another language?

Thanks in advance.

All the best and keep good work,
Jan
Re: Again to translation topic [message #18981 is a reply to message #11406] Fri, 22 September 2006 12:58 Go to previous messageGo to next message
jan masaryk is currently offline jan masaryk
Messages: 50
Registered: July 2009
Member
can I ask for some answer?

thanks in advance,
jan

On Mon, 29 May 2006 15:36:31 +0200, jan masaryk <jan.masaryk@asseco.sk>
wrote:

> Hi all,
>
> I'm reading conversation concerning translation of OpenUP and I would to
> expand question to this topic ...
>
> Some ways we can translate "core" content which I mean concrete method
> content (for example OpenUP). However when I translate whole OpenUP
> inside EPF tool and publish it, this export still contains english
> parts. Just look at published content, visit one of task-type page and
> look at words
> - Task : ..
> - Discipline
> - Relationships
> - and so on.
>
> My questions:
> 1. How can we translate these non-core parts of published content?
> 2. How can we translate EPF composer enviroment to another language?
>
> Thanks in advance.
>
> All the best and keep good work,
> Jan
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: Again to translation topic [message #19024 is a reply to message #18981] Fri, 22 September 2006 16:02 Go to previous messageGo to next message
Eclipse User
Originally posted by: storaskar.xx.xxx.xxx

Initial release of EPF will not have NL support. We plan to add NL support
after EPF 1.0 release. The languages we will support will be published
afterwards as we get closer to that date.

Being said that, if you want to take up on translating non-core parts of
published content and EPF composer environment yourself, you would have to
get source code from CVS and translate all resources strings used in EPF
eg. all properties files and provide corresponding "nl" plugins for
particular language you are interested in. After that, running "epf" with
command-line options such as "-nl de" (eg. for German language) will have
environment translated.

Thanks
Re: Again to translation topic [message #19303 is a reply to message #19024] Mon, 25 September 2006 15:10 Go to previous messageGo to next message
jan masaryk is currently offline jan masaryk
Messages: 50
Registered: July 2009
Member
many thanks for your answer.
jan


On Fri, 22 Sep 2006 18:02:22 +0200, Shilpa Toraskar <storaskar@xx.xxx.xxx>
wrote:

> Initial release of EPF will not have NL support. We plan to add NL
> support after EPF 1.0 release. The languages we will support will be
> published afterwards as we get closer to that date.
>
> Being said that, if you want to take up on translating non-core parts of
> published content and EPF composer environment yourself, you would have
> to get source code from CVS and translate all resources strings used in
> EPF eg. all properties files and provide corresponding "nl" plugins for
> particular language you are interested in. After that, running "epf"
> with command-line options such as "-nl de" (eg. for German language)
> will have environment translated.
>
> Thanks
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: Again to translation topic [message #19711 is a reply to message #19024] Sun, 01 October 2006 18:36 Go to previous messageGo to next message
Eclipse User
Originally posted by: christopher.fuhrman.etsmtl.ca

Shilpa Toraskar wrote:
> Initial release of EPF will not have NL support. We plan to add NL
> support after EPF 1.0 release. The languages we will support will be
> published afterwards as we get closer to that date.
>
> Being said that, if you want to take up on translating non-core parts of
> published content and EPF composer environment yourself, you would have
> to get source code from CVS and translate all resources strings used in
> EPF eg. all properties files and provide corresponding "nl" plugins for
> particular language you are interested in. After that, running "epf"
> with command-line options such as "-nl de" (eg. for German language)
> will have environment translated.

Can you clarify? Does the EFP source code already use strings from
properties files (rather than hard-coded strings), or does translation
require source-code changes to support properties files (as well as the
translated strings)?

--
Prof. Christopher Fuhrman
Department of Software and IT Engineering
University of Quebec - École de technologie supérieure (ETS)
http://profs.logti.etsmtl.ca/cfuhrman/index.shtml?en
+1 (514) 396 8638
Re: Again to translation topic [message #19793 is a reply to message #19711] Mon, 02 October 2006 16:01 Go to previous messageGo to next message
Eclipse User
Originally posted by: storaskar.xx.xxx.xxx

EPF source already using properties files for the strings.

Shilpa
Re: Again to translation topic [message #21054 is a reply to message #19024] Fri, 06 October 2006 13:29 Go to previous messageGo to next message
jan masaryk is currently offline jan masaryk
Messages: 50
Registered: July 2009
Member
Shilpa Toraskar wrote:

> Initial release of EPF will not have NL support. We plan to add NL support
> after EPF 1.0 release. The languages we will support will be published
> afterwards as we get closer to that date.

> Being said that, if you want to take up on translating non-core parts of
> published content and EPF composer environment yourself, you would have to
> get source code from CVS and translate all resources strings used in EPF
> eg. all properties files and provide corresponding "nl" plugins for
> particular language you are interested in. After that, running "epf" with
> command-line options such as "-nl de" (eg. for German language) will have
> environment translated.

> Thanks

however, one more question ....
What does it mean "non-core parts of published content"?
Which parts do you mean?

many thanks,
jan
Re: Again to translation topic [message #21082 is a reply to message #21054] Mon, 09 October 2006 16:16 Go to previous messageGo to next message
Eclipse User
Originally posted by: storaskar.xx.xxx.xxx

It means words like "Task, Role, Discipline etc" in published content.
There are not exactly part of content pages.
Re: Again to translation topic [message #26299 is a reply to message #11406] Wed, 10 January 2007 11:00 Go to previous messageGo to next message
Mauro is currently offline Mauro
Messages: 79
Registered: July 2009
Member
Since EPF 1.0 is done ...there are some news about translation support?

"jan masaryk" <jan.masaryk@asseco.sk> escreveu na mensagem
news:1704006aa6f93386bfaf3d037c62de7f$1@www.eclipse.org...
> Hi all,
>
> I'm reading conversation concerning translation of OpenUP and I would to
> expand question to this topic ...
>
> Some ways we can translate "core" content which I mean concrete method
> content (for example OpenUP). However when I translate whole OpenUP inside
> EPF tool and publish it, this export still contains english parts. Just
> look at published content, visit one of task-type page and look at words
> - Task : ..
> - Discipline
> - Relationships
> - and so on.
>
> My questions:
> 1. How can we translate these non-core parts of published content?
> 2. How can we translate EPF composer enviroment to another language?
>
> Thanks in advance.
>
> All the best and keep good work,
> Jan
>
Re: Again to translation topic [message #26339 is a reply to message #26299] Wed, 10 January 2007 16:43 Go to previous messageGo to next message
Eclipse User
Originally posted by: storaskar.xx.xxx.xxx

EPF 1.0.1 has native language support for 9 languages for the EPF tool.
For EPF content, we would appreciate any volunteers. Check out more
information if you are interested in EPF tool translation support.

http://www.eclipse.org/epf/downloads/tool/epf1.0.1_downloads .php
Re: Again to translation topic [message #26377 is a reply to message #26339] Wed, 10 January 2007 17:19 Go to previous messageGo to next message
Mauro is currently offline Mauro
Messages: 79
Registered: July 2009
Member
Yep...I?ve downloaded the NLpack_epf-composer-1.0.1.zip and I?m now using
the localized version to pt_BR ...thanks...
But I did not see where to find "EPF tool translation support" ?
I?me interested in pt-BR localization for OpenUP content...as a Volunteers

"Shilpa Toraskar" <storaskar@xx.xxx.xxx> escreveu na mensagem
news:c6a257cb11dbe93a5a46f0b179f7a41a$1@www.eclipse.org...
>
> EPF 1.0.1 has native language support for 9 languages for the EPF tool.
> For EPF content, we would appreciate any volunteers. Check out more
> information if you are interested in EPF tool translation support.
>
> http://www.eclipse.org/epf/downloads/tool/epf1.0.1_downloads .php
>
Re: Again to translation topic [message #26414 is a reply to message #26377] Thu, 11 January 2007 00:00 Go to previous messageGo to next message
Ricardo Balduino is currently offline Ricardo Balduino
Messages: 191
Registered: July 2009
Senior Member
Mauro,

Today you have EPF Composer available in various languages, including
Brazilian Portuguese.

Some people have expressed their interest in translating OpenUP to
Portuguese. The general consensus is that we should wait until version 1.0
of OpenUP is released, so the content is stable in order to undergo a
translation effort. This effort would occur in a volunteer basis.

For more information on current OpenUP plan, see
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/des ign/content_dev_plans/?root=Technology_Project

Regards / Sauda
Re: Again to translation topic [message #26449 is a reply to message #26414] Thu, 11 January 2007 10:51 Go to previous messageGo to next message
Mauro is currently offline Mauro
Messages: 79
Registered: July 2009
Member
Thanks Balduino
"Ricardo Balduino" <balduino@us.ibm.com> escreveu na mensagem
news:eo3un6$os8$1@utils.eclipse.org...
> Mauro,
>
> Today you have EPF Composer available in various languages, including
> Brazilian Portuguese.
>
> Some people have expressed their interest in translating OpenUP to
> Portuguese. The general consensus is that we should wait until version 1.0
> of OpenUP is released, so the content is stable in order to undergo a
> translation effort. This effort would occur in a volunteer basis.
>
> For more information on current OpenUP plan, see
> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/des ign/content_dev_plans/?root=Technology_Project
>
> Regards / Sauda
Re: Again to translation topic [message #26779 is a reply to message #26339] Thu, 18 January 2007 08:17 Go to previous message
jan masaryk is currently offline jan masaryk
Messages: 50
Registered: July 2009
Member
I have a look at 'NLS Pack for EPF 1.0.1 and 1.0.1.x' for EPFC and
I really appreciate that localization has been separated. That's really
helpful ...

Hovewer can someone explain a little bit more how to create localization
of EPFC to any language?
I seriously thinking of localization EPFC to slovak ....

all the best,
jan

ps: thank's for great tool, it's definitelly in use. :-)


On Wed, 10 Jan 2007 17:43:22 +0100, Shilpa Toraskar <storaskar@xx.xxx.xxx>
wrote:

>
> EPF 1.0.1 has native language support for 9 languages for the EPF tool.
> For EPF content, we would appreciate any volunteers. Check out more
> information if you are interested in EPF tool translation support.
>
> http://www.eclipse.org/epf/downloads/tool/epf1.0.1_downloads .php
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: Again to translation topic [message #565754 is a reply to message #11406] Fri, 22 September 2006 12:58 Go to previous message
jan masaryk is currently offline jan masaryk
Messages: 50
Registered: July 2009
Member
can I ask for some answer?

thanks in advance,
jan

On Mon, 29 May 2006 15:36:31 +0200, jan masaryk <jan.masaryk@asseco.sk>
wrote:

> Hi all,
>
> I'm reading conversation concerning translation of OpenUP and I would to
> expand question to this topic ...
>
> Some ways we can translate "core" content which I mean concrete method
> content (for example OpenUP). However when I translate whole OpenUP
> inside EPF tool and publish it, this export still contains english
> parts. Just look at published content, visit one of task-type page and
> look at words
> - Task : ..
> - Discipline
> - Relationships
> - and so on.
>
> My questions:
> 1. How can we translate these non-core parts of published content?
> 2. How can we translate EPF composer enviroment to another language?
>
> Thanks in advance.
>
> All the best and keep good work,
> Jan
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: Again to translation topic [message #565816 is a reply to message #18981] Fri, 22 September 2006 16:02 Go to previous message
Shilpa Toraskar is currently offline Shilpa Toraskar
Messages: 102
Registered: July 2009
Senior Member
Initial release of EPF will not have NL support. We plan to add NL support
after EPF 1.0 release. The languages we will support will be published
afterwards as we get closer to that date.

Being said that, if you want to take up on translating non-core parts of
published content and EPF composer environment yourself, you would have to
get source code from CVS and translate all resources strings used in EPF
eg. all properties files and provide corresponding "nl" plugins for
particular language you are interested in. After that, running "epf" with
command-line options such as "-nl de" (eg. for German language) will have
environment translated.

Thanks
Re: Again to translation topic [message #565870 is a reply to message #19024] Mon, 25 September 2006 15:10 Go to previous message
jan masaryk is currently offline jan masaryk
Messages: 50
Registered: July 2009
Member
many thanks for your answer.
jan


On Fri, 22 Sep 2006 18:02:22 +0200, Shilpa Toraskar <storaskar@xx.xxx.xxx>
wrote:

> Initial release of EPF will not have NL support. We plan to add NL
> support after EPF 1.0 release. The languages we will support will be
> published afterwards as we get closer to that date.
>
> Being said that, if you want to take up on translating non-core parts of
> published content and EPF composer environment yourself, you would have
> to get source code from CVS and translate all resources strings used in
> EPF eg. all properties files and provide corresponding "nl" plugins for
> particular language you are interested in. After that, running "epf"
> with command-line options such as "-nl de" (eg. for German language)
> will have environment translated.
>
> Thanks
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: Again to translation topic [message #566215 is a reply to message #19024] Sun, 01 October 2006 18:36 Go to previous message
Eclipse User
Originally posted by: christopher.fuhrman.etsmtl.ca

Shilpa Toraskar wrote:
> Initial release of EPF will not have NL support. We plan to add NL
> support after EPF 1.0 release. The languages we will support will be
> published afterwards as we get closer to that date.
>
> Being said that, if you want to take up on translating non-core parts of
> published content and EPF composer environment yourself, you would have
> to get source code from CVS and translate all resources strings used in
> EPF eg. all properties files and provide corresponding "nl" plugins for
> particular language you are interested in. After that, running "epf"
> with command-line options such as "-nl de" (eg. for German language)
> will have environment translated.

Can you clarify? Does the EFP source code already use strings from
properties files (rather than hard-coded strings), or does translation
require source-code changes to support properties files (as well as the
translated strings)?

--
Prof. Christopher Fuhrman
Department of Software and IT Engineering
University of Quebec - École de technologie supérieure (ETS)
http://profs.logti.etsmtl.ca/cfuhrman/index.shtml?en
+1 (514) 396 8638
Re: Again to translation topic [message #566276 is a reply to message #19711] Mon, 02 October 2006 16:01 Go to previous message
Shilpa Toraskar is currently offline Shilpa Toraskar
Messages: 102
Registered: July 2009
Senior Member
EPF source already using properties files for the strings.

Shilpa
Re: Again to translation topic [message #566609 is a reply to message #19024] Fri, 06 October 2006 13:29 Go to previous message
jan masaryk is currently offline jan masaryk
Messages: 50
Registered: July 2009
Member
Shilpa Toraskar wrote:

> Initial release of EPF will not have NL support. We plan to add NL support
> after EPF 1.0 release. The languages we will support will be published
> afterwards as we get closer to that date.

> Being said that, if you want to take up on translating non-core parts of
> published content and EPF composer environment yourself, you would have to
> get source code from CVS and translate all resources strings used in EPF
> eg. all properties files and provide corresponding "nl" plugins for
> particular language you are interested in. After that, running "epf" with
> command-line options such as "-nl de" (eg. for German language) will have
> environment translated.

> Thanks

however, one more question ....
What does it mean "non-core parts of published content"?
Which parts do you mean?

many thanks,
jan
Re: Again to translation topic [message #566659 is a reply to message #21054] Mon, 09 October 2006 16:16 Go to previous message
Shilpa Toraskar is currently offline Shilpa Toraskar
Messages: 102
Registered: July 2009
Senior Member
It means words like "Task, Role, Discipline etc" in published content.
There are not exactly part of content pages.
Re: Again to translation topic [message #574613 is a reply to message #11406] Wed, 10 January 2007 11:00 Go to previous message
Mauro is currently offline Mauro
Messages: 79
Registered: July 2009
Member
Since EPF 1.0 is done ...there are some news about translation support?

"jan masaryk" <jan.masaryk@asseco.sk> escreveu na mensagem
news:1704006aa6f93386bfaf3d037c62de7f$1@www.eclipse.org...
> Hi all,
>
> I'm reading conversation concerning translation of OpenUP and I would to
> expand question to this topic ...
>
> Some ways we can translate "core" content which I mean concrete method
> content (for example OpenUP). However when I translate whole OpenUP inside
> EPF tool and publish it, this export still contains english parts. Just
> look at published content, visit one of task-type page and look at words
> - Task : ..
> - Discipline
> - Relationships
> - and so on.
>
> My questions:
> 1. How can we translate these non-core parts of published content?
> 2. How can we translate EPF composer enviroment to another language?
>
> Thanks in advance.
>
> All the best and keep good work,
> Jan
>
Re: Again to translation topic [message #574656 is a reply to message #26299] Wed, 10 January 2007 16:43 Go to previous message
Shilpa Toraskar is currently offline Shilpa Toraskar
Messages: 102
Registered: July 2009
Senior Member
EPF 1.0.1 has native language support for 9 languages for the EPF tool.
For EPF content, we would appreciate any volunteers. Check out more
information if you are interested in EPF tool translation support.

http://www.eclipse.org/epf/downloads/tool/epf1.0.1_downloads .php
Re: Again to translation topic [message #574672 is a reply to message #26339] Wed, 10 January 2007 17:19 Go to previous message
Mauro is currently offline Mauro
Messages: 79
Registered: July 2009
Member
Yep...I?ve downloaded the NLpack_epf-composer-1.0.1.zip and I?m now using
the localized version to pt_BR ...thanks...
But I did not see where to find "EPF tool translation support" ?
I?me interested in pt-BR localization for OpenUP content...as a Volunteers

"Shilpa Toraskar" <storaskar@xx.xxx.xxx> escreveu na mensagem
news:c6a257cb11dbe93a5a46f0b179f7a41a$1@www.eclipse.org...
>
> EPF 1.0.1 has native language support for 9 languages for the EPF tool.
> For EPF content, we would appreciate any volunteers. Check out more
> information if you are interested in EPF tool translation support.
>
> http://www.eclipse.org/epf/downloads/tool/epf1.0.1_downloads .php
>
Re: Again to translation topic [message #574688 is a reply to message #26377] Thu, 11 January 2007 00:00 Go to previous message
Ricardo Balduino is currently offline Ricardo Balduino
Messages: 191
Registered: July 2009
Senior Member
Mauro,

Today you have EPF Composer available in various languages, including
Brazilian Portuguese.

Some people have expressed their interest in translating OpenUP to
Portuguese. The general consensus is that we should wait until version 1.0
of OpenUP is released, so the content is stable in order to undergo a
translation effort. This effort would occur in a volunteer basis.

For more information on current OpenUP plan, see
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/des ign/content_dev_plans/?root=Technology_Project

Regards / Sauda
Re: Again to translation topic [message #574714 is a reply to message #26414] Thu, 11 January 2007 10:51 Go to previous message
Mauro is currently offline Mauro
Messages: 79
Registered: July 2009
Member
Thanks Balduino
"Ricardo Balduino" <balduino@us.ibm.com> escreveu na mensagem
news:eo3un6$os8$1@utils.eclipse.org...
> Mauro,
>
> Today you have EPF Composer available in various languages, including
> Brazilian Portuguese.
>
> Some people have expressed their interest in translating OpenUP to
> Portuguese. The general consensus is that we should wait until version 1.0
> of OpenUP is released, so the content is stable in order to undergo a
> translation effort. This effort would occur in a volunteer basis.
>
> For more information on current OpenUP plan, see
> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/des ign/content_dev_plans/?root=Technology_Project
>
> Regards / Sauda
Re: Again to translation topic [message #574943 is a reply to message #26339] Thu, 18 January 2007 08:17 Go to previous message
jan masaryk is currently offline jan masaryk
Messages: 50
Registered: July 2009
Member
I have a look at 'NLS Pack for EPF 1.0.1 and 1.0.1.x' for EPFC and
I really appreciate that localization has been separated. That's really
helpful ...

Hovewer can someone explain a little bit more how to create localization
of EPFC to any language?
I seriously thinking of localization EPFC to slovak ....

all the best,
jan

ps: thank's for great tool, it's definitelly in use. :-)


On Wed, 10 Jan 2007 17:43:22 +0100, Shilpa Toraskar <storaskar@xx.xxx.xxx>
wrote:

>
> EPF 1.0.1 has native language support for 9 languages for the EPF tool.
> For EPF content, we would appreciate any volunteers. Check out more
> information if you are interested in EPF tool translation support.
>
> http://www.eclipse.org/epf/downloads/tool/epf1.0.1_downloads .php
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Previous Topic:XP Plug-in 0.1 available
Next Topic:Guidance Attachment
Goto Forum:
  


Current Time: Sun Sep 21 14:15:08 GMT 2014

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

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