[gnome-devel-docs] Fixed bug #560505
- From: Daniel Mustieles GarcÃa <dmustieles src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-devel-docs] Fixed bug #560505
- Date: Tue, 20 Mar 2012 13:30:49 +0000 (UTC)
commit 3a8313e9886c93f2926753e3fa1b44d63db29a53
Author: Daniel Mustieles <daniel mustieles gmail com>
Date: Tue Mar 20 14:30:38 2012 +0100
Fixed bug #560505
hig/C/hig-ch-checks.xml | 2 +-
hig/C/hig-ch-controls.xml | 22 ++++++++--------
hig/C/hig-ch-icons.xml | 8 +++---
hig/C/hig-ch-input.xml | 6 ++--
hig/C/hig-ch-language.xml | 2 +-
hig/C/hig-ch-menus.xml | 6 ++--
hig/C/hig-ch-toolbars.xml | 4 +-
hig/C/hig-diff.xml | 58 ++++++++++++++++++++++----------------------
8 files changed, 54 insertions(+), 54 deletions(-)
---
diff --git a/hig/C/hig-ch-checks.xml b/hig/C/hig-ch-checks.xml
index d23ac3d..123a13e 100644
--- a/hig/C/hig-ch-checks.xml
+++ b/hig/C/hig-ch-checks.xml
@@ -67,7 +67,7 @@ example. An transitional paragraph probably needs to be added after the "right"
<para>Test various GNOME themes to ensure that your application respects all the available settings.</para>
- <para>Test your application with black and white, high contrast themes and confirm that all information is still conveyed correctly. If you don't have a suitable high contrast GNOME theme available to test, print off some screenshots in black and white (not greyscale) and make sure all the important information is still visibleâ this will approximate what a high contrast theme user will see.</para>
+ <para>Test your application with black and white, high contrast themes and confirm that all information is still conveyed correctly. If you don't have a suitable high contrast GNOME theme available to test, print off some screenshots in black and white (not grayscale) and make sure all the important information is still visibleâ this will approximate what a high contrast theme user will see.</para>
</sect2>
<sect2>
diff --git a/hig/C/hig-ch-controls.xml b/hig/C/hig-ch-controls.xml
index 2113688..de4e9e6 100644
--- a/hig/C/hig-ch-controls.xml
+++ b/hig/C/hig-ch-controls.xml
@@ -619,7 +619,7 @@
<para>Once a dialog is displayed, do not change its default button
from one button to another. You may add or remove default status from
the same button if it helps prevent user error, however. Changing the
- default from one button to another can be confusing and inefficent,
+ default from one button to another can be confusing and inefficient,
especially for users relying on assistive technologies.</para>
</listitem>
@@ -1271,12 +1271,12 @@
<!-- How odd, the whole point of a combo box is that it's a combination of a text field and a list... as such, therefore there is no such thing as an 'uneditable combo box' :o) -->
- <para>Drop-down combination boxes combine a text entry field and a dropdown list of
+ <para>Drop-down combination boxes combine a text entry field and a drop-down list of
pre-defined values. Selecting one of the pre-defined values sets the entry
field to that value.</para>
<figure>
- <title>A drop-down combination box before and after its dropdown list is displayed</title>
+ <title>A drop-down combination box before and after its drop-down list is displayed</title>
<mediaobject>
<imageobject>
@@ -1290,7 +1290,7 @@
<textobject>
<phrase>Two images, one of a drop-down combination box entry field displaying its
- current selection, and the other showing its dropdown list of
+ current selection, and the other showing its drop-down list of
available choices when clicked on</phrase>
</textobject>
</mediaobject>
@@ -1328,7 +1328,7 @@
For example, if the user types <userinput>blue</userinput>,
<userinput>Blue</userinput> and <userinput>BLUE</userinput> into the
same drop-down combination box on different occasions, only store one of these in the
- combo's dropdown list, unless your application makes a distinction
+ combo's drop-down list, unless your application makes a distinction
between the different forms (which is usually a bad idea).</para>
</listitem>
@@ -1341,7 +1341,7 @@
<listitem>
<para>Use <link linkend="layout-capitalization">sentence
- capitalization</link> for the dropdown list items, for example
+ capitalization</link> for the drop-down list items, for example
<guilabel>Switched movement</guilabel>.</para>
</listitem>
@@ -1749,7 +1749,7 @@
<para>A tabbed notebook control is a convenient way of presenting related
information in the same window, without having to display it all at the
- same time. It is analagous to the divider tabs in a ring binder or a file
+ same time. It is analogous to the divider tabs in a ring binder or a file
cabinet.</para>
<figure>
@@ -1896,7 +1896,7 @@
<sect2 id="controls-tab-status">
<title>Status Indicators</title>
<remark>This section needs more concrete recommendations, it's currently (almost) taken verbatim from Sebastian's patch in bug #72101.</remark>
- <para>In some tabbed windows, such as preference windows, it might be desirable to indicate the status of a particular tab. This can be used to notify the user that a web page that is still loading or has been loaded, a new message is waiting in a particular instant messasing conversation, or that a document has not been saved. Such a status indicator should be an icon that is placed directly to the left of the tab label. Additionally, the tab label's color might be changed to indicate a certain status. Do not simply rely on a different coloring scheme for status indication.</para>
+ <para>In some tabbed windows, such as preference windows, it might be desirable to indicate the status of a particular tab. This can be used to notify the user that a web page that is still loading or has been loaded, a new message is waiting in a particular instant messaging conversation, or that a document has not been saved. Such a status indicator should be an icon that is placed directly to the left of the tab label. Additionally, the tab label's color might be changed to indicate a certain status. Do not simply rely on a different coloring scheme for status indication.</para>
</sect2>
</sect1>
@@ -1911,7 +1911,7 @@
<para>You can use two main types of progress bars in your applicationâ
measured-progress bars and indeterminate-progress bars (the kind that
- bounce back and forth). In addition there are are three types of measured
+ bounce back and forth). In addition there are three types of measured
progress bars.</para>
<itemizedlist>
@@ -2203,7 +2203,7 @@
<para>Frames with a border around their perimeter have traditionally been
used for denoting groups of related controls. This is advantageous because
- it physically seperates disimilar controls, and also avoids repitition of
+ it physically separates dissimilar controls, and also avoids repetition of
the frame's label in individual member control labels. Unfortunately,
they add visual noise that can both make a window appear more complex than
it really is, and reduce the ability to quickly scan window elements.</para>
@@ -2260,7 +2260,7 @@
window, consider carefully if you really need it. It is usually better
to do without, if the groups can be separated by space alone. Do not
use frames and separators to compensate for poor control layout or
- alignnment.</para>
+ alignment.</para>
</listitem>
<listitem>
diff --git a/hig/C/hig-ch-icons.xml b/hig/C/hig-ch-icons.xml
index 67fd294..add4b00 100644
--- a/hig/C/hig-ch-icons.xml
+++ b/hig/C/hig-ch-icons.xml
@@ -5,7 +5,7 @@
<para>Icons are a graphical metaphor presenting a visual image that the user associates with a particular object, state or operation. When a user sees a good icon they are immediately reminded of the item it represents, whether that be an application in the panel menu or the "right aligned" state in a word processor toolbar.</para>
<para>
<itemizedlist>
- <listitem><para>Icons can assist the user in rapidly scanning a large number of objects to select the desired item. Particularly after a user is acustomed to an icon's appearance, they can identify it more rapidly than a text label.</para></listitem>
+ <listitem><para>Icons can assist the user in rapidly scanning a large number of objects to select the desired item. Particularly after a user is accustomed to an icon's appearance, they can identify it more rapidly than a text label.</para></listitem>
<listitem><para>Icons can augment text by providing visual suggestions to accompany the descriptive text. Some things are easier to communicate with a picture, even a very small one.</para></listitem>
<listitem><para>Icons can compactly represent a large number of objects when there is insufficient space to display textual descriptions (such as in a toolbar).</para></listitem>
</itemizedlist>
@@ -200,7 +200,7 @@
<listitem><para>Ensure that toolbar icons which will be used together are easy to visually distinguish. Try to <link linkend="icon_design_silhouettes">make the icons' silhouettes distinct</link> from one another.</para></listitem>
<listitem><para>While most user's will view toolbar icons at 24x24 pixels, it is important to include a "large print" set of icons at 48x48 pixels for accesibility reasons.</para></listitem>
<listitem><para>Often, you will not have to design any toolbar icons yourself as GTK provides a wide variety of stock icons. You should use these whenever representing one of their intended items. This establishes consistent language across applications, and makes it easier for users to search for items on the toolbar. Do not use stock toolbar icons for anything other than their intended purpose, however, as this will make your application inconsistent with others, and could easily confuse your users.</para>
- <para>To browse the available stock icons, install the development packages for GTK version 2.x and run <command>gtk-demo</command>. Double click on <guimenuitem>Stock Item and Icon Browser</guimenuitem> to activate the stock icon browser. Note that icons vary in available resolution, so the images presented in the icon browser should not be taken as indicative of the maximuum quality of an image. To view the images in PNG format, look in the GTK 2 source code under <filename class="directory">gtk/stock-icons</filename>.</para></listitem>
+ <para>To browse the available stock icons, install the development packages for GTK version 2.x and run <command>gtk-demo</command>. Double click on <guimenuitem>Stock Item and Icon Browser</guimenuitem> to activate the stock icon browser. Note that icons vary in available resolution, so the images presented in the icon browser should not be taken as indicative of the maximum quality of an image. To view the images in PNG format, look in the GTK 2 source code under <filename class="directory">gtk/stock-icons</filename>.</para></listitem>
</itemizedlist>
</sect2>
@@ -322,7 +322,7 @@
</mediaobject>
</listitem>
<listitem>
- <para>Now you should hand-create create a version of this icon at 24x24. Do <emphasis>not</emphasis> simply scale the larger icon, as this icon will be seen by the majority of users and the result of scaling would be less distinct:</para>
+ <para>Now you should hand-create a version of this icon at 24x24. Do <emphasis>not</emphasis> simply scale the larger icon, as this icon will be seen by the majority of users and the result of scaling would be less distinct:</para>
<mediaobject>
<imageobject><imagedata fileref="images/icon-design-process-9.png" format="PNG"/></imageobject>
<imageobject><imagedata fileref="images/icon-design-process-9.eps" format="EPS"/></imageobject>
@@ -491,7 +491,7 @@
<listitem><para>a high contrast large print theme</para></listitem>
<listitem><para>an inverse high contrast large print theme</para></listitem>
<listitem><para>a low contrast theme</para></listitem>
- <listitem><para>a low contrast,large print theme</para></listitem>
+ <listitem><para>a low contrast, large print theme</para></listitem>
</itemizedlist>
<para>To be considered fully accessible, all icons in your application
must be replaced by a suitable alternative when one of these
diff --git a/hig/C/hig-ch-input.xml b/hig/C/hig-ch-input.xml
index a01f389..8c79515 100644
--- a/hig/C/hig-ch-input.xml
+++ b/hig/C/hig-ch-input.xml
@@ -71,7 +71,7 @@
<listitem><para><keycombo><keycap>Ctrl</keycap><mousebutton>scrollwheel-up</mousebutton></keycombo> should zoom into the window or control under the mouse pointer, and <keycombo><keycap>Ctrl</keycap><mousebutton>scrollwheel-down</mousebutton></keycombo> should zoom out. Zooming in this way should not move keyboard focus to the window or control being zoomed.</para></listitem>
- <listitem><para>Do not depend on input from the middle or right mouse buttons. As well as being physically more difficult to click, some pointing devices and many assistive technology devices only support or emulate the left mouse button. Some assistive technologies may noteven emulate the mouse at all, but generate keyboard events instead.</para></listitem>
+ <listitem><para>Do not depend on input from the middle or right mouse buttons. As well as being physically more difficult to click, some pointing devices and many assistive technology devices only support or emulate the left mouse button. Some assistive technologies may not even emulate the mouse at all, but generate keyboard events instead.</para></listitem>
<listitem><para>Ensure that every operation in your application that can be done with the mouse can also be done with the keyboard. The only exceptions to this are actions where fine motor control is an essential part of the task. For example, controlling movement in some types of action games, or freehand painting in an image-editing application.</para></listitem>
@@ -352,7 +352,7 @@ user can select, either singly or multiply, ensure the following mechanisms are
<textobject><phrase>"Link" pointer</phrase></textobject>
</mediaobject>
</entry>
- <entry>Link selection. A link to the selection will be inserted at the drop location. How the link appears will be application-dependent, it may be a hyperlink, an icon, or a duplicate of the orignal selection, for example.</entry>
+ <entry>Link selection. A link to the selection will be inserted at the drop location. How the link appears will be application-dependent, it may be a hyperlink, an icon, or a duplicate of the original selection, for example.</entry>
</row>
<row>
@@ -1118,7 +1118,7 @@ user can select, either singly or multiply, ensure the following mechanisms are
<para>The rules for panel application keyboard navigation are mostly the same as those for any other window. However, there is one imporant difference:</para>
<itemizedlist>
- <listitem><para>Do <emphasis>not</emphasis> use the the <keycap>Tab</keycap> key as the means of moving focus between controls in a panel application. Use the arrow keys for this purpose instead.</para></listitem>
+ <listitem><para>Do <emphasis>not</emphasis> use the <keycap>Tab</keycap> key as the means of moving focus between controls in a panel application. Use the arrow keys for this purpose instead.</para></listitem>
</itemizedlist>
<para>When an object on a panel has focus, the <keycap>Tab</keycap> key normally moves focus to the next object on the panel. If your panel application also used <keycap>Tab</keycap> for its own internal navigation, the user would have to press <keycombo><keycap>Ctrl</keycap><keycap>Tab</keycap></keycombo> to move focus out of your panel application instead. This inconsistency would be detrimental to the user experience.</para>
diff --git a/hig/C/hig-ch-language.xml b/hig/C/hig-ch-language.xml
index 2044e9b..f07e66c 100644
--- a/hig/C/hig-ch-language.xml
+++ b/hig/C/hig-ch-language.xml
@@ -27,7 +27,7 @@
<listitem><para>Do not include text in windows that describes <emphasis>how</emphasis> to use the interface, for example <guilabel>You can install a new theme by dropping it here</guilabel>. As well as adding visual clutter, descriptive labels can also conflict with information provided in documentation.</para></listitem>
- <listitem><para>Use standard terms. You can find a list of standard user interface terms in the <ulink url="http://developer.gnome.org/documents/style-guide/wordlist.html";>GNOME Documentation Style Guide, Recommended Terminology</ulink>..</para></listitem>
+ <listitem><para>Use standard terms. You can find a list of standard user interface terms in the <ulink url="http://developer.gnome.org/documents/style-guide/wordlist.html";>GNOME Documentation Style Guide, Recommended Terminology</ulink>.</para></listitem>
<listitem><para>Apply standard capitalization rules. See <xref linkend="layout-capitalization"/> for guidelines about capitalization of user interface labels </para></listitem>
</itemizedlist>
diff --git a/hig/C/hig-ch-menus.xml b/hig/C/hig-ch-menus.xml
index fea0c3e..e79203e 100644
--- a/hig/C/hig-ch-menus.xml
+++ b/hig/C/hig-ch-menus.xml
@@ -540,7 +540,7 @@ the application saves state as it should.</remark>
<row>
<entry><guimenuitem>Print Previe<accel>w</accel></guimenuitem></entry>
<entry><keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>P</keycap></keycombo></entry>
- <entry>Shows the user what the printed document will look like. Present a new window containing an accruate represenation of the appearance of the document as it would be printed. The libgnomeprintui library provides a standard Print Preview window that you should use if possible.</entry>
+ <entry>Shows the user what the printed document will look like. Present a new window containing an accurate representation of the appearance of the document as it would be printed. The libgnomeprintui library provides a standard Print Preview window that you should use if possible.</entry>
</row>
<row>
@@ -861,7 +861,7 @@ the application saves state as it should.</remark>
</sect2>
<sect2 id="menu-standard-view">
<title>View</title>
- <para>The <guimenu>View</guimenu> menu contains only items that affect the user's view of the current document. Do not place any items on the <guimenu>View</guimenu> menu that affect the the content of the current document. (Exception: <menuchoice><guimenu>View</guimenu><guimenuitem>Reload</guimenuitem></menuchoice> may change the current contents if, for example, the document is a webpage that has been recently updated on the server).</para>
+ <para>The <guimenu>View</guimenu> menu contains only items that affect the user's view of the current document. Do not place any items on the <guimenu>View</guimenu> menu that affect the content of the current document. (Exception: <menuchoice><guimenu>View</guimenu><guimenuitem>Reload</guimenuitem></menuchoice> may change the current contents if, for example, the document is a webpage that has been recently updated on the server).</para>
<figure id="generic-view-menu">
<title>A generic View menu</title>
@@ -962,7 +962,7 @@ the application saves state as it should.</remark>
<row>
<entry><guimenuitem>S<accel>o</accel>rt By...</guimenuitem></entry>
<entry>None</entry>
- <entry>Sorts the contents of an container by user-specified criteria. Open a dialog allowing the user to choose from pre-defined sort keys (for example, Name, Size, or Modification Date in a file manager), or to specify their own if applicable.</entry>
+ <entry>Sorts the contents of a container by user-specified criteria. Open a dialog allowing the user to choose from pre-defined sort keys (for example, Name, Size, or Modification Date in a file manager), or to specify their own if applicable.</entry>
</row>
<row>
diff --git a/hig/C/hig-ch-toolbars.xml b/hig/C/hig-ch-toolbars.xml
index 163412a..979d16e 100644
--- a/hig/C/hig-ch-toolbars.xml
+++ b/hig/C/hig-ch-toolbars.xml
@@ -2,7 +2,7 @@
<chapter id="toolbars">
<title>Toolbars</title>
- <para>A toolbar is a strip of controls that allows convenient access to commonly-used functions. Most toolbars only contain graphical buttons, but in more complex applications, other types of controls such as dropdown lists, can also be useful.</para>
+ <para>A toolbar is a strip of controls that allows convenient access to commonly-used functions. Most toolbars only contain graphical buttons, but in more complex applications, other types of controls such as drop-down lists, can also be useful.</para>
<!-- This bit more relevant to the utility windows section
<note><para>Although the latter is just a side-effect of the fact that palettes can't be created with the standard toolbar widgetsâ it would be rather nice if they could, especially as they would then automatically feature in the toolbar keyboard navigation order.</para></note>
@@ -68,7 +68,7 @@
<sect2 id="vertical-toolbars">
<title>Vertical Toolbars</title>
- <para>In general, don't use vertical toolbars. The eye does not scan vertically as well as it does horizontally, groups of mutually exclusive buttons are less obvious when arranged vertically, and showing button labels is more awkard and less space-efficient. Also, some toolbar controls just cannot be used vertically, such as dropdown lists.</para>
+ <para>In general, don't use vertical toolbars. The eye does not scan vertically as well as it does horizontally, groups of mutually exclusive buttons are less obvious when arranged vertically, and showing button labels is more awkward and less space-efficient. Also, some toolbar controls just cannot be used vertically, such as drop-down lists.</para>
<para>Only consider using a vertical toolbar if:</para>
diff --git a/hig/C/hig-diff.xml b/hig/C/hig-diff.xml
index 957bb29..60a9870 100644
--- a/hig/C/hig-diff.xml
+++ b/hig/C/hig-diff.xml
@@ -3405,7 +3405,7 @@ the application saves state as it should.</remark>
<row>
<entry><guimenuitem>Print Previe<accel>w</accel></guimenuitem></entry>
<entry><keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>P</keycap></keycombo></entry>
- <entry>Shows the user what the printed document will look like. Present a new window containing an accruate represenation of the appearance of the document as it would be printed. The libgnomeprintui library provides a standard Print Preview window that you should use if possible.</entry>
+ <entry>Shows the user what the printed document will look like. Present a new window containing an accurate representation of the appearance of the document as it would be printed. The libgnomeprintui library provides a standard Print Preview window that you should use if possible.</entry>
</row>
<row>
@@ -3726,7 +3726,7 @@ the application saves state as it should.</remark>
</sect2>
<sect2 id="menu-standard-view">
<title>View</title>
- <para>The <guimenu>View</guimenu> menu contains only items that affect the user's view of the current document. Do not place any items on the <guimenu>View</guimenu> menu that affect the the content of the current document. (Exception: <menuchoice><guimenu>View</guimenu><guimenuitem>Reload</guimenuitem></menuchoice> may change the current contents if, for example, the document is a webpage that has been recently updated on the server).</para>
+ <para>The <guimenu>View</guimenu> menu contains only items that affect the user's view of the current document. Do not place any items on the <guimenu>View</guimenu> menu that affect the content of the current document. (Exception: <menuchoice><guimenu>View</guimenu><guimenuitem>Reload</guimenuitem></menuchoice> may change the current contents if, for example, the document is a webpage that has been recently updated on the server).</para>
<figure id="generic-view-menu">
<title>A generic View menu</title>
@@ -3827,7 +3827,7 @@ the application saves state as it should.</remark>
<row>
<entry><guimenuitem>S<accel>o</accel>rt By...</guimenuitem></entry>
<entry>None</entry>
- <entry>Sorts the contents of an container by user-specified criteria. Open a dialog allowing the user to choose from pre-defined sort keys (for example, Name, Size, or Modification Date in a file manager), or to specify their own if applicable.</entry>
+ <entry>Sorts the contents of a container by user-specified criteria. Open a dialog allowing the user to choose from pre-defined sort keys (for example, Name, Size, or Modification Date in a file manager), or to specify their own if applicable.</entry>
</row>
<row>
@@ -4450,7 +4450,7 @@ the application saves state as it should.</remark>
<chapter id="toolbars">
<title>Toolbars</title>
- <para>A toolbar is a strip of controls that allows convenient access to commonly-used functions. Most toolbars only contain graphical buttons, but in more complex applications, other types of controls such as dropdown lists, can also be useful.</para>
+ <para>A toolbar is a strip of controls that allows convenient access to commonly-used functions. Most toolbars only contain graphical buttons, but in more complex applications, other types of controls such as drop-down lists, can also be useful.</para>
<!-- This bit more relevant to the utility windows section
<note><para>Although the latter is just a side-effect of the fact that palettes can't be created with the standard toolbar widgetsâ it would be rather nice if they could, especially as they would then automatically feature in the toolbar keyboard navigation order.</para></note>
@@ -4549,7 +4549,7 @@ the application saves state as it should.</remark>
<sect2 id="vertical-toolbars">
<title>Vertical Toolbars</title>
- <para>In general, don't use vertical toolbars. The eye does not scan vertically as well as it does horizontally, groups of mutually exclusive buttons are less obvious when arranged vertically, and showing button labels is more awkard and less space-efficient. Also, some toolbar controls just cannot be used vertically, such as dropdown lists.</para>
+ <para>In general, don't use vertical toolbars. The eye does not scan vertically as well as it does horizontally, groups of mutually exclusive buttons are less obvious when arranged vertically, and showing button labels is more awkward and less space-efficient. Also, some toolbar controls just cannot be used vertically, such as drop-down lists.</para>
<para>Only consider using a vertical toolbar if:</para>
@@ -5386,7 +5386,7 @@ the application saves state as it should.</remark>
<para>Once a dialog is displayed, do not change its default button
from one button to another. You may add or remove default status from
the same button if it helps prevent user error, however. Changing the
- default from one button to another can be confusing and inefficent,
+ default from one button to another can be confusing and inefficient,
especially for users relying on assistive technologies.</para>
</listitem>
@@ -5719,7 +5719,7 @@ the application saves state as it should.</remark>
<!-- CB-Fig: Show context for drawing application. -->
<para><remark>At time of writing, the exact visual appearance of a
- mixed state radio button in gtk was undecided</remark><phrase revisionflag="deleted">. In this situation, clicking any radio button in the group should set the clicked button, and unset all the others. Thereafter, the group should behave like a normal radio button group</phrase><phrase revisionflag="deleted"> there is no way to reset a radio button to its mixed state by clicking on it. Provide a </phrase><phrase revisionflag="added">. In this
+ mixed state radio button in gtk was undecided</remark><phrase revisionflag="deleted"> In this situation, clicking any radio button in the group should set the clicked button, and unset all the others. Thereafter, the group should behave like a normal radio button group</phrase><phrase revisionflag="deleted"> there is no way to reset a radio button to its mixed state by clicking on it. Provide a </phrase><phrase revisionflag="added">. In this
situation, clicking any radio button in the group should set the
clicked button, and unset all the others. Thereafter, the group should
behave like a normal radio button groupâ there is no way to reset a
@@ -6014,19 +6014,19 @@ the application saves state as it should.</remark>
<!-- CB-Fig: Be aware that some people may not distinguish between drop-down lists and combo boxes; that is, they are taken as two types of combo boxes, editable and uneditable (see JLF DG). -->
- <!-- How odd, the whole point of a combo box is that it's a combination of a text field and a list... as such, therefore there is no such thing as an 'uneditable combo box' :o) --><para revisionflag="deleted">Combo boxes combine a text entry field and a dropdown list of pre-defined values. Selecting one of the pre-defined values sets the entry field to that value.</para>
+ <!-- How odd, the whole point of a combo box is that it's a combination of a text field and a list... as such, therefore there is no such thing as an 'uneditable combo box' :o) --><para revisionflag="deleted">Combo boxes combine a text entry field and a drop-down list of pre-defined values. Selecting one of the pre-defined values sets the entry field to that value.</para>
- <para revisionflag="added">Drop-down combination boxes combine a text entry field and a dropdown list of
+ <para revisionflag="added">Drop-down combination boxes combine a text entry field and a drop-down list of
pre-defined values. Selecting one of the pre-defined values sets the entry
field to that value.</para>
- <figure><phrase revisionflag="deleted">A combo box before and after its dropdown list is displayed</phrase>
- <title revisionflag="added">A drop-down combination box before and after its dropdown list is displayed</title>
+ <figure><phrase revisionflag="deleted">A combo box before and after its drop-down list is displayed</phrase>
+ <title revisionflag="added">A drop-down combination box before and after its drop-down list is displayed</title>
<mediaobject>
<imageobject>
<imagedata depth="127" fileref="images/controls-combo.png" format="PNG" width="385"/>
- </imageobject><phrase revisionflag="deleted">Two images, one of a combo box entry field displaying its current selection, and the other showing its dropdown list of available choices when clicked on</phrase>
+ </imageobject><phrase revisionflag="deleted">Two images, one of a combo box entry field displaying its current selection, and the other showing its drop-down list of available choices when clicked on</phrase>
<imageobject>
<imagedata fileref="images/controls-combo.eps" format="EPS"/>
@@ -6034,7 +6034,7 @@ the application saves state as it should.</remark>
<textobject>
<phrase revisionflag="added">Two images, one of a drop-down combination box entry field displaying its
- current selection, and the other showing its dropdown list of
+ current selection, and the other showing its drop-down list of
available choices when clicked on</phrase>
</textobject>
</mediaobject>
@@ -6071,7 +6071,7 @@ the application saves state as it should.</remark>
For example, if the user types </phrase><userinput>blue</userinput>,
<userinput>Blue</userinput> and <userinput>BLUE</userinput><phrase revisionflag="changed"> into the
same drop-down combination box on different occasions, only store one of these in the
- combo's dropdown list, unless your application makes a distinction
+ combo's drop-down list, unless your application makes a distinction
between the different forms (which is usually a bad idea).</phrase></para>
</listitem>
@@ -6084,7 +6084,7 @@ the application saves state as it should.</remark>
<listitem>
<para>Use <link linkend="layout-capitalization">sentence
- capitalization</link> for the dropdown list items, for example
+ capitalization</link> for the drop-down list items, for example
<guilabel>Switched movement</guilabel>.</para>
</listitem>
@@ -6407,7 +6407,7 @@ the application saves state as it should.</remark>
<para>A tabbed notebook control is a convenient way of presenting related
information in the same window, without having to display it all at the
- same time. It is analagous to the divider tabs in a ring binder or a file
+ same time. It is analogous to the divider tabs in a ring binder or a file
cabinet.</para>
<figure>
@@ -6549,7 +6549,7 @@ the application saves state as it should.</remark>
<sect2 id="controls-tab-status"><para revisionflag="deleted">FUTURE: it would be good if the notebook control supported a standard way of showing that a tab had pending changes, e.g. changing the font or label colour to some (themed) alternative. </para>
<title revisionflag="added">Status Indicators</title>
<remark revisionflag="added">This section needs more concrete recommendations, it's currently (almost) taken verbatim from Sebastian's patch in bug #72101.</remark>
- <para revisionflag="added">In some tabbed windows, such as preference windows, it might be desirable to indicate the status of a particular tab. This can be used to notify the user that a web page that is still loading or has been loaded, a new message is waiting in a particular instant messasing conversation, or that a document has not been saved. Such a status indicator should be an icon that is placed directly to the left of the tab label. Additionally, the tab label's color might be changed to indicate a certain status. Do not simply rely on a different coloring scheme for status indication.</para>
+ <para revisionflag="added">In some tabbed windows, such as preference windows, it might be desirable to indicate the status of a particular tab. This can be used to notify the user that a web page that is still loading or has been loaded, a new message is waiting in a particular instant messaging conversation, or that a document has not been saved. Such a status indicator should be an icon that is placed directly to the left of the tab label. Additionally, the tab label's color might be changed to indicate a certain status. Do not simply rely on a different coloring scheme for status indication.</para>
</sect2>
</sect1>
@@ -6562,7 +6562,7 @@ the application saves state as it should.</remark>
<para><phrase revisionflag="deleted">There are two types of progress indicator: "measured" progress, which shows what proportion of the task has been completed, and "indeterminate" progress, which only shows that the application is busy. The progress bar control is used to show measured progress. (For more information on indeterminate progress indicators, see </phrase><phrase revisionflag="deleted">.)</phrase><phrase revisionflag="added">You can use two main types of progress bars in your applicationâ
measured-progress bars and indeterminate-progress bars (the kind that
- bounce back and forth). In addition there are are three types of measured
+ bounce back and forth). In addition there are three types of measured
progress bars.</phrase></para>
<itemizedlist><phrase revisionflag="deleted">A measured ("time remaining") progress dialog</phrase>
@@ -6847,7 +6847,7 @@ the application saves state as it should.</remark>
<para>Frames with a border around their perimeter have traditionally been
used for denoting groups of related controls. This is advantageous because
- it physically seperates disimilar controls, and also avoids repitition of
+ it physically separates dissimilar controls, and also avoids repetition of
the frame's label in individual member control labels. Unfortunately,
they add visual noise that can both make a window appear more complex than
it really is, and reduce the ability to quickly scan window elements.</para>
@@ -6903,7 +6903,7 @@ the application saves state as it should.</remark>
window, consider carefully if you really need it. It is usually better
to do without, if the groups can be separated by space alone. Do not
use frames and separators to compensate for poor control layout or
- alignnment.</para>
+ alignment.</para>
</listitem>
<listitem>
@@ -8626,7 +8626,7 @@ Message Dialogs should be 600 by 200.</phrase><remark revisionflag="added"> I'm
<para>Icons are a graphical metaphor presenting a visual image that the user associates with a particular object, state or operation. When a user sees a good icon they are immediately reminded of the item it represents, whether that be an application in the panel menu or the "right aligned" state in a word processor toolbar.</para>
<para>
<itemizedlist>
- <listitem><para>Icons can assist the user in rapidly scanning a large number of objects to select the desired item. Particularly after a user is acustomed to an icon's appearance, they can identify it more rapidly than a text label.</para></listitem>
+ <listitem><para>Icons can assist the user in rapidly scanning a large number of objects to select the desired item. Particularly after a user is accustomed to an icon's appearance, they can identify it more rapidly than a text label.</para></listitem>
<listitem><para>Icons can augment text by providing visual suggestions to accompany the descriptive text. Some things are easier to communicate with a picture, even a very small one.</para></listitem>
<listitem><para>Icons can compactly represent a large number of objects when there is insufficient space to display textual descriptions (such as in a toolbar).</para></listitem>
</itemizedlist>
@@ -8811,7 +8811,7 @@ Message Dialogs should be 600 by 200.</phrase><remark revisionflag="added"> I'm
<sect2 id="application_icons">
<title>Application Icons</title>
<!-- FIXME: we could give a lot more useful guidance here -->
- <para>Application's that handle documents should reflect the kind of document they handle in the icon. If an application's predominant purpose is to edit a particular kind of document, it should use this document's icon as its icon.</para>
+ <para>Applications that handle documents should reflect the kind of document they handle in the icon. If an application's predominant purpose is to edit a particular kind of document, it should use this document's icon as its icon.</para>
</sect2>
<sect2 id="toolbar_icons">
@@ -8821,7 +8821,7 @@ Message Dialogs should be 600 by 200.</phrase><remark revisionflag="added"> I'm
<listitem><para>Ensure that toolbar icons which will be used together are easy to visually distinguish. Try to <link linkend="icon_design_silhouettes">make the icons' silhouettes distinct</link> from one another.</para></listitem>
<listitem><para>While most user's will view toolbar icons at 24x24 pixels, it is important to include a "large print" set of icons at 48x48 pixels for accesibility reasons.</para></listitem>
<listitem><para>Often, you will not have to design any toolbar icons yourself as GTK provides a wide variety of stock icons. You should use these whenever representing one of their intended items. This establishes consistent language across applications, and makes it easier for users to search for items on the toolbar. Do not use stock toolbar icons for anything other than their intended purpose, however, as this will make your application inconsistent with others, and could easily confuse your users.</para>
- <para>To browse the available stock icons, install the development packages for GTK version 2.x and run <command>gtk-demo</command>. Double click on <guimenuitem>Stock Item and Icon Browser</guimenuitem> to activate the stock icon browser. Note that icons vary in available resolution, so the images presented in the icon browser should not be taken as indicative of the maximuum quality of an image. To view the images in PNG format, look in the GTK 2 source code under <filename class="directory">gtk/stock-icons</filename>.</para></listitem>
+ <para>To browse the available stock icons, install the development packages for GTK version 2.x and run <command>gtk-demo</command>. Double click on <guimenuitem>Stock Item and Icon Browser</guimenuitem> to activate the stock icon browser. Note that icons vary in available resolution, so the images presented in the icon browser should not be taken as indicative of the maximum quality of an image. To view the images in PNG format, look in the GTK 2 source code under <filename class="directory">gtk/stock-icons</filename>.</para></listitem>
</itemizedlist>
</sect2>
@@ -8943,7 +8943,7 @@ Message Dialogs should be 600 by 200.</phrase><remark revisionflag="added"> I'm
</mediaobject>
</listitem>
<listitem>
- <para>Now you should hand-create create a version of this icon at 24x24. Do <emphasis>not</emphasis> simply scale the larger icon, as this icon will be seen by the majority of users and the result of scaling would be less distinct:</para>
+ <para>Now you should hand-create a version of this icon at 24x24. Do <emphasis>not</emphasis> simply scale the larger icon, as this icon will be seen by the majority of users and the result of scaling would be less distinct:</para>
<mediaobject>
<imageobject><imagedata fileref="images/icon-design-process-9.png" format="PNG"/></imageobject>
<imageobject><imagedata fileref="images/icon-design-process-9.eps" format="EPS"/></imageobject>
@@ -9189,7 +9189,7 @@ End:
<listitem><para><keycombo><keycap><phrase revisionflag="deleted">(or perhaps </phrase>Ctrl</keycap><mousebutton revisionflag="changed">scrollwheel-up</mousebutton></keycombo><phrase revisionflag="changed"> should zoom into the window or control under the mouse pointer, and </phrase><keycombo><keycap revisionflag="changed">Ctrl</keycap><mousebutton revisionflag="added">scrollwheel-down</mousebutton></keycombo><phrase revisionflag="added"> should zoom out. Zooming in this way should not move keyboard focus to the window or control being zoomed.</phrase></para></listitem>
- <listitem><para>Do not depend on input from the middle or right mouse buttons. As well as being physically more difficult to click, some pointing devices and many assistive technology devices only support or emulate the left mouse button. Some assistive technologies may noteven emulate the mouse at all, but generate keyboard events instead.</para></listitem>
+ <listitem><para>Do not depend on input from the middle or right mouse buttons. As well as being physically more difficult to click, some pointing devices and many assistive technology devices only support or emulate the left mouse button. Some assistive technologies may not even emulate the mouse at all, but generate keyboard events instead.</para></listitem>
<listitem><para>Ensure that every operation in your application that can be done with the mouse can also be done with the keyboard. The only exceptions to this are actions where fine motor control is an essential part of the task. For example, controlling movement in some types of action games, or freehand painting in an image-editing application.</para></listitem>
@@ -9474,7 +9474,7 @@ or by dropping the object on an invalid drop target.</phrase>
<textobject><phrase revisionflag="added">"Link" pointer</phrase></textobject>
</mediaobject>
</entry>
- <entry revisionflag="added">Link selection. A link to the selection will be inserted at the drop location. How the link appears will be application-dependent, it may be a hyperlink, an icon, or a duplicate of the orignal selection, for example.</entry>
+ <entry revisionflag="added">Link selection. A link to the selection will be inserted at the drop location. How the link appears will be application-dependent, it may be a hyperlink, an icon, or a duplicate of the original selection, for example.</entry>
</row>
<row><phrase revisionflag="deleted">"Link" pointer</phrase>
@@ -10240,7 +10240,7 @@ or by dropping the object on an invalid drop target.</phrase>
<para>The rules for panel application keyboard navigation are mostly the same as those for any other window. However, there is one imporant difference:</para>
<itemizedlist>
- <listitem><para>Do <emphasis>not</emphasis> use the the <keycap>Tab</keycap> key as the means of moving focus between controls in a panel application. Use the arrow keys for this purpose instead.</para></listitem>
+ <listitem><para>Do <emphasis>not</emphasis> use the <keycap>Tab</keycap> key as the means of moving focus between controls in a panel application. Use the arrow keys for this purpose instead.</para></listitem>
</itemizedlist>
<para>When an object on a panel has focus, the <keycap>Tab</keycap> key normally moves focus to the next object on the panel. If your panel application also used <keycap>Tab</keycap> for its own internal navigation, the user would have to press <keycombo><keycap>Ctrl</keycap><keycap>Tab</keycap></keycombo> to move focus out of your panel application instead. This inconsistency would be detremental to the user experience.</para>
@@ -10280,7 +10280,7 @@ or by dropping the object on an invalid drop target.</phrase>
<listitem><para>Do not include text in windows that describes <emphasis>how</emphasis> to use the interface, for example <guilabel>You can install a new theme by dropping it here</guilabel>. As well as adding visual clutter, descriptive labels can also conflict with information provided in documentation.</para></listitem>
- <listitem><para>Use standard terms. You can find a list of standard user interface terms in the <ulink url="http://developer.gnome.org/documents/style-guide/wordlist.html";>GNOME Documentation Style Guide, Recommended Terminology</ulink>..</para></listitem>
+ <listitem><para>Use standard terms. You can find a list of standard user interface terms in the <ulink url="http://developer.gnome.org/documents/style-guide/wordlist.html";>GNOME Documentation Style Guide, Recommended Terminology</ulink>.</para></listitem>
<listitem><para>Apply standard capitalization rules. See <xref linkend="layout-capitalization"/> for guidelines about capitalization of user interface labels </para></listitem>
</itemizedlist>
@@ -10427,7 +10427,7 @@ example. An transitional paragraph probably needs to be added after the "right"
<para>Test various GNOME themes to ensure that your application respects all the available settings.</para>
- <para>Test your application with black and white, high contrast themes and confirm that all information is still conveyed correctly. If you don't have a suitable high contrast GNOME theme available to test, print off some screenshots in black and white (not greyscale) and make sure all the important information is still visibleâ this will approximate what a high contrast theme user will see.</para>
+ <para>Test your application with black and white, high contrast themes and confirm that all information is still conveyed correctly. If you don't have a suitable high contrast GNOME theme available to test, print off some screenshots in black and white (not grayscale) and make sure all the important information is still visibleâ this will approximate what a high contrast theme user will see.</para>
</sect2>
<sect2>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
