Re: about apache ignite's document localization(Simplified Chinese)

2016-01-12 Thread Dmitriy Setrakyan
Thanks Yujue Li! On Tue, Jan 12, 2016 at 4:11 AM, 李玉珏@163 <18624049...@163.com> wrote: > Hi: > > About the 1.5 version of the chinese manual, in addition to the following > mentioned some of the streamers, all have been translated. > > Address for:https://www.zybuluo.com/liyuj/note/230739。 > > 在

Re: about apache ignite's document localization(Simplified Chinese)

2015-12-28 Thread 李玉珏
Hi: OK! 在 15/12/28 17:12, Denis Magda 写道: Hi Yujue Li, I've added documentation for Ignite Semaphore to Distributed Data Structures section https://apacheignite.readme.io/docs/distributed-semaphore Missed documentation for MQTT and Twitter streamers will be added a bit later. I'll let you

Re: about apache ignite's document localization(Simplified Chinese)

2015-12-28 Thread Denis Magda
Hi Yujue Li, I've added documentation for Ignite Semaphore to Distributed Data Structures section https://apacheignite.readme.io/docs/distributed-semaphore Missed documentation for MQTT and Twitter streamers will be added a bit later. I'll let you know when this happens. The rest of the

Re: about apache ignite's document localization(Simplified Chinese)

2015-12-25 Thread 李玉珏
Hi: In addition, I saw release note, https://github.com/apache/ignite/blob/ignite-1.5/RELEASE_NOTES.txt: * Added IgniteSemaphore data structure. * Added MQTT Streamer. * Added Twitter Streamer. I did not see the relevant documents on the three items mentioned above. Is there no such

Re: about apache ignite's document localization(Simplified Chinese)

2015-12-05 Thread 李玉珏
Hi: As of today, distributed data structures have been translated, and https://www.zybuluo.com/liyuj/note/230739 has been updated. On the whole, I have about half the workload. My spare time is completely in the translation work, so the overall progress is still very fast, if everything

Re: about apache ignite's document localization(Simplified Chinese)

2015-12-04 Thread Dmitriy Setrakyan
Thanks, Yujue Li, for your contribution! We really appreciate the work you are doing. I have added the link to the Chinese documentation to our website. I have also noticed that the documentation is for 1.4 version. Would it be possible to upgrade it to 1.5? All the documentation changes are

Re: about apache ignite's document localization(Simplified Chinese)

2015-12-03 Thread 李玉珏
Hi: As of today, the InteractiveSQL and Streaming parts have been translated to complete, the relevant page has been updated to zybuluo.com, the address is: https://www.zybuluo.com/liyuj/note/230739. In addition, I have the Markdown of the source file to the GitHub, the address is:

Re: about apache ignite's document localization(Simplified Chinese)

2015-11-30 Thread Dmitriy Setrakyan
Thanks Yujue Li! I will add the link to this documentation on our website. Please keep us posted on your progress. On Mon, Nov 30, 2015 at 4:17 AM, 李玉珏@163 <18624049...@163.com> wrote: > Hi: > > As of today, the data grid has been translated and completed. > > I tried to put the HTML on the GIT

Re: about apache ignite's document localization(Simplified Chinese)

2015-11-30 Thread 李玉珏
Hi: As of today, the data grid has been translated and completed. I tried to put the HTML on the GIT repository, but the effect was not good. As a temporary solution, I'm going to put the HTM on the www.zybuluo.com site, and I also use the site to provide the tools for translation. By my

Re: about apache ignite's document localization(Simplified Chinese)

2015-11-17 Thread 李玉珏
Hi: I had hoped that I would finish the translation work, because the workload is not particularly great. The reason to put the code on git.oschina.net, in addition to some of my personal information (such as blogs) are placed on the oschina.net, the main reason is that I want to put the

Re: about apache ignite's document localization(Simplified Chinese)

2015-11-17 Thread Dmitriy Setrakyan
Thanks Yujue Li! We really appreciate the work you are doing. As far as permissions go, is it possible to add users to the project, much in the same way as in GitHub? Another way to suggest documentation fixes could be to file issues in the oschina git (looks like it supports issues in the same

Re: about apache ignite's document localization(Simplified Chinese)

2015-11-16 Thread Dmitriy Setrakyan
In general, it would be great if anyone in the community would be able to contribute. Looks like oschina.net is a copy of GitHub. I tried to create a user there, but could not (I am not getting a verification email). Any ideas? I think the best way to share this process would be to add users to

Re: about apache ignite's document localization(Simplified Chinese)

2015-11-16 Thread Dmitriy Setrakyan
I just got confirmation from oschina (it just took a while). My username is “diset”, can you please add me to the project? D. On Mon, Nov 16, 2015 at 1:38 PM, Dmitriy Setrakyan wrote: > In general, it would be great if anyone in the community would be able to >

Re: about apache ignite's document localization(Simplified Chinese)

2015-11-15 Thread 姜 为
Hi: I do not agree with Yujue Li,his approach is very selfish. At first I wanted to help him complete the Chinese translation of the open-source project, but he can not be on the oschina fork, which means that if he appeared wrong semantic translation, others

Re: about apache ignite's document localization(Simplified Chinese)

2015-11-04 Thread 李玉珏
Hi: My name is Yujue Li. Later I will send an email to dev-subscr...@ignite.apache.org. The reason for the link to be unable to open is a problem for the oschina code hosting platform,in the community, there have been people with similar problems,interested developers can try a few times. 在

Re: about apache ignite's document localization(Simplified Chinese)

2015-11-03 Thread Dmitriy Setrakyan
(adding the contributor to the CC) Hi, I am sorry, I do not know your name, but it is a great contribution! Can I ask you to properly subscribe to the dev list? You need to send an email to “dev-subscr...@ignite.apache.org” and then follow the simply instructions in the reply. This will make