Hyperledger Foundation Hyperledger Global Forum 2022, 6 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Beyond the Language Barrier – Translating Hyperledger Fabric Documen... Yuki Kondo & Daiki Nakashima

Description

Beyond the Language Barrier – Translating Hyperledger Fabric Documentation Into Japanese - Yuki Kondo, Hitachi, Ltd. & Daiki Nakashima, Mitsubishi Electric Corporation

Hyperledger Fabric is used for various use cases all over the world. However, it was hard for non-English speakers to learn the technology correctly because the official documentation was written in English and updated quickly. The quick updates made the local language's learning resources outdated soon. To remove the language barrier, Hyperledger Fabric Documentation Working Group started translating the official documentation in various language. When the content is available in the native language, more non-English speakers will easily learn and adopt Hyperledger Fabric technologies. As one of the sub-groups, Japanese Doc WG was launched in July 2020. Japanese Doc WG created the translation contribution process, communication channel (e.g. monthly Zoom meeting, Japanese chat group) and Kanban board. To improve the productivity and quality, Japanese Doc WG made Japanese terminology and introduced a translation tool while collaborating with translation experts. Japanese Doc WG also hosted Meetups to increase the number of contributors. In this session, Japanese Documentation WG will share their experiences for other language communities to work on the translation.

Sessions Details & Slides (if available): https://sched.co/14H4H
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
Hyperledger – Open Source Blockchain Technologies

Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use

Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory

Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter

Follow-us on Twitter @Hyperledger

Learn about Hyperledger Membership: https://www.hyperledger.org/about/join

#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)

A

We want to start our session, so I'm lucky from Hitachi and his daddy from Mitsubishi Electric. Thank you for coming here. We are very happy to have you here today. We will talk about our contribution about translating average fabric documentation into Japanese.

A

Fabric is used all over the world. Many people are working to achieve their Innovation by using blockchain Technologies.

A

Some of them are not English speakers, so they have some programs learning and reading English documents because they are no native English speakers to overcome those barriers. Private fabric, the creation working group has been working on transmission level. Damages Japanese working group is from so today we will share our motivation, Community Development International tips and challenges.

A

Okay, heavy, okay, okay, sorry and okay. So uh after a station I hope more people will start the transformation effort.

A

So the first topic is motivation. Why we are here, you know fabric is a great blockchain platform, so many people use it. However, you know English speakers have hard time, keep up with frequent, updated hybrids document and there are two program cases. The first case is transaction tools, do not provide enough quality, their famous threshold is still selective, l or Google translate those are great tools, but they cannot understand the technical context, so automatically translated documents do not provide good quality.

A

In other case, some local Engineers write blog posts in their local language, but those articles become outdated soon, because fabric is updated. Frequently, for example, some guys write how to deploy fabric. We want to that wearing fabric. We do to express those documents are outdated.

A

A short no native speakers have language barriers.

A

Look out those language barriers, hybrid fabric. The question working group has studied initiative to translate. We should document into local languages. The goal is to enable more English speakers to learn. Average fabric is a local languages.

A

If the document is available as a local language, what people will adopt a budget Technologies and as a working group there are 11 language teams. Each local community has their own contributors and they are working on translation.

A

Japanese foreign group is a force group. The the greatest working group helped study youth language translation. They provide good good guidelines and communication tools.

A

So why we translate I think we have three good reasons. The first motivation is learning blockchain technology to translate the document. We need to understand the technology in detail and the second reason is learning open source contribution. Contributing code is little difficult, so translation is a good starting point to understand the contribution, process and tools.

A

Lastly, we can connect with local community. We can get feedbacks from local guys and we can connect with current companies in local community. These are the motivations.

A

So the next topic is Community Development.

A

This graph shows the overview of geography. Integration, working group contributors pick up an English document and then they translate it into Japanese, and this survey is a dog to the digital repository and maintenance jacket, and the document is erased, contributors for the visual process and they use communication tools. These contribution process and communication tools are supported by Aboriginal, staffs and fabric education watching groups.

A

This graph is the latest version. So when we started the team and there is no concrete process, so we faced a lot of programs. So we solve those problems and we build Community Management like this one by Troian era, so that we share some problems and solutions. Today.

A

This is a history of our community building, launching translation, working group, develop contribution, process, standardized, suggestion, Guru and recruit contributors.

A

So first topic is studying a transaction team studying attraction starting a translation team is building new open source community. However, we do not have enough knowledge and experience for organizing a new community. We didn't know how to build a transaction team, how to call for contributors.

