Hello We definitely should do this. However, we all need to be open and honest about how much work Internationalization is. While at the same time we must keep in mind what a tremendous opportunity it is to make the software available for a larger user base and contributors.
We have to consider all extensions, logs, web ui, docs, etc.. It will take quite an effort. Also not sure if some languages or characters would require UI changes to even render properly. Non-trivial for sure. We should probably make sure there are folks who can volunteer to make language translations before we head too far down this route. Are there any examples of open source projects that have taken this sort of thing on successfully? Thanks Joe On Thu, Oct 22, 2015 at 3:27 PM, Ryan.Xia <[email protected]> wrote: > Hi, > > Our team is working on 2 projects which may use nifi as data flow > controller. But we need add multi lanuage support, such as Chinese and > Japanese. > > We prepare to start add some label properties in JavaScript or JSP as > usual(nifi-web-ui bundle), but before do that, let's confirm whether nifi > community has plan to do it. We'd better follow the right plan. > > Before we head toward nifi, we use Rapidminer to build ETL work flow and > scripts. But now, Rapidminer is not open source product and it's not web > based. Some customers want see their data flow be done and be monitored in > the browser. > > Thanks in advance. > > -- > Regards, > Ryan > > > >
