Convert external links to markdown syntax

This commit is contained in:
Matthias Clasen 2014-02-05 21:23:28 -05:00
parent 0cc20b7e0b
commit cb588d4532
45 changed files with 170 additions and 147 deletions

View File

@ -981,9 +981,8 @@ g_app_launch_context_get_display (GAppLaunchContext *context,
* Initiates startup notification for the application and returns the * Initiates startup notification for the application and returns the
* `DESKTOP_STARTUP_ID` for the launched operation, if supported. * `DESKTOP_STARTUP_ID` for the launched operation, if supported.
* *
* Startup notification IDs are defined in the <ulink * Startup notification IDs are defined in the
* url="http://standards.freedesktop.org/startup-notification-spec/startup-notification-latest.txt"> * [FreeDesktop.Org Startup Notifications standard](http://standards.freedesktop.org/startup-notification-spec/startup-notification-latest.txt").
* FreeDesktop.Org Startup Notifications standard</ulink>.
* *
* Returns: a startup notification ID for the application, or %NULL if * Returns: a startup notification ID for the application, or %NULL if
* not supported. * not supported.

View File

@ -89,7 +89,7 @@
* *
* If used, the expected form of an application identifier is very close * If used, the expected form of an application identifier is very close
* to that of of a * to that of of a
* <ulink url="http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names-interface">DBus bus name</ulink>. * [DBus bus name](http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names-interface).
* Examples include: "com.example.MyApp", "org.example.internal-apps.Calculator". * Examples include: "com.example.MyApp", "org.example.internal-apps.Calculator".
* For details on valid application identifiers, see g_application_id_is_valid(). * For details on valid application identifiers, see g_application_id_is_valid().
* *

View File

@ -102,7 +102,8 @@
* return 0; * return 0;
* } * }
* ]| * ]|
* The complete example can be found here: <ulink url="https://git.gnome.org/browse/glib/tree/gio/tests/gapplication-example-cmdline.c">gapplication-example-cmdline.c</ulink> * The complete example can be found here:
* [gapplication-example-cmdline.c](https://git.gnome.org/browse/glib/tree/gio/tests/gapplication-example-cmdline.c)
* *
* In more complicated cases, the handling of the comandline can be * In more complicated cases, the handling of the comandline can be
* split between the launcher and the primary instance. * split between the launcher and the primary instance.
@ -152,7 +153,8 @@
* options are passed to the #GApplication::command-line handler * options are passed to the #GApplication::command-line handler
* which runs in the primary instance. * which runs in the primary instance.
* *
* The complete example can be found here: <ulink url="https://git.gnome.org/browse/glib/tree/gio/tests/gapplication-example-cmdline2.c">gapplication-example-cmdline2.c</ulink> * The complete example can be found here:
* [gapplication-example-cmdline2.c](https://git.gnome.org/browse/glib/tree/gio/tests/gapplication-example-cmdline2.c)
* *
* If handling the commandline requires a lot of work, it may * If handling the commandline requires a lot of work, it may
* be better to defer it. * be better to defer it.
@ -193,7 +195,8 @@
* later (in this example, in an idle). Note that it is necessary to * later (in this example, in an idle). Note that it is necessary to
* hold the application until you are done with the commandline. * hold the application until you are done with the commandline.
* *
* The complete example can be found here: <ulink url="https://git.gnome.org/browse/glib/tree/gio/tests/gapplication-example-cmdline3.c">gapplication-example-cmdline3.c</ulink> * The complete example can be found here:
* [gapplication-example-cmdline3.c](https://git.gnome.org/browse/glib/tree/gio/tests/gapplication-example-cmdline3.c)
*/ */
/** /**

View File

@ -40,7 +40,9 @@
* @include: gio/gio.h * @include: gio/gio.h
* *
* A content type is a platform specific string that defines the type * A content type is a platform specific string that defines the type
* of a file. On UNIX it is a <ulink url="http://www.wikipedia.org/wiki/Internet_media_type">mime type</ulink> like "text/plain" or "image/png". * of a file. On UNIX it is a
* [mime type](http://www.wikipedia.org/wiki/Internet_media_type)
* like "text/plain" or "image/png".
* On Win32 it is an extension string like ".doc", ".txt" or a perceived * On Win32 it is an extension string like ".doc", ".txt" or a perceived
* string like "audio". Such strings can be looked up in the registry at * string like "audio". Such strings can be looked up in the registry at
* HKEY_CLASSES_ROOT. * HKEY_CLASSES_ROOT.
@ -486,7 +488,8 @@ g_content_type_get_symbolic_icon (const gchar *type)
* *
* Gets the generic icon name for a content type. * Gets the generic icon name for a content type.
* *
* See the <ulink url="http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec">shared-mime-info</ulink> * See the
* [shared-mime-info](http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec)
* specification for more on the generic icon name. * specification for more on the generic icon name.
* *
* Returns: (allow-none): the registered generic icon name for the given @type, * Returns: (allow-none): the registered generic icon name for the given @type,
@ -1374,7 +1377,8 @@ match_match (TreeMatch *match,
* *
* The types returned all have the form x-content/foo, e.g. * The types returned all have the form x-content/foo, e.g.
* x-content/audio-cdda (for audio CDs) or x-content/image-dcf * x-content/audio-cdda (for audio CDs) or x-content/image-dcf
* (for a camera memory card). See the <ulink url="http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec">shared-mime-info</ulink> * (for a camera memory card). See the
* [shared-mime-info](http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec)
* specification for more on x-content types. * specification for more on x-content types.
* *
* This function is useful in the implementation of * This function is useful in the implementation of

View File

@ -208,11 +208,11 @@ g_dbus_interface_skeleton_class_init (GDBusInterfaceSkeletonClass *klass)
* *
* Note that this signal is emitted in a thread dedicated to * Note that this signal is emitted in a thread dedicated to
* handling the method call so handlers are allowed to perform * handling the method call so handlers are allowed to perform
* blocking IO. This means that it is appropriate to call * blocking IO. This means that it is appropriate to call e.g.
* e.g. <ulink * [polkit_authority_check_authorization_sync()](http://hal.freedesktop.org/docs/polkit/PolkitAuthority.html#polkit-authority-check-authorization-sync)
* url="http://hal.freedesktop.org/docs/polkit/PolkitAuthority.html#polkit-authority-check-authorization-sync">polkit_authority_check_authorization_sync()</ulink> * with the
* with the <ulink * [POLKIT_CHECK_AUTHORIZATION_FLAGS_ALLOW_USER_INTERACTION](http://hal.freedesktop.org/docs/polkit/PolkitAuthority.html#POLKIT-CHECK-AUTHORIZATION-FLAGS-ALLOW-USER-INTERACTION:CAPS)
* url="http://hal.freedesktop.org/docs/polkit/PolkitAuthority.html#POLKIT-CHECK-AUTHORIZATION-FLAGS-ALLOW-USER-INTERACTION:CAPS">POLKIT_CHECK_AUTHORIZATION_FLAGS_ALLOW_USER_INTERACTION</ulink> flag set. * flag set.
* *
* If %FALSE is returned then no further handlers are run and the * If %FALSE is returned then no further handlers are run and the
* signal handler must take a reference to @invocation and finish * signal handler must take a reference to @invocation and finish

View File

@ -38,7 +38,7 @@
* used when registering objects with g_dbus_connection_register_object(). * used when registering objects with g_dbus_connection_register_object().
* *
* The format of D-Bus introspection XML is specified in the * The format of D-Bus introspection XML is specified in the
* <ulink url="http://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format">D-Bus specification</ulink>. * [D-Bus specification](http://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format)
*/ */
/* ---------------------------------------------------------------------------------------------------- */ /* ---------------------------------------------------------------------------------------------------- */

View File

@ -33,8 +33,8 @@
* @include: gio/gio.h * @include: gio/gio.h
* *
* The #GDBusObjectManager type is the base type for service- and * The #GDBusObjectManager type is the base type for service- and
* client-side implementations of the standardized <ulink * client-side implementations of the standardized
* url="http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager">org.freedesktop.DBus.ObjectManager</ulink> * [org.freedesktop.DBus.ObjectManager](http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager)
* interface. * interface.
* *
* See #GDBusObjectManagerClient for the client-side implementation * See #GDBusObjectManagerClient for the client-side implementation

View File

@ -45,8 +45,8 @@
* *
* #GDBusObjectManagerClient is used to create, monitor and delete object * #GDBusObjectManagerClient is used to create, monitor and delete object
* proxies for remote objects exported by a #GDBusObjectManagerServer (or any * proxies for remote objects exported by a #GDBusObjectManagerServer (or any
* code implementing the <ulink * code implementing the
* url="http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager">org.freedesktop.DBus.ObjectManager</ulink> * [org.freedesktop.DBus.ObjectManager](http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager)
* interface). * interface).
* *
* Once an instance of this type has been created, you can connect to * Once an instance of this type has been created, you can connect to

View File

@ -38,8 +38,8 @@
* @include: gio/gio.h * @include: gio/gio.h
* *
* #GDBusObjectManagerServer is used to export #GDBusObject instances using * #GDBusObjectManagerServer is used to export #GDBusObject instances using
* the standardized <ulink * the standardized
* url="http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager">org.freedesktop.DBus.ObjectManager</ulink> * [org.freedesktop.DBus.ObjectManager](http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager)
* interface. For example, remote D-Bus clients can get all objects * interface. For example, remote D-Bus clients can get all objects
* and properties in a single call. Additionally, any change in the * and properties in a single call. Additionally, any change in the
* object hierarchy is broadcast using signals. This means that D-Bus * object hierarchy is broadcast using signals. This means that D-Bus

View File

@ -372,9 +372,10 @@ g_dbus_proxy_class_init (GDBusProxyClass *klass)
* *
* - Properties received via the initial <literal>GetAll()</literal> call * - Properties received via the initial <literal>GetAll()</literal> call
* or via the <literal>::PropertiesChanged</literal> signal (on the * or via the <literal>::PropertiesChanged</literal> signal (on the
* <ulink url="http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties">org.freedesktop.DBus.Properties</ulink> interface) or * [org.freedesktop.DBus.Properties](http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties)
* set using g_dbus_proxy_set_cached_property() with a type signature * interface) or set using g_dbus_proxy_set_cached_property()
* mismatch are ignored and a warning is logged via g_warning(). * with a type signature mismatch are ignored and a warning is
* logged via g_warning().
* *
* Note that these checks are never done on methods, signals and * Note that these checks are never done on methods, signals and
* properties that are not referenced in the given * properties that are not referenced in the given

View File

@ -58,7 +58,7 @@
* #GDesktopAppInfo is an implementation of #GAppInfo based on * #GDesktopAppInfo is an implementation of #GAppInfo based on
* desktop files. * desktop files.
* *
* Note that `<gio/gdesktopappinfo.h>` belongs to the UNIX-specific * Note that `&lt;gio/gdesktopappinfo.h&gt;` belongs to the UNIX-specific
* GIO interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config * GIO interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
* file when using it. * file when using it.
*/ */
@ -1310,8 +1310,8 @@ g_desktop_app_info_new_from_filename (const char *filename)
* data directories (i.e. the directories specified in the `XDG_DATA_HOME` * data directories (i.e. the directories specified in the `XDG_DATA_HOME`
* and `XDG_DATA_DIRS` environment variables). GIO also supports the * and `XDG_DATA_DIRS` environment variables). GIO also supports the
* prefix-to-subdirectory mapping that is described in the * prefix-to-subdirectory mapping that is described in the
* <ulink url="http://standards.freedesktop.org/menu-spec/latest/">Menu * [Menu Spec](http://standards.freedesktop.org/menu-spec/latest/)
* Spec</ulink> (i.e. a desktop id of kde-foo.desktop will match * (i.e. a desktop id of kde-foo.desktop will match
* `/usr/share/applications/kde/foo.desktop`). * `/usr/share/applications/kde/foo.desktop`).
* *
* Returns: a new #GDesktopAppInfo, or %NULL if no desktop file with that id * Returns: a new #GDesktopAppInfo, or %NULL if no desktop file with that id
@ -2476,8 +2476,9 @@ g_desktop_app_info_launch_uris_as_manager (GDesktopAppInfo *appinfo,
* <literal>OnlyShowIn</literal> and <literal>NotShowIn</literal> * <literal>OnlyShowIn</literal> and <literal>NotShowIn</literal>
* desktop entry fields. * desktop entry fields.
* *
* The <ulink url="http://standards.freedesktop.org/menu-spec/latest/">Desktop * The
* Menu specification</ulink> recognizes the following: * [Desktop Menu specification](http://standards.freedesktop.org/menu-spec/latest/)
* recognizes the following:
* <simplelist> * <simplelist>
* <member>GNOME</member> * <member>GNOME</member>
* <member>KDE</member> * <member>KDE</member>
@ -3126,8 +3127,8 @@ g_desktop_app_info_delete (GAppInfo *appinfo)
* Creates a new #GAppInfo from the given information. * Creates a new #GAppInfo from the given information.
* *
* Note that for @commandline, the quoting rules of the Exec key of the * Note that for @commandline, the quoting rules of the Exec key of the
* <ulink url="http://freedesktop.org/Standards/desktop-entry-spec">freedesktop.org Desktop * [freedesktop.org Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec)
* Entry Specification</ulink> are applied. For example, if the @commandline contains * are applied. For example, if the @commandline contains
* percent-encoded URIs, the percent-character must be doubled in order to prevent it from * percent-encoded URIs, the percent-character must be doubled in order to prevent it from
* being swallowed by Exec key unquoting. See the specification for exact quoting rules. * being swallowed by Exec key unquoting. See the specification for exact quoting rules.
* *

View File

@ -142,7 +142,8 @@
* short. Entity tags are somewhat like a more abstract version of the * short. Entity tags are somewhat like a more abstract version of the
* traditional mtime, and can be used to quickly determine if the file * traditional mtime, and can be used to quickly determine if the file
* has been modified from the version on the file system. See the * has been modified from the version on the file system. See the
* HTTP 1.1 <ulink url="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html">specification</ulink> * HTTP 1.1
* [specification](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html)
* for HTTP Etag headers, which are a very similar concept. * for HTTP Etag headers, which are a very similar concept.
* </para> * </para>
**/ **/

View File

@ -32,7 +32,7 @@
* #GFileDescriptorBased is implemented by streams (implementations of * #GFileDescriptorBased is implemented by streams (implementations of
* #GInputStream or #GOutputStream) that are based on file descriptors. * #GInputStream or #GOutputStream) that are based on file descriptors.
* *
* Note that `<gio/gfiledescriptorbased.h>` belongs to the UNIX-specific * Note that `&lt;gio/gfiledescriptorbased.h&gt;` belongs to the UNIX-specific
* GIO interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config * GIO interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
* file when using it. * file when using it.
* *

View File

@ -767,7 +767,8 @@ g_mount_remount_finish (GMount *mount,
* Tries to guess the type of content stored on @mount. Returns one or * Tries to guess the type of content stored on @mount. Returns one or
* more textual identifiers of well-known content types (typically * more textual identifiers of well-known content types (typically
* prefixed with "x-content/"), e.g. x-content/image-dcf for camera * prefixed with "x-content/"), e.g. x-content/image-dcf for camera
* memory cards. See the <ulink url="http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec">shared-mime-info</ulink> * memory cards. See the
* [shared-mime-info](http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec)
* specification for more on x-content types. * specification for more on x-content types.
* *
* This is an asynchronous operation (see * This is an asynchronous operation (see
@ -854,7 +855,8 @@ g_mount_guess_content_type_finish (GMount *mount,
* Tries to guess the type of content stored on @mount. Returns one or * Tries to guess the type of content stored on @mount. Returns one or
* more textual identifiers of well-known content types (typically * more textual identifiers of well-known content types (typically
* prefixed with "x-content/"), e.g. x-content/image-dcf for camera * prefixed with "x-content/"), e.g. x-content/image-dcf for camera
* memory cards. See the <ulink url="http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec">shared-mime-info</ulink> * memory cards. See the
* [shared-mime-info](http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec)
* specification for more on x-content types. * specification for more on x-content types.
* *
* This is an synchronous operation and as such may block doing IO; * This is an synchronous operation and as such may block doing IO;

View File

@ -95,7 +95,8 @@
* by the <link linkend="glib-compile-schemas">glib-compile-schemas</link> * by the <link linkend="glib-compile-schemas">glib-compile-schemas</link>
* utility. The input is a schema description in an XML format. * utility. The input is a schema description in an XML format.
* *
* A DTD for the gschema XML format can be found here: <ulink url="https://git.gnome.org/browse/glib/tree/gio/gschema.dtd">gschema.dtd</ulink> * A DTD for the gschema XML format can be found here:
* [gschema.dtd](https://git.gnome.org/browse/glib/tree/gio/gschema.dtd)
* *
* The <link linkend="glib-compile-schemas">glib-compile-schemas</link> * The <link linkend="glib-compile-schemas">glib-compile-schemas</link>
* tool expects schema files to have the extension `.gschema.xml`. * tool expects schema files to have the extension `.gschema.xml`.

View File

@ -361,7 +361,8 @@ _g_test_watcher_remove_pid (GPid pid)
* you can proceed to set up a GTest fixture using the #GTestDBus scaffolding. * you can proceed to set up a GTest fixture using the #GTestDBus scaffolding.
* *
* An example of a test fixture for D-Bus services can be found * An example of a test fixture for D-Bus services can be found
* here: <ulink url="https://git.gnome.org/browse/glib/tree/gio/tests/gdbus-test-fixture.c">gdbus-test-fixture.c</ulink> * here:
* [gdbus-test-fixture.c](https://git.gnome.org/browse/glib/tree/gio/tests/gdbus-test-fixture.c)
* *
* Note that these examples only deal with isolating the D-Bus aspect of your * Note that these examples only deal with isolating the D-Bus aspect of your
* service. To successfully run isolated unit tests on your service you may need * service. To successfully run isolated unit tests on your service you may need

View File

@ -39,7 +39,7 @@
* It contains functions to do some of the UNIX socket specific * It contains functions to do some of the UNIX socket specific
* functionality like passing file descriptors. * functionality like passing file descriptors.
* *
* Note that `<gio/gunixconnection.h>` belongs to the UNIX-specific * Note that `&lt;gio/gunixconnection.h&gt;` belongs to the UNIX-specific
* GIO interfaces, thus you have to use the `gio-unix-2.0.pc` * GIO interfaces, thus you have to use the `gio-unix-2.0.pc`
* pkg-config file when using it. * pkg-config file when using it.
* *

View File

@ -26,7 +26,7 @@
* the %G_SOCKET_ADDRESS_UNIX family by using g_socket_send_message() * the %G_SOCKET_ADDRESS_UNIX family by using g_socket_send_message()
* and received using g_socket_receive_message(). * and received using g_socket_receive_message().
* *
* Note that `<gio/gunixfdlist.h>` belongs to the UNIX-specific GIO * Note that `&lt;gio/gunixfdlist.h&gt;` belongs to the UNIX-specific GIO
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config * interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
* file when using it. * file when using it.
*/ */

View File

@ -29,7 +29,7 @@
* stream-oriented UNIX sockets, see g_unix_connection_send_fd() and * stream-oriented UNIX sockets, see g_unix_connection_send_fd() and
* g_unix_connection_receive_fd(). * g_unix_connection_receive_fd().
* *
* Note that `<gio/gunixfdmessage.h>` belongs to the UNIX-specific GIO * Note that `&lt;gio/gunixfdmessage.h&gt;` belongs to the UNIX-specific GIO
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config * interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
* file when using it. * file when using it.
*/ */

View File

@ -51,7 +51,7 @@
* asynchronous I/O. If it refers to a regular file, it will fall back * asynchronous I/O. If it refers to a regular file, it will fall back
* to doing asynchronous I/O in another thread.) * to doing asynchronous I/O in another thread.)
* *
* Note that `<gio/gunixinputstream.h>` belongs to the UNIX-specific GIO * Note that `&lt;gio/gunixinputstream.h&gt;` belongs to the UNIX-specific GIO
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config * interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
* file when using it. * file when using it.
*/ */

View File

@ -79,7 +79,7 @@ static const char *_resolve_dev_root (void);
* *
* Routines for managing mounted UNIX mount points and paths. * Routines for managing mounted UNIX mount points and paths.
* *
* Note that `<gio/gunixmounts.h>` belongs to the UNIX-specific GIO * Note that `&lt;gio/gunixmounts.h&gt;` belongs to the UNIX-specific GIO
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config * interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
* file when using it. * file when using it.
*/ */

View File

@ -51,7 +51,7 @@
* asynchronous I/O. If it refers to a regular file, it will fall back * asynchronous I/O. If it refers to a regular file, it will fall back
* to doing asynchronous I/O in another thread.) * to doing asynchronous I/O in another thread.)
* *
* Note that `<gio/gunixoutputstream.h>` belongs to the UNIX-specific GIO * Note that `&lt;gio/gunixoutputstream.h&gt;` belongs to the UNIX-specific GIO
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config file * interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config file
* when using it. * when using it.
*/ */

View File

@ -44,7 +44,7 @@
* errors. You can use g_unix_socket_address_abstract_names_supported() * errors. You can use g_unix_socket_address_abstract_names_supported()
* to see if abstract names are supported. * to see if abstract names are supported.
* *
* Note that `<gio/gunixsocketaddress.h>` belongs to the UNIX-specific GIO * Note that `&lt;gio/gunixsocketaddress.h&gt;` belongs to the UNIX-specific GIO
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config file * interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config file
* when using it. * when using it.
*/ */

View File

@ -44,7 +44,7 @@
* #GWin32InputStream implements #GInputStream for reading from a * #GWin32InputStream implements #GInputStream for reading from a
* Windows file handle. * Windows file handle.
* *
* Note that `<gio/gwin32inputstream.h>` belongs to the Windows-specific GIO * Note that `&lt;gio/gwin32inputstream.h&gt;` belongs to the Windows-specific GIO
* interfaces, thus you have to use the `gio-windows-2.0.pc` pkg-config file * interfaces, thus you have to use the `gio-windows-2.0.pc` pkg-config file
* when using it. * when using it.
*/ */

View File

@ -45,7 +45,7 @@
* #GWin32OutputStream implements #GOutputStream for writing to a * #GWin32OutputStream implements #GOutputStream for writing to a
* Windows file handle. * Windows file handle.
* *
* Note that `<gio/gwin32outputstream.h>` belongs to the Windows-specific GIO * Note that `&lt;gio/gwin32outputstream.h&gt;` belongs to the Windows-specific GIO
* interfaces, thus you have to use the `gio-windows-2.0.pc` pkg-config file * interfaces, thus you have to use the `gio-windows-2.0.pc` pkg-config file
* when using it. * when using it.
*/ */

View File

@ -1428,7 +1428,7 @@
* sign, mantissa and exponent of IEEE floats and doubles. These unions are * sign, mantissa and exponent of IEEE floats and doubles. These unions are
* defined as appropriate for a given platform. IEEE floats and doubles are * defined as appropriate for a given platform. IEEE floats and doubles are
* supported (used for storage) by at least Intel, PPC and Sparc. See * supported (used for storage) by at least Intel, PPC and Sparc. See
* <ulink url="http://en.wikipedia.org/wiki/IEEE_float">IEEE 754-2008</ulink> * [IEEE 754-2008](http://en.wikipedia.org/wiki/IEEE_float)
* for more information about IEEE number formats. * for more information about IEEE number formats.
*/ */

View File

@ -37,9 +37,11 @@
* *
* Base64 is an encoding that allows a sequence of arbitrary bytes to be * Base64 is an encoding that allows a sequence of arbitrary bytes to be
* encoded as a sequence of printable ASCII characters. For the definition * encoded as a sequence of printable ASCII characters. For the definition
* of Base64, see <ulink url="http://www.ietf.org/rfc/rfc1421.txt">RFC * of Base64, see
* 1421</ulink> or <ulink url="http://www.ietf.org/rfc/rfc2045.txt">RFC * [RFC 1421](http://www.ietf.org/rfc/rfc1421.txt)
* 2045</ulink>. Base64 is most commonly used as a MIME transfer encoding * or
* [RFC 2045](http://www.ietf.org/rfc/rfc2045.txt).
* Base64 is most commonly used as a MIME transfer encoding
* for email. * for email.
* *
* GLib supports incremental encoding using g_base64_encode_step() and * GLib supports incremental encoding using g_base64_encode_step() and

View File

@ -60,13 +60,12 @@
* like its MIME type, the application that is registering the bookmark and * like its MIME type, the application that is registering the bookmark and
* the icon that should be used to represent the bookmark. The data is stored * the icon that should be used to represent the bookmark. The data is stored
* using the * using the
* <ulink url="http://www.gnome.org/~ebassi/bookmark-spec">Desktop Bookmark * [Desktop Bookmark Specification](http://www.gnome.org/~ebassi/bookmark-spec).
* Specification</ulink>.
* *
* The syntax of the bookmark files is described in detail inside the Desktop * The syntax of the bookmark files is described in detail inside the Desktop
* Bookmark Specification, here is a quick summary: bookmark files use a * Bookmark Specification, here is a quick summary: bookmark files use a
* sub-class of the <ulink url="">XML Bookmark Exchange Language</ulink> * sub-class of the XML Bookmark Exchange Language specification,
* specification, consisting of valid UTF-8 encoded XML, under the * consisting of valid UTF-8 encoded XML, under the
* <literal>xbel</literal> root element; each bookmark is stored inside a * <literal>xbel</literal> root element; each bookmark is stored inside a
* <literal>bookmark</literal> element, using its URI: no relative paths can * <literal>bookmark</literal> element, using its URI: no relative paths can
* be used inside a bookmark file. The bookmark may have a user defined title * be used inside a bookmark file. The bookmark may have a user defined title
@ -80,7 +79,8 @@
* registered; the URI and MIME type of an icon, to be used when displaying * registered; the URI and MIME type of an icon, to be used when displaying
* the bookmark inside a GUI. * the bookmark inside a GUI.
* *
* Here is an example of a bookmark file: <ulink url="https://git.gnome.org/browse/glib/tree/glib/tests/bookmarks.xbel">bookmarks.xbel</ulink> * Here is an example of a bookmark file:
* [bookmarks.xbel](https://git.gnome.org/browse/glib/tree/glib/tests/bookmarks.xbel)
* *
* A bookmark file might contain more than one bookmark; each bookmark * A bookmark file might contain more than one bookmark; each bookmark
* is accessed through its URI. * is accessed through its URI.

View File

@ -126,7 +126,8 @@
* a more secure hash function when using a GHashTable with keys * a more secure hash function when using a GHashTable with keys
* that originate in untrusted data (such as HTTP requests). * that originate in untrusted data (such as HTTP requests).
* Using g_str_hash() in that situation might make your application * Using g_str_hash() in that situation might make your application
* vulerable to <ulink url="https://lwn.net/Articles/474912/">Algorithmic Complexity Attacks</ulink>. * vulerable to
* [Algorithmic Complexity Attacks](https://lwn.net/Articles/474912/).
* *
* The key to choosing a good hash is unpredictability. Even * The key to choosing a good hash is unpredictability. Even
* cryptographic hashes are very easy to find collisions for when the * cryptographic hashes are very easy to find collisions for when the

View File

@ -42,7 +42,8 @@
* HMACs should be used when producing a cookie or hash based on data * HMACs should be used when producing a cookie or hash based on data
* and a key. Simple mechanisms for using SHA1 and other algorithms to * and a key. Simple mechanisms for using SHA1 and other algorithms to
* digest a key and data together are vulnerable to various security * digest a key and data together are vulnerable to various security
* issues. <ulink url="http://en.wikipedia.org/wiki/HMAC">HMAC</ulink> * issues.
* [HMAC](http://en.wikipedia.org/wiki/HMAC)
* uses algorithms like SHA1 in a secure way to produce a digest of a * uses algorithms like SHA1 in a secure way to produce a digest of a
* key and data. * key and data.
* *

View File

@ -38,9 +38,9 @@
* converting between Unicode and ASCII-encoded forms of * converting between Unicode and ASCII-encoded forms of
* Internationalized Domain Names (IDNs). * Internationalized Domain Names (IDNs).
* *
* The <ulink * The
* url="http://www.ietf.org/rfc/rfc3490.txt">Internationalized Domain * [Internationalized Domain Names for Applications (IDNA)](http://www.ietf.org/rfc/rfc3490.txt)
* Names for Applications (IDNA)</ulink> standards allow for the use * standards allow for the use
* of Unicode domain names in applications, while providing * of Unicode domain names in applications, while providing
* backward-compatibility with the old ASCII-only DNS, by defining an * backward-compatibility with the old ASCII-only DNS, by defining an
* ASCII-Compatible Encoding of any given Unicode name, which can be * ASCII-Compatible Encoding of any given Unicode name, which can be

View File

@ -77,14 +77,13 @@
* key-value pairs, which we call <firstterm>key files</firstterm> for * key-value pairs, which we call <firstterm>key files</firstterm> for
* lack of a better name. Several freedesktop.org specifications use * lack of a better name. Several freedesktop.org specifications use
* key files now, e.g the * key files now, e.g the
* <ulink url="http://freedesktop.org/Standards/desktop-entry-spec">Desktop * [Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec)
* Entry Specification</ulink> and the * and the
* <ulink url="http://freedesktop.org/Standards/icon-theme-spec">Icon * [Icon Theme Specification](http://freedesktop.org/Standards/icon-theme-spec).
* Theme Specification</ulink>.
* *
* The syntax of key files is described in detail in the * The syntax of key files is described in detail in the
* <ulink url="http://freedesktop.org/Standards/desktop-entry-spec">Desktop * [Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec),
* Entry Specification</ulink>, here is a quick summary: Key files * here is a quick summary: Key files
* consists of groups of key-value pairs, interspersed with comments. * consists of groups of key-value pairs, interspersed with comments.
* *
* |[ * |[
@ -150,8 +149,8 @@
* true and false (in lower case) are allowed. * true and false (in lower case) are allowed.
* *
* Note that in contrast to the * Note that in contrast to the
* <ulink url="http://freedesktop.org/Standards/desktop-entry-spec">Desktop * [Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec),
* Entry Specification</ulink>, groups in key files may contain the same * groups in key files may contain the same
* key multiple times; the last entry wins. Key files may also contain * key multiple times; the last entry wins. Key files may also contain
* multiple groups with the same name; they are merged together. * multiple groups with the same name; they are merged together.
* Another difference is that keys and group names in key files are not * Another difference is that keys and group names in key files are not
@ -199,8 +198,8 @@
* G_KEY_FILE_DESKTOP_GROUP: * G_KEY_FILE_DESKTOP_GROUP:
* *
* The name of the main group of a desktop entry file, as defined in the * The name of the main group of a desktop entry file, as defined in the
* <ulink url="http://freedesktop.org/Standards/desktop-entry-spec">Desktop * [Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec).
* Entry Specification</ulink>. Consult the specification for more * Consult the specification for more
* details about the meanings of the keys below. * details about the meanings of the keys below.
* *
* Since: 2.14 * Since: 2.14
@ -368,9 +367,8 @@
* G_KEY_FILE_DESKTOP_KEY_STARTUP_NOTIFY: * G_KEY_FILE_DESKTOP_KEY_STARTUP_NOTIFY:
* *
* A key under #G_KEY_FILE_DESKTOP_GROUP, whose value is a boolean * A key under #G_KEY_FILE_DESKTOP_GROUP, whose value is a boolean
* stating whether the application supports the <ulink * stating whether the application supports the
* url="http://www.freedesktop.org/Standards/startup-notification-spec">Startup * [Startup Notification Protocol Specification](http://www.freedesktop.org/Standards/startup-notification-spec).
* Notification Protocol Specification</ulink>.
* *
* Since: 2.14 * Since: 2.14
*/ */

View File

@ -40,8 +40,7 @@
/** /**
* SECTION:markup * SECTION:markup
* @Title: Simple XML Subset Parser * @Short_description: parses a subset of XML * @Title: Simple XML Subset Parser * @Short_description: parses a subset of XML
* @See_also: <ulink url="http://www.w3.org/TR/REC-xml/">XML * @See_also: [XML Specification](http://www.w3.org/TR/REC-xml/)
* Specification</ulink>
* *
* The "GMarkup" parser is intended to parse a simple markup format * The "GMarkup" parser is intended to parse a simple markup format
* that's a subset of XML. This is a small, efficient, easy-to-use * that's a subset of XML. This is a small, efficient, easy-to-use
@ -57,8 +56,9 @@
* the parser may accept documents that an XML parser would not. * the parser may accept documents that an XML parser would not.
* However, XML documents which are not well-formed (which is a * However, XML documents which are not well-formed (which is a
* weaker condition than being valid. See the * weaker condition than being valid. See the
* <ulink url="http://www.w3.org/TR/REC-xml/">XML specification</ulink> * [XML specification](http://www.w3.org/TR/REC-xml/)
* for definitions of these terms.) are not considered valid GMarkup documents. * for definitions of these terms.) are not considered valid GMarkup
* documents.
* *
* Simplifications to XML include: * Simplifications to XML include:
* *

View File

@ -174,8 +174,8 @@
* A convenience function/macro to log a warning message. * A convenience function/macro to log a warning message.
* *
* You can make warnings fatal at runtime by setting the `G_DEBUG` * You can make warnings fatal at runtime by setting the `G_DEBUG`
* environment variable (see <ulink url="glib-running.html">Running * environment variable (see
* GLib Applications</ulink>). * [Running GLib Applications](glib-running.html)).
* *
* If g_log_default_handler() is used as the log handler function, * If g_log_default_handler() is used as the log handler function,
* a newline character will automatically be appended to @..., and * a newline character will automatically be appended to @..., and
@ -196,7 +196,7 @@
* *
* You can also make critical warnings fatal at runtime by * You can also make critical warnings fatal at runtime by
* setting the `G_DEBUG` environment variable (see * setting the `G_DEBUG` environment variable (see
* <ulink url="glib-running.html">Running GLib Applications</ulink>). * [Running GLib Applications](glib-running.html)).
* *
* If g_log_default_handler() is used as the log handler function, a new-line * If g_log_default_handler() is used as the log handler function, a new-line
* character will automatically be appended to @..., and need not be entered * character will automatically be appended to @..., and need not be entered
@ -450,7 +450,7 @@ g_log_domain_get_handler_L (GLogDomain *domain,
* *
* You can also make some message levels fatal at runtime by setting * You can also make some message levels fatal at runtime by setting
* the `G_DEBUG` environment variable (see * the `G_DEBUG` environment variable (see
* <ulink url="glib-running.html">Running GLib Applications</ulink>). * [Running GLib Applications](glib-running.html)).
* *
* Returns: the old fatal mask * Returns: the old fatal mask
*/ */

View File

@ -78,9 +78,8 @@
* *
* GRand uses the Mersenne Twister PRNG, which was originally * GRand uses the Mersenne Twister PRNG, which was originally
* developed by Makoto Matsumoto and Takuji Nishimura. Further * developed by Makoto Matsumoto and Takuji Nishimura. Further
* information can be found at <ulink * information can be found at
* url="http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html"> * [this page](http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html).
* http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html</ulink>.
* *
* If you just need a random number, you simply call the g_random_* * If you just need a random number, you simply call the g_random_*
* functions, which will create a globally used #GRand and use the * functions, which will create a globally used #GRand and use the

View File

@ -98,7 +98,7 @@
* '\U' always matches 'U' instead of being an error in the pattern. Finally, * '\U' always matches 'U' instead of being an error in the pattern. Finally,
* pattern matching is modified so that back references to an unset subpattern * pattern matching is modified so that back references to an unset subpattern
* group produces a match with the empty string instead of an error. See * group produces a match with the empty string instead of an error. See
* <ulink>man:pcreapi(3)</ulink> for more information. * pcreapi(3) for more information.
* *
* Creating and manipulating the same #GRegex structure from different * Creating and manipulating the same #GRegex structure from different
* threads is not a problem as #GRegex does not modify its internal * threads is not a problem as #GRegex does not modify its internal
@ -106,8 +106,9 @@
* is not threadsafe. * is not threadsafe.
* *
* The regular expressions low-level functionalities are obtained through * The regular expressions low-level functionalities are obtained through
* the excellent <ulink url="http://www.pcre.org/">PCRE</ulink> library * the excellent
* written by Philip Hazel. * [PCRE](http://www.pcre.org/)
* library written by Philip Hazel.
*/ */
/* Mask of all the possible values for GRegexCompileFlags. */ /* Mask of all the possible values for GRegexCompileFlags. */
@ -878,7 +879,7 @@ g_match_info_get_match_count (const GMatchInfo *match_info)
* There were formerly some restrictions on the pattern for partial matching. * There were formerly some restrictions on the pattern for partial matching.
* The restrictions no longer apply. * The restrictions no longer apply.
* *
* See <ulink>man:pcrepartial</ulink> for more information on partial matching. * See pcrepartial(3) for more information on partial matching.
* *
* Returns: %TRUE if the match was partial, %FALSE otherwise * Returns: %TRUE if the match was partial, %FALSE otherwise
* *

View File

@ -66,9 +66,11 @@
* *
* To achieve these goals, the slice allocator uses a sophisticated, * To achieve these goals, the slice allocator uses a sophisticated,
* layered design that has been inspired by Bonwick's slab allocator * layered design that has been inspired by Bonwick's slab allocator
* (<ulink url="http://citeseer.ist.psu.edu/bonwick94slab.html">[Bonwick94]</ulink> Jeff Bonwick, The slab allocator: An object-caching kernel * ([Bonwick94](http://citeseer.ist.psu.edu/bonwick94slab.html)
* Jeff Bonwick, The slab allocator: An object-caching kernel
* memory allocator. USENIX 1994, and * memory allocator. USENIX 1994, and
* <ulink url="http://citeseer.ist.psu.edu/bonwick01magazines.html">[Bonwick01]</ulink> Bonwick and Jonathan Adams, Magazines and vmem: Extending the * [Bonwick01](http://citeseer.ist.psu.edu/bonwick01magazines.html)
* Bonwick and Jonathan Adams, Magazines and vmem: Extending the
* slab allocator to many cpu's and arbitrary resources. USENIX 2001) * slab allocator to many cpu's and arbitrary resources. USENIX 2001)
* *
* It uses posix_memalign() to optimize allocations of many equally-sized * It uses posix_memalign() to optimize allocations of many equally-sized

View File

@ -482,11 +482,11 @@ g_time_val_from_iso8601 (const gchar *iso_date,
* "YYYY-MM-DDTHH:MM:SSZ" or "YYYY-MM-DDTHH:MM:SS.fffffZ". * "YYYY-MM-DDTHH:MM:SSZ" or "YYYY-MM-DDTHH:MM:SS.fffffZ".
* *
* This corresponds to the Internet date/time format defined by * This corresponds to the Internet date/time format defined by
* <ulink url="https://www.ietf.org/rfc/rfc3339.txt">RFC 3339</ulink>, and * [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt),
* to either of the two most-precise formats defined by * and to either of the two most-precise formats defined by
* <ulink url="http://www.w3.org/TR/NOTE-datetime-19980827">the W3C Note * the W3C Note
* "Date and Time Formats"</ulink>. Both of these documents are profiles of * [Date and Time Formats](http://www.w3.org/TR/NOTE-datetime-19980827).
* ISO 8601. * Both of these documents are profiles of ISO 8601.
* *
* Use g_date_time_format() or g_strdup_printf() if a different * Use g_date_time_format() or g_strdup_printf() if a different
* variation of ISO 8601 format is required. * variation of ISO 8601 format is required.

View File

@ -1351,17 +1351,16 @@ rules_from_identifier (const gchar *identifier,
* available and it is greater than 2037, then it will followed * available and it is greater than 2037, then it will followed
* instead. * instead.
* *
* See <ulink * See
* url='http://tools.ietf.org/html/rfc3339#section-5.6'>RFC3339 * [RFC3339 §5.6](http://tools.ietf.org/html/rfc3339#section-5.6)
* §5.6</ulink> for a precise definition of valid RFC3339 time offsets * for a precise definition of valid RFC3339 time offsets
* (the <literal>time-offset</literal> expansion) and ISO 8601 for the * (the <literal>time-offset</literal> expansion) and ISO 8601 for the
* full list of valid time offsets. See <ulink * full list of valid time offsets. See
* url='http://www.gnu.org/s/libc/manual/html_node/TZ-Variable.html'>The * [The GNU C Library manual](http://www.gnu.org/s/libc/manual/html_node/TZ-Variable.html)
* GNU C Library manual</ulink> for an explanation of the possible * for an explanation of the possible
* values of the `TZ` environment variable. See <ulink * values of the `TZ` environment variable. See
* url='http://msdn.microsoft.com/en-us/library/ms912391%28v=winembedded.11%29.aspx'> * [Microsoft Time Zone Index Values](http://msdn.microsoft.com/en-us/library/ms912391%28v=winembedded.11%29.aspx)
* Microsoft Time Zone Index Values</ulink> for the list of time zones * for the list of time zones on Windows.
* on Windows.
* *
* You should release the return value by calling g_time_zone_unref() * You should release the return value by calling g_time_zone_unref()
* when you are done with it. * when you are done with it.

View File

@ -35,7 +35,7 @@
* *
* The implementations of the Unicode functions in GLib are based * The implementations of the Unicode functions in GLib are based
* on the Unicode Character Data tables, which are available from * on the Unicode Character Data tables, which are available from
* <ulink url="http://www.unicode.org/">www.unicode.org</ulink>. * [www.unicode.org](http://www.unicode.org/).
* GLib 2.8 supports Unicode 4.0, GLib 2.10 supports Unicode 4.1, * GLib 2.8 supports Unicode 4.0, GLib 2.10 supports Unicode 4.1,
* GLib 2.12 supports Unicode 5.0, GLib 2.16.3 supports Unicode 5.1, * GLib 2.12 supports Unicode 5.0, GLib 2.16.3 supports Unicode 5.1,
* GLib 2.30 supports Unicode 6.0. * GLib 2.30 supports Unicode 6.0.
@ -595,7 +595,8 @@ decompose_hangul_step (gunichar ch,
* recursively call this function on @a. Or use * recursively call this function on @a. Or use
* g_unichar_fully_decompose(). * g_unichar_fully_decompose().
* *
* See <ulink url="http://unicode.org/reports/tr15/">UAX#15</ulink> * See
* [UAX#15](http://unicode.org/reports/tr15/)
* for details. * for details.
* *
* Returns: %TRUE if the character could be decomposed * Returns: %TRUE if the character could be decomposed
@ -661,7 +662,8 @@ g_unichar_decompose (gunichar ch,
* *
* If @a and @b do not compose a new character, @ch is set to zero. * If @a and @b do not compose a new character, @ch is set to zero.
* *
* See <ulink url="http://unicode.org/reports/tr15/">UAX#15</ulink> * See
* [UAX#15](http://unicode.org/reports/tr15/)
* for details. * for details.
* *
* Returns: %TRUE if the characters could be composed * Returns: %TRUE if the characters could be composed
@ -703,7 +705,8 @@ g_unichar_compose (gunichar a,
* decompositions, so that is the size recommended. This is provided * decompositions, so that is the size recommended. This is provided
* as %G_UNICHAR_MAX_DECOMPOSITION_LENGTH. * as %G_UNICHAR_MAX_DECOMPOSITION_LENGTH.
* *
* See <ulink url="http://unicode.org/reports/tr15/">UAX#15</ulink> * See
* [UAX#15](http://unicode.org/reports/tr15/)
* for details. * for details.
* *
* Return value: the length of the full decomposition. * Return value: the length of the full decomposition.

View File

@ -492,9 +492,9 @@ g_unichar_iswide (gunichar c)
* Determines if a character is typically rendered in a double-width * Determines if a character is typically rendered in a double-width
* cell under legacy East Asian locales. If a character is wide according to * cell under legacy East Asian locales. If a character is wide according to
* g_unichar_iswide(), then it is also reported wide with this function, but * g_unichar_iswide(), then it is also reported wide with this function, but
* the converse is not necessarily true. See the * the converse is not necessarily true. See the
* <ulink url="http://www.unicode.org/reports/tr11/">Unicode Standard * [Unicode Standard Annex #11](http://www.unicode.org/reports/tr11/)
* Annex #11</ulink> for details. * for details.
* *
* If a character passes the g_unichar_iswide() test then it will also pass * If a character passes the g_unichar_iswide() test then it will also pass
* this test, but not the other way around. Note that some characters may * this test, but not the other way around. Note that some characters may
@ -1454,8 +1454,9 @@ static const guint32 iso15924_tags[] =
* big-endian fashion. That is, the code returned for Arabic is * big-endian fashion. That is, the code returned for Arabic is
* 0x41726162 (0x41 is ASCII code for 'A', 0x72 is ASCII code for 'r', etc). * 0x41726162 (0x41 is ASCII code for 'A', 0x72 is ASCII code for 'r', etc).
* *
* See <ulink url="http://unicode.org/iso15924/codelists.html">Codes for the * See
* representation of names of scripts</ulink> for details. * [Codes for the representation of names of scripts](http://unicode.org/iso15924/codelists.html)
* for details.
* *
* Return value: the ISO 15924 code for @script, encoded as an integer, * Return value: the ISO 15924 code for @script, encoded as an integer,
* of zero if @script is %G_UNICODE_SCRIPT_INVALID_CODE or * of zero if @script is %G_UNICODE_SCRIPT_INVALID_CODE or
@ -1485,8 +1486,9 @@ g_unicode_script_to_iso15924 (GUnicodeScript script)
* big-endian fashion. That is, the code expected for Arabic is * big-endian fashion. That is, the code expected for Arabic is
* 0x41726162 (0x41 is ASCII code for 'A', 0x72 is ASCII code for 'r', etc). * 0x41726162 (0x41 is ASCII code for 'A', 0x72 is ASCII code for 'r', etc).
* *
* See <ulink url="http://unicode.org/iso15924/codelists.html">Codes for the * See
* representation of names of scripts</ulink> for details. * [Codes for the representation of names of scripts](http://unicode.org/iso15924/codelists.html)
* for details.
* *
* Return value: the Unicode script for @iso15924, or * Return value: the Unicode script for @iso15924, or
* of %G_UNICODE_SCRIPT_INVALID_CODE if @iso15924 is zero and * of %G_UNICODE_SCRIPT_INVALID_CODE if @iso15924 is zero and

View File

@ -37,8 +37,9 @@
* @short_description: manipulating URIs * @short_description: manipulating URIs
* *
* Functions for manipulating Universal Resource Identifiers (URIs) as * Functions for manipulating Universal Resource Identifiers (URIs) as
* defined by <ulink url="http://www.ietf.org/rfc/rfc3986.txt"> * defined by
* RFC 3986</ulink>. It is highly recommended that you have read and * [RFC 3986](http://www.ietf.org/rfc/rfc3986.txt).
* It is highly recommended that you have read and
* understand RFC 3986 for understanding this API. * understand RFC 3986 for understanding this API.
*/ */

View File

@ -1134,10 +1134,10 @@ g_set_application_name (const gchar *application_name)
* Returns a base directory in which to access application data such * Returns a base directory in which to access application data such
* as icons that is customized for a particular user. * as icons that is customized for a particular user.
* *
* On UNIX platforms this is determined using the mechanisms described in * On UNIX platforms this is determined using the mechanisms described
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec"> * in the
* XDG Base Directory Specification</ulink>. * [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
* In this case the directory retrieved will be XDG_DATA_HOME. * In this case the directory retrieved will be `XDG_DATA_HOME`.
* *
* On Windows this is the folder to use for local (as opposed to * On Windows this is the folder to use for local (as opposed to
* roaming) application data. See documentation for * roaming) application data. See documentation for
@ -1220,10 +1220,10 @@ g_init_user_config_dir (void)
* Returns a base directory in which to store user-specific application * Returns a base directory in which to store user-specific application
* configuration information such as user preferences and settings. * configuration information such as user preferences and settings.
* *
* On UNIX platforms this is determined using the mechanisms described in * On UNIX platforms this is determined using the mechanisms described
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec"> * in the
* XDG Base Directory Specification</ulink>. * [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
* In this case the directory retrieved will be XDG_CONFIG_HOME. * In this case the directory retrieved will be `XDG_CONFIG_HOME`.
* *
* On Windows this is the folder to use for local (as opposed to * On Windows this is the folder to use for local (as opposed to
* roaming) application data. See documentation for * roaming) application data. See documentation for
@ -1252,9 +1252,9 @@ g_get_user_config_dir (void)
* Returns a base directory in which to store non-essential, cached * Returns a base directory in which to store non-essential, cached
* data specific to particular user. * data specific to particular user.
* *
* On UNIX platforms this is determined using the mechanisms described in * On UNIX platforms this is determined using the mechanisms described
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec"> * in the
* XDG Base Directory Specification</ulink>. * [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
* In this case the directory retrieved will be XDG_CACHE_HOME. * In this case the directory retrieved will be XDG_CACHE_HOME.
* *
* On Windows is the directory that serves as a common repository for * On Windows is the directory that serves as a common repository for
@ -1308,9 +1308,10 @@ g_get_user_cache_dir (void)
* Returns a directory that is unique to the current user on the local * Returns a directory that is unique to the current user on the local
* system. * system.
* *
* On UNIX platforms this is determined using the mechanisms described in * On UNIX platforms this is determined using the mechanisms described
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec"> * in the
* XDG Base Directory Specification</ulink>. This is the directory * [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
* This is the directory
* specified in the `XDG_RUNTIME_DIR` environment variable. * specified in the `XDG_RUNTIME_DIR` environment variable.
* In the case that this variable is not set, GLib will issue a warning * In the case that this variable is not set, GLib will issue a warning
* message to stderr and return the value of g_get_user_cache_dir(). * message to stderr and return the value of g_get_user_cache_dir().
@ -1893,9 +1894,9 @@ g_win32_get_system_data_dirs_for_module (void (*address_of_function)(void))
* Returns an ordered list of base directories in which to access * Returns an ordered list of base directories in which to access
* system-wide application data. * system-wide application data.
* *
* On UNIX platforms this is determined using the mechanisms described in * On UNIX platforms this is determined using the mechanisms described
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec"> * in the
* XDG Base Directory Specification</ulink> * [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec)
* In this case the list of directories retrieved will be XDG_DATA_DIRS. * In this case the list of directories retrieved will be XDG_DATA_DIRS.
* *
* On Windows the first elements in the list are the Application Data * On Windows the first elements in the list are the Application Data
@ -1960,10 +1961,10 @@ g_get_system_data_dirs (void)
* Returns an ordered list of base directories in which to access * Returns an ordered list of base directories in which to access
* system-wide configuration information. * system-wide configuration information.
* *
* On UNIX platforms this is determined using the mechanisms described in * On UNIX platforms this is determined using the mechanisms described
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec"> * in the
* XDG Base Directory Specification</ulink>. * [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
* In this case the list of directories retrieved will be XDG_CONFIG_DIRS. * In this case the list of directories retrieved will be `XDG_CONFIG_DIRS`.
* *
* On Windows is the directory that contains application data for all users. * On Windows is the directory that contains application data for all users.
* A typical path is C:\Documents and Settings\All Users\Application Data. * A typical path is C:\Documents and Settings\All Users\Application Data.

View File

@ -34,11 +34,11 @@
* @short_description: introduction to the GVariant type system * @short_description: introduction to the GVariant type system
* @see_also: #GVariantType, #GVariant * @see_also: #GVariantType, #GVariant
* *
* This section introduces the GVariant type system. It is based, in * This section introduces the GVariant type system. It is based, in
* large part, on the D-Bus type system, with two major changes and some minor * large part, on the D-Bus type system, with two major changes and
* lifting of restrictions. The <ulink * some minor lifting of restrictions. The
* url='http://dbus.freedesktop.org/doc/dbus-specification.html'>DBus * [D-Bus specification](http://dbus.freedesktop.org/doc/dbus-specification.html),
* specification</ulink>, therefore, provides a significant amount of * therefore, provides a significant amount of
* information that is useful when working with GVariant. * information that is useful when working with GVariant.
* *
* The first major change with respect to the D-Bus type system is the * The first major change with respect to the D-Bus type system is the

View File

@ -1368,8 +1368,8 @@ va_to_ffi_type (GType gtype,
* marshaller, see g_closure_set_marshal() and * marshaller, see g_closure_set_marshal() and
* g_closure_set_meta_marshal() * g_closure_set_meta_marshal()
* *
* A generic marshaller function implemented via <ulink * A generic marshaller function implemented via
* url="http://sourceware.org/libffi/">libffi</ulink>. * [libffi](http://sourceware.org/libffi/).
* *
* Since: 2.30 * Since: 2.30
*/ */