[TF-dev] Re: community translation update

This is great news.

I think the bottom line from Timon's experience is that the translation 
system does not need to be 100% perfect. So long as it works reasonably 
well and everyone knows how to use it, and knows what the problems are, 
it's OK.

Also, another point concerns flexibility: yes, that's nice. On the other 
hand, clarity and simplicity is preferable -- let's make one specific 
process, one specific tool, and one specific set of guidelines 
available. Flexibility can come later, let's first have clarity.

Sounds like the OmegaT environment is the way to go  -- despite any 
problems it might have. Now, how do we get the existing translations 
that were last done in 7.0 into the OmegaT system in such a way that we 
can start working on them again?

Gj

On 02/27/2013 11:35 AM, Masaki Katakai wrote:
> 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
>
>