A

So our parent group, that is hybrids for the question working group, helped us to organize a community. They provided us communication, 2 and constitutional guides.

A

Japan also helped us the code for contributors in Japan because they have connection with local Engineers. I am one of them.

A

After study was a chair. We had qualification program because original members used emails to connect with each other. So communication was closed, so Universe cannot access to communication logs.

A

The other problem is English is required to ask questions at fabric dog I attend Channel, and this is other communication barrier. So to solve the question, we asked hyperte staffs to create a new channel for each other's look watching group structure their effort. Now we have Wiki this code and GitHub Zoom for the Japanese stock watching group, so we communicate in Japanese and everyone can see the communication log. This is how we solve the communication program.

A

Next topic is setting the milestone. I know, fabric has various active versions. Each value has documents so which version is best for translation. To answer this question reset criteria. The criteria includes LTS version number of users at blockchain services and used for a long time when we started the project fabric, 2.2 was the latest ATS. However, most workshops provide the use fabric 1.4 for the actual service, so readers read articles and really wonderful.

A

Concerning the situation, we wanted to follow, maybe a good candidate, but it may not be used for a long time. For the future. We decided to translate 2.2.

A

It was a good decision because now most School crowd providers provide Fabric in 2.4, so it was a good decision.

A

After sitting the Milestone, we needed to decide the priority of translation, because there are many tokens. So where do we start the translation? To start to answer this question fabric documentation group provided as biology guidelines? There are student levels, first topics documents for document contributors. They include a contribution guide and grocery suggested next topics. Next priority.

A

It has high priority documents for Developers, for example, key Concepts getting started. Tutorials are encoded as the topics for Developers, for example, operational guides and Architectural. Friends are equally so we follow this guideline, so we first translate first topics and suggest next topics. Now we are working on others, foreign. So the next step is developing cultivation process. Contribution process is important to collaborate efficiently.

A

The first solution is contributor role: Japanese segregation group consists of Engineers fabric code contributors and professional translators. They had different level of experience about hybrid fabric, so we had to find a way to collaborate efficiently as one team. So we introduced three ways for contribution.

A

Translator is a law through traffic document. They don't need to have any equipment.

A

We will check the translated translated documents. They need to have previous experience about hybrid fabric, for example, fabric called contributor fabric application developer, and a certification holder of Linux Foundation to record support is a low full support using a tools, so each continue pick up a role as they like.

A

And the translation floor is also important for collaboration, so we decide translation flow. The requirement is simple contribution process, because our community has beginners about open source contributions, so we looked for translation process and as a open source community, the most famous one was Sphinx that we give up use following things, because the contribution process is very complicated and the fabric has multiple formats, like.me and Dot rst, but strings only supported.rsd, so we keep up using Sphinx.

A

Instead, we introduce more simple translation flow. We just followed Fabric's GitHub contribution process, so it's contributor picks up a file. They translate and they just keep the document forward. So it was it's a simple but, as we think is effectively are working.

A

And the next topic is task management, so there are many pages reading translation, so we need to collaborate as one team, so we use GitHub camper board, uh yeah I know your family was comfortable, so this event shows the cover board and the left side is to the tasks and the next Lane is a progress task and the right bank is uh task completed. So each contributor can pick up an issue that we can share. Who is working on what tasks and what is left?

A

Thank you. So the next step is standardize translation rule. The purpose is to keep the quality and productivity of translation, so we introduced translation workbook on terminology.

A

Good documentation has common style throughout all pages, but we didn't have common styles so, where a translator submit the request, maybe as I had to compare with the previous documents, so contributors and reviewers had no time to check the styles, but we wanted to focus on what content itself so to solve the problem. We introduced a transmission book translator a check. The documents before submitting our reviews use the checklist as a checking point.

A

The rule book itself is updated anytime because we may find some of your problems and tips.

A

This view shows the examples of transpiration rubric. It includes terminology, Japanese style, no broken format and PR template. For example, no broker format is used to check if the documentation format is not broken. For example, the link to other documents may be broken after transition, so we need to check it. Another example is a PR tablet.

A

We have a rule but call it has only one page, because we want to avoid The Logical fact. So we need to introduce this rules and we also have a rule that as a tech jgp, because all language groups share origin repository so adding the tab is useful to pick up already. Japanese document issues.

A

