|
|
Re: Again to translation topic [message #19024 is a reply to message #18981] |
Fri, 22 September 2006 16:02 |
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 #19711 is a reply to message #19024] |
Sun, 01 October 2006 18: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 #566215 is a reply to message #19024] |
Sun, 01 October 2006 18: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
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04910 seconds