| Again to translation topic [message #11406] |
Mon, 29 May 2006 09:36  |
Eclipse User |
|
|
|
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 #26779 is a reply to message #26339] |
Thu, 18 January 2007 03:17  |
| Eclipse User |
|
|
|
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 08:58 |
| Eclipse User |
|
|
|
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 12:02 |
| Eclipse User |
|
|
|
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 11:10 |
| Eclipse User |
|
|
|
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 14:36 |
| 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 #566609 is a reply to message #19024] |
Fri, 06 October 2006 09:29 |
| Eclipse User |
|
|
|
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 #574613 is a reply to message #11406] |
Wed, 10 January 2007 06:00 |
| Eclipse User |
|
|
|
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 #574943 is a reply to message #26339] |
Thu, 18 January 2007 03:17 |
| Eclipse User |
|
|
|
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/
|
|
|
Powered by
FUDForum. Page generated in 0.06399 seconds
Home