Need translation workflow?

[sotayamashita]

In open source community, translation is important but it is very difficult so we are creating localization tool to help translated ones updated as well. 💯 It's name is GitLocalize. The reason that we built it was translation problem of Node.js.

It have been used in "GitHub - vuejs/vue-ssr-docs, GitLocalize - vuejs/vue-ssr-docs" So I think it is a time to try our service in Nuxt.js community. We provide these features below:

• Have a split view to make people translate
• When original one is updated, we will notify translators
• Translation flow looks like a GitHub flow:
  1. Sync GitHub and GitLocalize
  2. Translate
  3. Create a review request such as Pull Request of GitHub
  4. GitLocalize will create pull request to GitHub repository
  5. And merge. That's it ✨

Looking forward to hearing your thoughts 😄

cc:/ @gbezyuk, @inouetakuya, @DiyLecko, @mamboer, @chuyik

[sotayamashita]

@alexchopin Wow. I appreciate you creating the repository on GitLocalize!

we are now verifying your translation files and creating translation flow note for users who wants to join localization.

[sotayamashita]

@alexchopin We found issues for parsing and we am figuring it out now. It will be solved soon 🙇

[alexchopin]

@sotayamashita Ok, Thanks.

[gbezyuk]

ping @Alex-Sokolov

[sotayamashita]

@gbezyuk

I look into Translation Gang and it is rad. I have a question about it.
Does Translation Gang help only people who want to translate something into Russian?

[inouetakuya]

Cool !!!

[gbezyuk]

@sotayamashita nope, it's supposed to be totally international.

[atinux]

Thank you @sotayamashita

GitLocalize is a great project 👍

[atinux]

Hi @sotayamashita

Is there a way for our team to update the English files directly from GitLocalize?

[sotayamashita]

@atinux You can not edit English files directly from GitLocalize because it is localization tool. Do you
want to edit directly? and why?

[atinux]

Because I like the editor of GitLocalize @sotayamashita :)

[sotayamashita]

@atinux

Because I like the editor of GitLocalize @sotayamashita :)

Could you tell me more specifically? I created a few question blow:

• Why do you like GitLocalize editor? (Preview?, Communication? )
• What editor do you use to write markdown file or docs?

Thanks in advance 🙇

[sotayamashita]

@chuyik

I don't know if @sotayamashita you are the creator/developer of GitLocalize

I am an engineer of it. 💻
I appreciate you giving us feedback. We are trying to fix it. 💪

Wishlist

1. Auto-resize editor box (<textarea />)

I will fix soon

2. Allow to revert changes

I understand. I have a question. You want to see all history of each sentence?

3. Batch PR

It's little difficult now but I know the why you want it.

[chikathreesix]

Hi @chuyik

I am Ryo, also a creator of GitLocalize.
Thank you so much for your feedback!

Usability issues

1. Have to edit the raw html rather than markdown. As a translator, we should only edit the markdown and leaves the transformation job to the converter.

I am fixing it by showing the html tags as more abstracted format so that no need to take care of the details of the tag.

2. Incorrect highlight. Maybe there're some bugs when converting the existing content on Github.

Looking into it now and will be fixed soon

3. Misplaced content. Some translation segment are linked wrong, just screwed.

I fixed the linking on the file. Integrating with a project which already has translated resources is a bit tricky since the system needs to make sure that the translated and the original have exactly the same structure. I will look over all files to make sure nothing screwed and I might need to send some pull requests to fix the conflicts.

4. Failed to link the segments.

This is also related to 3. It failed because the translated file and the original file have a different structure. Let me send a pull request for the Chinese file in accordance with the English one.

Thanks again for giving us great feedbacks!