Hello, On 14 January 2013 12:52, Federico Bruni <[email protected]> wrote:
> 2013/1/14 Werner LEMBERG <[email protected]> > >> >> > So how can we improve the efficiency of our current translation work >> > force, and how can we make it easier for people to help in a way >> > that does not step on anybody's toes and actually leads to better >> > results? >> >> Yeah. Let's assume that I would like to quickly improve various >> places of the German translation (for example, just fixing a typo). >> What should I do? Directly committing to `staging' doesn't seem >> appropriate... >> >> >> Werner >> > > All the translation work should be made in the translation branch. > > git checkout -b translation origin/translation > > and push changes to translation. > > If you just fix a typo and don't update anything, _don't_ change the > committish in the document. > > Once a lot of checkins to translation have occurred, and someone decides it needs to be pushed to staging, does someone do a doc build first or what else happens? Is there something that we could add to patchy to help for example with testing any new translation builds - I have horsepower and time but not translation skills. James
_______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
