Commit 2a45418b authored by William Jon McCann's avatar William Jon McCann

docs: use proper quotes

parent c3dfb170
......@@ -494,7 +494,7 @@ find_item_label (GtkWidget *item)
/* This function returns a string of the form A;B;C where A is
* the keybinding for the widget; B is the keybinding to traverse
* from the menubar and C is the accelerator. The items in the
* keybinding to traverse from the menubar are separated by ":".
* keybinding to traverse from the menubar are separated by “:”.
*/
static const gchar *
gtk_menu_item_accessible_get_keybinding (AtkAction *action,
......
......@@ -456,7 +456,7 @@ gtk_widget_accessible_get_index_in_parent (AtkObject *accessible)
/* This function is the default implementation for the notify_gtk
* vfunc which gets called when a property changes value on the
* GtkWidget associated with a GtkWidgetAccessible. It constructs
* an AtkPropertyValues structure and emits a "property_changed"
* an AtkPropertyValues structure and emits a “property_changed”
* signal which causes the user specified AtkPropertyChangeHandler
* to be called.
*/
......
......@@ -68,7 +68,7 @@
* Apart from regular actions, there are <link linkend="GtkToggleAction">toggle
* actions</link>, which can be toggled between two states and <link
* linkend="GtkRadioAction">radio actions</link>, of which only one in a group
* can be in the "active" state. Other actions can be implemented as #GtkAction
* can be in the “active” state. Other actions can be implemented as #GtkAction
* subclasses.
*
* Each action can have one or more proxy widgets. To act as an action proxy,
......@@ -862,7 +862,7 @@ disconnect_proxy (GtkAction *action,
* - if @action is invisible, @proxy is too
*
* - if @empty is %TRUE, hide @proxy unless the "hide-if-empty"
* - if @empty is %TRUE, hide @proxy unless the “hide-if-empty”
* property of @action indicates otherwise
*
* This function is used in the implementation of #GtkUIManager.
......@@ -922,7 +922,7 @@ _gtk_action_emit_activate (GtkAction *action)
* gtk_action_activate:
* @action: the action object
*
* Emits the "activate" signal on the specified action, if it isn't
* Emits the “activate” signal on the specified action, if it isn't
* insensitive. This gets called by the proxy widgets when they get
* activated.
*
......
......@@ -1108,7 +1108,7 @@ gtk_action_group_list_actions (GtkActionGroup *action_group)
* This is a convenience function to create a number of actions and add them
* to the action group.
*
* The "activate" signals of the actions are connected to the callbacks and
* The “activate” signals of the actions are connected to the callbacks and
* their accel paths are set to
* `&lt;Actions&gt;/group-name/action-name`.
*
......@@ -1243,7 +1243,7 @@ gtk_action_group_add_actions_full (GtkActionGroup *action_group,
* This is a convenience function to create a number of toggle actions and add them
* to the action group.
*
* The "activate" signals of the actions are connected to the callbacks and
* The “activate” signals of the actions are connected to the callbacks and
* their accel paths are set to
* `&lt;Actions&gt;/group-name/action-name`.
*
......@@ -1363,7 +1363,7 @@ gtk_action_group_add_toggle_actions_full (GtkActionGroup *action_gro
* This is a convenience routine to create a group of radio actions and
* add them to the action group.
*
* The "changed" signal of the first radio action is connected to the
* The “changed” signal of the first radio action is connected to the
* @on_change callback and the accel paths of the actions are set to
* `&lt;Actions&gt;/group-name/action-name`.
*
......
......@@ -107,7 +107,7 @@
* G_OBJECT_CLASS (foo_bar_parent_class)->dispose (object);
* }
*
* ... Handle the "related-action" and "use-action-appearance" properties ...
* ... Handle the “related-action” and “use-action-appearance” properties ...
*
* static void
* foo_bar_set_property (GObject *object,
......
......@@ -55,8 +55,8 @@
*
* The GtkColorSelectionDialog implementation of the GtkBuildable interface
* exposes the embedded #GtkColorSelection as internal child with the
* name "color_selection". It also exposes the buttons with the names
* "ok_button", "cancel_button" and "help_button".
* name “color_selection”. It also exposes the buttons with the names
* “ok_button”, “cancel_button” and “help_button”.
*/
......
......@@ -1380,8 +1380,8 @@ gtk_font_selection_get_size (GtkFontSelection *fontsel)
* Note that this can be a different string than what you set with
* gtk_font_selection_set_font_name(), as the font selection widget may
* normalize font names and thus return a string with a different structure.
* For example, "Helvetica Italic Bold 12" could be normalized to
* "Helvetica Bold Italic 12". Use pango_font_description_equal()
* For example, “Helvetica Italic Bold 12” could be normalized to
* “Helvetica Bold Italic 12”. Use pango_font_description_equal()
* if you want to compare two font descriptions.
*
* Return value: A string with the name of the current font, or %NULL if
......@@ -1510,7 +1510,7 @@ gtk_font_selection_select_font_desc (GtkFontSelection *fontsel,
/**
* gtk_font_selection_set_font_name:
* @fontsel: a #GtkFontSelection
* @fontname: a font name like "Helvetica 12" or "Times Bold 18"
* @fontname: a font name like “Helvetica 12” or “Times Bold 18”
*
* Sets the currently-selected font.
*
......@@ -1630,8 +1630,8 @@ gtk_font_selection_set_preview_text (GtkFontSelection *fontsel,
*
* The GtkFontSelectionDialog implementation of the GtkBuildable interface
* exposes the embedded #GtkFontSelection as internal child with the
* name "font_selection". It also exposes the buttons with the names
* "ok_button", "cancel_button" and "apply_button".
* name “font_selection”. It also exposes the buttons with the names
* “ok_button”, “cancel_button” and “apply_button”.
*/
static void gtk_font_selection_dialog_buildable_interface_init (GtkBuildableIface *iface);
......@@ -1834,8 +1834,8 @@ gtk_font_selection_dialog_buildable_get_internal_child (GtkBuildable *buildable,
* Note that this can be a different string than what you set with
* gtk_font_selection_dialog_set_font_name(), as the font selection widget
* may normalize font names and thus return a string with a different
* structure. For example, "Helvetica Italic Bold 12" could be normalized
* to "Helvetica Bold Italic 12". Use pango_font_description_equal()
* structure. For example, “Helvetica Italic Bold 12” could be normalized
* to “Helvetica Bold Italic 12”. Use pango_font_description_equal()
* if you want to compare two font descriptions.
*
* Return value: A string with the name of the current font, or %NULL if no
......@@ -1858,7 +1858,7 @@ gtk_font_selection_dialog_get_font_name (GtkFontSelectionDialog *fsd)
/**
* gtk_font_selection_dialog_set_font_name:
* @fsd: a #GtkFontSelectionDialog
* @fontname: a font name like "Helvetica 12" or "Times Bold 18"
* @fontname: a font name like “Helvetica 12” or “Times Bold 18”
*
* Sets the currently selected font.
*
......
......@@ -145,7 +145,7 @@ enum {
* of the drag offset by the distance that the cursor
* has moved.
*
* 2) These rectangles must have one edge, the "snap_edge"
* 2) These rectangles must have one edge, the “snap_edge”
* of the handlebox, aligned within TOLERANCE.
*
* 3) On the other dimension, the extents of one rectangle
......@@ -999,7 +999,7 @@ gtk_handle_box_get_handle_position (GtkHandleBox *handle_box)
*
* Sets the snap edge of a handlebox. The snap edge is
* the edge of the detached child that must be aligned
* with the corresponding edge of the "ghost" left
* with the corresponding edge of the “ghost” left
* behind when the child was detached to reattach
* the torn-off window. Usually, the snap edge should
* be chosen so that it stays in the same place on
......
......@@ -284,7 +284,7 @@ gtk_icon_factory_new (void)
*
* Adds the given @icon_set to the icon factory, under the name
* @stock_id. @stock_id should be namespaced for your application,
* e.g. "myapp-whatever-icon". Normally applications create a
* e.g. “myapp-whatever-icon”. Normally applications create a
* #GtkIconFactory, then add it to the list of default factories with
* gtk_icon_factory_add_default(). Then they pass the @stock_id to
* widgets such as #GtkImage to display the icon. Themes can provide
......@@ -1695,7 +1695,7 @@ G_GNUC_END_IGNORE_DEPRECATIONS;
}
/* Order sources by their "wildness", so that "wilder" sources are
* greater than "specific" sources; for determining ordering,
* greater than “specific” sources; for determining ordering,
* direction beats state beats size.
*/
......@@ -1743,7 +1743,7 @@ icon_source_compare (gconstpointer ap, gconstpointer bp)
* icons). So a single icon set would contain all those variants of
* the icon, and you might add a separate source for each one.
*
* You should nearly always add a "default" icon source with all
* You should nearly always add a “default” icon source with all
* fields wildcarded, which will be used as a fallback if no more
* specific source matches. #GtkIconSet always prefers more specific
* icon sources to more generic icon sources. The order in which you
......@@ -1861,10 +1861,10 @@ gtk_icon_set_get_sizes (GtkIconSet *icon_set,
* image filename) that serves as the base image for one or more of the
* icons in a #GtkIconSet, along with a specification for which icons in the
* icon set will be based on that pixbuf or image file. An icon set contains
* a set of icons that represent "the same" logical concept in different states,
* a set of icons that represent “the same” logical concept in different states,
* different global text directions, and different sizes.
*
* So for example a web browser's "Back to Previous Page" icon might
* So for example a web browser's “Back to Previous Page” icon might
* point in a different direction in Hebrew and in English; it might
* look different when insensitive; and it might change size depending
* on toolbar mode (small/large icons). So a single icon set would
......
......@@ -382,18 +382,18 @@
* * `font = font`
*
* Starting with GTK+ 2.0, the "font" and "fontset"
* declarations are ignored; use "font_name" declarations instead.
* Starting with GTK+ 2.0, the “font” and “fontset”
* declarations are ignored; use “font_name” declarations instead.
*
* * `fontset = font`
*
* Starting with GTK+ 2.0, the "font" and "fontset"
* declarations are ignored; use "font_name" declarations instead.
* Starting with GTK+ 2.0, the “font” and “fontset”
* declarations are ignored; use “font_name” declarations instead.
*
* * `font_name = font`
*
* Sets the font for a widget. font must be
* a Pango font name, e.g. `"Sans Italic 10"`.
* a Pango font name, e.g. “Sans Italic 10” .
* For details about Pango font names, see
* pango_font_description_from_string().
*
......
......@@ -332,7 +332,7 @@ guint gtk_rc_parse_priority (GScanner *scanner,
* GtkRcProperty:
* @type_name: quark-ified type identifier
* @property_name: quark-ified property identifier like
* "GtkScrollbar::spacing"
* “GtkScrollbar::spacing”
* @origin: field similar to one found in #GtkSettingsValue
* @value:field similar to one found in #GtkSettingsValue
*
......@@ -340,7 +340,7 @@ guint gtk_rc_parse_priority (GScanner *scanner,
*/
struct _GtkRcProperty
{
/* quark-ified property identifier like "GtkScrollbar::spacing" */
/* quark-ified property identifier like “GtkScrollbar::spacing” */
GQuark type_name;
GQuark property_name;
......
......@@ -40,7 +40,7 @@ Prebuilt common menu/toolbar items and corresponding icons
* @Title: Stock Items
*
* Stock items represent commonly-used menu or toolbar items such as
* "Open" or "Exit". Each stock item is identified by a stock ID;
* “Open” or “Exit”. Each stock item is identified by a stock ID;
* stock IDs are just strings, but macros such as #GTK_STOCK_OPEN are
* provided to avoid typing mistakes in the strings.
* Applications can register their own stock items in addition to those
......
This diff is collapsed.
......@@ -3853,8 +3853,8 @@ gtk_paint_handle (GtkStyle *style,
*
* Draws an expander as used in #GtkTreeView. @x and @y specify the
* center the expander. The size of the expander is determined by the
* "expander-size" style property of @widget. (If widget is not
* specified or doesn't have an "expander-size" property, an
* “expander-size” style property of @widget. (If widget is not
* specified or doesn't have an “expander-size” property, an
* unspecified default size will be used, since the caller doesn't
* have sufficient information to position the expander, this is
* likely not useful.) The expander is expander_size pixels tall
......@@ -4071,9 +4071,9 @@ gtk_widget_get_default_style (void)
* widget->style = gtk_style_attach (widget->style, widget->window);
* ]|
*
* and should only ever be called in a derived widget's "realize"
* and should only ever be called in a derived widget's “realize”
* implementation which does not chain up to its parent class'
* "realize" implementation, because one of the parent classes
* “realize” implementation, because one of the parent classes
* (finally #GtkWidget) would attach the style itself.
*
* Since: 2.20
......@@ -4376,7 +4376,7 @@ gtk_widget_modify_fg (GtkWidget *widget,
* See also gtk_widget_modify_style().
*
* <note><para>
* Note that "no window" widgets (which have the %GTK_NO_WINDOW
* Note that “no window” widgets (which have the %GTK_NO_WINDOW
* flag set) draw on their parent container's window and thus may
* not draw any background themselves. This is the case for e.g.
* #GtkLabel.
......@@ -4476,7 +4476,7 @@ gtk_widget_modify_text (GtkWidget *widget,
* and #GtkTextView. See also gtk_widget_modify_style().
*
* <note><para>
* Note that "no window" widgets (which have the %GTK_NO_WINDOW
* Note that “no window” widgets (which have the %GTK_NO_WINDOW
* flag set) draw on their parent container's window and thus may
* not draw any background themselves. This is the case for e.g.
* #GtkLabel.
......@@ -4600,7 +4600,7 @@ gtk_widget_reset_rc_styles (GtkWidget *widget)
* periods. The name of a widget comes from
* gtk_widget_get_name(). Paths are used to apply styles to a widget
* in gtkrc configuration files. Widget names are the type of the
* widget by default (e.g. "GtkButton") or can be set to an
* widget by default (e.g. “GtkButton”) or can be set to an
* application-specific value with gtk_widget_set_name(). By setting
* the name of a widget, you allow users or theme authors to apply
* styles to that specific widget in their gtkrc
......
......@@ -44,7 +44,7 @@
* @Title: GtkToggleAction
*
* A #GtkToggleAction corresponds roughly to a #GtkCheckMenuItem. It has an
* "active" state specifying whether the action has been checked or not.
* “active” state specifying whether the action has been checked or not.
*/
struct _GtkToggleActionPrivate
......@@ -264,7 +264,7 @@ gtk_toggle_action_activate (GtkAction *action)
* gtk_toggle_action_toggled:
* @action: the action object
*
* Emits the "toggled" signal on the toggle action.
* Emits the “toggled” signal on the toggle action.
*
* Since: 2.4
*
......
......@@ -190,9 +190,9 @@
*
* a keyboard accelerator
*
* The "position" attribute determines where a constructed widget is positioned
* The “position” attribute determines where a constructed widget is positioned
* wrt. to its siblings in the partially constructed tree. If it is
* "top", the widget is prepended, otherwise it is appended.
* “top”, the widget is prepended, otherwise it is appended.
*
* # UI Merging # {#UI-Merging}
*
......@@ -201,7 +201,7 @@
*
* Merging is done based on the names of the XML elements. Each element is
* identified by a path which consists of the names of its anchestors, separated
* by slashes. For example, the menuitem named "Left" in the example above
* by slashes. For example, the menuitem named “Left” in the example above
* has the path `/ui/menubar/JustifyMenu/Left` and the
* toolitem with the same name has path
* `/ui/toolbar1/JustifyToolItems/Left`.
......@@ -215,7 +215,7 @@
*
* # Smart Separators # {#Smart-Separators}
*
* The separators created by #GtkUIManager are "smart", i.e. they do not show up
* The separators created by #GtkUIManager are “smart”, i.e. they do not show up
* in the UI unless they end up between two visible menu or tool items. Separators
* which are located at the very beginning or end of the menu or toolbar
* containing them, or multiple separators next to each other, are hidden. This
......@@ -235,9 +235,9 @@
*
* - make them disappear by hiding the menu item they're attached to
*
* - add an insensitive "Empty" item
* - add an insensitive “Empty” item
*
* The behaviour is chosen based on the "hide_if_empty" property of the action
* The behaviour is chosen based on the “hide_if_empty” property of the action
* to which the submenu is associated.
*
* # GtkUIManager as GtkBuildable # {#GtkUIManager-BUILDER-UI}
......@@ -250,7 +250,7 @@
*
* The widgets that are constructed by a GtkUIManager can be embedded in
* other parts of the constructed user interface with the help of the
* "constructor" attribute. See the example below.
* “constructor” attribute. See the example below.
*
* ## An embedded GtkUIManager UI definition
*
......@@ -873,7 +873,7 @@ gtk_ui_manager_get_add_tearoffs (GtkUIManager *manager)
* @manager: a #GtkUIManager
* @add_tearoffs: whether tearoff menu items are added
*
* Sets the "add_tearoffs" property, which controls whether menus
* Sets the “add_tearoffs” property, which controls whether menus
* generated by this #GtkUIManager will have tearoff menu items.
*
* Note that this only affects regular menus. Generated popup
......
......@@ -1656,9 +1656,9 @@ gtk_about_dialog_get_translator_credits (GtkAboutDialog *about)
* |[<!-- language="C" -->
* gtk_about_dialog_set_translator_credits (about, _("translator-credits"));
* ]|
* It is a good idea to use the customary msgid "translator-credits" for this
* It is a good idea to use the customary msgid “translator-credits” for this
* purpose, since translators will already know the purpose of that msgid, and
* since #GtkAboutDialog will detect if "translator-credits" is untranslated
* since #GtkAboutDialog will detect if “translator-credits” is untranslated
* and hide the tab.
*
* Since: 2.6
......
......@@ -52,7 +52,7 @@
* Note that “accelerators” are different from
* “mnemonics”. Accelerators are shortcuts for
* activating a menu item; they appear alongside the menu item they're a
* shortcut for. For example "Ctrl+Q" might appear alongside the "Quit"
* shortcut for. For example “Ctrl+Q” might appear alongside the “Quit”
* menu item. Mnemonics are shortcuts for GUI elements such as text
* entries or buttons; they appear as underlined characters. See
* gtk_label_new_with_mnemonic(). Menu items can have both accelerators
......@@ -964,7 +964,7 @@ gtk_accel_groups_activate (GObject *object,
*
* Determines whether a given keyval and modifier mask constitute
* a valid keyboard accelerator. For example, the #GDK_KEY_a keyval
* plus #GDK_CONTROL_MASK is valid - this is a "Ctrl+a" accelerator.
* plus #GDK_CONTROL_MASK is valid - this is a “Ctrl+a” accelerator.
* But, you can't, for instance, use the #GDK_KEY_Control_L keyval
* as an accelerator.
*
......@@ -1442,14 +1442,14 @@ out:
* modifier mask, %NULL
*
* Parses a string representing an accelerator. The
* format looks like "&lt;Control&gt;a" or "&lt;Shift&gt;&lt;Alt&gt;F1"
* or "&lt;Release&gt;z" (the last one is for key release).
* format looks like “&lt;Control&gt;a” or “&lt;Shift&gt;&lt;Alt&gt;F1”
* or “&lt;Release&gt;z” (the last one is for key release).
*
* The parser is fairly liberal and allows lower or upper case,
* and also abbreviations such as "&lt;Ctl&gt;" and "&lt;Ctrl&gt;".
* and also abbreviations such as “&lt;Ctl&gt;” and “&lt;Ctrl&gt;”.
* Key names are parsed using gdk_keyval_from_name(). For character
* keys the name is not the symbol, but the lowercase name, e.g. one
* would use "&lt;Ctrl&gt;minus" instead of "&lt;Ctrl&gt;-".
* would use “&lt;Ctrl&gt;minus” instead of “&lt;Ctrl&gt;-”.
*
* If the parse fails, @accelerator_key and @accelerator_mods will
* be set to 0 (zero).
......@@ -1512,7 +1512,7 @@ gtk_accelerator_name_with_keycode (GdkDisplay *display,
* Converts an accelerator keyval and modifier mask
* into a string parseable by gtk_accelerator_parse().
* For example, if you pass in #GDK_KEY_q and #GDK_CONTROL_MASK,
* this function returns "&lt;Control&gt;q".
* this function returns “&lt;Control&gt;q”.
*
* If you need to display accelerators in the user interface,
* see gtk_accelerator_get_label().
......
......@@ -42,7 +42,7 @@
* @See_also: #GtkAccelGroup
*
* The #GtkAccelLabel widget is a subclass of #GtkLabel that also displays an
* accelerator key on the right of the label text, e.g. 'Ctl+S'.
* accelerator key on the right of the label text, e.g. “Ctl+S”.
* It is commonly used in menus to show the keyboard short-cuts for commands.
*
* The accelerator key to display is not set explicitly.
......@@ -51,10 +51,10 @@
* gtk_accel_label_set_accel_widget().
*
* For example, a #GtkMenuItem widget may have an accelerator added to emit the
* "activate" signal when the 'Ctl+S' key combination is pressed.
* “activate” signal when the “Ctl+S” key combination is pressed.
* A #GtkAccelLabel is created and added to the #GtkMenuItem, and
* gtk_accel_label_set_accel_widget() is called with the #GtkMenuItem as the
* second argument. The #GtkAccelLabel will now display 'Ctl+S' after its label.
* second argument. The #GtkAccelLabel will now display “Ctl+S” after its label.
*
* Note that creating a #GtkMenuItem with gtk_menu_item_new_with_label() (or
* one of the similar functions for #GtkCheckMenuItem and #GtkRadioMenuItem)
......@@ -612,7 +612,7 @@ gtk_accel_label_get_string (GtkAccelLabel *accel_label)
}
/* Underscores in key names are better displayed as spaces
* E.g., Page_Up should be "Page Up".
* E.g., Page_Up should be “Page Up”.
*
* Some keynames also have prefixes that are not suitable
* for display, e.g XF86AudioMute, so strip those out, too.
......
......@@ -45,7 +45,7 @@
* Accelerator maps are used to define runtime configurable accelerators.
* Functions for manipulating them are are usually used by higher level
* convenience mechanisms like #GtkUIManager and are thus considered
* "low-level". You'll want to use them if you're manually creating menus that
* “low-level”. You'll want to use them if you're manually creating menus that
* should have user-configurable accelerators.
*
* An accelerator is uniquely defined by:
......@@ -54,15 +54,15 @@
* - accelerator modifiers
*
* The accelerator path must consist of
* "&lt;WINDOWTYPE&gt;/Category1/Category2/.../Action", where WINDOWTYPE
* “&lt;WINDOWTYPE&gt;/Category1/Category2/.../Action”, where WINDOWTYPE
* should be a unique application-specific identifier that corresponds
* to the kind of window the accelerator is being used in, e.g.
* "Gimp-Image", "Abiword-Document" or "Gnumeric-Settings".
* The "Category1/.../Action" portion is most appropriately chosen by
* “Gimp-Image”, “Abiword-Document” or “Gnumeric-Settings”.
* The “Category1/.../Action” portion is most appropriately chosen by
* the action the accelerator triggers, i.e. for accelerators on menu
* items, choose the item's menu path, e.g. "File/Save As",
* "Image/View/Zoom" or "Edit/Select All". So a full valid accelerator
* path may look like: "&lt;Gimp-Toolbox&gt;/File/Dialogs/Tool Options...".
* items, choose the item's menu path, e.g. “File/Save As”,
* “Image/View/Zoom” or “Edit/Select All”. So a full valid accelerator
* path may look like: “&lt;Gimp-Toolbox&gt;/File/Dialogs/Tool Options...”.
*
* All accelerators are stored inside one global #GtkAccelMap that can
* be obtained using gtk_accel_map_get(). See <link
......
......@@ -110,7 +110,7 @@ gtk_actionable_get_action_name (GtkActionable *actionable)
* Usually this function is used when the widget is located (or will be
* located) within the hierarchy of a #GtkApplicationWindow.
*
* Names are of the form "win.save" or "app.quit" for actions on the
* Names are of the form “win.save” or “app.quit” for actions on the
* containing #GtkApplicationWindow or its associated #GtkApplication,
* respectively. This is the same form used for actions in the #GMenu
* associated with the window.
......@@ -160,11 +160,11 @@ gtk_actionable_get_action_target_value (GtkActionable *actionable)
* The target value has two purposes. First, it is used as the
* parameter to activation of the action associated with the
* #GtkActionable widget. Second, it is used to determine if the widget
* should be rendered as "active" - the widget is active if the state
* should be rendered as “active” - the widget is active if the state
* is equal to the given target.
*
* Consider the example of associating a set of buttons with a #GAction
* with string state in a typical "radio button" situation. Each button
* with string state in a typical “radio button” situation. Each button
* will be associated with the same action, but with a different target
* value for that action. Clicking on a particular button will activate
* the action with the target of that button, which will typically cause
......
......@@ -42,14 +42,14 @@
* application (such as 'fullscreen').
*
* In this case, each of these action groups could be added to a
* #GtkActionMuxer with the prefixes "app" and "win", respectively. This
* would expose the actions as "app.quit" and "win.fullscreen" on the
* #GtkActionMuxer with the prefixes “app” and “win”, respectively. This
* would expose the actions as “app.quit” and “win.fullscreen” on the
* #GActionGroup interface presented by the #GtkActionMuxer.
*
* Activations and state change requests on the #GtkActionMuxer are wired
* through to the underlying action group in the expected way.
*
* This class is typically only used at the site of "consumption" of
* This class is typically only used at the site of “consumption” of
* actions (eg: when displaying a menu that contains many actions on
* different objects).
*/
......@@ -653,12 +653,12 @@ gtk_action_muxer_class_init (GObjectClass *class)
* action `x` in @action_group, there is an equivalent
* action @prefix`.x` in @muxer.
*
* For example, if @prefix is "`app`" and @action_group
* contains an action called "`quit`", then @muxer will
* now contain an action called "`app.quit`".
* For example, if @prefix is “`app`” and @action_group
* contains an action called “`quit`”, then @muxer will
* now contain an action called “`app.quit`”.
*
* If any #GtkActionObservers are registered for actions in the group,
* "action_added" notifications will be emitted, as appropriate.
* “action_added” notifications will be emitted, as appropriate.
*
* @prefix must not contain a dot ('.').
*/
......@@ -704,7 +704,7 @@ gtk_action_muxer_insert (GtkActionMuxer *muxer,
* Removes a #GActionGroup from the #GtkActionMuxer.
*
* If any #GtkActionObservers are registered for actions in the group,
* "action_removed" notifications will be emitted, as appropriate.
* “action_removed” notifications will be emitted, as appropriate.
*/
void
gtk_action_muxer_remove (GtkActionMuxer *muxer,
......
......@@ -163,7 +163,7 @@ gtk_action_observer_action_removed (GtkActionObserver *observer,
* @observer: a #GtkActionObserver
* @observable: the source of the event
* @action_name: the name of the action
* @action_and_target: detailed action of the changed accel, in "action and target" format
* @action_and_target: detailed action of the changed accel, in “action and target” format
*
* This function is called when an action that the observer is
* registered to receive events for has one of its accelerators changed.
......
......@@ -1022,7 +1022,7 @@ gtk_application_get_window_by_id (GtkApplication *application,
* gtk_application_get_active_window:
* @application: a #GtkApplication
*
* Gets the "active" window for the application.
* Gets the “active” window for the application.
*
* The active window is the one that was most recently focused (within
* the application). This window may not have the focus at the moment
......@@ -1064,12 +1064,12 @@ gtk_application_update_accels (GtkApplication *application)
*
* @accelerator must be a string that can be parsed by
* gtk_accelerator_parse(), e.g. "&lt;Primary&gt;q" or
* "&lt;Control&gt;&lt;Alt&gt;p".
* “&lt;Control&gt;&lt;Alt&gt;p”.
*
* @action_name must be the name of an action as it would be used
* in the app menu, i.e. actions that have been added to the application
* are referred to with an "app." prefix, and window-specific actions
* with a "win." prefix.
* are referred to with an “app.” prefix, and window-specific actions
* with a “win.” prefix.
*
* GtkApplication also extracts accelerators out of 'accel' attributes
* in the #GMenuModels passed to gtk_application_set_app_menu() and
......@@ -1141,8 +1141,8 @@ gtk_application_remove_accelerator (GtkApplication *application,
* The application menu is a single menu containing items that typically
* impact the application as a whole, rather than acting on a specific
* window or document. For example, you would expect to see
* "Preferences" or "Quit" in an application menu, but not "Save" or
* "Print".
* “Preferences” or “Quit” in an application menu, but not “Save” or
* “Print”.
*
* If supported, the application menu will be rendered by the desktop
* environment.
......
......@@ -47,8 +47,8 @@
* This class implements the #GActionGroup and #GActionMap interfaces,
* to let you add window-specific actions that will be exported by the
* associated #GtkApplication, together with its application-wide
* actions. Window-specific actions are prefixed with the "win."
* prefix and application-wide actions are prefixed with the "app."
* actions. Window-specific actions are prefixed with the “win.”
* prefix and application-wide actions are prefixed with the “app.”
* prefix. Actions must be addressed with the prefixed name when
* referring to them from a #GMenuModel.
*
......
......@@ -38,7 +38,7 @@
* drawing a small preview of a larger image. #GtkAspectFrame
* derives from #GtkFrame, so it can draw a label and
* a frame around the child. The frame will be
* "shrink-wrapped" to the size of the child.
* “shrink-wrapped” to the size of the child.
*/
#include "config.h"
......
......@@ -45,7 +45,7 @@
*
* The GtkAssistant implementation of the #GtkBuildable interface
* exposes the @action_area as internal children with the name
* "action_area".
* “action_area”.
*
* To add pages to an assistant in #GtkBuilder, simply add it as a
* child to the GtkAssistant object, and set its child properties
......
......@@ -64,7 +64,7 @@ G_BEGIN_DECLS
* %GTK_ASSISTANT_PAGE_CONFIRM, %GTK_ASSISTANT_PAGE_SUMMARY or
* %GTK_ASSISTANT_PAGE_PROGRESS to be correct.
*
* The Cancel button will only be shown if the page isn't "committed".
* The Cancel button will only be shown if the page isn't “committed”.
* See gtk_assistant_commit() for details.
*/
typedef enum
......@@ -125,8 +125,8 @@ struct _GtkAssistantClass
*
* A function used by gtk_assistant_set_forward_page_func() to know which
* is the next page given a current one. It's called both for computing the
* next page when the user presses the "forward" button and for handling
* the behavior of the "last" button.
* next page when the user presses the “forward” button and for handling
* the behavior of the “last” button.
*
* Returns: The next page number.
*/
......
......@@ -88,7 +88,7 @@
* precedence over the default bindings shipped with GTK+, overriding
* existing bindings as demonstrated in
* <link linkend="gtk-bindings-install">Installing a key binding</link>
* works as expected. The same mechanism can not be used to "unbind"
* works as expected. The same mechanism can not be used to “unbind”
* existing bindings, however.
*
* |[
......@@ -104,15 +104,15 @@
* ]|
*
* The above example will not have the desired effect of causing
* "&lt;Control&gt;Right" and "&lt;Control&gt;Left" key presses to
* “&lt;Control&gt;Right” and “&lt;Control&gt;Left” key presses to
* be ignored by GTK+. Instead, it just causes any existing bindings
* from the bindings set "MoveCursor3" to be deleted, so when
* "&lt;Control&gt;Right" or "&lt;Control&gt;Left" are pressed, no
* binding for these keys is found in binding set "MoveCursor3".
* from the bindings set “MoveCursor3” to be deleted, so when
* “&lt;Control&gt;Right” or “&lt;Control&gt;Left” are pressed, no
* binding for these keys is found in binding set “MoveCursor3”.
* GTK+ will thus continue to search for matching key bindings, and
* will eventually lookup and find the default GTK+ bindings for
* entries which implement word movement. To keep GTK+ from activating
* its default bindings, the "unbind" keyword can be used like this:
* its default bindings, the “unbind” keyword can be used like this:
*
* |[
* @binding-set MoveCursor3
......@@ -126,9 +126,9 @@
* }
* ]|
*
* Now, GTK+ will find a match when looking up "&lt;Control&gt;Right"
* and "&lt;Control&gt;Left" key presses before it resorts to its default
* bindings, and the match instructs it to abort ("unbind") the search,
* Now, GTK+ will find a match when looking up “&lt;Control&gt;Right”
* and “&lt;Control&gt;Left” key presses before it resorts to its default
* bindings, and the match instructs it to abort (“unbind”) the search,
* so the key presses are not consumed by this widget. As usual, further
* processing of the key presses, e.g. by an entry's parent widget, is
* now possible.
......
......@@ -202,7 +202,7 @@ gtk_buildable_parser_finished (GtkBuildable *buildable,
*
* Constructs a child of @buildable with the name @name.