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 @propensive1 reply 0 retweets 1 like
Replying to @dwijnand
Doesn't sound like it was a disaster. The merge conflicts corresponding to a need for a new translation is what I hoped for. I think I'm missing a convenient way to see all new content which would need translating. Maybe a merge hook.
11:58 PM - 30 Oct 2019
0 replies
0 retweets
0 likes
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.