Patch for the freedesktop wiki

Thanks for applying this by hand - I don't have access to the old cgit
:)

  Federico

From 00afc2e5f4cb708c09303361f97c6b9a8049bf22 Mon Sep 17 00:00:00 2001
From: Federico Mena Quintero <federico@gnome.org>
Date: Wed, 28 Sep 2022 11:19:15 -0500
Subject: [PATCH] Fix links that went to git.gnome.org / developer.gnome.org

git.gnome.org -> gitlab.gnome.org/GNOME

developer.gnome.org -> API references for the relevant modules are now
generated as GitLab pages.
Message-Id: <7118ff51a13024cf252fab896f5adb4a58cf3c0d.camel@gmail.com>

2 files changed, 7 insertions, 7 deletions

diff --git a/Accessibility.mdwn b/Accessibility.mdwn
index e178f282..28123bdb 100644
--- a/Accessibility.mdwn
+++ b/Accessibility.mdwn
@@ -68,8 +68,8 @@ A [[Accessibility/Walkthrough/]] documents the RPC and function calls details.
 
 [[Accessibility/MakingWidgetAccessible]] documents a brief summary how to add accessibility support
 
-* GTK2/GTK3: good support, through [[atk|https://git.gnome.org/atk]] ([[documentation|https://developer.gnome.org/atk/]]), and atk-bridge from [[at-spi2-atk|https://git.gnome.org/at-spi2-atk/]]
-* GTK4: drops the use of atk, to directly talk at-spi, see [[Accessibility/Gtk4atspi]] for an instance
+* GTK2/GTK3: good support, through [[atk|https://gitlab.gnome.org/GNOME/at-spi2-core/-/tree/main/atk]] ([[documentation|https://gnome.pages.gitlab.gnome.org/at-spi2-core/atk/]]), and [[atk-bridge|https://gitlab.gnome.org/GNOME/at-spi2-core/-/tree/main/atk-adaptor]].
+* GTK4: drops the use of atk, to directly talk at-spi, see [[Accessibility/Gtk4atspi]] for an instance, or the [[GTK4 documentation on accessibility|https://docs.gtk.org/gtk4/section-accessibility.html]].
 * Qt5: improving, [[integrated in Qt5|http://doc.qt.io/qt-5/accessible.html]]
 * Qt4: only preliminary support, through [[qt-at-spi|https://community.kde.org/Accessibility/qt-atspi]]
 * wxWidgets: gtk-based widgets inherit gtk accessibility, wxWidgets-specific widgets have accessibility support on Windows, but missing a bridge on Linux, see [[https://www.wxwidgets.org/docs/tutorials/accessibility/]]
@@ -83,7 +83,7 @@ Gnome provides an [[Accessibility development guide|https://developer.gnome.org/
 
 For ATK, there is [[a best ATK practices guide|https://wiki.gnome.org/Accessibility/ATK/BestPractices]] , and a minimal example of extending a base atk implementation is the GtkScaleAccessible class, based on GtkRangeAccessible, see gtk/gtk/a11y/gtkscaleaccessible.[ch]
 
-For adding accessibility support to a custom-made widget, the [[evince implementation|https://git.gnome.org/browse/evince/tree/libview/ev-view-accessible.c#n71]] can be used as an example.
+For adding accessibility support to a custom-made widget, the [[evince implementation|https://gitlab.gnome.org/GNOME/evince/-/blob/main/libview/ev-view-accessible.c#n71]] can be used as an example.
 
 For Qt5, there is [[a guide for QWidget|http://doc.qt.io/qt-5/accessible-qwidget.html]] and [[a guide for Qt Quick|http://doc.qt.io/qt-5/accessible-qtquick.html]]
 
diff --git a/Accessibility/AT-SPI2.mdwn b/Accessibility/AT-SPI2.mdwn
index 5be807ac..9afa3cd9 100644
--- a/Accessibility/AT-SPI2.mdwn
+++ b/Accessibility/AT-SPI2.mdwn
@@ -6,21 +6,21 @@ Formal information is available on
 [[http://www.linuxfoundation.org/collaborate/workgroups/accessibility/atkat-spiat-spiond-bus]], [[https://wiki.linuxfoundation.org/accessibility/start]]
 
 A C binding library for the client side, libatspi, is available, and its documentation provides details on how At-Spi works
-[[libatspi API|https://developer.gnome.org/libatspi/stable/]]
+[[libatspi API|https://gnome.pages.gitlab.gnome.org/at-spi2-core/libatspi/]]
 
 The core that defines the protocol and starts the dbus accessibility bus is [[at-spi2-core|https://github.com/GNOME/at-spi2-core]] , the formal definition of RPCs is available as xml files in at-spi2-core/xml/
 
 The protocol essentially consists in dbus RPCs and notifications. For each application (seen as a dbus sender), its tree of widgets is represented as a tree of dbus paths.
 
 The server side, implemented in atk and at-spi2-atk, is basically the server implementation for all the RPC calls that one would make with the client-side library:
-[[atk API|https://developer.gnome.org/atk/unstable/]], and [[KDE atk overview|https://accessibility.kde.org/developer/atk.php]]
+[[atk API|https://gnome.pages.gitlab.gnome.org/at-spi2-core/atk/]], and [[KDE atk overview|https://accessibility.kde.org/developer/atk.php]]
 
 A [[Accessibility/Walkthrough/]] documents the RPC and function calls details.
 
 There are recommandation for applications to be accessible:
 [[https://wiki.gnome.org/Accessibility/ATK/BestPractices]]
 
-Convenient python bindings are available for screen readers: [[pyatspi2|https://git.gnome.org/pyatspi2]] , the documentation is available through <tt>pydoc pyatspi</tt>, <tt>pydoc pyatspi.text</tt>, etc. , a [[example of playing with it|PyAtSpi2Example]] is available, and is probably the recommended way to explore At-Spi from the client side.
+Convenient python bindings are available for screen readers: [[pyatspi2|https://gitlab.gnome.org/GNOME/pyatspi2]] , the documentation is available through <tt>pydoc pyatspi</tt>, <tt>pydoc pyatspi.text</tt>, etc. , a [[example of playing with it|PyAtSpi2Example]] is available, and is probably the recommended way to explore At-Spi from the client side.
 
 Getting it started by hand (normally done by the Desktop Environment session manager):
 
@@ -61,7 +61,7 @@ Getting it started by hand (normally done by the Desktop Environment session man
         $ source env.sh
         $ make check
 
-[[Accerciser|https://git.gnome.org/accerciser]] to test the availability of the content
+[[Accerciser|https://gitlab.gnome.org/GNOME/accerciser]] to test the availability of the content
 
 ***