Update the CG about new mailing list and infrastructure for translations

diff --git a/Documentation/contributor/doc-translation-list.itexi b/Documentation/contributor/doc-translation-list.itexi
index 9184fede9f8edbb33e5ac399875d392987e34d0d..9ed969bec8d9ec8d8f924a62774ed9b0859b04f9 100644 (file)
--- a/Documentation/contributor/doc-translation-list.itexi
+++ b/Documentation/contributor/doc-translation-list.itexi
@@ -16,6 +16,8 @@ Priorities:
 Files marked with priority 3, 4 or 5 may be submitted individually.
 Word counts (excluding LilyPond snippets) are given for each file.
 
+FIXME: take into account the new web site integration in main sources.
+
 @example
 -1- Documentation index and Tutorial
 429   learning.tely

diff --git a/Documentation/contributor/doc-work.itexi b/Documentation/contributor/doc-work.itexi
index 08dd49f2fd336cfcafc21a16232da4ab9a131277..e485e274bd04e6a32c7f3ecf42f0804e4fe3b3e5 100644 (file)
--- a/Documentation/contributor/doc-work.itexi
+++ b/Documentation/contributor/doc-work.itexi
@@ -1065,6 +1065,15 @@ This also updates translated documentation.
 @node Translating the documentation
 @section Translating the documentation
 
+The mailing list @code{translations@@lilynet.net} is dedicated to
+LilyPond web site and documentation translation; on this list, you will
+get support from the Translations Meister and experimented translators,
+and we regularly discuss translations issues common to all languagues.
+All people interested in LilyPond translations are invited to subscribe
+to this list regardless of the amount of their contribution, by sending
+an email to @code{translations-request@@lilynet.net} with subject
+@code{subscribe} and an empty message body.
+
 @menu
 * Getting started with documentation translation::
 * Documentation translation details::
@@ -1104,12 +1113,12 @@ motivation and a suitable system, it can be very useful to build at
 least the documentation so that you can check the output yourself and
 more quickly; if you are interested, see @ref{Compiling from source}.
 
-@menu
-@end menu
 
 @node Which documentation can be translated
 @unnumberedsubsubsec Which documentation can be translated
 
+FIXME: take into account the new web site integration in main sources.
+
 The makefiles and scripts infrastructure currently supports translation
 of the following documentation:
 
@@ -1329,10 +1338,11 @@ and editing snippets}.
 names, file names and comments should be translated.
 
 Finally, please carefully apply every rule exposed in @ref{Texinfo
-introduction and usage policy}, and @ref{Documentation policy}.  If
-one of these rules conflicts with a rule specific to your language,
-please ask the Translation meister and/or the Documentation Editors on
-@email{lilypond-devel@@gnu.org}.
+introduction and usage policy}, and @ref{Documentation policy}.  If one
+of these rules conflicts with a rule specific to your language, please
+ask the Translation meister on @email{translations@@lilynet.net} list
+and/or the Documentation Editors on @email{lilypond-devel@@gnu.org}
+list.
 
 
 @node Translating the Notation Reference and Application Usage
@@ -1385,6 +1395,11 @@ revision of the translation.  To check a single file, cd into
 make CHECKED_FILES=@var{MY_LANGUAGE}/@var{manual}/@var{foo}.itely check-translation
 @end example
 
+@noindent
+In case this file has been renamed since you last updated the
+translation, you should specify both old and new file names,
+e.g. @code{CHECKED_FILES=@var{MY_LANGUAGE}/@{@var{manual},user@}/@var{foo}.itely}.
+
 To see only which files need to be updated, do
 
 @example

diff --git a/Documentation/contributor/git-starting.itexi b/Documentation/contributor/git-starting.itexi
index 1dad5879ddfc630c85ab4976088fb338346455a9..0a150d004935c951fa22093c7239bfe09f278f4e 100644 (file)
--- a/Documentation/contributor/git-starting.itexi
+++ b/Documentation/contributor/git-starting.itexi
@@ -42,6 +42,10 @@ repository by @ref{Updating the source code}.
 command-line version of Git 1.5 or higher.  Windows users should
 skip to @ref{Git on Windows}.}
 
+Some sections of this guide will redirect to specific Git man pages;
+however, if you think you need to understand more of Git, you might want
+to read the book @uref{http://progit.org/,Pro Git}.
+
 
 @node Git user configuration
 @subsection Git user configuration
@@ -241,24 +245,25 @@ If you added a file to the source code, you must add it to git
 with:
 
 @example
-git add FILENAME
+git add @var{FILENAME}
 @end example
 
 @noindent
 (and possibly modify the @file{GNUmakefile})
 
-These commands will produce one or more files named
-@file{0001-xyz}, @file{0002-abc}, etc. in the top directory of the
-git tree.  Send an email to @email{lilypond-devel@@gnu.org} with
-these files attached, and a developer will review and apply the
-patches to the main repository.
+These commands will produce one or more files named @file{0001-xyz},
+@file{0002-abc}, etc. in the top directory of the git tree.  Send an
+email to @email{lilypond-devel@@gnu.org} with these files attached, and
+a developer will review and apply the patches to the main repository.
+If your patch is some translation work, you may send it to
+@email{translations@@lilynet.net} instead.
 
 
 @node Committing directly
 @subsection Committing directly
 
-Most contributors do not have permission to commit directly.  If you
-do, make sure you have set up your name and email in @ref{Git user
+Most contributors do not have permission to commit directly.  If you do,
+make sure you have set up your name and email in @ref{Git user
 configuration}, then edit @file{.git/config}: change the line
 
 @example