If I had a Git repo containing text, and wanted to maintain separate branches for different language versions of that same text, is there a good workflow/process which would require any change to the main branch to be reviewed (i.e. translated) when it's merged to another branch?
-
Show this thread
-
Typically the main branch would be English, and everything else would follow from that. A French (say) translator would want to see the EN -> EN' diff to work out what corresponding FR -> FR' change to make in their branch.
1 reply 0 retweets 1 likeShow this thread -
Is this even a good idea? (Regardless of whether it is or not, I'd be interested to hear answers to the first question!)
3 replies 0 retweets 1 likeShow this thread -
Replying to @propensive
A translation is hardly ever 1-to-1, also in the sense that a change in the original material may resultv in changing the translation all over the place. Usually it's better to wait with the translation for the release of the original and then do it for the whole text at once.
1 reply 0 retweets 0 likes
I'm fixing that exact problem in another way... ;)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.