From 82b6e49bd75b044069cb4d953de9bdcf3dc9ae01 Mon Sep 17 00:00:00 2001 From: Murray Cumming Date: Thu, 24 Mar 2011 10:07:36 +0100 Subject: Documentation: Change DBus to D-Bus. * glib/src/varianttype.hg: Use the correct name for D-Bus. I made the same change in the C documentation. --- ChangeLog | 7 +++++++ glib/src/varianttype.hg | 12 ++++++------ 2 files changed, 13 insertions(+), 6 deletions(-) diff --git a/ChangeLog b/ChangeLog index a63552b7..4970af67 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,10 @@ +2011-03-24 Murray Cumming + + Documentation: Change DBus to D-Bus. + + * glib/src/varianttype.hg: Use the correct name for D-Bus. + I made the same change in the C documentation. + 2011-03-24 Murray Cumming Variant: Improved the documentation, based on the C documentation. diff --git a/glib/src/varianttype.hg b/glib/src/varianttype.hg index 73136ea5..f59e018a 100644 --- a/glib/src/varianttype.hg +++ b/glib/src/varianttype.hg @@ -29,13 +29,13 @@ namespace Glib { /** VariantType - The VariantBase type system. - * The VariantBase type system is based, in large part, on the DBus type + * The VariantBase type system is based, in large part, on the D-Bus type * system, with two major changes and some minor lifting of restrictions. The - * DBus specification, therefore, provides a significant amount of + * D-Bus specification, therefore, provides a significant amount of * information that is useful when working with VariantBase. * - * The first major change with respect to the DBus type system is the + * The first major change with respect to the D-Bus type system is the * introduction of maybe (or "nullable") types. Any type in VariantBase * can be converted to a maybe type, in which case, "nothing" (or "null") * becomes a valid value. Maybe types have been added by introducing the @@ -44,7 +44,7 @@ namespace Glib * The second major change is that the VariantBase type system supports * the concept of "indefinite types" -- types that are less specific than the * normal types found in DBus. For example, it is possible to speak of "an - * array of any type" in VariantBase, where the DBus type system would + * array of any type" in VariantBase, where the D-Bus type system would * require you to speak of "an array of integers" or "an array of strings". * Indefinite types have been added by introducing the characters "*", "?" and * "r" to type strings. @@ -55,12 +55,12 @@ namespace Glib * * Just as in DBus, VariantBase types are described with strings ("type * strings"). Subject to the differences mentioned above, these strings are of - * the same form as those found in DBus. Note, however: DBus always works in + * the same form as those found in DBus. Note, however: D-Bus always works in * terms of messages and therefore individual type strings appear nowhere in * its interface. Instead, "signatures" are a concatenation of the strings of * the type of each argument in a message. VariantBase deals with single * values directly so VariantBase type strings always describe the type - * of exactly one value. This means that a DBus signature string is generally + * of exactly one value. This means that a D-Bus signature string is generally * not a valid VariantBase type string -- except in the case that it is * the signature of a message containing exactly one argument. * -- cgit v1.2.1