And let me explain the terminology in detail. This is very important topics. We studied the translation, we used Fabrics grocery to standardize terminology. It contains 47 pairs of English and Japanese words. However, it did not work enough, it's so the 47 words are not enough to cover our words, so we initiated a special subgroup for creating a new terminology for Japanese, so we collected terminologies from previously class 19 documents, so we found 467 460 three terms and we categorized those words into four levels: level. One is the highest priority.

A

Those words are fabric words like Audra or endorser level. Two instruction words by equipped currency level, 3 is additional times and level. 4 is called archiverse. This terminology is still in progress, so we manage those articles or GitHub.

A

This is an example of our terminology. The left lane is English as a redneck is Japanese, so contributors check if they use a correct staff energy before submitting a request.

A

Creative terminology introduce other program because we have over 400 words here, so checking over us is heavy work, so how much the translators are? Reviews for the topology to answer this question. We introduce a practical policy based on other levels.

A

You know so contributors must follow level. Two. It means that we need to follow public words and block universe are checking level three and four is additional. So this is how we balance the quality and productivity of translation.

A

The last topic is recruiting new contributors a year after the launch of the team. The number of active contributors decreased. I said it also. It also happens at open source quality. So we need to how what do you contribute us?

A

So we had meetups with Lux Furniture Japan as the Meetup. We introduced our translation activity and we share the verification and explain transition flow after the Meetup November joins the better. Thank you. He is also the new contributor, so we will be happy to have your members, foreign state of our team. We have cooperated translating 91 percent adjustment.

A

We hope we will complete our tasks soon, probably by the end of this year, as the translated document is available here. So if you have time, please check it and there are many languages here. So please check it. We have French Chinese, parish and so on.

A

Okay, so next topic is translation tips. So I've lost my mic to Daddy, go ahead.

B

Thank you so, from this session.

B

It's playing uh three translation rule are tips so add to first it's the point of translation rule. uh As we mentioned before, uh we made a translation rule.

B

So I introduced a.

B

The point of their translation tips and language, so a solution for language specific manner in Japanese. There are two point of view: end of the sentence and the punctuation mark, so both of them. There are many types in Japanese like punctuation, mark, Maru, 10.

B

and sometimes Japanese, use, Dot and comma depend on their document like thesis, it's actually up to people. So we put uh solution for language, specific manner to translation rule and another thing is a permutation to working members, and you know there are that's their important thing to use.

B

Translation root by working members continually, so we tried many things like share by Wiki and put uh review process like that. So next is a sentence not to be translated.

B

Sometimes you sometimes it is better to not be translated to local language, because sometimes you have a technical problem or contents and, for example, we have a technical problem. When we translate link sentence, we couldn't go to jump, go jump to URL pages, so we guess it's a language, specific problem. So because Japanese is not the Latin language, so we decided. Sir uh link sentence is not to translate it in into Japanese and after that we put them to your translation rule. You know it's a so important thing.

B

So last it's a it's for review viewer to understand easily you know, Japanese is so complicated sentence uh because a conclusion sentence is lost.

B

For example, in terms of grammar Japanese, uh no English is a subject and verb and the object while Japanese is a subject, object and verb. So that's why Japanese so complicated.

B

So, for example, you translate uh this example. Some sentence by Machine translation, you get left side sentence, so red line is a conclusion sentence. So by Machine translation, it's a conclusion sentences uh separate it. So we Endeavor to try to make sentence shorter and the conclusion first. Maybe it's very easy to understand.

B

So next challenges for our work, better.

B

First call for more contributors, so actually we have only seven active members so to activate our working group, we have to share a recruit more contributors, so we try to to do something like these things.

B

Second catch up to next LTS version. We know that the next LTS version will be released soon, so we have to think about how to get new release version into documentation.

B

Third, if a variation for Japanese documents, so we know we want to know how use for how useful Japanese documentation is. So we guess we think that you, we use metrics for page viewers to another any kinds of two, but you know uh you. We have some ideas where we do not have a specific plan. So actually we would like to discuss with you so last conclusion:.

B

We show the four things motivation. We want to remove the barrier for no English speaker to understand fabric technology and this through documentation activity. We can understand hyper fabric, deeply Community Development, so we tried many many things to build, develop and improve constantly for our better transfer transaction tips, which showed three translation tips for space solution.

B

Specific problems, the last challenges we will try to three things for our work better. You know uh our back activity is still developing.

B

So, thank you so much for listening and thank special thanks for Linux Foundation steps, uh fabric documentation, working group and thank you for everything. Japanese documentation, working group members.

