Hi Fabian,
Yes, I think so.
We can find a way to move the translated content to crowdin to reuse the
translation effort if we want to migrate to Docusaurus in the future.
Regards,
Jark
On Fri, 15 Feb 2019 at 15:19, Fabian Hueske wrote:
> Hi Jark,
>
> Thanks so much for evaluating Docusaurus an
Hi Jark,
Thanks so much for evaluating Docusaurus and Crowdin and writing up this
report!
It seems that staying with the current approach and avoiding the effort of
porting the documentation is the best solution for now.
We might want to reconsider Docusaurus if we want to restructure the
documen
Hi all,
Qianjing Xu and I have been exploring Docusaurus and crowdin in recent days
to see how can Flink fit into them to support multi-language.
Here is the summary from our side:
(we didn't learn deeply, so we may miss something or misunderstand. Please
correct us if we are wrong)
# What is Do
Hi,
I agree with the proposal, Gordon and Jark, and I think it's a good solution
for major doc changes. We also created separated JIRAs for English
documentation in the past.
For minor doc changes, I think it’s better to encourage Chinese-speaking
contributors to participate in the reviewing p
Hi @Sijie,
Thank you for the valuable information. I will explore Docusaurus and
feedback here.
Best,
Jark
On Tue, 12 Feb 2019 at 18:18, Fabian Hueske wrote:
> Hi everyone,
>
> +1 to what Gordon and Jark proposed.
> We should make use of the review bot to ensure that new features are
> documen
Hi everyone,
+1 to what Gordon and Jark proposed.
We should make use of the review bot to ensure that new features are
documented at least in English.
If the Chinese docs are not updated, a Jira issue must be created.
@Sijie, thank for the pointer to Docusaurus! IMO, this looks very
interesting a
Hi,
Sorry for interrupting the thread. But this topic sounds interesting to me.
It might be worth for you guys checking out docusaurus
https://docusaurus.io/docs/en/translation . Docusaurus is a documentation
framework open sourced by Facebook. It has handled versioning and
localization (via crowd
On Tue, Feb 12, 2019 at 3:17 PM Jark Wu wrote:
> Hi Gordon,
>
> I totally agree with your proposal.
>
> A minor comment: "updated required English documentation" should be
> "updated required Chinese documentation" ?
>
Actually, that was what I meant to say.
My intention is that at least the Eng
Hi Gordon,
I totally agree with your proposal.
A minor comment: "updated required English documentation" should be
"updated required Chinese documentation" ?
Btw, I like the "zh-doc" label!
Regards,
Jark
On Tue, 12 Feb 2019 at 14:48, Tzu-Li (Gordon) Tai
wrote:
> Hi,
>
> While I 100% agree wi
Hi,
While I 100% agree with @Xingcan that we should try to avoid adding extra
burden for contributors, at the very least, creating JIRA issues for adding
missing Chinese / English document updates must be done.
In the past, even with English documentation only, we already had the
problem of mergi
Hi @Xingcan,
> I think assigning pages to someones and synchronizing them regularly may
be a better idea.
> 1. We encourage contributors who are familiar with Chinese and would like
to do the translation to provide Chinese doc updates in sync, but should
not add extra burden (even like creating tr
Hi all,
Thanks @Jark for creating the translation terminology document! I think the
idea of keeping some of the terminologies untranslated and keeping such
document in place is absolutely good.
I actually share the same concern with @Shaoxuan regarding the discrepancy
getting larger. The dilemma i
Hi,
Thank you for working on this.
I think assigning pages to someones and synchronizing them regularly may be a
better idea.
1. We encourage contributors who are familiar with Chinese and would like to do
the translation to provide Chinese doc updates in sync, but should not add
extra burden
Hi Shaoxuan,
Thank you for your feedback.
If the author is not familiar with Chinese, he/she should create a
translation JIRA before the pull request is merged in.
The created JIRA can be attached a "chinese-translation" tag so that it can
be searched easily. Then a Chinese contributor can take t
Thanks for spending efforts to build a Flink web in Chinese, everyone.
Good job, Jark!
This looks look to me. I have only one concern about the synchronization of
the English and Chinese website. We can not expect the author of the
English doc to produce Chinese doc at the same time. If no one fo
Hi Rong,
You raised a good question. The terminology translation is a difficult
problem because different people may prefer different translations.
So I would like to start a terminology translation specification discussion
(maybe it should be another thread) to reach a consensus in the community.
+1. Thanks for the proposal @Jark.
I think utilizing review-bot will definitely be a good plus.
I remember @Robert mentioned that there was an auto checklist
functionality, maybe we can utilize that to flag/tag a specific PR is ready
for documentation parity review?
I would also like to follow up
Hi all,
Thanks for the positive feedback we received so far.
I have created two umbrella JIRA for tracking the efforts:
For flink-web: https://issues.apache.org/jira/browse/FLINK-11526
For flink-docs: https://issues.apache.org/jira/browse/FLINK-11529
I'm working on the framework changes for fli
Nice proposal
+1
On Tue, Feb 5, 2019 at 8:16 AM Hequn Cheng wrote:
> Hi,
>
> big +1 for this!
> Thank you Jark for writing the great document. I totally agree with the
> proposal. It not only keep the English document same as before but also
> proposes a way to integrate with Chinese ones.
>
>
Hi,
big +1 for this!
Thank you Jark for writing the great document. I totally agree with the
proposal. It not only keep the English document same as before but also
proposes a way to integrate with Chinese ones.
Best, Hequn
On Mon, Feb 4, 2019 at 6:18 PM Fabian Hueske wrote:
> Happy Chinese
Happy Chinese New Year!
Thank you Jark for working on a prototype and writing up the this great
proposal.
+1 for the suggested approach
Best,
Fabian
Am Mo., 4. Feb. 2019 um 11:05 Uhr schrieb jincheng sun <
sunjincheng...@gmail.com>:
> +1 ， Happy Chinese New Year! :)
>
> Best，Jincheng
> From Sin
+1 ， Happy Chinese New Year! :)
Best，Jincheng
>From Singapore
Jark Wu 于2019年2月4日 周一13:23写道：
> Hi all,
>
> I have drafted the proposal:
>
> https://docs.google.com/document/d/1R1-uDq-KawLB8afQYrczfcoQHjjIhq6tvUksxrfhBl0/edit#
> Please feel free to give any feedbacks!
>
> I have also created a pro
+1 for the proposal.
Cheers,
Till
On Mon, Feb 4, 2019 at 9:50 AM Robert Metzger wrote:
> Hey Jark,
>
> Happy New Year :)
>
> thanks a lot for the proposal and the prototype. I fully agree with your
> proposal and I think it's good to go!
>
> Regarding the review-bot: We can add another item for
Hey Jark,
Happy New Year :)
thanks a lot for the proposal and the prototype. I fully agree with your
proposal and I think it's good to go!
Regarding the review-bot: We can add another item for documentation in both
English and Chinese, once the framework for the Flink docs has been merged.
On
Hi all,
I have drafted the proposal:
https://docs.google.com/document/d/1R1-uDq-KawLB8afQYrczfcoQHjjIhq6tvUksxrfhBl0/edit#
Please feel free to give any feedbacks!
I have also created a prototype to integrate Chinese for flink-web, here is
the branch: https://github.com/wuchong/flink-web/tree/mult
Hi,
Great seeing efforts in pushing this forward, Jark!
A bit late in the party here, but I just want to also point out that:
- +1 to https://flink.apache.org/zh/ as the website address
- Add to the contribution checklist in PRs that both English / Chinese docs
have been updated accordingly.
I
Hi Jark,
Thanks for working out a plan to integrate the Chinese translation!
I would propose to first contribute and integrate the Chinese version of
the main page (flink.apache.org).
It is much smaller than the docs and a smaller scope might help to find
tricks to ease the integration of the doc
Hi,
Thank you all for welcoming this proposal.
I will draft a detailed proposal about how to do contribute it step by step
in the next few days, and create umbrella JIRA once the proposal is
accepted.
@Fabian @JIngcheng Regarding the name, I'm fine with
https://flink.apache.org/zh/.
@Yun Tang T
Is the build-system for flink-china.org identical to flink-web?
On 28.01.2019 12:48, Jark Wu wrote:
Hi all,
In the past year, the Chinese community is working on building a Chinese
translated Flink website (http://flink.apache.org) and documents (
http://ci.apache.org/projects/flink/flink-docs-
Hi Jark,
I am glad to see your exciting email about contributing to Flink Chinese
Community. Remebering the days to solve outstanding issues in Spark
Officical Documents, the project was developped slowly, I am looking forward
to more and more contributions to Flink Chinese Community. Of course
Hi Jark,
Thank you for starting this discussion.I am very willing to participate in
flink document translation.
Best,
Nicholas
--
Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
create a jira for the Chinese documents.
-- --
??: "fudian.fd";
: 2019??1??29??(??) 1:30
??: "dev";
: Re: [DISCUSS] Contributing Chinese website and docs to Apache Flink
Hi Jark,
Thanks a lot for startin
Keep also in mind the other direction eg a new/modified version of the Chinese
documentation needs to be reflected in the English one.
> Am 29.01.2019 um 06:35 schrieb SteNicholas :
>
> Hi Jark,
>
> Thank you for starting this discussion.I am very willing to participate in
> flink document tra
Hi Jark,
Thank you for starting this discussion.I am very willing to participate in
flink document translation.
Best,
Nicholas
--
Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
Hi Jark,
Thanks a lot for starting the discussion! It would be great to have an official
Flink Chinese doc. For the long term maintaining problem, I think creating a
JIRA when the English documentation is updated is a good idea. Should we add
one item such as "Does this pull request updated th
Thanks Jark starting this discussion!
Hi Fabian, very glad to hear that you like this proposal.
As far as I know， `zh` is the language, `cn` is the territory, such as:
`zh-cn` representative
Simplified Chinese (China) , `zh-tw` representative Traditional Chinese
(Taiwan), So i like the naming the
gt; > You signed out in another tab or window. Reload to refresh your session.
> > github.com
> >
> > Best
> > Yun Tang
> >
> > From: Fabian Hueske
> > Sent: Monday, January 28, 2019 21:48
> > To: dev
> > Sub
cn>
> You signed in with another tab or window. Reload to refresh your session.
> You signed out in another tab or window. Reload to refresh your session.
> github.com
>
> Best
> Yun Tang
> ________
> From: Fabian Hueske
> Sent: Monday, Janua
m
Best
Yun Tang
From: Fabian Hueske
Sent: Monday, January 28, 2019 21:48
To: dev
Subject: Re: [DISCUSS] Contributing Chinese website and docs to Apache Flink
Hi Jark,
Thank you for starting this discussion!
I'm very happy about the various efforts to support the Chinese Flin
Hi Jark,
Thank you for starting this discussion!
I'm very happy about the various efforts to support the Chinese Flink
community.
Offering a translated website and documentation gives Flink a lot more
reach and will help many users.
I think integrating the website and documentation as subdirector
Hi all,
In the past year, the Chinese community is working on building a Chinese
translated Flink website (http://flink.apache.org) and documents (
http://ci.apache.org/projects/flink/flink-docs-master/) in order to help
Chinese speaking users. This is http://flink-china.org and it has received
a
41 matches
Mail list logo
