CG: updates to translation instructions

Also add link from Making patch to section about using Rietveld.

diff --git a/Documentation/contributor/doc-work.itexi b/Documentation/contributor/doc-work.itexi
index 5c4a9ef8f607328ccea9698ef05a6db0dcb16a7a..09b423778ef875024e290d5d2bd4a80c349f4238 100644 (file)
--- a/Documentation/contributor/doc-work.itexi
+++ b/Documentation/contributor/doc-work.itexi
@@ -1363,7 +1363,19 @@ for each untranslated node with something like
 @@untranslated
 @end example
 
-@noindent
+@warning{you do not have to translate the node name of a cross-reference
+to a node that you do not have translated.  If you do, you must define
+an @qq{empty} node like explained just above; this will produce a
+cross-reference with the translated node name in output, although the
+target node will still be in English.  On the opposite, if all
+cross-references that refer to an untranslated node use the node name in
+English, then you do not have to define such an @qq{empty} node, and the
+cross-reference text will appear in English in the output.  The choice
+between these two strategies implies its particular maintenance
+requirements and is left to the translators, although the opinion of the
+Translation meister leans towards not translating these
+cross-references.}
+
 Finally, press in Emacs @key{C-c C-u C-a} to update or generate
 menus. This process should be made easier in the future, when the helper
 script @command{texi-langutils.py} and the makefile target are updated.
@@ -1378,6 +1390,11 @@ through the Free Translation Project.
 Take care of using typographic rules for your language, especially in
 @file{macros.itexi}.
 
+If you wonder whether a word, phrase or larger piece of text should be
+translated, whether it is an argument of a Texinfo command or a small
+piece sandwiched between two Texinfo commands, try to track whether and
+where it appears in PDF and/or HTML output as visible text.  This piece
+of advice is especially useful for translating @file{macros.itexi}.
 
 Please keep verbatim copies of music snippets (in @code{@@lilypond}
 blocs).  However, some music snippets containing text that shows in

diff --git a/Documentation/contributor/git-starting.itexi b/Documentation/contributor/git-starting.itexi
index d84d8b3d33be612abbfdb98de15bdc9a14f11d24..4d903787d6340da7b49a027635a3e2544873eba8 100644 (file)
--- a/Documentation/contributor/git-starting.itexi
+++ b/Documentation/contributor/git-starting.itexi
@@ -287,6 +287,12 @@ If this command lists any @emph{Changed but not updated} files,
 you should do a @command{git commit}.  If it lists any
 @emph{Untracked files}, then you should do a @command{git add}.
 
+@seealso
+
+If your patch includes a significant amount of code, you may want to see
+@ref{Adding or modifying features}, especially @emph{Post patch for
+comments}.
+
 
 @node Committing directly
 @subsection Committing directly

diff --git a/Documentation/contributor/website-work.itexi b/Documentation/contributor/website-work.itexi
index e2073d15d9dfdc25a9054c8333faad42623c2126..3fe7f49f0cfbc51374e2d5e096286e474c898b5f 100644 (file)
--- a/Documentation/contributor/website-work.itexi
+++ b/Documentation/contributor/website-work.itexi
@@ -12,8 +12,8 @@
 @section Introduction to website work
 
 The website is @emph{not} written directly in HTML;
-instead, the source is texinfo, which is then generated into HTML,
-pdf, and info formats.  The sources are
+instead, the source is Texinfo, which is then generated into HTML,
+PDF, and Info formats.  The sources are
 
 @verbatim
 Documentation/web.texi
@@ -22,7 +22,7 @@ Documentation/web/*.texi
 
 Unless otherwise specified, follow the instructions and policies
 given in @ref{Documentation work}.  That chapter also contains a
-quick introduction to texinfo; consulting an external texinfo
+quick introduction to Texinfo; consulting an external Texinfo
 manual should be not necessary.
 
 @subheading Exceptions to the documentation policies
@@ -45,5 +45,5 @@ existing texinfo files.
 @node Translating the website
 @section Translating the website
 
-
-
+As it has much more audience, the website should be translated before
+the documentation; see @ref{Translating the documentation}.