replace remaining occurrences of www.lilypond.org with lilypond.org

Some occurrences of www.lilypond.org were overlooked in previous
patch for issue 5014. Command used:

git grep -l "@uref{http://www.lilypond.org/" | xargs sed -i "s|@uref{http://www.lilypond.org/|@uref{http://lilypond.org/|g"

diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi
index 365582e87f7a8beef00a6e437f67d7b005fba98a..9b13c25d53107f5696a528af18b04347f98a2639 100644 (file)
--- a/Documentation/contributor/regressions.itexi
+++ b/Documentation/contributor/regressions.itexi
@@ -506,7 +506,7 @@ code has been exercised by the tests.
 For tracking memory usage as part of this test, you will need
 GUILE CVS; especially the following patch:
 @smallexample
-@uref{http://www.lilypond.org/vc/old/gub.darcs/patches/guile-1.9-gcstats.patch}.
+@uref{http://lilypond.org/vc/old/gub.darcs/patches/guile-1.9-gcstats.patch}.
 @end smallexample
 
 @subheading Code coverage

diff --git a/Documentation/es/web/news.itexi b/Documentation/es/web/news.itexi
index 61d5b8d8913967d42c80aa2bd89f860927a662e2..4a9ba9de9fa051bf4b6bcb8880fe8a105ad17480 100644 (file)
--- a/Documentation/es/web/news.itexi
+++ b/Documentation/es/web/news.itexi
@@ -613,10 +613,10 @@ funcionalidades es coherente, que la documentación es correcta y
 que no se ha pasado por alto ningún problema importante.  Para la
 actualización de la sintaxis de sus archivos de entrada a la
 última versión, consulte
-@uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
+@uref{http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
 Updating files with convert-ly}.  Le rogamos que pruebe esta
 versión y nos informe de cualquier problema, véase
-@uref{http://www.lilypond.org/website/bug-reports.html, Informes
+@uref{http://lilypond.org/website/bug-reports.html, Informes
 de fallo}.
 
 @newsEnd
@@ -631,10 +631,10 @@ el conjunto de funcionalidades es coherente, que la documentación
 es correcta y que no se ha pasado por alto ningún problema
 importante.  Para la actualización de la sintaxis de sus archivos
 de entrada a la última versión, consulte
-@uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
+@uref{http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
 Updating files with convert-ly}.  Le rogamos que pruebe esta
 versión y nos informe de cualquier problema, véase
-@uref{http://www.lilypond.org/website/bug-reports.html, Informes
+@uref{http://lilypond.org/website/bug-reports.html, Informes
 de fallo}.
 
 @newsEnd
@@ -649,10 +649,10 @@ el conjunto de funcionalidades es coherente, que la documentación
 es correcta y que no se ha pasado por alto ningún problema
 importante.  Para la actualización de la sintaxis de sus archivos
 de entrada a la última versión, consulte
-@uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
+@uref{http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
 Updating files with convert-ly}.  Le rogamos que pruebe esta
 versión y nos informe de cualquier problema, véase
-@uref{http://www.lilypond.org/website/bug-reports.html, Informes
+@uref{http://lilypond.org/website/bug-reports.html, Informes
 de fallo}.
 
 

diff --git a/Documentation/web/news.itexi b/Documentation/web/news.itexi
index d5d907d0073c3fd719cf6b14e9093b98071ac3c1..20a91fa78020e3993e18c2b13e1ad09b2606d6ce 100644 (file)
--- a/Documentation/web/news.itexi
+++ b/Documentation/web/news.itexi
@@ -715,9 +715,9 @@ a potential final beta release for the upcoming stable release@tie{}2.18.  The
 developers believe this to be feature-complete, the
 documentation to be accurate, and no important issues to be
 overlooked.  For upgrading the syntax of your input files to the
-latest version, see @uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly, Updating files with convert-ly}.
+latest version, see @uref{http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly, Updating files with convert-ly}.
 Please test this release and report back any problems, see
-@uref{http://www.lilypond.org/website/bug-reports.html, Bug reports}.
+@uref{http://lilypond.org/website/bug-reports.html, Bug reports}.
 
 @newsEnd
 
@@ -729,9 +729,9 @@ a further beta release for the upcoming stable release@tie{}2.18.  The
 developers believe the release to be feature-complete, the
 documentation to be accurate, and no important issues to be
 overlooked.  For upgrading the syntax of your input files to the
-latest version, see @uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly, Updating files with convert-ly}.
+latest version, see @uref{http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly, Updating files with convert-ly}.
 Please test this release and report back any problems, see
-@uref{http://www.lilypond.org/website/bug-reports.html, Bug reports}.
+@uref{http://lilypond.org/website/bug-reports.html, Bug reports}.
 
 @newsEnd
 

diff --git a/input/regression/musicxml/00-Introduction.itexi b/input/regression/musicxml/00-Introduction.itexi
index a929697d19bc5bfc25e732366132cc057eb0cd23..3c995422f8414577c94c82a13c66a24fb0406454 100644 (file)
--- a/input/regression/musicxml/00-Introduction.itexi
+++ b/input/regression/musicxml/00-Introduction.itexi
@@ -25,7 +25,7 @@ This collection of MusicXML test files is distributed under the
 means that you can use the files for any purpose, as long as you leave the
 copyright notice (or the LICENSE file) intact.
 
-@heading Connection with @uref{http://www.lilypond.org/,LilyPond}
+@heading Connection with @uref{http://lilypond.org/,LilyPond}
 
 At the same time as providing a generic test suite for MusicXML document,
 this test suite also serves as proofs for the musicxml2ly script provided with