From 94e40792498c41fbd987933cfd69b19ea37b26fa Mon Sep 17 00:00:00 2001 From: Jonas Hahnfeld Date: Wed, 18 Sep 2019 09:19:04 +0200 Subject: [PATCH] Replace code.google.com by SourceForge Google Code was shut down in early 2016 and the issues are now tracked at http://sourceforge.net/p/testlilyissues/issues/. There are a few remaining mentions of code.google.com: * Documentation/common-macros.itexi, in the macro bugfixes. This was used in old release announcements before v2.12.0. I think this should be left as-is. * Documentation/web/news-old.itexi, to reference bug reports in old release announcements. The links still work, so this can be left as-is. * scripts/auxiliar/make-countdown-announcement.sh: I guess there is a new script somewhere that works with SourceForge. Maybe this script can be deleted? --- Documentation/ca/web/community.itexi | 6 +++--- Documentation/contributor/source-code.itexi | 4 ++-- Documentation/cs/web/community.itexi | 2 +- Documentation/de/web/community.itexi | 4 ++-- Documentation/es/included/acknowledge.itexi | 4 ++-- Documentation/es/notation/editorial.itely | 4 ++-- Documentation/es/notation/spacing.itely | 2 +- Documentation/fr/notation/editorial.itely | 4 ++-- Documentation/fr/notation/spacing.itely | 2 +- Documentation/hu/web/community.itexi | 2 +- Documentation/included/acknowledge.itexi | 4 ++-- Documentation/it/notation/editorial.itely | 4 ++-- Documentation/it/notation/spacing.itely | 2 +- Documentation/ja/notation/spacing.itely | 2 +- Documentation/notation/editorial.itely | 4 ++-- Documentation/notation/spacing.itely | 2 +- Documentation/web/server/lilypond.org.htaccess | 1 - Documentation/zh/web/community.itexi | 6 +++--- input/regression/midi-grace-after-tie.ly | 2 +- scripts/auxiliar/doc-section.sh | 2 +- scripts/build/create-weblinks-itexi.py | 2 +- 21 files changed, 32 insertions(+), 33 deletions(-) diff --git a/Documentation/ca/web/community.itexi b/Documentation/ca/web/community.itexi index 706bd41224..bdde6fe4f0 100644 --- a/Documentation/ca/web/community.itexi +++ b/Documentation/ca/web/community.itexi @@ -407,7 +407,7 @@ sortida defectuosa, això és una fallada. Probablement ja coneixem aquesta fallada. Comproveu-ho aquí: @example -@uref{http://code.google.com/p/lilypond/issues/list} +@uref{http://sourceforge.net/p/testlilyissues/issues/} @end example @warning{Us preguem que @strong{NO} afegeixi informes de fallades @@ -897,13 +897,13 @@ que vulguin implicar-se en aquests projectes. Per descomptat, hi ha moltes més coses a millorar al LilyPond, entre elles algunes de molt petites. Hi ha una llista completa -@uref{http://code.google.com/p/lilypond/issues/list, aquí}. +@uref{http://sourceforge.net/p/testlilyissues/issues/, aquí}. @subheading Notes de adorn Arreglar problemes amb la sincronització de les notes d'adorn, junt a tota l'arquitectura subjacent (vegeu -@uref{http://code.google.com/p/lilypond/issues/detail?id=34, el +@uref{https://sourceforge.net/p/testlilyissues/issues/34/, el problema número 34 del nostre sistema de seguiment}). Les notes d'adorn confonen el sistema de comptabilització de temps del LilyPond perquè són com anar cap a darrere en el temps. Això diff --git a/Documentation/contributor/source-code.itexi b/Documentation/contributor/source-code.itexi index 5ba7f46430..51518ce144 100644 --- a/Documentation/contributor/source-code.itexi +++ b/Documentation/contributor/source-code.itexi @@ -1518,7 +1518,7 @@ The Patch Meister reviews the tracker periodically, to list patches which have been on review for at least 24 hours. The list is found at @smallexample -@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:patch%20patch=review&sort=modified+patch&colspec=ID%20Type%20Status%20Priority%20Owner%20Patch%20Summary%20Modified} +@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+_patch%3Areview} @end smallexample @item @@ -1591,7 +1591,7 @@ There is a single Patch Meister, and a number of Patch Helpers (rename this?). The list of known patches awaiting review is: @example -@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:patch&sort=patch} +@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+%28_patch%3Anew+OR+_patch%3Areview+OR+_patch%3Acountdown+OR+_patch%3Apush+OR+_patch%3Awaiting+OR+_patch%3Aabandoned+OR+_patch%3Aneeds_work%29} @end example diff --git a/Documentation/cs/web/community.itexi b/Documentation/cs/web/community.itexi index 4f4b1d4955..f4ca187272 100644 --- a/Documentation/cs/web/community.itexi +++ b/Documentation/cs/web/community.itexi @@ -345,7 +345,7 @@ chybnou sazbu not, potom je to ta chyba. Seznam se známými chybami je při sledování chyb Google: @example -@uref{http://code.google.com/p/lilypond/issues/list} +@uref{https://sourceforge.net/p/testlilyissues/issues/} @end example @warning{Sami, prosím, @strong{NEPŘIDÁVEJTE} nová hlášení chyb! diff --git a/Documentation/de/web/community.itexi b/Documentation/de/web/community.itexi index 80cf62264f..2cd9c90bda 100644 --- a/Documentation/de/web/community.itexi +++ b/Documentation/de/web/community.itexi @@ -417,7 +417,7 @@ handelt es sich um einen Fehler. Vielleicht ist der Fehler schon bekannt. Prüfen Sie hier: @example -@uref{http://code.google.com/p/lilypond/issues/list} +@uref{https://sourceforge.net/p/testlilyissues/issues/} @end example @warning{Bitte fügen Sie @strong{NICHT} selber neue Fehlerberichte @@ -909,7 +909,7 @@ verbessern und das LilyPond Entwicklerteam wird jederzeit jede/n gern unterstüt die/der Aufgaben wie jene unten aufgeführten angehen möchte. Eine vollständige Liste aller aktuell offenen Punkte findet sich -@uref{http://code.google.com/p/lilypond/issues/list, hier}. +@uref{https://sourceforge.net/p/testlilyissues/issues/, hier}. @divEnd diff --git a/Documentation/es/included/acknowledge.itexi b/Documentation/es/included/acknowledge.itexi index 08939eadf1..6f63370203 100644 --- a/Documentation/es/included/acknowledge.itexi +++ b/Documentation/es/included/acknowledge.itexi @@ -34,8 +34,8 @@ Linuxaudio/VirgniaTech Descargas de los lanzamientos @item -Google Code -@uref{http://code.google.com/} +SourceForge +@uref{https://sourceforge.net/} Seguimiento de las incidencias @item diff --git a/Documentation/es/notation/editorial.itely b/Documentation/es/notation/editorial.itely index f407271551..2a85735a01 100644 --- a/Documentation/es/notation/editorial.itely +++ b/Documentation/es/notation/editorial.itely @@ -318,8 +318,8 @@ Referencia de funcionamiento interno: @rinternals{font-interface}. @c The two issues mentioned below: -@c http://code.google.com/p/lilypond/issues/detail?id=3987 -@c http://code.google.com/p/lilypond/issues/detail?id=3990 +@c https://sourceforge.net/p/testlilyissues/issues/3987/ +@c https://sourceforge.net/p/testlilyissues/issues/3990/ @knownissues Actualmente hay dos falos del programa que impiden un correcto espaciado horizontal al usar @code{\magnifyMusic}. Solamente diff --git a/Documentation/es/notation/spacing.itely b/Documentation/es/notation/spacing.itely index afc2e7852a..a912de6adf 100644 --- a/Documentation/es/notation/spacing.itely +++ b/Documentation/es/notation/spacing.itely @@ -22,7 +22,7 @@ Negative numbers are allowed: Clarify -http://code.google.com/p/lilypond/issues/detail?id=68 +https://sourceforge.net/p/testlilyissues/issues/68/ @end ignore diff --git a/Documentation/fr/notation/editorial.itely b/Documentation/fr/notation/editorial.itely index 3bb232a875..c436c34676 100644 --- a/Documentation/fr/notation/editorial.itely +++ b/Documentation/fr/notation/editorial.itely @@ -319,8 +319,8 @@ Référence des propriétés internes : @rinternals{font-interface}. @c The two issues mentioned below: -@c http://code.google.com/p/lilypond/issues/detail?id=3987 -@c http://code.google.com/p/lilypond/issues/detail?id=3990 +@c https://sourceforge.net/p/testlilyissues/issues/3987/ +@c https://sourceforge.net/p/testlilyissues/issues/3990/ @knownissues Deux bogues actuellement répertoriés font obstacle à un espacement horizontal correct avec @code{\magnifyMusic}. La seule façon de les diff --git a/Documentation/fr/notation/spacing.itely b/Documentation/fr/notation/spacing.itely index 187765e01d..b7c3865637 100644 --- a/Documentation/fr/notation/spacing.itely +++ b/Documentation/fr/notation/spacing.itely @@ -24,7 +24,7 @@ Negative numbers are allowed: Clarify -http://code.google.com/p/lilypond/issues/detail?id=68 +https://sourceforge.net/p/testlilyissues/issues/68/ @end ignore diff --git a/Documentation/hu/web/community.itexi b/Documentation/hu/web/community.itexi index a97ab3da4f..ff99dc4327 100644 --- a/Documentation/hu/web/community.itexi +++ b/Documentation/hu/web/community.itexi @@ -322,7 +322,7 @@ akkor hibával állunk szemben. Az ismert hibák listája a következő oldalon található: @example -@uref{http://code.google.com/p/lilypond/issues/list} +@uref{https://sourceforge.net/p/testlilyissues/issues/} @end example @warning{Ide @strong{TILOS} új hibákat bejelenteni, a hibajelentés a diff --git a/Documentation/included/acknowledge.itexi b/Documentation/included/acknowledge.itexi index c7fd2f3446..0432832d24 100644 --- a/Documentation/included/acknowledge.itexi +++ b/Documentation/included/acknowledge.itexi @@ -29,8 +29,8 @@ Linuxaudio/VirgniaTech Release downloads @item -Google Code -@uref{http://code.google.com/} +SourceForge +@uref{https://sourceforge.net/} Issue tracker @item diff --git a/Documentation/it/notation/editorial.itely b/Documentation/it/notation/editorial.itely index 46eb6f8ad2..e0ed1b2841 100644 --- a/Documentation/it/notation/editorial.itely +++ b/Documentation/it/notation/editorial.itely @@ -305,8 +305,8 @@ Guida al funzionamento interno: @rinternals{font-interface}. @c The two issues mentioned below: -@c http://code.google.com/p/lilypond/issues/detail?id=3987 -@c http://code.google.com/p/lilypond/issues/detail?id=3990 +@c https://sourceforge.net/p/testlilyissues/issues/3987/ +@c https://sourceforge.net/p/testlilyissues/issues/3990/ @knownissues Attualmente ci sono due bug che impediscono una corretta spaziatura orizzontale quando si usa @code{\magnifyMusic}. C'è un solo modo diff --git a/Documentation/it/notation/spacing.itely b/Documentation/it/notation/spacing.itely index 0c0b230dc3..b305f24d46 100644 --- a/Documentation/it/notation/spacing.itely +++ b/Documentation/it/notation/spacing.itely @@ -25,7 +25,7 @@ Negative numbers are allowed: Clarify -http://code.google.com/p/lilypond/issues/detail?id=68 +https://sourceforge.net/p/testlilyissues/issues/68/ @end ignore diff --git a/Documentation/ja/notation/spacing.itely b/Documentation/ja/notation/spacing.itely index 156480ee0d..97d61423ae 100644 --- a/Documentation/ja/notation/spacing.itely +++ b/Documentation/ja/notation/spacing.itely @@ -51,7 +51,7 @@ knowledge to fix this? Clarify -http://code.google.com/p/lilypond/issues/detail?id=68 +https://sourceforge.net/p/testlilyissues/issues/68/ @end ignore diff --git a/Documentation/notation/editorial.itely b/Documentation/notation/editorial.itely index b2bf47628b..f4b851c492 100644 --- a/Documentation/notation/editorial.itely +++ b/Documentation/notation/editorial.itely @@ -294,8 +294,8 @@ Internals Reference: @rinternals{font-interface}. @c The two issues mentioned below: -@c http://code.google.com/p/lilypond/issues/detail?id=3987 -@c http://code.google.com/p/lilypond/issues/detail?id=3990 +@c https://sourceforge.net/p/testlilyissues/issues/3987/ +@c https://sourceforge.net/p/testlilyissues/issues/3990/ @knownissues There are currently two bugs that are preventing proper horizontal spacing when using @code{\magnifyMusic}. There is only one diff --git a/Documentation/notation/spacing.itely b/Documentation/notation/spacing.itely index 6a5187c9ca..07a810d1ce 100644 --- a/Documentation/notation/spacing.itely +++ b/Documentation/notation/spacing.itely @@ -22,7 +22,7 @@ Negative numbers are allowed: Clarify -http://code.google.com/p/lilypond/issues/detail?id=68 +https://sourceforge.net/p/testlilyissues/issues/68/ @end ignore diff --git a/Documentation/web/server/lilypond.org.htaccess b/Documentation/web/server/lilypond.org.htaccess index 9a11bb1859..f92a0fe4f3 100644 --- a/Documentation/web/server/lilypond.org.htaccess +++ b/Documentation/web/server/lilypond.org.htaccess @@ -40,7 +40,6 @@ RedirectMatch ^/documentation/$ /doc # RedirectMatch ^/documentation$ /doc # RedirectMatch ^/bugs /bug-reports -#RedirectMatch ^/bugs http://code.google.com/p/lilypond/issues/list # the new website already has an /authors #RedirectMatch ^/authors /doc/Documentation/topdocs/AUTHORS RedirectMatch ^/stable /doc/stable diff --git a/Documentation/zh/web/community.itexi b/Documentation/zh/web/community.itexi index 17a5e0fd24..924aaeb82f 100644 --- a/Documentation/zh/web/community.itexi +++ b/Documentation/zh/web/community.itexi @@ -397,7 +397,7 @@ then that is a bug. We may already know about this bug. Check here: @example -@uref{http://code.google.com/p/lilypond/issues/list} +@uref{https://sourceforge.net/p/testlilyissues/issues/} @end example @warning{Please @strong{DO NOT} add bug reports directly to the @@ -870,13 +870,13 @@ to tackle these projects. Of course, there are many more things to improve in LilyPond, including very small ones. A full list of all known issues can be found -@uref{http://code.google.com/p/lilypond/issues/list, here}. +@uref{https://sourceforge.net/p/testlilyissues/issues/, here}. @subheading Grace notes Fix problems with synchronization of grace notes, together with all underlying architecture (see -@uref{http://code.google.com/p/lilypond/issues/detail?id=34, +@uref{https://sourceforge.net/p/testlilyissues/issues/34/, issue 34 in our tracker}). Grace notes are confusing to LilyPond's timing because they're like going back in time. This causes weird effects, especially when one staff has a grace note and the other diff --git a/input/regression/midi-grace-after-tie.ly b/input/regression/midi-grace-after-tie.ly index ead10bf793..dce5312277 100644 --- a/input/regression/midi-grace-after-tie.ly +++ b/input/regression/midi-grace-after-tie.ly @@ -3,7 +3,7 @@ texidoc = "Tied notes sound as one note in MIDI. Grace notes following a tied note shorten the resulting single note in MIDI." - % https://code.google.com/p/lilypond/issues/detail?id=3091 + % https://sourceforge.net/p/testlilyissues/issues/3091/ } \version "2.19.21" \score { diff --git a/scripts/auxiliar/doc-section.sh b/scripts/auxiliar/doc-section.sh index 963476840a..b8cb37b794 100755 --- a/scripts/auxiliar/doc-section.sh +++ b/scripts/auxiliar/doc-section.sh @@ -16,7 +16,7 @@ # At the end of the run, the user is prompted whether or not to # remove the generated files. # -# According to http://code.google.com/p/lilypond/issues/detail?id=1236 +# According to https://sourceforge.net/p/testlilyissues/issues/1236/ # the location of the lilypond git tree is taken from $LILYPOND_GIT # if specified, otherwise it is auto-detected. # diff --git a/scripts/build/create-weblinks-itexi.py b/scripts/build/create-weblinks-itexi.py index 2d190e8224..825ae2b156 100644 --- a/scripts/build/create-weblinks-itexi.py +++ b/scripts/build/create-weblinks-itexi.py @@ -10,7 +10,7 @@ import os import glob ### translation data -- shouldn't be here; see issue -### http://code.google.com/p/lilypond/issues/detail?id=1050 +### https://sourceforge.net/p/testlilyissues/issues/1050/ import langdefs # GUB only has python 2.4 !!! -- 2.23.0