[TF-dev] Re: community translation update
Filippo Mineo <[email protected]> Mon, 4 Mar 2013 10:41:10 +0100
| Newsgroups | gmane.comp.java.netbeans.modules.translated-files.devel |
|---|---|
| Message-ID | <[email protected]> |
--------------090800030901060703000000
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Hi everybody,
glad to see that this project is still alive. Hopefully I will continue
to contribute in the Italian translation.
Regards,
Filippo
> Hi Masaki,
>
> I am happy, that Netbeans translation continues again. I will gladly
> assist you in translating to German.
>
> Yours
>
> Peter Heusch
>> Hi Team,
>>
>> Very sorry that I and Paul haven't updated progress of translation
>> tool for long time. We just got a idea about Timon's OmegaT environment
>> (see attachment) so let me explain current status and my idea.
>>
>> Actually we still can not find a good common/single translation
>> environment other than OpenCTI.
>>
>> We had used OmegaT before. I had evaluated Launchpad. I understand these
>> are working well against small-medium size project but not working
>> well at
>> huge project e.g. NetBeans IDE. NetBeans IDE has large number of
>> .properties
>> and strings to be translated.
>>
>> I believe that Timon's environment can work well against general
>> NetBeans RCP apps,
>> but I'm not sure if it works effectively for NetBeans IDE because of
>> its size,
>> and some issues of OmegaT what we had experienced before.
>>
>> However, if community people really want to try NetBeans IDE
>> translation by OmegaT
>> on that environment, I understand it's worth a try again, and I and Paul
>> are very happy to help as much as we can.
>>
>> I'm just wondering - to provide more flexibility to community people.
>>
>> Here are my idea for now:
>>
>> - NB(I and Paul) continues to support ja,zh_CN,pt_BR and ru all
>> translations and es, de, fr and it NetBeans Platform translation.
>>
>> - NB will provide possible information and resources to community
>>
>> o release schedule
>> o English files to be translated
>> after excluding un-necessary keys - over-translations will cause
>> critical errors
>>
>> - NB will provide a privilege to community people for
>> source code integration to netbeans source tree in translation area
>>
>> o community people can update and integrate translated files
>> o if not able to use hg, I can help
>>
>> - NB will not recommend a single translation tool and environment
>>
>> o community can use own preferred tool e.g. OmegaT, vim and etc.
>> at translation
>> o Will inform Timon's environment but do not enforce
>>
>> What do you think? Any comments? idea?
>>
>> Regards,
>> Masaki
>>
>>> On 2013-2-26 17:38, Timon Veenstra wrote:
>>> Hi all,
>>>
>>> Translation of netbeans rcp applications consist of 2 parts:
>>> - The NetBeans rich client platform
>>> - Application specific
>>>
>>> For the first part of the translation, we have published the
>>> community translations to maven central.
>>>
>>> <dependency>
>>> <groupId>nl.cloudfarming.client</groupId>
>>> <artifactId>lib-platform-l10n</artifactId>
>>> <version>1.0-NB72</version>
>>> </dependency>
>>>
>>> When you are using ant, you could include all the translation jars
>>> to your branding module.
>>> http://java.net/projects/nb-library-wrappers/sources/core/show/lib-platform-l10n/nb72_platform_l10n/platform
>>>
>>>
>>> For the second part we have created an omegat maven plugin.
>>> With the plugin you can extract all the translation sources (bundles
>>> and help files etc) into omegat projects for each language you want
>>> to support.
>>> You can zip those projects (together with the shared-sources) and
>>> send them to your translators.
>>> After they send back the translation projects, you can use another
>>> target to merge the translations back into your source tree.
>>>
>>> More details about it here:
>>> http://java.net/projects/omegat-maven-plugin/pages/Home
>>>
>>> The sources for the plugin are also available, so you could use them
>>> to create an ant task for it.
>>>
>>> Hope it helps.
>>>
>>> Cheers,
>>> Timon
>>
>>
>
>
--------------090800030901060703000000
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta content=3D"text/html=3B charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
</head>
<body text=3D"#000000" bgcolor=3D"#FFFFFF">
Hi everybody=2C<br>
glad to see that this project is still alive. Hopefully I will
continue to contribute in the Italian translation.<br>
Regards=2C<br>
Filippo<br>
<br>
<blockquote cite=3D"mid:[email protected]" type=3D"cite=
">Hi
Masaki=2C
<br>
<br>
I am happy=2C that Netbeans translation continues again. I will
gladly assist you in translating to German.
<br>
<br>
Yours
<br>
<br>
Peter Heusch
<br>
<blockquote type=3D"cite">Hi Team=2C
<br>
<br>
Very sorry that I and Paul haven't updated progress of
translation
<br>
tool for long time. We just got a idea about Timon's OmegaT
environment
<br>
(see attachment) so let me explain current status and my idea.
<br>
<br>
Actually we still can not find a good common/single translation
<br>
environment other than OpenCTI.
<br>
<br>
We had used OmegaT before. I had evaluated Launchpad. I
understand these
<br>
are working well against small-medium size project but not
working well at
<br>
huge project e.g. NetBeans IDE. NetBeans IDE has large number of
.properties
<br>
and strings to be translated.
<br>
<br>
I believe that Timon's environment can work well against general
NetBeans RCP apps=2C
<br>
but I'm not sure if it works effectively for NetBeans IDE
because of its size=2C
<br>
and some issues of OmegaT what we had experienced before.
<br>
<br>
However=2C if community people really want to try NetBeans IDE
translation by OmegaT
<br>
on that environment=2C I understand it's worth a try again=2C and I
and Paul
<br>
are very happy to help as much as we can.
<br>
<br>
I'm just wondering - to provide more flexibility to community
people.
<br>
<br>
Here are my idea for now:
<br>
<br>
- NB(I and Paul) continues to support ja=2Czh_CN=2Cpt_BR and ru all
<br>
=C2=A0 translations and es=2C de=2C fr and it NetBeans Platform
translation.
<br>
<br>
- NB will provide possible information and resources to
community
<br>
<br>
=C2=A0 o release schedule
<br>
=C2=A0 o English files to be translated
<br>
=C2=A0=C2=A0=C2=A0=C2=A0 after excluding un-necessary keys - over-t=
ranslations will
cause
<br>
=C2=A0=C2=A0=C2=A0=C2=A0 critical errors
<br>
<br>
- NB will provide a privilege to community people for
<br>
=C2=A0 source code integration to netbeans source tree in translati=
on
area
<br>
<br>
=C2=A0 o community people can update and integrate translated files
<br>
=C2=A0 o if not able to use hg=2C I can help
<br>
<br>
- NB will not recommend a single translation tool and
environment
<br>
<br>
=C2=A0 o community can use own preferred tool e.g. OmegaT=2C vim an=
d
etc.
<br>
=C2=A0=C2=A0=C2=A0 at translation
<br>
=C2=A0 o Will inform Timon's environment but do not enforce
<br>
<br>
What do you think? Any comments? idea?
<br>
<br>
Regards=2C
<br>
Masaki
<br>
<br>
<blockquote type=3D"cite">On 2013-2-26 17:38=2C Timon Veenstra
wrote:
<br>
Hi all=2C
<br>
<br>
Translation of netbeans rcp applications consist of 2 parts:
<br>
- The NetBeans rich client platform
<br>
- Application specific
<br>
<br>
For the first part of the translation=2C we have published the
community translations to maven central.
<br>
<br>
<=3Bdependency>=3B
<br>
<=3BgroupId>=3Bnl.cloudfarming.client<=3B/groupId>=3B
<br>
<=3BartifactId>=3Blib-platform-l10n<=3B/artifactId>=3B
<br>
<=3Bversion>=3B1.0-NB72<=3B/version>=3B
<br>
<=3B/dependency>=3B
<br>
<br>
When you are using ant=2C you could include all the translation
jars to your branding module.
<br>
<a class=3D"moz-txt-link-freetext" href=3D"http://java.net/projec=
ts/nb-library-wrappers/sources/core/show/lib-platform-l10n/nb72_platform_l1=
0n/platform">http://java.net/projects/nb-library-wrappers/sources/core/show=
/lib-platform-l10n/nb72_platform_l10n/platform</a>
<br>
<br>
For the second part we have created an omegat maven plugin.
<br>
With the plugin you can extract all the translation sources
(bundles and help files etc) into omegat projects for each
language you want to support.
<br>
You can zip those projects (together with the shared-sources)
and send them to your translators.
<br>
After they send back the translation projects=2C you can use
another target to merge the translations back into your source
tree.
<br>
<br>
More details about it here:
<br>
<a class=3D"moz-txt-link-freetext" href=3D"http://java.net/projec=
ts/omegat-maven-plugin/pages/Home">http://java.net/projects/omegat-maven-pl=
ugin/pages/Home</a>
<br>
<br>
The sources for the plugin are also available=2C so you could
use them to create an ant task for it.
<br>
<br>
Hope it helps.
<br>
<br>
Cheers=2C
<br>
Timon
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</body>
</html>
--------------090800030901060703000000--