Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need translation workflow? #125

Closed
sotayamashita opened this issue May 29, 2017 · 16 comments

Comments

@sotayamashita
Copy link
Contributor

commented May 29, 2017

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

This feature request is available on Nuxt.js community (#c27)
@sotayamashita

This comment has been minimized.

Copy link
Contributor Author

commented May 29, 2017

@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

This comment has been minimized.

Copy link
Contributor Author

commented May 29, 2017

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

@alexchopin

This comment has been minimized.

Copy link
Member

commented May 29, 2017

@sotayamashita Ok, Thanks.

@gbezyuk

This comment has been minimized.

Copy link
Contributor

commented May 29, 2017

@sotayamashita

This comment has been minimized.

Copy link
Contributor Author

commented May 29, 2017

@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

This comment has been minimized.

Copy link
Collaborator

commented May 30, 2017

Cool !!!

@gbezyuk

This comment has been minimized.

Copy link
Contributor

commented May 30, 2017

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

@Atinux

This comment has been minimized.

Copy link
Member

commented May 30, 2017

Thank you @sotayamashita

GitLocalize is a great project 馃憤

@Atinux

This comment has been minimized.

Copy link
Member

commented May 30, 2017

Hi @sotayamashita

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

@sotayamashita

This comment has been minimized.

Copy link
Contributor Author

commented May 30, 2017

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

@Atinux

This comment has been minimized.

Copy link
Member

commented May 31, 2017

Because I like the editor of GitLocalize @sotayamashita :)

@sotayamashita

This comment has been minimized.

Copy link
Contributor Author

commented Jun 1, 2017

@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 馃檱

@chuyik

This comment has been minimized.

Copy link
Contributor

commented Jun 1, 2017

@sotayamashita

GitLocalize is a great platform to organize and keep updating the translation.
But after looking into GitLocalize, I found that there are some serious problems.
I don't know if @sotayamashita you are the creator/developer of GitLocalize, and I wanna point out some here:

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.
    image

  2. Incorrect highlight. Maybe there're some bugs when converting the existing content on Github.
    image
    Reproduce url: https://gitlocalize.com/repo/100/zh/en/guide/assets.md

  3. Misplaced content. Some translation segment are linked wrong, just screwed.
    image
    Reproduce url: https://gitlocalize.com/repo/100/zh/en/api/configuration-build.md

  4. Failed to link the segments.
    image
    Reproduce url: https://gitlocalize.com/repo/100/zh/en/api/configuration-dev.md


Besides the issues mentioned above, I also suggest some features that may help improve the experience:

Wishlist

  1. Auto-resize editor box (<textarea />)
    It's very crucial to a long paragraph.

  2. Allow to revert changes
    This is a good-to-have feature, especially for someone who want the previous translation back.

  3. Batch PR
    We should be allowed to send a PR that contains multiple markdown files, and review them once.

After all, I love GitLocalize, but yet to be mature.

@sotayamashita

This comment has been minimized.

Copy link
Contributor Author

commented Jun 1, 2017

@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

  1. Allow to revert changes

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

  1. Batch PR

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

@chikathreesix

This comment has been minimized.

Copy link
Contributor

commented Jun 2, 2017

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.

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

Looking into it now and will be fixed soon

  1. 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.

  1. 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!

@chuyik

This comment has been minimized.

Copy link
Contributor

commented Jun 2, 2017

@sotayamashita @chikathreesix
I didn't expect such quick responses from you guys 馃憤 , you are welcome.

You want to see all history of each sentence?

Hey Sota, again this is good to have, but of course I will want it.
I think it's common to revise the texts back and forth during the translation.
But I don't mean a full history of it, maybe just a UNDO can help. Imagine when I remove a sentence with some mistake, and the texts are gone along with the submit button hit.

I love to interview new stuff, but I don't know if it's cool to keep the conversation here since it's irrelevant to nuxt/docs. So if any issues found I may use email or any other tools better for feedback.

@Atinux Atinux closed this Aug 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can鈥檛 perform that action at this time.