Doc: cleanup @file{}, take 2: remove all @/ escaping sequences.

[lilypond.git] / Documentation / contributor / issues.itexi

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index df1a6cb2bc371548fd99347b231be35178850004..2d496e830e79f9ba489902a06199232c0880685c 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -204,6 +204,11 @@ documentation available from:
 or ask the lilypond-user mailing list.
 @end example
 
+@item
+If the email mentions @qq{the latest git}, or any version number
+that has not yet been officially released, forward it to
+@code{lilypond-devel}.
+
 @item
 If a bug report is not in the form of a Tiny example, direct the
 user to resubmit the report with this response:
@@ -215,7 +220,6 @@ step 2 in our bug reporting guidelines:
   @uref{http://lilypond.org/website/bug-reports.html}
 @end example
 
-
 @item
 If anything is unclear, ask the user for more information.
 
@@ -606,7 +610,7 @@ Include output with the first applicable method:
 
 @item
 If the issue has a notation example which fits in one system,
-generate a small @file{bug@/.preview@/.png} file with:
+generate a small @file{bug.preview.png} file with:
 
 @example
 lilypond -dpreview bug.ly
@@ -614,7 +618,7 @@ lilypond -dpreview bug.ly
 
 @item
 If the issue has an example which requires more than one system
-(i.e. a spacing bug), generate a @file{bug@/.png} file with:
+(i.e. a spacing bug), generate a @file{bug.png} file with:
 
 @example
 lilypond --png bug.ly
@@ -622,7 +626,7 @@ lilypond --png bug.ly
 
 @item
 If the issue requires multi-page output, then generate a
-@file{bug@/.pdf} file with the normal:
+@file{bug.pdf} file with the normal:
 
 @example
 lilypond --png bug.ly