mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2024-11-09 19:06:15 +01:00
Convert external links to markdown syntax
This commit is contained in:
Matthias Clasen
parent
0cc20b7e0b
commit
cb588d4532
@ -981,9 +981,8 @@ g_app_launch_context_get_display (GAppLaunchContext *context,
|
||||
* Initiates startup notification for the application and returns the
|
||||
* `DESKTOP_STARTUP_ID` for the launched operation, if supported.
|
||||
*
|
||||
* Startup notification IDs are defined in the <ulink
|
||||
* url="http://standards.freedesktop.org/startup-notification-spec/startup-notification-latest.txt">
|
||||
* FreeDesktop.Org Startup Notifications standard</ulink>.
|
||||
* Startup notification IDs are defined in the
|
||||
* [FreeDesktop.Org Startup Notifications standard](http://standards.freedesktop.org/startup-notification-spec/startup-notification-latest.txt").
|
||||
*
|
||||
* Returns: a startup notification ID for the application, or %NULL if
|
||||
* not supported.
|
||||
|
||||
@ -89,7 +89,7 @@
|
||||
*
|
||||
* If used, the expected form of an application identifier is very close
|
||||
* 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".
|
||||
* For details on valid application identifiers, see g_application_id_is_valid().
|
||||
*
|
||||
|
||||
@ -102,7 +102,8 @@
|
||||
* 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
|
||||
* split between the launcher and the primary instance.
|
||||
@ -152,7 +153,8 @@
|
||||
* options are passed to the #GApplication::command-line handler
|
||||
* 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
|
||||
* be better to defer it.
|
||||
@ -193,7 +195,8 @@
|
||||
* later (in this example, in an idle). Note that it is necessary to
|
||||
* 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)
|
||||
*/
|
||||
|
||||
/**
|
||||
|
||||
@ -40,7 +40,9 @@
|
||||
* @include: gio/gio.h
|
||||
*
|
||||
* 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
|
||||
* string like "audio". Such strings can be looked up in the registry at
|
||||
* 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.
|
||||
*
|
||||
* 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.
|
||||
*
|
||||
* 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.
|
||||
* 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.
|
||||
*
|
||||
* This function is useful in the implementation of
|
||||
|
||||
@ -208,11 +208,11 @@ g_dbus_interface_skeleton_class_init (GDBusInterfaceSkeletonClass *klass)
|
||||
*
|
||||
* Note that this signal is emitted in a thread dedicated to
|
||||
* handling the method call so handlers are allowed to perform
|
||||
* blocking IO. This means that it is appropriate to call
|
||||
* e.g. <ulink
|
||||
* url="http://hal.freedesktop.org/docs/polkit/PolkitAuthority.html#polkit-authority-check-authorization-sync">polkit_authority_check_authorization_sync()</ulink>
|
||||
* with the <ulink
|
||||
* 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.
|
||||
* blocking IO. This means that it is appropriate to call e.g.
|
||||
* [polkit_authority_check_authorization_sync()](http://hal.freedesktop.org/docs/polkit/PolkitAuthority.html#polkit-authority-check-authorization-sync)
|
||||
* with the
|
||||
* [POLKIT_CHECK_AUTHORIZATION_FLAGS_ALLOW_USER_INTERACTION](http://hal.freedesktop.org/docs/polkit/PolkitAuthority.html#POLKIT-CHECK-AUTHORIZATION-FLAGS-ALLOW-USER-INTERACTION:CAPS)
|
||||
* flag set.
|
||||
*
|
||||
* If %FALSE is returned then no further handlers are run and the
|
||||
* signal handler must take a reference to @invocation and finish
|
||||
|
||||
@ -38,7 +38,7 @@
|
||||
* used when registering objects with g_dbus_connection_register_object().
|
||||
*
|
||||
* 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)
|
||||
*/
|
||||
|
||||
/* ---------------------------------------------------------------------------------------------------- */
|
||||
|
||||
@ -33,8 +33,8 @@
|
||||
* @include: gio/gio.h
|
||||
*
|
||||
* The #GDBusObjectManager type is the base type for service- and
|
||||
* client-side implementations of the standardized <ulink
|
||||
* url="http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager">org.freedesktop.DBus.ObjectManager</ulink>
|
||||
* client-side implementations of the standardized
|
||||
* [org.freedesktop.DBus.ObjectManager](http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager)
|
||||
* interface.
|
||||
*
|
||||
* See #GDBusObjectManagerClient for the client-side implementation
|
||||
|
||||
@ -45,8 +45,8 @@
|
||||
*
|
||||
* #GDBusObjectManagerClient is used to create, monitor and delete object
|
||||
* proxies for remote objects exported by a #GDBusObjectManagerServer (or any
|
||||
* code implementing the <ulink
|
||||
* url="http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager">org.freedesktop.DBus.ObjectManager</ulink>
|
||||
* code implementing the
|
||||
* [org.freedesktop.DBus.ObjectManager](http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager)
|
||||
* interface).
|
||||
*
|
||||
* Once an instance of this type has been created, you can connect to
|
||||
|
||||
@ -38,8 +38,8 @@
|
||||
* @include: gio/gio.h
|
||||
*
|
||||
* #GDBusObjectManagerServer is used to export #GDBusObject instances using
|
||||
* the standardized <ulink
|
||||
* url="http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager">org.freedesktop.DBus.ObjectManager</ulink>
|
||||
* the standardized
|
||||
* [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
|
||||
* and properties in a single call. Additionally, any change in the
|
||||
* object hierarchy is broadcast using signals. This means that D-Bus
|
||||
|
||||
@ -372,9 +372,10 @@ g_dbus_proxy_class_init (GDBusProxyClass *klass)
|
||||
*
|
||||
* - Properties received via the initial <literal>GetAll()</literal> call
|
||||
* 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
|
||||
* set using g_dbus_proxy_set_cached_property() with a type signature
|
||||
* mismatch are ignored and a warning is logged via g_warning().
|
||||
* [org.freedesktop.DBus.Properties](http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties)
|
||||
* interface) or set using g_dbus_proxy_set_cached_property()
|
||||
* 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
|
||||
* properties that are not referenced in the given
|
||||
|
||||
@ -58,7 +58,7 @@
|
||||
* #GDesktopAppInfo is an implementation of #GAppInfo based on
|
||||
* desktop files.
|
||||
*
|
||||
* Note that `<gio/gdesktopappinfo.h>` belongs to the UNIX-specific
|
||||
* Note that `<gio/gdesktopappinfo.h>` belongs to the UNIX-specific
|
||||
* GIO interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
|
||||
* 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`
|
||||
* and `XDG_DATA_DIRS` environment variables). GIO also supports the
|
||||
* prefix-to-subdirectory mapping that is described in the
|
||||
* <ulink url="http://standards.freedesktop.org/menu-spec/latest/">Menu
|
||||
* Spec</ulink> (i.e. a desktop id of kde-foo.desktop will match
|
||||
* [Menu Spec](http://standards.freedesktop.org/menu-spec/latest/)
|
||||
* (i.e. a desktop id of kde-foo.desktop will match
|
||||
* `/usr/share/applications/kde/foo.desktop`).
|
||||
*
|
||||
* 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>
|
||||
* desktop entry fields.
|
||||
*
|
||||
* The <ulink url="http://standards.freedesktop.org/menu-spec/latest/">Desktop
|
||||
* Menu specification</ulink> recognizes the following:
|
||||
* The
|
||||
* [Desktop Menu specification](http://standards.freedesktop.org/menu-spec/latest/)
|
||||
* recognizes the following:
|
||||
* <simplelist>
|
||||
* <member>GNOME</member>
|
||||
* <member>KDE</member>
|
||||
@ -3126,8 +3127,8 @@ g_desktop_app_info_delete (GAppInfo *appinfo)
|
||||
* Creates a new #GAppInfo from the given information.
|
||||
*
|
||||
* 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
|
||||
* Entry Specification</ulink> are applied. For example, if the @commandline contains
|
||||
* [freedesktop.org Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec)
|
||||
* are applied. For example, if the @commandline contains
|
||||
* 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.
|
||||
*
|
||||
|
||||
@ -142,7 +142,8 @@
|
||||
* short. Entity tags are somewhat like a more abstract version of the
|
||||
* traditional mtime, and can be used to quickly determine if the file
|
||||
* 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.
|
||||
* </para>
|
||||
**/
|
||||
|
||||
@ -32,7 +32,7 @@
|
||||
* #GFileDescriptorBased is implemented by streams (implementations of
|
||||
* #GInputStream or #GOutputStream) that are based on file descriptors.
|
||||
*
|
||||
* Note that `<gio/gfiledescriptorbased.h>` belongs to the UNIX-specific
|
||||
* Note that `<gio/gfiledescriptorbased.h>` belongs to the UNIX-specific
|
||||
* GIO interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
|
||||
* file when using it.
|
||||
*
|
||||
|
||||
@ -767,7 +767,8 @@ g_mount_remount_finish (GMount *mount,
|
||||
* Tries to guess the type of content stored on @mount. Returns one or
|
||||
* more textual identifiers of well-known content types (typically
|
||||
* 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.
|
||||
*
|
||||
* 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
|
||||
* more textual identifiers of well-known content types (typically
|
||||
* 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.
|
||||
*
|
||||
* This is an synchronous operation and as such may block doing IO;
|
||||
|
||||
@ -95,7 +95,8 @@
|
||||
* by the <link linkend="glib-compile-schemas">glib-compile-schemas</link>
|
||||
* 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>
|
||||
* tool expects schema files to have the extension `.gschema.xml`.
|
||||
|
||||
@ -361,7 +361,8 @@ _g_test_watcher_remove_pid (GPid pid)
|
||||
* 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
|
||||
* 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
|
||||
* service. To successfully run isolated unit tests on your service you may need
|
||||
|
||||
@ -39,7 +39,7 @@
|
||||
* It contains functions to do some of the UNIX socket specific
|
||||
* functionality like passing file descriptors.
|
||||
*
|
||||
* Note that `<gio/gunixconnection.h>` belongs to the UNIX-specific
|
||||
* Note that `<gio/gunixconnection.h>` belongs to the UNIX-specific
|
||||
* GIO interfaces, thus you have to use the `gio-unix-2.0.pc`
|
||||
* pkg-config file when using it.
|
||||
*
|
||||
|
||||
@ -26,7 +26,7 @@
|
||||
* the %G_SOCKET_ADDRESS_UNIX family by using g_socket_send_message()
|
||||
* and received using g_socket_receive_message().
|
||||
*
|
||||
* Note that `<gio/gunixfdlist.h>` belongs to the UNIX-specific GIO
|
||||
* Note that `<gio/gunixfdlist.h>` belongs to the UNIX-specific GIO
|
||||
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
|
||||
* file when using it.
|
||||
*/
|
||||
|
||||
@ -29,7 +29,7 @@
|
||||
* stream-oriented UNIX sockets, see g_unix_connection_send_fd() and
|
||||
* g_unix_connection_receive_fd().
|
||||
*
|
||||
* Note that `<gio/gunixfdmessage.h>` belongs to the UNIX-specific GIO
|
||||
* Note that `<gio/gunixfdmessage.h>` belongs to the UNIX-specific GIO
|
||||
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
|
||||
* file when using it.
|
||||
*/
|
||||
|
||||
@ -51,7 +51,7 @@
|
||||
* asynchronous I/O. If it refers to a regular file, it will fall back
|
||||
* to doing asynchronous I/O in another thread.)
|
||||
*
|
||||
* Note that `<gio/gunixinputstream.h>` belongs to the UNIX-specific GIO
|
||||
* Note that `<gio/gunixinputstream.h>` belongs to the UNIX-specific GIO
|
||||
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
|
||||
* file when using it.
|
||||
*/
|
||||
|
||||
@ -79,7 +79,7 @@ static const char *_resolve_dev_root (void);
|
||||
*
|
||||
* Routines for managing mounted UNIX mount points and paths.
|
||||
*
|
||||
* Note that `<gio/gunixmounts.h>` belongs to the UNIX-specific GIO
|
||||
* Note that `<gio/gunixmounts.h>` belongs to the UNIX-specific GIO
|
||||
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config
|
||||
* file when using it.
|
||||
*/
|
||||
|
||||
@ -51,7 +51,7 @@
|
||||
* asynchronous I/O. If it refers to a regular file, it will fall back
|
||||
* to doing asynchronous I/O in another thread.)
|
||||
*
|
||||
* Note that `<gio/gunixoutputstream.h>` belongs to the UNIX-specific GIO
|
||||
* Note that `<gio/gunixoutputstream.h>` belongs to the UNIX-specific GIO
|
||||
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config file
|
||||
* when using it.
|
||||
*/
|
||||
|
||||
@ -44,7 +44,7 @@
|
||||
* errors. You can use g_unix_socket_address_abstract_names_supported()
|
||||
* to see if abstract names are supported.
|
||||
*
|
||||
* Note that `<gio/gunixsocketaddress.h>` belongs to the UNIX-specific GIO
|
||||
* Note that `<gio/gunixsocketaddress.h>` belongs to the UNIX-specific GIO
|
||||
* interfaces, thus you have to use the `gio-unix-2.0.pc` pkg-config file
|
||||
* when using it.
|
||||
*/
|
||||
|
||||
@ -44,7 +44,7 @@
|
||||
* #GWin32InputStream implements #GInputStream for reading from a
|
||||
* Windows file handle.
|
||||
*
|
||||
* Note that `<gio/gwin32inputstream.h>` belongs to the Windows-specific GIO
|
||||
* Note that `<gio/gwin32inputstream.h>` belongs to the Windows-specific GIO
|
||||
* interfaces, thus you have to use the `gio-windows-2.0.pc` pkg-config file
|
||||
* when using it.
|
||||
*/
|
||||
|
||||
@ -45,7 +45,7 @@
|
||||
* #GWin32OutputStream implements #GOutputStream for writing to a
|
||||
* Windows file handle.
|
||||
*
|
||||
* Note that `<gio/gwin32outputstream.h>` belongs to the Windows-specific GIO
|
||||
* Note that `<gio/gwin32outputstream.h>` belongs to the Windows-specific GIO
|
||||
* interfaces, thus you have to use the `gio-windows-2.0.pc` pkg-config file
|
||||
* when using it.
|
||||
*/
|
||||
|
||||
@ -1428,7 +1428,7 @@
|
||||
* sign, mantissa and exponent of IEEE floats and doubles. These unions 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
|
||||
* <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.
|
||||
*/
|
||||
|
||||
|
||||
@ -37,9 +37,11 @@
|
||||
*
|
||||
* Base64 is an encoding that allows a sequence of arbitrary bytes to be
|
||||
* encoded as a sequence of printable ASCII characters. For the definition
|
||||
* of Base64, see <ulink url="http://www.ietf.org/rfc/rfc1421.txt">RFC
|
||||
* 1421</ulink> or <ulink url="http://www.ietf.org/rfc/rfc2045.txt">RFC
|
||||
* 2045</ulink>. Base64 is most commonly used as a MIME transfer encoding
|
||||
* of Base64, see
|
||||
* [RFC 1421](http://www.ietf.org/rfc/rfc1421.txt)
|
||||
* or
|
||||
* [RFC 2045](http://www.ietf.org/rfc/rfc2045.txt).
|
||||
* Base64 is most commonly used as a MIME transfer encoding
|
||||
* for email.
|
||||
*
|
||||
* GLib supports incremental encoding using g_base64_encode_step() and
|
||||
|
||||
@ -60,13 +60,12 @@
|
||||
* 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
|
||||
* using the
|
||||
* <ulink url="http://www.gnome.org/~ebassi/bookmark-spec">Desktop Bookmark
|
||||
* Specification</ulink>.
|
||||
* [Desktop Bookmark Specification](http://www.gnome.org/~ebassi/bookmark-spec).
|
||||
*
|
||||
* The syntax of the bookmark files is described in detail inside the Desktop
|
||||
* Bookmark Specification, here is a quick summary: bookmark files use a
|
||||
* sub-class of the <ulink url="">XML Bookmark Exchange Language</ulink>
|
||||
* specification, consisting of valid UTF-8 encoded XML, under the
|
||||
* sub-class of the XML Bookmark Exchange Language specification,
|
||||
* consisting of valid UTF-8 encoded XML, under the
|
||||
* <literal>xbel</literal> root element; each bookmark is stored inside a
|
||||
* <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
|
||||
@ -80,7 +79,8 @@
|
||||
* registered; the URI and MIME type of an icon, to be used when displaying
|
||||
* 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
|
||||
* is accessed through its URI.
|
||||
|
||||
@ -126,7 +126,8 @@
|
||||
* a more secure hash function when using a GHashTable with keys
|
||||
* that originate in untrusted data (such as HTTP requests).
|
||||
* 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
|
||||
* cryptographic hashes are very easy to find collisions for when the
|
||||
|
||||
@ -42,7 +42,8 @@
|
||||
* 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
|
||||
* 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
|
||||
* key and data.
|
||||
*
|
||||
|
||||
@ -38,9 +38,9 @@
|
||||
* converting between Unicode and ASCII-encoded forms of
|
||||
* Internationalized Domain Names (IDNs).
|
||||
*
|
||||
* The <ulink
|
||||
* url="http://www.ietf.org/rfc/rfc3490.txt">Internationalized Domain
|
||||
* Names for Applications (IDNA)</ulink> standards allow for the use
|
||||
* The
|
||||
* [Internationalized Domain Names for Applications (IDNA)](http://www.ietf.org/rfc/rfc3490.txt)
|
||||
* standards allow for the use
|
||||
* of Unicode domain names in applications, while providing
|
||||
* backward-compatibility with the old ASCII-only DNS, by defining an
|
||||
* ASCII-Compatible Encoding of any given Unicode name, which can be
|
||||
|
||||
@ -77,14 +77,13 @@
|
||||
* key-value pairs, which we call <firstterm>key files</firstterm> for
|
||||
* lack of a better name. Several freedesktop.org specifications use
|
||||
* key files now, e.g the
|
||||
* <ulink url="http://freedesktop.org/Standards/desktop-entry-spec">Desktop
|
||||
* Entry Specification</ulink> and the
|
||||
* <ulink url="http://freedesktop.org/Standards/icon-theme-spec">Icon
|
||||
* Theme Specification</ulink>.
|
||||
* [Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec)
|
||||
* and the
|
||||
* [Icon Theme Specification](http://freedesktop.org/Standards/icon-theme-spec).
|
||||
*
|
||||
* The syntax of key files is described in detail in the
|
||||
* <ulink url="http://freedesktop.org/Standards/desktop-entry-spec">Desktop
|
||||
* Entry Specification</ulink>, here is a quick summary: Key files
|
||||
* [Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec),
|
||||
* here is a quick summary: Key files
|
||||
* consists of groups of key-value pairs, interspersed with comments.
|
||||
*
|
||||
* |[
|
||||
@ -150,8 +149,8 @@
|
||||
* true and false (in lower case) are allowed.
|
||||
*
|
||||
* Note that in contrast to the
|
||||
* <ulink url="http://freedesktop.org/Standards/desktop-entry-spec">Desktop
|
||||
* Entry Specification</ulink>, groups in key files may contain the same
|
||||
* [Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec),
|
||||
* groups in key files may contain the same
|
||||
* key multiple times; the last entry wins. Key files may also contain
|
||||
* multiple groups with the same name; they are merged together.
|
||||
* Another difference is that keys and group names in key files are not
|
||||
@ -199,8 +198,8 @@
|
||||
* G_KEY_FILE_DESKTOP_GROUP:
|
||||
*
|
||||
* 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
|
||||
* Entry Specification</ulink>. Consult the specification for more
|
||||
* [Desktop Entry Specification](http://freedesktop.org/Standards/desktop-entry-spec).
|
||||
* Consult the specification for more
|
||||
* details about the meanings of the keys below.
|
||||
*
|
||||
* Since: 2.14
|
||||
@ -368,9 +367,8 @@
|
||||
* G_KEY_FILE_DESKTOP_KEY_STARTUP_NOTIFY:
|
||||
*
|
||||
* A key under #G_KEY_FILE_DESKTOP_GROUP, whose value is a boolean
|
||||
* stating whether the application supports the <ulink
|
||||
* url="http://www.freedesktop.org/Standards/startup-notification-spec">Startup
|
||||
* Notification Protocol Specification</ulink>.
|
||||
* stating whether the application supports the
|
||||
* [Startup Notification Protocol Specification](http://www.freedesktop.org/Standards/startup-notification-spec).
|
||||
*
|
||||
* Since: 2.14
|
||||
*/
|
||||
|
||||
@ -40,8 +40,7 @@
|
||||
/**
|
||||
* SECTION:markup
|
||||
* @Title: Simple XML Subset Parser * @Short_description: parses a subset of XML
|
||||
* @See_also: <ulink url="http://www.w3.org/TR/REC-xml/">XML
|
||||
* Specification</ulink>
|
||||
* @See_also: [XML Specification](http://www.w3.org/TR/REC-xml/)
|
||||
*
|
||||
* 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
|
||||
@ -57,8 +56,9 @@
|
||||
* the parser may accept documents that an XML parser would not.
|
||||
* However, XML documents which are not well-formed (which is a
|
||||
* weaker condition than being valid. See the
|
||||
* <ulink url="http://www.w3.org/TR/REC-xml/">XML specification</ulink>
|
||||
* for definitions of these terms.) are not considered valid GMarkup documents.
|
||||
* [XML specification](http://www.w3.org/TR/REC-xml/)
|
||||
* for definitions of these terms.) are not considered valid GMarkup
|
||||
* documents.
|
||||
*
|
||||
* Simplifications to XML include:
|
||||
*
|
||||
|
||||
@ -174,8 +174,8 @@
|
||||
* A convenience function/macro to log a warning message.
|
||||
*
|
||||
* You can make warnings fatal at runtime by setting the `G_DEBUG`
|
||||
* environment variable (see <ulink url="glib-running.html">Running
|
||||
* GLib Applications</ulink>).
|
||||
* environment variable (see
|
||||
* [Running GLib Applications](glib-running.html)).
|
||||
*
|
||||
* If g_log_default_handler() is used as the log handler function,
|
||||
* a newline character will automatically be appended to @..., and
|
||||
@ -196,7 +196,7 @@
|
||||
*
|
||||
* You can also make critical warnings fatal at runtime by
|
||||
* 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
|
||||
* 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
|
||||
* 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
|
||||
*/
|
||||
|
||||
@ -78,9 +78,8 @@
|
||||
*
|
||||
* GRand uses the Mersenne Twister PRNG, which was originally
|
||||
* developed by Makoto Matsumoto and Takuji Nishimura. Further
|
||||
* information can be found at <ulink
|
||||
* url="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>.
|
||||
* information can be found at
|
||||
* [this page](http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html).
|
||||
*
|
||||
* If you just need a random number, you simply call the g_random_*
|
||||
* functions, which will create a globally used #GRand and use the
|
||||
|
||||
@ -98,7 +98,7 @@
|
||||
* '\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
|
||||
* 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
|
||||
* threads is not a problem as #GRegex does not modify its internal
|
||||
@ -106,8 +106,9 @@
|
||||
* is not threadsafe.
|
||||
*
|
||||
* The regular expressions low-level functionalities are obtained through
|
||||
* the excellent <ulink url="http://www.pcre.org/">PCRE</ulink> library
|
||||
* written by Philip Hazel.
|
||||
* the excellent
|
||||
* [PCRE](http://www.pcre.org/)
|
||||
* library written by Philip Hazel.
|
||||
*/
|
||||
|
||||
/* 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.
|
||||
* 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
|
||||
*
|
||||
|
||||
@ -66,9 +66,11 @@
|
||||
*
|
||||
* To achieve these goals, the slice allocator uses a sophisticated,
|
||||
* 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
|
||||
* <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)
|
||||
*
|
||||
* It uses posix_memalign() to optimize allocations of many equally-sized
|
||||
|
||||
@ -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".
|
||||
*
|
||||
* This corresponds to the Internet date/time format defined by
|
||||
* <ulink url="https://www.ietf.org/rfc/rfc3339.txt">RFC 3339</ulink>, and
|
||||
* to either of the two most-precise formats defined by
|
||||
* <ulink url="http://www.w3.org/TR/NOTE-datetime-19980827">the W3C Note
|
||||
* "Date and Time Formats"</ulink>. Both of these documents are profiles of
|
||||
* ISO 8601.
|
||||
* [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt),
|
||||
* and to either of the two most-precise formats defined by
|
||||
* the W3C Note
|
||||
* [Date and Time Formats](http://www.w3.org/TR/NOTE-datetime-19980827).
|
||||
* Both of these documents are profiles of ISO 8601.
|
||||
*
|
||||
* Use g_date_time_format() or g_strdup_printf() if a different
|
||||
* variation of ISO 8601 format is required.
|
||||
|
||||
@ -1351,17 +1351,16 @@ rules_from_identifier (const gchar *identifier,
|
||||
* available and it is greater than 2037, then it will followed
|
||||
* instead.
|
||||
*
|
||||
* See <ulink
|
||||
* url='http://tools.ietf.org/html/rfc3339#section-5.6'>RFC3339
|
||||
* §5.6</ulink> for a precise definition of valid RFC3339 time offsets
|
||||
* See
|
||||
* [RFC3339 §5.6](http://tools.ietf.org/html/rfc3339#section-5.6)
|
||||
* for a precise definition of valid RFC3339 time offsets
|
||||
* (the <literal>time-offset</literal> expansion) and ISO 8601 for the
|
||||
* full list of valid time offsets. See <ulink
|
||||
* url='http://www.gnu.org/s/libc/manual/html_node/TZ-Variable.html'>The
|
||||
* GNU C Library manual</ulink> for an explanation of the possible
|
||||
* values of the `TZ` environment variable. See <ulink
|
||||
* url='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
|
||||
* on Windows.
|
||||
* full list of valid time offsets. See
|
||||
* [The GNU C Library manual](http://www.gnu.org/s/libc/manual/html_node/TZ-Variable.html)
|
||||
* for an explanation of the possible
|
||||
* values of the `TZ` environment variable. See
|
||||
* [Microsoft Time Zone Index Values](http://msdn.microsoft.com/en-us/library/ms912391%28v=winembedded.11%29.aspx)
|
||||
* for the list of time zones on Windows.
|
||||
*
|
||||
* You should release the return value by calling g_time_zone_unref()
|
||||
* when you are done with it.
|
||||
|
||||
@ -35,7 +35,7 @@
|
||||
*
|
||||
* The implementations of the Unicode functions in GLib are based
|
||||
* 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.12 supports Unicode 5.0, GLib 2.16.3 supports Unicode 5.1,
|
||||
* GLib 2.30 supports Unicode 6.0.
|
||||
@ -595,7 +595,8 @@ decompose_hangul_step (gunichar ch,
|
||||
* recursively call this function on @a. Or use
|
||||
* 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.
|
||||
*
|
||||
* 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.
|
||||
*
|
||||
* See <ulink url="http://unicode.org/reports/tr15/">UAX#15</ulink>
|
||||
* See
|
||||
* [UAX#15](http://unicode.org/reports/tr15/)
|
||||
* for details.
|
||||
*
|
||||
* 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
|
||||
* 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.
|
||||
*
|
||||
* Return value: the length of the full decomposition.
|
||||
|
||||
@ -492,9 +492,9 @@ g_unichar_iswide (gunichar c)
|
||||
* Determines if a character is typically rendered in a double-width
|
||||
* 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
|
||||
* the converse is not necessarily true. See the
|
||||
* <ulink url="http://www.unicode.org/reports/tr11/">Unicode Standard
|
||||
* Annex #11</ulink> for details.
|
||||
* the converse is not necessarily true. See the
|
||||
* [Unicode Standard Annex #11](http://www.unicode.org/reports/tr11/)
|
||||
* for details.
|
||||
*
|
||||
* 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
|
||||
@ -1454,8 +1454,9 @@ static const guint32 iso15924_tags[] =
|
||||
* 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).
|
||||
*
|
||||
* See <ulink url="http://unicode.org/iso15924/codelists.html">Codes for the
|
||||
* representation of names of scripts</ulink> for details.
|
||||
* See
|
||||
* [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,
|
||||
* 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
|
||||
* 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
|
||||
* representation of names of scripts</ulink> for details.
|
||||
* See
|
||||
* [Codes for the representation of names of scripts](http://unicode.org/iso15924/codelists.html)
|
||||
* for details.
|
||||
*
|
||||
* Return value: the Unicode script for @iso15924, or
|
||||
* of %G_UNICODE_SCRIPT_INVALID_CODE if @iso15924 is zero and
|
||||
|
||||
@ -37,8 +37,9 @@
|
||||
* @short_description: manipulating URIs
|
||||
*
|
||||
* Functions for manipulating Universal Resource Identifiers (URIs) as
|
||||
* defined by <ulink url="http://www.ietf.org/rfc/rfc3986.txt">
|
||||
* RFC 3986</ulink>. It is highly recommended that you have read and
|
||||
* defined by
|
||||
* [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.
|
||||
*/
|
||||
|
||||
|
||||
@ -1134,10 +1134,10 @@ g_set_application_name (const gchar *application_name)
|
||||
* Returns a base directory in which to access application data such
|
||||
* as icons that is customized for a particular user.
|
||||
*
|
||||
* On UNIX platforms this is determined using the mechanisms described in
|
||||
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec">
|
||||
* XDG Base Directory Specification</ulink>.
|
||||
* In this case the directory retrieved will be XDG_DATA_HOME.
|
||||
* On UNIX platforms this is determined using the mechanisms described
|
||||
* in the
|
||||
* [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
|
||||
* In this case the directory retrieved will be `XDG_DATA_HOME`.
|
||||
*
|
||||
* On Windows this is the folder to use for local (as opposed to
|
||||
* 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
|
||||
* configuration information such as user preferences and settings.
|
||||
*
|
||||
* On UNIX platforms this is determined using the mechanisms described in
|
||||
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec">
|
||||
* XDG Base Directory Specification</ulink>.
|
||||
* In this case the directory retrieved will be XDG_CONFIG_HOME.
|
||||
* On UNIX platforms this is determined using the mechanisms described
|
||||
* in the
|
||||
* [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
|
||||
* In this case the directory retrieved will be `XDG_CONFIG_HOME`.
|
||||
*
|
||||
* On Windows this is the folder to use for local (as opposed to
|
||||
* 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
|
||||
* data specific to particular user.
|
||||
*
|
||||
* On UNIX platforms this is determined using the mechanisms described in
|
||||
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec">
|
||||
* XDG Base Directory Specification</ulink>.
|
||||
* On UNIX platforms this is determined using the mechanisms described
|
||||
* in the
|
||||
* [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
|
||||
* In this case the directory retrieved will be XDG_CACHE_HOME.
|
||||
*
|
||||
* 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
|
||||
* system.
|
||||
*
|
||||
* On UNIX platforms this is determined using the mechanisms described in
|
||||
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec">
|
||||
* XDG Base Directory Specification</ulink>. This is the directory
|
||||
* On UNIX platforms this is determined using the mechanisms described
|
||||
* in the
|
||||
* [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
|
||||
* This is the directory
|
||||
* specified in the `XDG_RUNTIME_DIR` environment variable.
|
||||
* 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().
|
||||
@ -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
|
||||
* system-wide application data.
|
||||
*
|
||||
* On UNIX platforms this is determined using the mechanisms described in
|
||||
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec">
|
||||
* XDG Base Directory Specification</ulink>
|
||||
* On UNIX platforms this is determined using the mechanisms described
|
||||
* in the
|
||||
* [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec)
|
||||
* 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
|
||||
@ -1960,10 +1961,10 @@ g_get_system_data_dirs (void)
|
||||
* Returns an ordered list of base directories in which to access
|
||||
* system-wide configuration information.
|
||||
*
|
||||
* On UNIX platforms this is determined using the mechanisms described in
|
||||
* the <ulink url="http://www.freedesktop.org/Standards/basedir-spec">
|
||||
* XDG Base Directory Specification</ulink>.
|
||||
* In this case the list of directories retrieved will be XDG_CONFIG_DIRS.
|
||||
* On UNIX platforms this is determined using the mechanisms described
|
||||
* in the
|
||||
* [XDG Base Directory Specification](http://www.freedesktop.org/Standards/basedir-spec).
|
||||
* 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.
|
||||
* A typical path is C:\Documents and Settings\All Users\Application Data.
|
||||
|
||||
@ -34,11 +34,11 @@
|
||||
* @short_description: introduction to the GVariant type system
|
||||
* @see_also: #GVariantType, #GVariant
|
||||
*
|
||||
* 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
|
||||
* lifting of restrictions. The <ulink
|
||||
* url='http://dbus.freedesktop.org/doc/dbus-specification.html'>DBus
|
||||
* specification</ulink>, therefore, provides a significant amount of
|
||||
* 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 lifting of restrictions. The
|
||||
* [D-Bus specification](http://dbus.freedesktop.org/doc/dbus-specification.html),
|
||||
* therefore, provides a significant amount of
|
||||
* information that is useful when working with GVariant.
|
||||
*
|
||||
* The first major change with respect to the D-Bus type system is the
|
||||
|
||||
@ -1368,8 +1368,8 @@ va_to_ffi_type (GType gtype,
|
||||
* marshaller, see g_closure_set_marshal() and
|
||||
* g_closure_set_meta_marshal()
|
||||
*
|
||||
* A generic marshaller function implemented via <ulink
|
||||
* url="http://sourceware.org/libffi/">libffi</ulink>.
|
||||
* A generic marshaller function implemented via
|
||||
* [libffi](http://sourceware.org/libffi/).
|
||||
*
|
||||
* Since: 2.30
|
||||
*/
|
||||
|
||||
Loading…
Reference in New Issue
Block a user