B

Thank you so much so thank you for listening.

B

So if you have any queries, please let me know.

C

B

Another language actually do you know it.

A

Is a quality? Oh yes, so I think a contribution process is very important for collaboration so because, um if we work on transition by only one person, it's very hard work so cooperating with other people are very good ways to translation so to work efficiently. With other guys, contributions is a very important, so fabric, sequential vertical, provided us good Baseline, but each language has different situation, so I think it's a good idea to improve those basically drives to fit their own language.

A

For example, Japanese still introduced terminology for Japanese, because English and Japanese don't fit one-to-one, so we've been able to decide the appropriate words for a Japanese, so yeah ethical, creating the contributions process is important for other language. Community, too, welcome go.

C

C

Other translating tools, for instance,.

A

Yeah, we also tried at Google, translate and DBL.

C

A

Of course they provide such documents, but they cannot understand the typical context for blockchain or hybrid fabric, so sometimes they display weird translation, so yeah. We need to translate by ourselves to provide good quality documentation for leaders.

C

So is it okay to ask you to express your personal opinions about quality of a public documentation.

A

It's a good question, so I think uh fabric contributors provide good documentation because it's very well organized so they provide the getting started. Tutorials give Concepts and reference architecture. So, okay, uh we get checked talk about at based on our levels, so beers can use tutorials and getting started and if operator, who are working on production level, take care of these reference architecture or operational guys. So, let's see the documentation is very organized uh yeah. Of course. Sometimes I cannot understand someone there, but yeah. Also I, think public provides good quality of documentation.

A

Does it make sense.

C

Does it fit your expectations as a Japanese industry.

A

C

I understand, that's a good documentation, but does it fit your expectations as a Japanese engineer, are you satisfied with the documentation or you would like to give more details.

A

A

I know see a Japanese culture Engineers customers want to go to court of documentation, but this is the open source community. So if you want to improve the quality of documentation, we can contribute so yeah I think it's a challenge, but our next step is to contribute to public documentation itself. So, after completing the translation yeah, we can propose some improvements for problem documentation itself, so yeah I think it's a good contribution from our site.

A

A

Any other comments or questions.

C

I have questions because we work in Japan a lot for over 20 years, I kind of understand a little bit of.

A

C

So what was the main issue of introducing more like a hyperological technology, digital foreign.

A

Concepts, but we have earlier food production level, services, so I don't know what what is that um root cause of hesitation, but it's hard for us to go to the production level. So it's a corporation in Japanese boxing world.

A

You're welcome. Thank you. You have any comments.

B

uh Actually, uh in terms of technological documentation in English, I think it's not enough to uh build or like prototype hypothetic system. So actually it's not technically technological problem, but you know in English. Documentation is also important, I think so.

B

I I won't to I want.

B

I won't I want to to I want the community to.

B

Improve documentation, contents more and more deeply.

B

Okay, thank you. So much.

D

D

Easy to translate into different languages, just like we talk about some standards. Can we have those standards when we make documentation in English? So it's much easier for you guys to translate into like enable language also.

A

Yeah I said it's a good suggestion, so I think we can share some levels so yeah. We can understand that, as at some levels equals continuous process and time, energy cover programs and other languages, so I think it's a good idea to shift knowledge between different language groups and taking also customize at some point to improve their own language specific program. Yeah. Thank you for your advice.

E

I have something begins with you know: digitizing the documents like uh you know, I've been working with some organizations who have like 40, 50 or even 17 years of old documents which are still relevant for them and they wanted to militize them. So as part of it, you know, prepares many challenges, but.

A

E

Thing that we understood was, if you know like carrying on the same point, if the documentation when it was done, it followed certain principles. Like you know, this is the app format. This is the font. This is how paragraph should start. If it followed those things you know, then it then the job was very easier, like the same job that you know would take someone a year could be reduced very well to a month right, 12 times, 30 or 15 times.

E

You can reduce that if you know the documentation was done in a particular format, so that you know you can build tools and you know reusable components which can actually start so that we can actually read through and find out. Okay, you know these are the punctuation marks. These are the some of the headings right. So all those things it could, you know, figure out. So that was you know my experience.

E

And we did about you know 40, uh like four million Pages, we converted four million pages of different. You know books and different formats into a you know very specialized XML form.

A

Okay yeah. Thank you for the share with your experience, yeah.

A

Okay, so thank you for coming here. Yeah, we got very good feedback from you. I really appreciate it. Thank you. Thank.

B