X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fcontributor%2Fdoc-work.itexi;h=e8d993703a8f9db8b6a66351afb299c28ff0422b;hb=512d405d07aba8742658902b105a94ebbd40c2dc;hp=cdf0e26f8d518de9487f8198bc53f7c3054ad0ff;hpb=2047ac3ecaefeface8ca66d8199590b39c317a1c;p=lilypond.git diff --git a/Documentation/contributor/doc-work.itexi b/Documentation/contributor/doc-work.itexi index cdf0e26f8d..e8d993703a 100644 --- a/Documentation/contributor/doc-work.itexi +++ b/Documentation/contributor/doc-work.itexi @@ -2003,11 +2003,6 @@ the changes it made with @command{git diff} before committing; if you don't do so, some @code{@@lilypond} snippets might be broken or make no sense in their context. -When you have updated texidocs in -@file{Documentation/@var{MY-LANGUAGE}/texidocs}, you can get these -changes into compiled snippets in @file{Documentation/snippets}, see -@q{General guidelines} in @ref{Adding and editing snippets}. - Finally, a command runs the three update processes above for all enabled languages (from @file{Documentation/}): @@ -2042,23 +2037,6 @@ by doing git rev-list HEAD |head -1 @end example -A special case is updating Snippet documentation strings in -@file{Documentation/@var{MY-LANGUAGE}/texidocs}. For these to be -correctly marked as up-to-date, first run @code{makelsr.py} as -explained in @ref{Adding and editing snippets}, and commit the -resulting compiled snippets left in @file{Documentation/snippets/}. -Say the SHA1 ID code of this commit is . Now edit again your -translated files in @file{Documentation/@var{MY-LANGUAGE}/texidocs} -adjusting the 40-digit committish that appears in the text to be ; -finally, commit these updated files. Not doing so would result in -changes made both to your updates and original snippets to -persistently appear in the check-translation output as if they were -out of sync. - -This two-phase mechanism avoids the (practically) unsolvable problem -of guessing what committish will have our update, and pretending to -put this very committish on the files in the same commit. - @c http://lists.gnu.org/archive/html/lilypond-devel/2009-01/msg00245.html @c contains a helper script which could be used to perform massive @c committish updates.