[TF-dev] Re: community translation update
Geertjan Wielenga <[email protected]> Wed, 06 Mar 2013 13:48:39 +0100
| Newsgroups | gmane.comp.java.netbeans.modules.translated-files.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------020505020907020400000303
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Yes, I think having all the files in a public repo, e.g., java.net,
would be ideal. That way, no ZIP file would need to be downloaded.
Instead, we'll check out the files -- one folder for each language, and
work on translating them. Before working on a file, we'll do an update
on the file to make sure that changes done by anyone else on the file
are incorporated before making any further changes.
Very much looking forward to this process,
Gj
On 03/06/2013 09:34 AM, Masaki Katakai wrote:
> Thank you very much Peter and Filippo!
>
> I really appreciate your contributions at NetBeans community releases!
>
> Peter, Filippo and Team:
>
> Let's start to think about translation process by using OmegaT.
> Here is our process when we used OmegaT before:
>
> http://nblocalization.netbeans.org/6.5/index.html
>
> I can imagine that new process will be almost the same,
>
> 1) pickup English files to be translated
> 2) translate & generate by using OmegaT
> 3) integration
> 4) build & test
>
> As I mentioned before, I'd like to ask you to participate more.
> Our team members had good experiences at past releases.
> Any suggestion about this process?
>
> For 1), I have put zip files on nblocalization:
> http://netbeans.org/projects/nblocalization/downloads/download/7.3/nb73_l10nkit.zip
> (English files to be translated)
> http://netbeans.org/projects/nblocalization/downloads/download/7.3/nb73_l10n.zip
> (Current translations)
> I will try to prepare source repository on public place e.g. java.net.
>
> The way to share translation memory may depend on each community at 2).
> However it's nice if you could provide a good example from your
> experiences.
>
> Anyway, please share your experiences and opinions!
>
> Regards,
> Masaki
>
> 03/04/13 18:41, Filippo Mineo wrote:
>> 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
>>>>
>>>>
>>>
>>>
>>
>
--------------020505020907020400000303
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
</head>
<body bgcolor=3D"#FFFFFF" text=3D"#000000">
<div class=3D"moz-cite-prefix"><br>
<br>
Yes, I think having all the files in a public repo, e.g.,
java.net, would be ideal. That way, no ZIP file would need to be
downloaded. Instead, we'll check out the files -- one folder for
each language, and work on translating them. Before working on a
file, we'll do an update on the file to make sure that changes
done by anyone else on the file are incorporated before making any
further changes.<br>
<br>
Very much looking forward to this process,<br>
<br>
Gj<br>
<br>
On 03/06/2013 09:34 AM, Masaki Katakai wrote:<br>
</div>
<blockquote cite=3D"mid:[email protected]" type=3D"cite">
<meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-=
Type">
<div class=3D"moz-cite-prefix">Thank you very much Peter and
Filippo!<br>
<br>
I really appreciate your contributions at NetBeans community
releases!<br>
<br>
Peter, Filippo and Team:<br>
<br>
Let's start to think about translation process by using OmegaT.<b=
r>
Here is our process when we used OmegaT before:<br>
<br>
<meta http-equiv=3D"content-type" content=3D"text/html;
charset=3DUTF-8">
<a moz-do-not-send=3D"true"
href=3D"http://nblocalization.netbeans.org/6.5/index.html">http=
://nblocalization.netbeans.org/6.5/index.html</a><br>
<br>
I can imagine that new process will be almost the same,<br>
<br>
=C2=A01) pickup English files to be translated<br>
=C2=A02) translate & generate by using OmegaT<br>
=C2=A03) integration<br>
=C2=A04) build & test<br>
<br>
As I mentioned before, I'd like to ask you to participate more.<b=
r>
Our team members had good experiences at past releases.<br>
Any suggestion about this process?<br>
<br>
For 1), I have put zip files on nblocalization:<br>
=C2=A0
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext"
href=3D"http://netbeans.org/projects/nblocalization/downloads/download/7.=
3/nb73_l10nkit.zip">http://netbeans.org/projects/nblocalization/downloads=
/download/7.3/nb73_l10nkit.zip</a>
(English files to be translated)<br>
=C2=A0 <a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext=
"
href=3D"http://netbeans.org/projects/nblocalization/downloads/download/7.=
3/nb73_l10n.zip">http://netbeans.org/projects/nblocalization/downloads/do=
wnload/7.3/nb73_l10n.zip</a>
(Current translations)<br>
I will try to prepare source repository on public place e.g.
java.net.<br>
<br>
The way to share translation memory may depend on each community
at 2).<br>
However it's nice if you could provide a good example from your
experiences.<br>
<br>
Anyway, please share your experiences and opinions!<br>
<br>
Regards,<br>
Masaki<br>
<br>
03/04/13 18:41, Filippo Mineo wrote:<br>
</div>
<blockquote
cite=3D"mid:[email protected]"
type=3D"cite">
<meta content=3D"text/html; charset=3DUTF-8"
http-equiv=3D"Content-Type">
Hi everybody,<br>
glad to see that this project is still alive. Hopefully I will
continue to contribute in the Italian translation.<br>
Regards,<br>
Filippo<br>
<br>
<blockquote cite=3D"mid:[email protected]"
type=3D"cite">Hi Masaki, <br>
<br>
I am happy, 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, <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, <br>
but I'm not sure if it works effectively for NetBeans IDE
because of its size, <br>
and some issues of OmegaT what we had experienced before. <br=
>
<br>
However, if community people really want to try NetBeans IDE
translation by OmegaT <br>
on that environment, I understand it's worth a try again,
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,zh_CN,pt_BR and ru
all <br>
=C2=A0 translations and es, de, 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-translations
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
translation area <br>
<br>
=C2=A0 o community people can update and integrate translated
files <br>
=C2=A0 o if not able to use hg, 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, vi=
m
and 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, <br>
Masaki <br>
<br>
<blockquote type=3D"cite">On 2013-2-26 17:38, Timon Veenstra
wrote: <br>
Hi all, <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, we have published
the community translations to maven central. <br>
<br>
<dependency> <br>
<groupId>nl.cloudfarming.client</groupId> <br>
<artifactId>lib-platform-l10n</artifactId> <br>
<version>1.0-NB72</version> <br>
</dependency> <br>
<br>
When you are using ant, you could include all the
translation jars to your branding module. <br>
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext"
href=3D"http://java.net/projects/nb-library-wrappers/sources/core/show/li=
b-platform-l10n/nb72_platform_l10n/platform">http://java.net/projects/nb-=
library-wrappers/sources/core/show/lib-platform-l10n/nb72_platform_l10n/p=
latform</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, you can use
another target to merge the translations back into your
source tree. <br>
<br>
More details about it here: <br>
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext"
href=3D"http://java.net/projects/omegat-maven-plugin/page=
s/Home">http://java.net/projects/omegat-maven-plugin/pages/Home</a>
<br>
<br>
The sources for the plugin are also available, so you
could use them to create an ant task for it. <br>
<br>
Hope it helps. <br>
<br>
Cheers, <br>
Timon <br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>
--------------020505020907020400000303--