[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 2721 di

The following sentence I wrote in the lilypond-translation-guide.en.rst file is wrong:

• @ref are links to nodes within current manual. You can leave them untranslated, because they will
be automatically translated, because of @translationof.

Not translated @ref work fine only on html output, while links are broken in PDF.
So they should be translated, just like the crossreferences. In fact spanish and french manuals have them translated.

[issues:#2721] CG 3.2.1: Improve and update instructions on how to track the translation branch

Status: Accepted
Created: Tue Aug 07, 2012 02:52 PM UTC by Anonymous
Last Updated: Thu Jul 10, 2014 05:01 AM UTC
Owner: nobody

Originally created by: *anonymous

Originally created by: address@hidden
Originally owned by: address@hidden

Federico Bruni reported here:
http://lists.gnu.org/archive/html/bug-lilypond/2012-08/msg00006.html

http://old.nabble.com/CG-3.2.1%3A-missing-instructions-on-how-to-track-the-translation-branch-to34248557.html

http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/35904

Quoting the original post:
--------------------------
Hi

in CG 3.2.1, Initializing a repository
the recommended way to download the source code is using clone:

git clone git://git.sv.gnu.org/lilypond.git ~/lilypond-git

git clone sets only the master branch.
Previously the doc contained complex git commands but there were full instructions for both developers and translators. Now (new) translators are missing some information.

I think that all translators should know is these two commands:

git branch --track translation origin/translation
git checkout translation

On a side note, 'git clone' sees _all_ the remote branches.
I think that it would be nice to say also how to clean all the remote branches that one will never use. You may say it's a nitpick, yes it is :-) but 'git branch -a' is a bit messy.

I know how to remove them one by one, for example:
git branch -d -r origin/stable/0.0

but obviously this is not the way to go.

Wildcards unfortunately don't work:

git branch -d -r origin/stable/*
error: remote branch 'origin/stable/*' not found.

And this doesn't work neither:
git branch -a | grep dev | xargs git branch -d

-------------------------
End of quote

In a subsequent post Federico suggested the following documentation change:

This paragraph is marked as obsolete:
http://lilypond.org/doc/v2.15/Documentation/contributor/downloading-remote-branches

So if you want to open an issue, here's a quick and dirty description:

We currently recommend in 3.2.1 to use 'git clone' to download the repository. This command downloads all the remote branches and makes the checkout of the master branch.
3.2.4, Downloading individual branch, is obsolete and should be removed.

What we should keep are the instructions on how to start working on a new branch, different from master, that is:

git checkout -b branch origin/branch

This means that translators should use:

git checkout translation origin/translation

Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

From:	Auto mailings of changes to Lily Issues
Subject:	[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 2721 discussion
Date:	Sun, 16 Apr 2017 08:00:42 +0000