Feature: Translation Progress #2033

Activity

1. stomar commented on Apr 22, 2019

   

   stomar

   on Apr 22, 2019

   Contributor

   More actions

   I do not see yet how this is supposed to work in practice. Using the commit hash would not be possible nor would it help.
2. yous commented on Apr 23, 2019

   

   yous

   on Apr 23, 2019

   Last edited by yous

   Member

   More actions

   This is how I understand:

   1. Let's say I translated "en/news/_posts/2019-04-23-move-to-git-from-svn.md" right after the merge of Announce Moving Ruby repository to Git #2050
   2. Then in the "ko/news/_posts/2019-04-23-move-to-git-from-svn.md", there would be either commit: 992af44 (the last commit of the pull request) or commit: e020291 (the merge commit)
   3. Then in master branch, someone updates the "en/news/_posts/2019-04-23-move-to-git-from-svn.md" (like cdade5d)
   4. After some time, translators run git diff 992af44 -- en/news/_posts/2019-04-23-move-to-git-from-svn.md (or using e020291) to see if there are updates, and then diff will show the content of cdade5d

   Edit: For the step 2, translators can use git log -- en/news/_posts/2019-04-23-move-to-git-from-svn.md to see the latest commit for that file. Right after the merge, it'll show 992af44.
3. stomar commented on Apr 27, 2019

   

   stomar

   on Apr 27, 2019

   Contributor

   More actions

   That probably could work (but relies heavily on the thoroughness of the translators).

   I misunderstood the proposed system, because the given example also added a commit field in the en file, which wouldn‘t work for a commit hash.