<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY whatsnew SYSTEM "hig-ch-whatsnew.xml">
<!ENTITY checks SYSTEM "hig-ch-checks.xml">
<!ENTITY controls SYSTEM "hig-ch-controls.xml">
<!ENTITY credits SYSTEM "hig-ch-credits.xml">
<!ENTITY desktop SYSTEM "hig-ch-desktop.xml">
<!--ENTITY dialogs-old SYSTEM "hig-ch-dialogs-old.xml"--><!ENTITY feedback SYSTEM "hig-ch-feedback.xml">
<!ENTITY gnome3 SYSTEM "hig-ch-gnome3.xml">
<!ENTITY icons SYSTEM "hig-ch-icons.xml">
<!--ENTITY icons-new SYSTEM "hig-ch-icons-new.xml"--><!ENTITY input SYSTEM "hig-ch-input.xml">
<!ENTITY intro SYSTEM "hig-ch-intro.xml">
<!ENTITY language SYSTEM "hig-ch-language.xml">
<!ENTITY layout SYSTEM "hig-ch-layout.xml">
<!ENTITY menus SYSTEM "hig-ch-menus.xml">
<!ENTITY principles SYSTEM "hig-ch-principles.xml">
<!ENTITY toolbars SYSTEM "hig-ch-toolbars.xml">
<!ENTITY windows SYSTEM "hig-ch-windows.xml">
<!ENTITY bibliography SYSTEM "hig-ch-bibliography.xml">
]>
<book id="index" lang="es">
<bookinfo>
    <author role="maintainer"><firstname>El proyecto de usabilidad de GNOME</firstname></author>
<copyright>
<year>2002-2011</year>
<holder>Calum Benson, Adam Elman, Seth Nickell, Colin Z Robertson</holder>
</copyright><copyright><year>2011</year><holder>Daniel Mustieles (daniel.mustieles@gmail.com)</holder></copyright><copyright><year>2011</year><holder>Benjamín Valero Espinosa (benjavalero@gmail.com)</holder></copyright><copyright><year>2009</year><holder>Jorge González (jorgegonz@svn.gnome.org)</holder></copyright>
<pubdate>2011-03-21</pubdate>
<edition>2.2.2</edition>

<abstract role="description">
<para>Este documento le dice cómo crear aplicaciones que parezcan correctas, se comporten de forma apropiada y que se ajusten a la interfaz de usuario de GNOME como un todo. Está escrito para diseñadores de interfaces, artistas gráficos y desarrolladores de software que crearán software para el entorno GNOME. Se cubren consejos específicos tanto acerca del uso efectivo de los elementos de la interfaz como de los principios de filosofía y diseño generales detrás de la interfaz de GNOME.</para>
</abstract>

<legalnotice>
  <para>Se otorga permiso para copiar, distribuir y/o modificar este documento bajo los términos de la <citetitle>Licencia de Documentación Libre de GNU</citetitle>, Versión 1.1 o cualquier otra versión posterior publicada por la Free Software Foundation; sin Secciones Invariantes ni Textos de Cubierta Delantera ni Textos de Cubierta Trasera. Puede encontrar una copia de la licencia <citetitle>Licencia de Documentación Libre de GNU</citetitle> de la Free Software Foundation visitando <ulink type="http" url="http://www.fsf.org">su página web</ulink> o escribiendo a: Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, EE. UU.</para>
  <para>Muchos de los nombres usados por compañías para distinguir sus productos y servicios se mencionan como marcas comerciales. Donde aparezcan dichos nombres en cualquier documentación GNOME, y para que los miembros del proyecto de documentación las reconozcan dichas marcas comerciales, dichos nombres se imprimen en mayúsculas o iniciales mayúsculas.</para>
</legalnotice>

<title>Guías de la interfaz humana de GNOME 2.2.2</title>

</bookinfo>


<!-- :xml.root=hig-book.xml: -->

  <preface id="whatsnew">
    <title>¿Qué hay nuevo?</title>
    <para>Esta sección resalta los cambios recientes en el HIG que pueden afectar a su aplicación.</para>

    <para>Se realizaron los siguientes cambios en las GIH v2.2.2:</para>
    <itemizedlist>
	<listitem><para>Adición de <xref linkend="note-on-gnome3"/> respecto a la relevancia de la guía en GNOME 3.</para></listitem>
	</itemizedlist>

     <para>Se realizaron los siguientes cambios en las GIH v2.2.1:</para>
    <itemizedlist>
	<listitem><para>Mencionar en la <xref linkend="windows-progress"/> que se prefieren los indicadores de progreso en lugar de las ventanas de diálogo de progreso.</para></listitem>
    	<listitem><para>Cambie la orientación en la <xref linkend="windows-progress"/> acerca de las ventanas de progreso que tienen el título igual que su texto primario, conducen a una redundancia innecesaria. El consejo ahora es que el título de la ventana de progreso debe resumir el funcionamiento general.</para></listitem>	
	</itemizedlist>

    <para>Se añadieron las siguientes secciones en las GIH v2.0:</para>
    <itemizedlist>
    	<listitem><para>
	    	<xref linkend="gconf-keys"/>
		</para></listitem>	
	<listitem><para>
	    	<xref linkend="windows-show-hide"/>
		</para></listitem>
	<listitem><para>
	    	<xref linkend="desktop-notification-area"/>
		</para></listitem>
	<listitem><para>
	    	<xref linkend="windows-progress"/>
		</para></listitem>
        <listitem><para>
	    	<xref linkend="toolbars-media"/>
		</para></listitem>
		<listitem><para>
	    	<xref linkend="controls-scrollbars"/>
		</para></listitem>
	<listitem><para>
	    	<xref linkend="controls-lists-sortable"/>
		</para></listitem>
	<listitem><para>
	    	<xref linkend="controls-trees-sortable"/>
		</para></listitem>
	<listitem><para>
	    	<xref linkend="controls-tab-status"/>
		</para></listitem>
	<listitem><para>
	    	<xref linkend="controls-progress-bars"/>
		</para></listitem>
		<listitem><para>
	    	<xref linkend="icons-design-accessible"/>
		</para></listitem>
	<listitem><para>
	    	<xref linkend="bibliography"/>
		</para></listitem>
	</itemizedlist>

	
    <para>Se añadieron o revisaron nuevas guías en las GIH v2.0 a las siguientes secciones:</para>

  	<itemizedlist>
	    <listitem><para>
		<xref linkend="internationalization"/>
		</para></listitem>

	    <listitem><para>
		<xref linkend="desktop-integration"/>
		</para></listitem>

	    <listitem><para>
		<xref linkend="windows-primary"/>
		</para></listitem>
	    
	    <listitem><para>
		<xref linkend="windows-utility"/>
		</para></listitem>

	     <listitem><para>
		<xref linkend="alerts-confirmation"/>
		</para></listitem>
	
	     <listitem><para>
		<xref linkend="windows-assistant"/>
		</para></listitem>

	     <listitem><para>
		<xref linkend="menus-menubar"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="the-file-menu"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="menu-standard-view"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="menu-standard-bookmarks"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="menu-standard-go"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="application-windows-menu"/>
		</para></listitem>

	       <listitem><para>
		<xref linkend="controls-status-bars"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="controls-entry"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="controls-frames"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="feedback-choosing"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="feedback-interrupting"/>
		</para></listitem>

	       <listitem><para>
		<xref linkend="layout-capitalization"/>
		</para></listitem>

	     <listitem><para>
		<xref linkend="mouse-buttons"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="selection"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="drag-drop"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="choosing-access-keys"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="shortcuts"/>
		</para></listitem>

	      <listitem><para>
		<xref linkend="standard-shortcuts"/>
		</para></listitem>

	</itemizedlist>

<para>Se introdujeron los siguientes cambios de terminología en las GIH v2.0:</para>
<itemizedlist>
	<listitem><para>Ahora los «Menús de opciones» se llaman «Listas desplegables»</para></listitem>
	<listitem><para>Ahora a las «Cajas de combinación» se las llama «Cajas de combinación desplegables»</para></listitem>
</itemizedlist>

</preface>



  <preface id="intro">
    <title>Introducción</title>
    <para>Este documento le dice cómo crear aplicaciones que parezcan correctas, se comporten de forma apropiada y que se ajusten a la interfaz de usuario de GNOME como un todo. Está escrito para diseñadores de interfaces, artistas gráficos y desarrolladores de software que crearán software para el entorno GNOME. Se cubren consejos específicos tanto acerca del uso efectivo de los elementos de la interfaz como de los principios de filosofía y diseño generales detrás de la interfaz de GNOME.</para>
    <para>Estas guías están pensadas para ayudarle a diseñar y escribir aplicaciones fáciles de usar y consistentes con el Escritorio GNOME. Seguir las guías proporciona muchos beneficios: <itemizedlist>
	<listitem><para>Los usuarios aprenderán a usar su programa más rápidamente porque los elementos de la interfaz parecerán y se comportarán de la forma a la que están acostumbrados.</para></listitem>
	<listitem><para>Tanto los usuarios nuevos y avanzados serán capaces de completar tareas rápida y fácilmente porque la interfaz no les confundirá ni pondrá las cosas difíciles.</para></listitem>
	<listitem><para>Su aplicación tendrá un aspecto atractivo que encaja con el resto del escritorio.</para></listitem>
	<listitem><para>Su aplicación continuará siendo atractiva cuando los usuarios cambien los temas, tipografías y colores del escritorio.</para></listitem>
	<listitem><para>Su aplicación sera accesible para todos los usuarios, incluyendo aquellos con discapacidades o necesidades especiales.</para></listitem>
      </itemizedlist></para>
    <para>Para ayudarle a lograr esos objetivos, estas guías cubren elementos de interfaz básicos, cómo usarlos y conjuntarlos de forma efectiva y cómo hacer que su aplicación se integre bien con el escritorio.</para>
    <para>Las recomendaciones aquí construidas son acerca de aspectos de diseño que funcionan bien en otros sistemas operativos, incluyendo Mac OS, Windows, Java y KDE. Al mismo tiempo contienen un sabor único para GNOME.</para>

    <tip><title>Recuerde...</title>
       <para>Seguir las guías hará su trabajo más fácil, no más difícil</para>
    </tip>

  </preface>




  <preface id="note-on-gnome3">
    <title>Aplicabilidad en GNOME 3</title>
	<para>Esta versión de la Guía de la interfaz humana la escribieron diseñadores y desarrolladores de las aplicaciones de GNOME 2. Está enfocada en reflejar los consejos ofrecidos y en las ilustraciones que los acompañan.</para>

	<para>Ya que muchas se aplican igual para GNOME 3, puede y debe continuar seguir la mayoría de estos principios y guías de accesibilidad para GNOME 3.</para>

	<para>Se publicará un documento enfocado en la Guía de la interfaz humana para GNOME 3. Mientras tanto, puede encontrar algunas guías específicas en la página wiki <ulink url="http://live.gnome.org/GnomeShell/Design/Guidelines">Guía para GNOME Shell</ulink>.</para>

	<para>El proyecto de usabilidad de GNOME, marzo de 2011</para>

  </preface>




  <chapter id="principles">
    
    <title>Principios de usabilidad</title>

    <para>Esta sección explica algunos de los principios básicos detrás de las guías técnicas más específicas recomendadas en este documento. Creemos que esos principios son importantes para todo desarrollo de aplicación.</para>

    <sect1 id="principles-people">
      <title>Diseñe para personas</title>

      <para>Recuerde que el propósito de cualquier aplicación de software es permitir a un grupo de personas llevar a cabo un conjunto de tareas específicas. De tal forma que lo primero que establecer al diseñar una aplicación es:</para>

	<orderedlist>
		<listitem><para>quiénes son sus usuarios</para></listitem>
		<listitem><para>lo que quiere permitirles hacer</para></listitem>
	</orderedlist>

      <para>Por ejemplo, puede que esté diseñando una aplicación que permita a los ingenieros (de software, electricidad o mecánica) crear diagramas. Puede que esté diseñando una aplicación que permita a los administradores de sistemas configurar y monitorizar un servidor web. Puede que esté diseñando una aplicación que ayude a estudiantes de primaria a aprender matemáticas.</para>

      <para>Lo importante es que conozca a su audiencia y que comprenda tanto sus metas como las tareas necesarias para conseguir estas metas. Hay una gran cantidad de diseñadores de interacción profesionales que escriben libros e imparten cursos sobre métodos de diseño que pueden ayudar en este proceso, muchos de los cuales son increíblemente útiles: vea la <xref linkend="bibliography"/> para una selección. Sin embargo, la mayoría de estos métodos se reducen a especificar maneras de entender a sus usuarios, entender las tareas que quiere ayudarles a realizar y encontrar maneras para soportar esas tareas en su aplicación.</para>

    </sect1>
    <sect1 id="principles-broad-userbase">
      <title>No limite su base de usuarios</title>

      <para>Si está diseñando una aplicación para que la usen ingenieros, niños o administradores de sistemas, asegúrese de crear una aplicación que puedan usar <emphasis>todos</emphasis> los ingenieros, niños o administradores de sistemas, incluidos los discapacitados o aquellos con una lengua madre distinta a la suya. Sea consciente de los problemas de accesibilidad, internacionalización y localización, la mayoría de los cuales son tratados en las guías de este documento.</para>

      <sect2 id="accessibility">
	<title>Accesibilidad</title>

	<para>Accesibilidad (a veces llamada <emphasis>a11y</emphasis>) significa posibilitar la participación de las personas con algún tipo de discapacidad en las actividades de la vida diaria: en este caso, especialmente usar su software. Por ejemplo:</para>

	<itemizedlist>
		<listitem><para>Puede que los usuarios daltónicos no sean capaces de usar su aplicación si confía en el coloreado de datos para distinguir distintos tipos de información</para></listitem>
		<listitem><para>Puede que los usuarios con discapacidades auditivas no sean capaces de usar su aplicación si confía en los sonidos para indicar información crítica</para></listitem>
		<listitem><para>Los usuarios con movilidad limitada pueden no ser capaces de usar su aplicación si no proporciona equivalentes de teclado para los comandos</para></listitem>
	</itemizedlist>

	<para>Su software debería poder utilizarse también con interfaces de voz, lectores de pantalla como <ulink url="http://developer.gnome.org/projects/gap/AT/Gnopernicus/index.html">Gnopernicus</ulink>, dispositivos de entrada alternativos y otras tecnologías de asistencia. Las bibliotecas estándar de GNOME hacen la mayoría de este trabajo por usted, pero con un poco más de esfuerzo puede hacer que su aplicación igual de útil para los usuarios que confían en esas tecnologías como en los que no.</para>

	<para>GNOME tiene un excelente soporte integrado para la accesibilidad gracias a las bibliotecas ATK y GAIL, que en muchos de los casos pueden hacer la mayor parte del trabajo por usted. Puede encontrar más información sobre accesibilidad en GNOME en el <ulink url="http://developer.gnome.org/projects/gap/">Proyecto de accesibilidad de GNOME</ulink>.</para>

      </sect2>
      <sect2 id="internationalization">
	<title>Internacionalización y localización</title>

	<para>La internacionalización significa diseñar software de manera que pueda funcionar en diferentes entornos lingüísticos. La localización es el proceso de traducir realmente mensajes, etiquetas y otros elementos de la interfaz de una aplicación a otro idioma.</para>

	<para>GNOME tiene un soporte excelente tanto para la internacionalización (también mencionada como i18n) como para la localización (también mencionada como l10n). En la mayoría de los casos, el simple uso de las API estándares de GNOME para mostrar texto y mensajes le permitirá (y también a otros) localizar su aplicación para otros idiomas. Para más información sobre cómo hacer su aplicación localizable, consulte la <ulink url="http://www.pango.org">página del proyecto Pango</ulink> (Pango es la biblioteca GNOME para mostrar texto internacionalizado), la <ulink url="http://www.gnome.org/i18n/">página de traducciones de GNOME</ulink> y la <ulink url="http://developer.gnome.org/projects/gtp/">página del proyecto de traducción de GNOME</ulink>.</para>
	
	<para>Es importante considerar la sensibilidad sobre cuestiones culturales y políticas. Diseñar iconos y sonidos, e incluso elegir colores requiere comprender algunas de las connotaciones que pueden tener en un usuario de una parte diferente del mundo.</para>
	<para>Ejemplos de lo que es mejor evitar por estas razones incluyen:</para>
	<itemizedlist>
		<listitem><para>Imágenes de banderas o dinero</para></listitem>
		<listitem><para>Mapas mostrando límites políticos o nombres de ubicaciones polémicas</para></listitem>
		<listitem><para>Lista de países o ciudades en orden no alfabético (a no ser que se solicite o requiera por el contexto)</para></listitem> 
		<listitem><para>Iconos que representen animales</para></listitem>
		<listitem><para>Iconos que representen solamente pies o manos</para></listitem>
	</itemizedlist>

      </sect2>
    
    </sect1>

    <sect1 id="principles-match">
      <title>Crear una coincidencia entre su aplicación y el mundo real</title>

      <para id="use-users-language">Use siempre palabras, frases y conceptos que sean familiares para el usuario en lugar de términos del sistema subyacente. Use términos relacionados con el conocimiento del usuario sobre las tareas que soporta su aplicación. Por ejemplo, en medicina, a la carpeta que contiene toda la información sobre un paciente específico se le llama «historial». Por tanto, una aplicación médica podría referirse al registro de un paciente que contiene la misma información que un historial como «historial del paciente» en lugar de «registro del paciente de la base de datos».</para>

      <para>A menudo puede aprovecharse del conocimiento de sus usuarios del mundo real usando metáforas (esto es, un concepto familiar del mundo exterior) para representar elementos dentro de su aplicación. Por ejemplo:</para>

	<itemizedlist>
		<listitem><para>una imagen de un archivo de carpeta sugiere un contenedor donde se pueden introducir documentos</para></listitem>
		<listitem><para>una papelera de reciclaje sugiere un contenedor donde se pueden ubicar elementos cuando no se necesitan</para></listitem>
	</itemizedlist>

      <para>Sin embargo, al usar metáforas, es importante no tomar las metáforas demasiado literalmente ni extender la metáfora más allá de su uso razonable. Por ejemplo, la capacidad de una carpeta de archivos no debería estar limitada a la capacidad de una carpeta de archivos física, que en principio puede contener solo unos pocos documentos antes de hacerse inmanejable. Por otra parte, una papelera no debería usarse para otra cosa que no sea contener archivos descartados. No debería usarse por ejemplo para sacar un disco extraíble como un disquete o un CD.</para>
    </sect1>

    <sect1 id="principles-consistency">
      <title>Haga que su aplicación sea consistente</title>

      <para>Haga su aplicación consistente con ella misma y con otras aplicaciones, tanto en su apariencia como en su comportamiento. Este es uno de los principios de diseño más importantes, y probablemente el más famoso, pero también es frecuentemente olvidado. Aunque este documento sirve como base para la consistencia entre las aplicaciones de GNOME, le animamos para que busque y siga las convenciones de otras aplicaciones donde este documento  no proporcione guías.</para>

      <para>La consistencia permite a los usuarios aplicar su conocimiento existente sobre su entorno informático y otras aplicaciones para entender una nueva aplicación. Esto no solo permite que los usuarios se familiaricen con las nuevas aplicaciones más rápidamente, sino que también ayuda a crear una sensación de comodidad y confianza en el entorno general. La mayoría de las recomendaciones en las guías HI de GNOME están diseñadas para ayudarle a crear aplicaciones que sean consistentes con el entorno GNOME y otras aplicaciones GNOME.</para>

      <para>Un toque de atención: una consistencia incorrecta o incompleta a menudo es peor que la inconsistencia. Si su aplicación incluye un elemento de menú <guimenuitem>Deshacer</guimenuitem> por consistencia, pero está siempre desactivado porque su aplicación no soporta realmente deshacer, esto reducirá la confianza del usuario en la disponibilidad de la acción deshacer en otras aplicaciones de su escritorio. Haga que su aplicación soporte deshacer, o bien elimine el elemento de menú <guimenuitem>Deshacer</guimenuitem>.</para>

    </sect1>

    <sect1 id="principles-feedback">
      <title>Mantener informado al usuario</title>

      <para>Permita siempre al usuario saber qué está pasando en su aplicación, proporcionando contexto adecuado en el momento adecuado. El usuario no debería tener que adivinar el estado del sistema o de su aplicación. Cuando el usuario realiza una acción, proporcione información para indicar que el sistema ha recibido la entrada y está trabajando en ella. La información puede ser visual, sonora o ambas. Si el sistema tarda mucho en procesar la solicitud, proporcione toda la información que sea posible sobre la duración que tendrá la operación. Los tipos de retroalimentación adecuados incluyen (pero no se limitan a): cambios en el cursor, imágenes animadas, indicadores de progreso, información sonora como un pitido y mensajes de error. Los mensajes de error deberían usar un lenguaje simple, aclarando el estado del problema y proporcionando soluciones para indicar al usuario cómo resolver la situación actual, si es posible.</para>

      <para>Es crítico que la respuesta sea <emphasis>clara</emphasis> y <emphasis>precisa</emphasis>. Si muestra algún indicador de progreso para mostrar el estado de finalización de una tarea y es impreciso, el usuario perderá confianza en los indicadores de progreso y verá el entorno menos útil. Si muestra algún mensaje de error genérico que indica que hay un problema pero falla al proporcionar suficiente información para diagnosticarlo o resolverlo, los usuarios no podrán continuar con su tarea.</para>
      <para>Para obtener más información acerca de los comentarios consulte la <xref linkend="feedback"/> y la <xref linkend="windows-alert"/>.</para>
    </sect1>

    <sect1 id="principles-simplicity">
      <title>Mantenerlo simple y bonito</title>

      <para>Su aplicación debe permitir al usuario concentrarse en su tarea actual. Por lo tanto, diseñe su aplicación para que solo muestre información y elementos de interfaz útiles y relevantes. Cada pieza extra de información o control en la interfaz compite con los verdaderos elementos de información y distrae al usuario de la información importante. Por tanto, no desordene su interfaz y no sobrecargue al usuario con botones, menús de opciones, iconos u otra información irrelevante. En su lugar, use la muestra progresiva y otras técnicas para limitar lo que el usuario ve en cada momento.</para>

      <para>Finalmente, presente su información y los elementos de la interfaz de una manera estéticamanete placentera. Una interfaz desordenada, desorganizada, con pocos elementos puede distraer tanto como una interfaz organizada con demasiada información. Asegúrese que los elementos de diálogo estén alineados y no abuse o use indebidamente gráficos o colores. Si conoce un diseñador gráfico, pídale consejo si puede; las guías en este documento le ayudarán con lo básico pero nada sustituye al ojo entrenado.</para>

	<para>Para obtener más información acerca del diseño visual y la apariencia de su aplicación consulte la <xref linkend="design"/> y la <xref linkend="icons"/>.</para>

    </sect1>

    <sect1 id="principles-user-control">
      <title>Dé el control al usuario</title>

      <para>Recuerde que las máquinas existen para servir a las personas. Un usuario debería sentir siempre que tiene el control y que es capaz de hacer lo que quiere cuando quiere. Esto significa que, generalmente, debería evitar los modos; los usuarios deberían poder cambiar entre diferentes tareas (y específicamente, entre diferentes ventanas) en cualquier comento. Para obtener más información sobre los modos, consulte la <xref linkend="window-props-modality"/>.</para>

      <para>El usuario debe poder adecuar aspectos de su entorno a sus preferencias personales. No obstante es muy importante evitar la trampa de permitir demasiadas opciones de configuración, o permitir la configuración de parámetros que la mayoría de los usuarios no entiendan o cuya modificación sea inútil. Siempre que sea posible herede parámetros visuales y de comportamiento de las preferencias y configuraciones globales, como las del tema GTK+ actual.</para>
    </sect1>

    <sect1 id="principles-forgiveness">
      <title>Perdonar al usuario</title>

      <para>Todo el mundo comete errores. Aunque esté explorando y aprendiendo cómo utilizar el sistema, o sea un experto que simplemente pulsó tecla equivocada, errar es humano. Su aplicación debe, por lo tanto, permitir al usuario deshacer rápidamente los resultados de sus acciones.</para>

      <para>Si una acción es muy peligrosa, y no hay forma de deshacer el resultado, advierta al usuario y solicite confirmación. Hágalo solo en casos extremos; si el usuario se enfrenta muy frecuentemente con esos mensajes de confirmación, tiende a ignorarlos, haciendo que sean más que inútiles.</para>

      <para>En todos los casos, el trabajo del usuario es sagrado. Nada que haga su aplicación debe destruir o perder el trabajo del usuario sin acción explícita del mismo. Entre otras técnicas, esto puede lograrse con guardado el automático de copias de respaldo de los documentos y permitiendo deshacer en múltiples niveles.</para>

    </sect1>

    <sect1 id="principles-direct-manipulation">
      <title>Proporcionar manipulación directa</title>

      <para>Siempre que sea posible, permita al usuario actuar sobre datos y objetos directamente en vez de mediante diálogos o comandos explícitos. Por ejemplo, es más intuitivo arrastrar un círculo por un diagrama que seleccionar el comando «Mover» de un menú mientras el círculo está marcado. De la misma manera, en una aplicación de correo, permita al usuario adjuntar archivos arrastrándolos desde el administrador de archivos y soltándolos en la ventana de edición del mensaje si lo desea.</para>

	<para>Para obtener más información acerca de la manipulación directa consulte la <xref linkend="input"/>.</para>

    </sect1>

  </chapter>




<chapter id="desktop-integration">
  <title>Integración en el escritorio</title>
  
  <para>Hay dos elementos básicos de integración con el entorno de usuario del escritorio GNOME. <orderedlist>
      <listitem><para>Ponga una entrada para su aplicación en el menú <guimenu>Aplicaciones</guimenu>. Este es el primer mecanismo por el cual los usuarios descubren y ejecutan aplicaciones.</para></listitem>
      <listitem><para>Si su aplicación puede abrir y guardar archivos, ubique entradas para esos tipos de archivo en la base de datos de la aplicación y en la base de datos de tipo de documento (MIME). Esto permite al administrador de archivos y otras aplicaciones lanzar automáticamente su aplicación cuando encuentren archivos que ésta pueda manipular.</para></listitem>
    </orderedlist> No agregue lanzadores ni otros iconos al escritorio cuando se instala su aplicación. El escritorio es el espacio del usuario y está reservado para iconos que él mismo agregue o requiera explícitamente.</para>
  <sect1 id="desktop-application-menu">
    <title>Poner entradas en el menú de Aplicaciones</title>
    
	<figure><title>El menú de Aplicaciones</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/desktop-applications-menu.png" format="PNG" width="160" depth="365"/></imageobject>
	    <imageobject><imagedata fileref="images/desktop-applications-menu.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Captura de pantalla del menú Aplicaciones en el panel del menú de GNOME</phrase></textobject>
	  </mediaobject>
	</figure>
	
       <para>El menú <guimenu>Aplicaciones</guimenu>, que aparece en el panel en la parte superior de la pantalla de manera predeterminada, es el mecanismo principal mediante el que los usuarios descubren y ejecutan aplicaciones. Puede agregar entradas a éste menú instalando un archivo <filename>.desktop</filename> adecuado.</para>

    <para>El menú se dispone en un conjunto de categorías, tales como Accesorios y Juegos. Las aplicaciones se ubican en categorías particulares por conjuntos de palabras clave que incluyen en su archivo <filename>.desktop</filename>.</para>

	<itemizedlist><title>Guías</title>
		<listitem><para>Asigne su aplicación a la única categoría en el menú <guimenu>Aplicaciones</guimenu></para></listitem>

		<listitem><para>Para conjuntos de aplicaciones que contienen pequeñas sub-aplicaciones en una sola ventana, como Evolution u OpenOffice.org, agregue una entrada de menú para cada sub-aplicación. Por ejemplo, el correo, calendario y lista de tareas de Evolution deberían tener cada una su entrada individual en el menú.</para></listitem>

	</itemizedlist>

	<para>Se pueden encontrar detalles técnicos en freedesktop.org, las especificaciones de <ulink url="http://freedesktop.org/Standards/menu-spec">menú</ulink> y <ulink url="http://www.freedesktop.org/Standards/desktop-entry-spec">entradas de escritorio</ulink>.</para>


    <sect2 id="menu-item-names">
      <title>Nombres de elementos del menú</title>


      <sect3 id="menu-item-functional-description">
	<title>Incluir una descripción funcional en el nombre del menú</title>

	<para>En la entrada de menú incluya una descripción de funcionalidad, así como el nombre apropiado para la aplicación. Esto es especialmente útil para usuarios novatos y para usuarios de sistemas donde hay instaladas numerosas aplicaciones de manera predeterminada. Los usuarios encontrarán su aplicación más fácil si el nombre que aparece en el menú contiene una descripción de su función.</para>

	<para>Por ejemplo, <ulink url="http://ist.mit.edu/services/consulting/usability">las pruebas de usuario sobre el sistema Athena del MIT</ulink> revelaron que los usuarios tenían dificultades para encontrar el gestor de archivos porque no estaban familiarizados con el nombre «Nautilus». Dado que los usuarios no asocian la palabra «Nautilus» con el concepto «gestor de archivos» el elemento del menú no les ayuda. Este es un ejemplo para no usar el lenguaje de usuario. Consulte la <xref linkend="principles-match"/> para obtener más información sobre este tema.</para>


	    <example>
		<title>Incluir una descripción funcional en el nombre del menú</title>
		<informaltable frame="all">
			
			<tgroup cols="2" align="left">
			  <thead>
				<row>
		      			<entry>Elemento original del menú</entry>
				      <entry>Elemento revisado del menú</entry>
	   			</row>
			  </thead>
			<tbody>
	     			<row>
					<entry>Epiphany</entry>
					<entry>Navegador web Epiphany</entry>
				</row>
	  		</tbody>
         	</tgroup>
		</informaltable>
	</example>

      </sect3>

      <sect3>
	<title>Ponga exclusivamente información útil en el nombre del menú</title>
	<para>No incluya palabras como «GNOME», «Sistema de ventanas X», «GTK+» ni cualquier otro detalle de la plataforma en los nombres del menú <guimenu>Aplicaciones</guimenu>. Probablemente, el usuario ya sabe qué plataforma está usando, y si no es así, los nombres de las aplicaciones no son el sitio correcto para indicarlo.</para>
	<example>
		<title>Quitar información no esencial de los nombres del menú</title>
		<informaltable frame="all">
			
			<tgroup cols="2" align="left">
			  <thead>
				<row>
		      			<entry>Elemento original del menú</entry>
				      <entry>Elemento revisado del menú</entry>
	   			</row>
			  </thead>
			<tbody>
	     			<row>
					<entry>Visor de imágenes de GNOME</entry>
					<entry>Visor de imágenes</entry>
				</row>
				<row>
					<entry>Editor de blog GTK</entry>
					<entry>Editor de blog</entry>
				</row>
	  		</tbody>
         	</tgroup>
		</informaltable>
	</example>

	<para>No incluya detalles técnicos cuando el usuario no necesita saberlos o pueden inferirles del contexto. Evite jerga técnica a no ser que la aplicación solo tenga un público objetivo técnico.</para>
	<para>Por ejemplo, cuando tanto un cliente como un servidor de algún servicio están listados en los menús, quite la plabara «Cliente» del nombre del menú para el cliente.</para>
	
	<example>
		<title>Quitar jerga técnica de los nombres de menú</title>
		<informaltable frame="all">
			
			<tgroup cols="2" align="left">
			  <thead>
				<row>
		      			<entry>Elemento original del menú</entry>
				      <entry>Elemento revisado del menú</entry>
	   			</row>
			  </thead>
			<tbody>
	     			<row>
					<entry>Cliente de Batalla naval de GNOME</entry>
					<entry>Batalla Naval</entry>
				</row>
				<row>
					<entry>Servidor de Batalla naval de GNOME</entry>
					<entry>Servidor multijugador de Batalla naval</entry>
				</row>
				<row>
					<entry>Cliente VideoLAN de GNOME</entry>
					<entry>Reproductor de vídeo VideoLAN</entry>
				</row>
	  		</tbody>
         	</tgroup>
		</informaltable>
	</example>

	<tip><title>Proporcionar la información correcta</title>
        <para>Trate de imaginar qué palabras buscarán los usuarios cuando seleccionen su aplicación en el menú <guimenu>Aplicaciones</guimenu>. Esta es la información que debería aparecer en el nombre del menú. Por ejemplo, un usuario que quiere reproducir una película, probablemente no buscará la palabra «Cliente». Por otro lado, un usuario que quiere enviar películas desde su equipo, sí puede buscar la palabra «Servidor». Evite pensar en el menú de aplicaciones como una ontología.</para></tip>
      </sect3>

      <sect3>
	<title>Formatos de nombres de menú</title>
	<orderedlist>
	  
         <listitem>
	    <para>Si el nombre adecuado de su aplicación ya es descriptivo de su funcionalidad y no solo sugestivo, use el formato: <replaceable>Nombre de la aplicación</replaceable></para>
	<example>
		<title>Usar el nombre de la aplicación como nombre en el menú</title>
		<informaltable frame="all">
			
			<tgroup cols="2" align="left">
			  <thead>
				<row>
		      			<entry>Nombre de la aplicación</entry>
				      <entry>Nombre del menú</entry>
	   			</row>
			  </thead>
			<tbody>
	     			<row>
					<entry>Diccionario</entry>
					<entry>Diccionario</entry>
				</row>
				<row>
					<entry>Herramienta de búsqueda</entry>
					<entry>Herramienta de búsqueda</entry>
				</row>
	  		</tbody>
         	</tgroup>
		</informaltable>
        	</example>
          </listitem>

	  <listitem>
	    <para>Si existe una descripción funcional sucinta de su aplicación, use el formato: <replaceable>NombreDeLaAplicación DescripciónFuncional</replaceable></para>

	<example>
		<title>Usar descripciones funcionales en los nombres del menú</title>
		<informaltable frame="all">
			
			<tgroup cols="2" align="left">
			  <thead>
				<row>
		      			<entry>Nombre de la aplicación</entry>
				      <entry>Nombre del elemento del menú</entry>
	   			</row>
			  </thead>
			<tbody>
	     			<row>
					<entry>El GIMP</entry>
					<entry>Editor de imágenes GIMP</entry>
				</row>
				<row>
					<entry>Subaplicación de correo Evolution</entry>
					<entry>Correo-e (Evolution)</entry>
				</row>
				<row>
					<entry>AbiWord</entry>
					<entry>Procesador de textos AbiWord</entry>
				</row>
				<row>
					<entry>Galeon</entry>
					<entry>Navegador web Galeon</entry>
				</row>
				<row>
					<entry>Gramps</entry>
					<entry>Genealogía Gramps</entry>
				</row>
				<row>
					<entry>AisleRiot</entry>
					<entry>Solitario AisleRiot</entry>
				</row>

	  		</tbody>
         	</tgroup>
		</informaltable>
	</example>


	  </listitem>

	  <listitem>
	    <para>Unas pocas aplicaciones, particularmente los juegos, no tienen descripciones funcionales apropiadas (pero note que muchos juegos sí la tienen). En este caso use el <replaceable>Nombre de la aplicación</replaceable> como el nombre de menú.</para>

	<example>
		<title>Using application's name as menu name where no functional description exists</title>
		<informaltable frame="all">
			
			<tgroup cols="2" align="left">
			  <thead>
				<row>
		      			<entry>Nombre de la aplicación</entry>
				      <entry>Nombre del elemento del menú</entry>
	   			</row>
			  </thead>
			<tbody>
	     			<row>
					<entry>Laberinto del bombardero</entry>
					<entry>Laberinto del bombardero</entry>
				</row>
	  		</tbody>
         	</tgroup>
		</informaltable>
	</example>

	  </listitem>

	</orderedlist>
      </sect3>
<!--
	<sect3>
	<title>Generic Name and Name</title>

        <para>There are two name types required for a menu item, a generic name and a proper name.  The menu item requires these two names to distinguish the applications when there are more than one of the same application type present and to simplify the item name when there is only one present.  If only one application of a generic name exists in the menu the application assumes the generic name, otherwise the proper name is displayed.</para>

	<example>
		<title>X-Chat .desktop file</title>
		 <programlisting>
	Name=X-Chat IRC
	GenericName=IRC
		 </programlisting>
	</example>

	<para>
	The generic name or GenericName, is a name describing only the applications functionality without the applications proper name.  This is the name to be displayed when there are no other applications of the same generic name present and should simply describe the pure functionality of the application without its actual name.
	</para>

	<para>
	A proper name or Name, is the displayed name of the application when there are more than one applications present with the same generic name.  This distinguishes the multiple generic names with the applications proper name.
	</para>

	<example>
		<title>GenericName and Name</title>
		<informaltable frame="all">
			
			<tgroup cols="2" align="left">
			  <thead>
				<row>
		      			<entry>GenericName</entry>
					<entry>Name</entry>
	   			</row>
			  </thead>
			  <tbody>
	     			<row>
					<entry>Web Browser</entry>
					<entry>Epiphany Web Browser</entry>
				</row>
	     			<row>
					<entry>Web Browser</entry>
					<entry>Mozilla Web Browser</entry>
				</row>
	     			<row>
					<entry>Word Processor</entry>
					<entry>AbiWord Word Processor</entry>
				</row>
	     			<row>
					<entry>Word Processor</entry>
					<entry>OpenOffice.org Word Processor</entry>
				</row>
	  		</tbody>
	         	</tgroup>
		</informaltable>
	</example>
	</sect3>
-->
    </sect2>
    <sect2 id="menu-item-tooltips">

      <title>Consejos de elementos de menú</title>

      <para>Los consejos de ayuda proporcionan a los usuarios suficiente información para ejecutar la aplicación correcta. Muchos usuarios usan los consejos para explorar un entorno nuevo.</para>
	<para>Proporcione un consejo para cada elemento del menú <guimenu>Aplicación</guimenu> que añada, siguiendo esta guía:</para>

	<itemizedlist><title>Guías</title>
		<listitem><para>Comience el consejo con un verbo en imperativo, por ejemplo «diseñe», «escriba» o «compruebe».</para></listitem>
		<listitem><para>Describa las tareas más importantes que los usuarios pueden realizar con su aplicación.</para></listitem>
		<listitem><para>Aunque los consejos nunca deben ser detallados, deben ser más largos y descriptivos que el nombre del elemento.</para></listitem>
	</itemizedlist>

	<example>
		<title>Ejemplos de consejos para aplicaciones GNOME</title>
		<informaltable frame="all">
			
			<tgroup cols="2" align="left">
			  <thead>
				<row>
		      			<entry>Aplicación</entry>
				      <entry>Consejo de elemento de menú</entry>
	   			</row>
			  </thead>
			<tbody>
	     			<row>
					<entry>Mapa de caracteres</entry>
					<entry>Inserte caracteres especiales en los documentos</entry>
				</row>

				<row>
					<entry>Memprof</entry>
					<entry>Compruebe si sus aplicaciones tienen pérdidas de memoria</entry>
				</row>
				<row>
					<entry>Same Gnome</entry>
					<entry>Coloque cadenas de bolas del mismo color juntas para eliminarlas</entry>
				</row>
				<row>
					<entry>Cliente de Batalla naval de GNOME</entry>
					<entry>Busque y hunda barcos enemigos en esta versión en red de Hundir la flota</entry>
				</row>
	  		</tbody>
	         	</tgroup>
		</informaltable>
	</example>

    </sect2>
   </sect1>
    <sect1 id="gconf-keys">

      <title>Claves de GConf</title>

      <para>Las claves de GConf son necesarias para tener descripciones largas y cortas para cada clave. Muchas claves no tienen interfaz a través de la aplicación, por lo que para que alguien administre los valores de la clave desde otra aplicación, cada campo de descripción será la única interfaz disponible.</para>

	<itemizedlist><title>Guías</title>
		<listitem><para>La «descripción corta» debe ser corta, menos de 8 palabras, y debe describir el propósito de la clave.</para></listitem>
		<listitem><para>La «descripción larga» debe describir de manera completa los valores posibles de la clave y los efectos que estos valores tienen en la aplicación.</para></listitem>
	</itemizedlist>

	<example>
		<title>Ejemplos de descripciones para claves de GConf de gnome-terminal</title>
		<informaltable frame="all">
			
			<tgroup cols="3" align="left">
			  <thead>
				<row>
					<entry>Clave</entry>
		      			<entry>Descripción corta</entry>
				      <entry>Descripción larga</entry>
	   			</row>
			  </thead>
			<tbody>
	     			<row>
					<entry>background_type</entry>
					<entry>Tipo de fondo</entry>
					<entry>El tipo de fondo del terminal. Puede ser «solid» para un color sólido, «image» para una imagen o «transparent» para una pseudo-transparencia.</entry>
				</row>	
	     			<row>
					<entry>eliminar_vinculación</entry>
					<entry>Efecto de la tecla «Suprimir» (Delete)</entry>
					<entry>Determina qué código genera la tecla Suprimir (Delete). Los valores posibles son «ascii-del» para el carácter ASCII para Supr., «control-h» para Control-H (también conocido como el carácter ASCII BS), «escape-sequence» para la secuencia de escape que típicamente está asociada con retroceso (backspace) o suprimir (delete). «escape-sequence» se considera normalmente como la configuración correcta para la tecla Suprimir (Delete).</entry>
				</row>	
			</tbody>
	         	</tgroup>
		</informaltable>
	</example>
   </sect1>
  
  <sect1 id="desktop-mimedatabase">
    <title>Mapear tipos de documentos a aplicaciones</title>
    
    <para>The document type (MIME) database allows users to specify their preferred applications for opening different types of documents. This is the mechanism by which Nautilus, Evolution and other applications decide which application to run when they encounter a document they cannot open themselves.</para>

    <para>Es importante que los usuarios puedan hacer doble pulsación sobre los documentos que ven en el escritorio, tales como archivos y mensajes de correo electrónico, y abrirlos con su aplicación favorita. Por lo tanto, la aplicación de GNOME debe asociarse en el momento de la instalación con todos los tipos de documentos que puede manejar. Los detalles técnicos sobre cómo hacer esto se pueden encontrar en la <ulink url="http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec"><citetitle>Especificación de información MIME compartida</citetitle></ulink> de Freedesktop y en la <ulink url="http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html"><citetitle>Especificación de entradas de escritorio</citetitle></ulink>.</para>

    <!-- FIXME: need to cover things like the preferred list and when an application should add itself to the preferred list -->

  </sect1>

  <sect1 id="desktop-notification-area">
	<title>Usar el área de notificación de estado</title>
	<para>Usando el área de notificación de estado de aplicaciones, puede notificar al usuario sobre eventos no críticos (por ejemplo la llegada de un correo nuevo o la entrada de un amigo en una charla) y exponer el estado de los procesos del sistema (por ejemplo la impresión de un documento o la carga de la batería del portátil).</para>

	<para>Seguir las guías de esta sección le ayudará a aclarar la diferencia en la mente del usuario entre la información presentada en el área de notificación y los controles y la información que se presentan en otras partes del panel.</para>

		<warning><para>La utilidad del área de notificación disminuye rápidamente cuando existen más de cuatro iconos siempre presentes. Por esta razón se prefieren los iconos que aparecen solo de forma temporal, en respuesta de eventos.</para></warning>

	<sect2 id="desktop-notification-or-applet"><title>¿Área de notificación o miniaplicación del panel?</title>
	<para>Probablemente debería escribir una miniaplicación en lugar de usar el área de notificación si:</para>
	<itemizedlist>
		<listitem><para>pulsar en el icono de su área de notificación no hace otra cosa que abrir una ventana directamente asociada con el icono (por ejemplo, una ventana de la carpeta de correo para un icono de correo nuevo o una ventana de la cola de impresión para el icono de notificación de impresora), o</para></listitem>
		<listitem><para>existen opciones específicas de icono en su menú contextual para hacer cualquier otra cosa</para></listitem> 
		<listitem><para>su aplicación podría necesitar mostrar más de un icono de notificación al mismo tiempo</para></listitem>
	</itemizedlist>
	</sect2>

	<sect2><title>Apariencia de los iconos</title>
	<itemizedlist><title>Guías</title>
		<listitem><para>Use perspectivas de tabla para iconos que representen dispositivos físicos, con la fuente de luz encima y a la izquierda del objeto representado. Por ejemplo, un icono de impresora durante la impresión. Para obtener más información acerca la perspectiva de tabla consulte la <xref linkend="icon_style_perspective"/>. </para></listitem>
		<listitem><para>Use perspectiva de estantería, con sobrecarga ligera, para el resto de iconos. Por ejemplo, un sobre mostrado cuando llega correo nuevo. Para obtener más detalles acerca de la perspectiva de estantería, consulte <xref linkend="icon_style_perspective"/>.</para></listitem>	
		<listitem><para>Para monitores o barras de progreso que cambian con el tiempo, tales como el monitor de carga de la batería, delimitar limpiamente el borde del área.</para></listitem>

		</itemizedlist>

		<itemizedlist><title>Guías</title>
			<listitem><para>Solo los programas del núcleo de GNOME pueden mostrar siempre un icono en el área de estado.</para></listitem>
			<listitem><para>Los programas que no sean parte del núcleo, para los que un icono perpetuo pueda ser útil, deben no mostrar el icono de forma predeterminada. Los usuarios pueden seleccionar activar el icono perpetuo como una opción. <remark>Una forma estándar de presentar esta opción estaría muy bien.</remark></para></listitem>
		</itemizedlist>

	</sect2>

	<sect2 id="notification-area-animation">
	<title>Animación</title>
	
	<itemizedlist><title>Guías</title>
		<listitem><para>Icons should not usually appear animated. They may change to
indicate a change of state, but should not do so when that change
occurs regularly or rapidly. A battery status indicator would
usually change slowly, therefore an icon is appropriate. By contrast,
a load meter would always be changing, therefore it should use a flat
image.</para></listitem>
<!--		<listitem><para>Icons are permitted to blink under a few conditions.
 An icon may blink for n (=5?) seconds when first displayed
   if showing the icon is not caused by user action.
   A printing-in-progress icon would be shown because the user
   is printing a document, therefore it should not blink.
   An incoming email or personal message (IM) would be shown
   because something has changed absent the user, therefore it
   may blink.</para></listitem>

 		<listitem><para>A icon may blink for n seconds if its conditions for initially
   blinking recur. For example, an incoming email icon which was
   shown and blinked when a message arrived and which has remained
   visible may blink again when another message arrives.</para></listitem>
-->
 		<listitem><para>Cualquier icono puede parpadear para indicar un error en deferencia a mostrar una alerta. Por ejemplo, un icono de impresora en progreso puede parpadear cuando hay papel atascado, pero no cuando la impresora está quemándose (ya que en su lugar debería mostrar una alerta).</para></listitem>
		<listitem><para>No dependa en destellos o animaciones como medio para alertar al usuario de cualqueir evento en particular.</para></listitem>
		</itemizedlist>

	</sect2>
	
	<sect2 id="notification-icon-interaction">
	<title>Interacción</title>
		<para>Icons should respond to these user actions.
(Keypresses apply only when the icon has focus, of course)</para>
		<itemizedlist><title>Guías</title>
  			<listitem><para>Las teclas de pulsación doble o el <keysym>Espacio</keysym> deberían realizar la acción predeterminada del icono. Generalmente suele abrir una ventana con datos relevantes, por ejemplo: <itemizedlist>
     				<listitem><para>la cola de impresión para un icono de progreso de impresión.</para></listitem>
     				<listitem><para>the inbox for an incoming email icon</para></listitem>
     				<listitem><para>el mensaje para un mensaje entrante</para></listitem>
			</itemizedlist></para></listitem>
  		<listitem><para>Pulsar con el botón derecho del ratón o <keycombo><keycap>Mayús</keycap><keycap>F10</keycap></keycombo> debería mostrar un menú que al menos contenga la acción predeterminada del icono.</para></listitem>

		<listitem><para>Si se pueden alterar las propiedades del icono, debería tener un elemento de menú <guimenuitem>Propiedades</guimenuitem> en su menú, y mostrar su propiedad en respuesta a Alt+Intro.</para></listitem>

		<listitem><para>Los iconos deben obedecer las convenciones normales para las sugerencias o consejos.</para></listitem>
		</itemizedlist>
	</sect2>
 </sect1>

</chapter>



<chapter id="windows">
  <title>Ventanas</title>

  <sect1 id="windows-properties">
    <title>Partes de las ventanas y del sistema de interacción</title>

    <sect2 id="window-props-titles">
      <title>Títulos</title>

      <para>Dé un título a cada ventana (a excepción de las <link linkend="windows-alert">alertas</link> y <link linkend="toolbox-windows">cajas de herramientas</link>). Un buen título de ventana contiene información relevante para el usuario y distingue una ventana en particular del resto de ventanas abiertas. Omita información que no ayuda en esta selección, por ejemplo el número de versión de la aplicación o el nombre del fabricante.</para>

      <figure>
        <title>Ejemplo de título de una ventana</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="28" fileref="images/windows-titlebar.png" format="PNG" width="379"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-titlebar.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Captura de pantalla mostrando una barra de título de ventana con el título «Partes de la interacción de las ventanas y el sistema - Mozilla Firefox»</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <para>Consulte la descripción de cada tipo de ventana en particular para los formatos de títulos.</para>
    </sect2>

    <sect2 id="window-props-borders">
      <title>Comandos de bordes y ventanas</title>

      <para>La mayoría de las ventanas tiene bordes, excepto cierto tipo de ventanas con formas y algunas ventanas «arrancadas». No intente dibujar sus propias ventanas sin bordes, en su lugar proporcione sugerencias al gestor de ventanas para el tipo de borde que quiere.</para>

      <para>Diferentes tipos de comandos son apropiados para diferentes tipos de ventana. Consulte la descripción para cada tipo de ventana en particular para obtener una lista de comandos de ventana apropiados. Están disponibles los siguientes comandos de ventana:</para>

      <itemizedlist>
        <listitem>
          <formalpara>
            <title>Cerrar</title>

            <para>Cierra la ventana. Dibuje <emphasis>siempre</emphasis> esto como un botón en el borde de la ventana cuando sea relevante al tipo de ventana.</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Maximizar</title>

            <para>Hace que la ventana ocupe todo el espacio sin usar de la pantalla</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Minimizar</title>

            <para>Hace que la ventana se oculte temporalmente. Seguirá apareciendo en la lista de ventanas del escritorio.</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Enrollar/desenrollar</title>

            <para>Solo muestra el título de la barra de la ventana, como si se hubiese «enrollado».</para>
          </formalpara>
        </listitem>
      </itemizedlist>
    </sect2>

    <sect2 id="window-props-modality">
      <title>Modalidad</title>

      <para>Una ventana <emphasis role="bold">no modal</emphasis> no restringe la interacción del usuario con otras ventanas abiertas del escritorio de ninguna manera. Usar ventanas no modales ofrece al usuario la máxima flexibilidad para realizar tareas en su aplicación en cualquier orden y de la manera que elija.</para>

      <para>La ventana de una <emphasis role="bold">aplicación modal</emphasis>, mientras está abierta, evita que el usuario interaccione con otras ventanas de la misma aplicación.</para>

      <para>Una ventana <emphasis role="bold">modal del sistema</emphasis>, mientras está abierta, evita que el usuario interaccione con cualquier otra ventana o aplicación, incluyendo el propio escritorio.</para>

      <itemizedlist>
        <title>Guías</title>

        <listitem>
          <para>Use una ventana modal sólo si el permitir la interacción con otras partes de la aplicación mientras la ventana está abierta puede hacer que se pierdan datos o que haya cualquier otro problema serio. Proporcione una manera clara de salir de la ventana modal, como un botón <guibutton>Cancel</guibutton> en una alerta.</para>
        </listitem>

        <listitem>
          <para>No usar las ventanas modales del sistema.</para>
        </listitem>
      </itemizedlist>
    </sect2>

    <sect2 id="window-props-focus">
      <title>Foco</title>

      <para>El foco es la manera en que un usuario designa a una ventana para que reciba los datos del teclado, el ratón o cualquier otro dispositivo de entrada. Si está usando un lector de pantalla o una tecnología de asistencia similar, el foco puede designar la ventana de la que el usuario quiere recibir información. La ventana con el foco se considera la ventana con la que el usuario está «trabajando» actualmente.</para>

      <para>Asegúrese de que su aplicación funciona correctamente con los tres mecanismos diferentes con los que las ventanas pueden recibir el foco en GNOME:</para>

      <itemizedlist>
        <listitem>
          <formalpara>
            <title>Pulsar para dar el foco</title>

            <para>Una ventana obtiene el foco al pulsar en ella.</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Apuntar para dar el foco</title>

            <para>Una ventana obtiene el foco moviendo el puntero sobre ella. A veces se llama a esto «foco descuidado».</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Foco del teclado</title>

            <para>Se da el foco a una ventana usando un atajo de teclado tal como <keycombo><keycap>Alt</keycap><keycap>Tab</keycap></keycombo>.</para>
          </formalpara>
        </listitem>
      </itemizedlist>

      <note>
        <title>Restricciones especiales para «apuntar para dar el foco»</title>

        <para>Tenga en cuenta que «apuntar para dar el foco» añade una serie de restricciones a las aplicaciones de GNOME que no están presentes en entornos como MacOS o Windows. Por ejemplo, las ventanas de utilidad compartidas entre varias ventanas de documentos, como la caja de herramientas en el editor de imágenes GIMP, no pueden ser sensibles al contexto, es decir, no puede iniciar una acción como <guibutton>Guardar</guibutton> en el documento actual. Esto es porque al mover el ratón del documento actual a la ventana de utilidad, el usuario puede pasar el puntero por otra ventana de documento sin darse cuenta, cambiando el foco y posiblemente guardando el documento incorrecto.</para>
      </note>
    </sect2>

    <sect2 id="windows-show-hide">
	<title>Mostrar y ocultar ventanas</title>
	<para>La forma en la que su aplicación muestra y oculta ventanas puede afectar mucho a la percepción de su aplicación por parte del usuario, particularmente su rendimiento.</para>
	<itemizedlist><title>Guías</title>
		<listitem><para>Muestre siempre una ventana tan pronto como le sea posible, pero asegúrese de que su ventana tiene el tamaño correcto antes de mostrarla. Redimensionar una ventana después de que sea visible desorienta y da una impresión de de una aplicación sin finalizar.</para></listitem>
		<listitem><para>si una ventana contiene información que tarda unos segundos en calcularse o en mostrarse, a menudo es mejor no rellenarla por completo antes de mostrar la ventana. Por ejemplo, una ventana que contenga una gran cantidad de texto se puede mostrar rápidamente y el texto puede rellenarse después (siempre que esto no implique que la ventana se redimensione). Esto hará que su aplicación sea más reactiva que si no se hubiese mostrado la ventana hasta haber completado su contenido.</para></listitem>
		<listitem><para>Oculte una ventana después de cerrarla tan pronto como sea posible. A menos que se deba mostrar una alerta, oculte inmdiatamente la ventana que el usuario ha cerrado pulsando el botón «Cerrar» del borde de la ventana; su aplicación puede todavía realizar alguna operación interna de limpieza posteriormente. Hacer de hacer que el sistema parezca lento, no hacer esto causa que el gestor de ventanas crear que la aplicación no está respondiendo, mostrando una advertencia innecesaria al usuario.</para></listitem>
	</itemizedlist> 

    </sect2>

  </sect1>

  <sect1 id="windows-primary">
    <title>Ventanas primarias</title>

    <para>Una ventana primaria generalmente presenta una vista de los datos del usuario, como un documento de texto en una aplicación de procesado de textos, una imagen en un programa de dibujo o cálculos en una calculadora o en una hoja de cálculo. También puede ser la vista de algo más abstracto, como un juego. Una única instancia de una aplicación puede tener más de una ventana primaria y más de un tipo de ventana primaria.</para>

    <para>Una ventana primaria siempre se muestra en la lista de ventanas del panel.</para>

    <figure>
      <title>Una típica ventana primaria (gedit)</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="372" fileref="images/windows-primary.png" format="PNG" width="397"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/windows-primary.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Una típica ventana primaria: la vista de documento de gedit</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <para>Generalmente la ventana de una aplicación primaria tiene un borde, una barra de menú y una barra de estado, y también puede contener una o más barras de herramientas.</para>

    <sect2 id="primary-window-titles">
      <title>Título</title>

      <para>The most important element of a document-based application's 
	      window title is the name of the open document.  For other
	      applications, it is usually the name of the application.
      </para>

      <itemizedlist><title>Guías</title>

	<listitem><para>Use el <replaceable>Nombre de archivo</replaceable> como el título de la ventana para aplicaciones basadas en documentos. No use la ruta completa, ya que el nombre de archivo es más fácil para distinguir entre otros títulos de ventanas abiertas, por ejemplo en la lista de ventanas.</para>
      	<example>
        <title>Usar los nombres de documentos como títulos de ventanas</title>

        <informaltable frame="all">
          <tgroup align="left" cols="2">
            <thead>
              <row>
                <entry>Aplicación</entry>

                <entry>Ejemplo de título de ventana</entry>
              </row>
            </thead>

            <tbody>
              <row>
                <entry>AbiWord</entry>

                <entry>Mi reporte.abw</entry>
              </row>

              <row>
                <entry>Evolution</entry>

                <entry>Bandeja de entrada</entry>
              </row>

              <row>
                <entry>Reproductor de música</entry>

                <entry>U2 - Better Than the Real Thing</entry>
              </row>
            </tbody>
          </tgroup>
        </informaltable>
      	</example>
	<para>Si la ruta es importante, por ejemplo, el usuario ha abierto dos documentos con el mismo nombre de carpetas diferentes en la misma aplicación, muestre la ruta completa en la barra de estado.</para>
	</listitem>
	
	<listitem><para>Antes de guardar un documento por primera vez, establezca el título de la ventana a <replaceable>«Tipo de documento» sin guardar</replaceable>. Por ejemplo, <replaceable>Dibujo sin guardar</replaceable>, <replaceable>Hoja de cálculo sin guardar</replaceable>, o el más genérico <replaceable>Documento sin guardar</replaceable>.</para>
	</listitem>



      	<listitem><para>Cuando un documento tiene cambios pendientes, introduzca un asterisco (*) al comienzo del título de la ventana. Por ejemplo, <replaceable>*Dibujo sin guardar</replaceable>, <replaceable>*InformeAnual</replaceable>.</para></listitem>
      
	<listitem><para>Para aplicaciones no basadas en documentos use <replaceable>Nombre de la aplicación</replaceable> como título de la ventana.</para>

      	<example>
        <title>Usar nombres de aplicaciones como títulos de ventanas</title>

        <informaltable frame="all">
          <tgroup align="left" cols="2">
            <thead>
              <row>
                <entry>Aplicación</entry>

                <entry>Título de la ventana</entry>
              </row>
            </thead>

            <tbody>
              <row>
                <entry>Diccionario</entry>

                <entry>Diccionario</entry>
              </row>

              <row>
                <entry>Calculadora</entry>

                <entry>Calculadora</entry>
              </row>
            </tbody>
          </tgroup>
        </informaltable>
      </example>
      </listitem>

      <listitem><para>No ponga números de versión, nombres de empresas ni otra información que no sea de uso inmediato para el usuario en el título de la ventana. Esto consume espcio, haciendo que los títulos en los espacios limitados como la lista de ventanas del sistema sean inútiles, y añaden más texto que el usuario tiene que analizar para encontrar información útil. En producto «beta», donde los números de versión son críticos para la información de errores, poner los números de versión puede ser útil, pero quítelos en las versiones estables. En vez de eso, ponga la información de la versión en la caja «Acerca de».</para></listitem>

     </itemizedlist>

      <para>While document names are most pertinent to users, we understand
      that application developers may want to increase recognition of their
      application. If you plan to include your application's name in the
      title of a primary window, use the following format:
      <replaceable>Document Name</replaceable> - <replaceable>Application Name</replaceable>.
      This will ensure that the document name appears in limited space
      situations such as the system window list.</para>

      <warning><para><emphasis role="bold">No</emphasis> se recomienda incluir el nombre de la aplicación en el título de una aplicación basada en documentos.</para></warning>

      <tip><para>Think about naming windows in the context of the panel window list. On a typical screen with a relatively small number of windows open, a window will have 20-30 characters of text and an icon. Consider which text will provide the most immediately obvious clues to a user looking for a particular window.</para></tip>

    </sect2>

    <sect2 id="primary-window-commands">
      <title>Comandos de ventana</title>

      <para>Cerrar, maximizar/restaurar, minimizar, enrollar/desenrrollar</para>
    </sect2>

    <sect2 id="document-interface-types">
      <title>Relación entre documentos y ventanas</title>

      <sect3 id="sdi">
        <title>Interfaz simple de documentos (ISD, «SDI»)</title>

        <para>Una interfaz simple de documento coloca cada documento en su ventana primaria. Las cajas de herramientas y otras ventanas de utilidades se pueden compartir entre varios documentos ISD, pero cerrarlas no debe tener efecto en las ventanas de los documentos. Use ISD para su aplicación GNOME a menos que haya una razón convincente para no hacerlo.</para>

        <figure>
          <title>Una aplicación SDI típica (Eye of GNOME)</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="226" fileref="images/windows-sdi.png" format="PNG" width="268"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/windows-sdi.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Un ejemplo típico de aplicación ISD: Eye of GNOME usada para inspeccionar un icono</phrase>
            </textobject>
          </mediaobject>
        </figure>
      </sect3>

      <sect3 id="mdi">
        <title>Interfaz de múltiples documentos (IMD, «MDI»)</title>

        <para>Una interfaz de múltiples documentos presenta dos documentos en dos paneles o pestañas, en una sola ventana.</para>

        <figure>
          <title>Una típica aplicación IMD (gedit) mostrando tres documentos abiertos en páginas en pestañas</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="349" fileref="images/windows-mdi.png" format="PNG" width="372"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/windows-mdi.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Una típica aplicación IMD: gedit con tres documentos abiertos en la misma ventana</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <para>MDI has several inherent usability problems, so its use is
        discouraged in applications. It is better to open each document in a
        new primary window, with its own menubar, toolbars and statusbar, or
        allow multiple instances of your application to be run simultaneously.
        In either case, this leaves it for the window manager (acting on the
        user's preferences) rather than your application to decide how to
        group and present document windows from the same application.</para>
      </sect3>

      <sect3 id="csdi">
        <title>Interfaz controlada de un solo documento (ICSD, «CSDI»)</title>
        <para>In a typical SDI application, document windows are treated as
        primary. For example, when all document windows have been closed, the 
        application (including utility windows) exits as well. In CSDI a utility
        window is treated as the primary window. For example, closing this
        utility window will close all document windows and exit the application.</para>

        <warning><para><emphasis role="bold">No</emphasis> se recomienda usar ICSD</para></warning>

        <para>CSDI is sometimes used because document windows might be too
        small to have menu bars. Typically this is not the normal use case for the
        application, but does represent a significant minority use case. For
        example, an image editor being used to edit small web page elements will
        often result in very small document windows that cannot accomodate
        a title bar.</para>

        <remark>NO TRADUCIR</remark>

        <para>A better way to address this problem is to allow menu bars to "collapse"
        into an overflow button, in much the same way toolbars operate when the window
        shrinks to below the toolbar width. This allows for small windows, but also
        provides an opportunity for people to figure out where their menus have gone.</para>

        <tip><para>Note that if very small documents are the <emphasis>primary</emphasis> use 
        case for your application, you should consider finding a means to avoid windows
        altogether. Windows are not an effective interface for dealing with large
        numbers of small items. Consider looking for a fixed/automated layout system
        for presenting the "documents". Also consider if the "documents" will be primarily
        used in a higher level grouping, in which case that grouping could become the
        document instead.</para></tip>
      </sect3>

    </sect2>
  </sect1>

  <sect1 id="windows-utility">
    <title>Ventanas de utilidad</title>

    <para>Las ventanas de utilidad, como las paletas y las cajas de herramientas, normalmente tienen bordes. No contienen una barra de menú, una barra de herramientas o una barra de estado.</para>
    <para>Una ventana de utilidad no debe aparecer en la lista de ventanas del panel a menos que sea, o pueda ser la única ventana mostrada por una aplicación. De otro modo, la ventana de utilidad se debe elevar por encima de la aplicación cuando la propia ventana de la aplicación se seleccione en la lista de ventanas.</para>

    <sect2 id="windows-instant-apply">
      <title>Ventanas de aplicación instantánea</title>

      <para>Para ventanas que permiten al usuario cambiar valores o configuraciones, como las propiedades y las ventanas de preferencias, actualice esos valores o configuraciones inmediatamente para reflejar los cambios hechos en la ventana. Esto se conoce como «aplicación instantánea». No obligue al usuario pulse un botón <guibutton>Aceptar</guibutton> o <guibutton>Aplicar</guibutton> para aplicar los cambios, a menos que:</para>

      <itemizedlist>
        <listitem>
          <para>el cambio llevará más de un segundo en aplicarse, en cuyo caso aplicar el cambio inmediatamente podría hacer que el sistema parezca lento o que no esté respondiendo, o</para>
        </listitem>

        <listitem>
          <para>se deben aplicar los cambios en la ventana de forma simultánea para prevenir que el sistema entre potencialmente en un estado inestable. Por ejemplo, los cambios de servidor y proxy en una ventana de propiedades de red.</para>
        </listitem>
      </itemizedlist>

      <para>If either of these conditions affect only a few of the controls in
      your window, arrange those controls together into one or more groups,
      each with its own <guibutton>Apply</guibutton> button. Leave the rest of
      the controls as instant apply.</para>

      <remark>NO TRADUCIR</remark>

	<itemizedlist>
		<title>Guías</title>
		
        	<listitem><para>Do not attempt to validate or apply changes caused by editing a
        text field control until the user has moved focus to a different
        control in the window, or the window is closed. 
	Validating after each keypress is usually
        annoying and unnecessary. Exception: if the field accepts only a fixed 
	number of characters, such as a hexadecimal color code, validate and
	apply the change as soon as that number of characters have been entered.
	</para></listitem>
		<listitem><para>When the user moves focus to a different control, do not indicate an invalid entry by displaying an alert or undoing the change the user made. Both of these methods are particularly disruptive for focus-follows-mouse users, for whom focus may leave the control more often than it does for a click-to-focus user.</para></listitem>
	</itemizedlist>
	<remark>NO TRADUCIR</remark>
      </sect2>

	<sect2 id="windows-explicit-apply">
		<title>Ventanas de aplicación explíticas</title>
      <para>If most of the controls in your window are not suitable for
      instant apply, consider making the whole window "explicit
      apply". An explicit apply window has these three buttons in its
      button box, plus an optional <guibutton>Help</guibutton> button:</para>

      <itemizedlist>
        <listitem>
          <formalpara>
            <title>Aplicar</title>

            <para>Aplica todos los ajuestes en la ventana, pero no cierra la ventana en caso de que el usuario quiera cambiar su opinión.</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Cancelar</title>

            <para>Resets all settings in the window to those that were in
            force when the window was opened. Note: this must undo the effects
            of all applications of the <guibutton>Apply</guibutton> since the
            window was opened, not just the most recent one.</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Aceptar</title>

            <para>Aplica todos los ajustes en la ventana y cierra la ventana.</para>
          </formalpara>
        </listitem>
      </itemizedlist>

      <figure id="explicit-apply-figure">
        <title>Botones en una ventana explícita de aplicar</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="55" fileref="images/windows-explicit-apply.png" format="PNG" width="387"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-explicit-apply.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Captura de pantalla mostrando la posición correcta para los botones Ayuda, Aplicar, Cancelar y Aceptar en un diálogo</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <remark>NO TRADUCIR</remark>
    </sect2>

    <sect2 id="default-buttons">
      <title>Botones predeterminados</title>

      <para>When designing a dialog or utility window, you can assign the
      <keycap>Return</keycap> key to activate a particular button in the
      window. GNOME indicates this button to the user by drawing a different
      border around it. For example, the <guibutton>Help</guibutton> button in
      <xref linkend="explicit-apply-figure"/>.</para>

      <para>Choose the default button to be the most likely action, such as a
      confirmation action or an action that applies changes in a utility
      window. Do not make a button the default if its action is irreversible,
      destructive or otherwise inconvenient to the user. If there is no
      appropriate button in your window, to designate as the default button,
      do not set one.</para>

      <para>En particular, <emphasis>no</emphasis> se recomienda que el botón <guibutton>Cerrar</guibutton> sea el predeterminado en una ventana de <link linkend="windows-instant-apply">aplicar de forma instantánea</link>, ya que esto puede llevar a que los usuarios cierren la ventana accidentalmente antes de que hayan terminado de usarla.</para>
    </sect2>

    <sect2 id="property-windows">
      <title>Ventanas de propiedades</title>

      <para>Las ventanas de propiedades permiten al usuario ver y cambiar las características de un objeto tal como un documento, archivo, dibujo o lanzador de aplicaciones.</para>

      <figure>
        <title>Ejemplo de una ventana de propiedades</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-properties.png" format="PNG" width="302" depth="335"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-properties.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Captura de pantalla mostrando la ventana «propiedades del archivo» en Nautilus</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <formalpara>
        <title>Formato del título:</title>

        <para>Propiedades de <replaceable>Nombre de objeto</replaceable></para>
      </formalpara>

      <formalpara>
        <title>Comandos de ventana:</title>

        <para>Cerrar, minimizar, enrollar/desenrollar</para>
      </formalpara>

      <formalpara>
        <title>Botones:</title>

        <para>Ubique un botón <guibutton>Cerrar</guibutton> en la esquina inferior derecha. Se puede ubicar un botón <guibutton>Ayuda</guibutton> en la esquina inferior izquierda.</para>
      </formalpara>
    </sect2>

    <sect2 id="preference-windows">
      <title>Ventanas de preferencias</title>

      <para>Ventanas de preferencias que permiten al usuario cambiar la forma en que se comporta o se muestra una aplicación</para>
      <remark>NO TRADUCIR</remark>

      <figure>
        <title>Ejemplo de una ventana de preferencias</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="249" fileref="images/windows-preferences.png" format="PNG" width="354"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-preferences.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Captura de pantalla mostrando la ventana de preferencias de Gnibbles</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <formalpara>
        <title>Formato del título:</title>

        <para><replaceable>Nombre de la aplicación</replaceable> Preferencias</para>
      </formalpara>

      <formalpara>
        <title>Comandos de ventana:</title>

        <para>Cerrar, minimizar, enrollar/desenrollar</para>
      </formalpara>

      <formalpara>
        <title>Botones:</title>

        <para>Ubique un botón <guibutton>Cerrar</guibutton> en la esquina inferior derecha. Se puede ubicar un botón <guibutton>Ayuda</guibutton> en la esquina inferior izquierda.</para>
      </formalpara>

      <sect3 id="preference-windows-overriding-colors">
        <title>Personalizar tipografías y colores</title>

	<para>Si su ventana de preferencias permite al usuario personalizar las tipografías o los colores, utilice la siguiente redacción y el siguiente diseño como una guía para estos controles:</para>
	
	<example>
		<title>Texto recomendado para sobreescribir los elementos del tema; reemplazar con una captura de pantalla.</title>	
		<programlisting>
	(o) Usar tipografía del tema
	(o) Usar esta tipografía: [ Selector de tipografías ]

	(o) Usar los colores del tema
	(o) Usar estos colores:
		Fondo: [ selector de color ]
		Primer plano: [ selector de color ]
		</programlisting>
	</example>

	<para>Las palabras de los botones de radio deben ser más específicas cuando se necesite, por ejemplo,, «Usar tipografía monoespaciada del tema» o «Usar color de fondo del tema».</para>
      </sect3>

    </sect2>

    <sect2 id="toolbox-windows">
      <title>Cajas de herramientas</title>

      <para>A toolbox provides convenient access to a set of actions and
      toggles through a set of small toolbar-like buttons. Toolboxes can be
      used to provide a specialized group of tools to augment a toolbar
      containing more universal items such as <guibutton>Save</guibutton> and
      <guibutton>open</guibutton>. A single toolbox can be shared between
      multiple documents to save screen space.</para>

      <figure id="toolbox-figure">
        <title>Ejemplo de caja de herramientas</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="89" fileref="images/windows-toolbox-small.png" format="PNG" width="136"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-toolbox-small.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Una captura de pantalla mostrando una barra de herramientas con ocho botones dispuestos en dos filas.</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <formalpara>
        <title>Formato del título:</title>

        <para>Las cajas de herramientas no tienen título</para>
      </formalpara>

      <remark>NO TRADUCIR</remark>

      <remark>NO TRADUCIR</remark>

      <remark>NO TRADUCIR</remark>

      <remark>NO TRADUCIR</remark>

      <formalpara>
        <title>Comandos de ventana:</title>

        <para>Cerrar, enrollar/desenrollar</para>
      </formalpara>

      <formalpara>
        <title>Botones:</title>

        <para>Las cajas de herramientas no tienen botones</para>
      </formalpara>

      <formalpara>
        <title>Redimensionar:</title>

        <para>Haga que las cajas de herramientas sean redimensionables, mediante valores discretos. En otras palabras, el usuario puede redimensionar la caja de herramientas el tamaño de uno, dos, tres, etc elementos, pero no el tamaño de un elemento y medio.</para>
      </formalpara>

      <itemizedlist>
        <title>Guías</title>

        <listitem>
          <para>Coloque botones en una caja de herramientas solo si no abren otra ventana.</para>
        </listitem>

        <listitem>
          <para>Toolboxes are best used for modal toggle buttons that affect
          the operation of the mouse on the document, such as a set of buttons
          for choosing between paintbrush, eraser, and fill modes in a drawing
          application. Buttons that initiate actions upon clicking (such as a
          save button) are better placed in toolbars.</para>
        </listitem>

        <listitem>
          <para>Asegúrese de que cerrar una barra de herramientas no cierra o altera cualquier otra ventana primaria con la que está asociada.</para>
        </listitem>

        <listitem>
          <para>No ubique cajas de herramientas en la lista de ventanas del sistema. Las cajas de herramientas siembre deben estar por encima de todos los botones primarios con los que están asociadas.</para>
        </listitem>

        <listitem>
          <para>Si todas las ventanas primarias asociadas con una caja de herramientas están cerradas o minimizadas, oculte también la caja de herramientas. Muestre la caja de herramientas de nuevo cuando una de las ventanas primarias se abre o restaura.</para>
        </listitem>

        <listitem>
          <para>Make a toolbox two items wide by default, unless it is broken
          into <link linkend="toolbox_windows_categories">categories</link>.
          Make categorized toolboxes four items wide by default.</para>
        </listitem>
      </itemizedlist>

      <sect3 id="toolbox_windows_categories">
        <title>Categorías de cajas de herramientas</title>

        <para>While categories may not be as visually appealing as a toolbox
        homogenously filled with beautiful icons, they make an unwieldy large
        toolbox more managable. Picking a small icon from more than fifteen
        other items is a difficult task. Additionally, categories allow users
        to hide sets of tool items that are not relevant to their current
        task.</para>

        <figure id="example-toolbox-figure">
          <title>Una caja de herramientas grande dividida en categorías</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="156" fileref="images/windows-toolbox-large.png" format="PNG" width="136"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/windows-toolbox-large.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase/>
            </textobject>
          </mediaobject>
        </figure>

        <itemizedlist>
          <title>Guías</title>

          <listitem>
            <para>Divida las cajas de herramientas con más de dieciséis elementos en categorías. El tamaño óptimo para una categoría está entre cuatro y diez elementos.</para>
          </listitem>

          <listitem>
            <para>Dé a cada categoría una etiqueta (con el título en mayúscula) y una flecha para contraerla. Pulsar en la etiqueta o en la flecha cambia la categoría entre contraída y expandida.</para>
          </listitem>
        </itemizedlist>
      </sect3>
    </sect2>

    <!-- FIXME - should eventually give general guidelines for other sorts of utility window
    <sect2 id="other-windows">
      <title>Other</title>
      <para>FIXME</para>
    </sect2>
    -->
  </sect1>

  <sect1 id="windows-alert">
    <title>Alertas</title>

    <para>Una alerta proporciona información sobre el estado de una aplicación del sistema, o pide información esencial sobre cómo proceder con una tarea en particular. Se distingue de otras ventanas en que el usuario no la solicita directamente, y generalmente contiene un mensaje o una pregunta en lugar de controles editables. Ya que las alertas son una intrusión no bienvenida en el trabajo del usuario, no las use salvo que sea necesario para prevenir pérdidas potenciales de datos u otros problemas graves.</para>

    <para>Una alerta tiene un borde similar a la de un diálogo y es un objeto modal.</para>
    <para>Una alerta no debería aparecer en el panel de ventanas a menos que sea, o que pueda ser, la única ventana mostrada por la aplicación. Por ejemplo. una alerta de recordatorio se puede mostrar después de haber cerrado la aplicación de calendario.</para>
    <para>De otro modo, una alerta se debe mostrar sobre la aplicación cuando la ventana de la aplicación en sí está seleccionada desde la lista de ventanas.</para>

    <figure id="example-alert-figure">
      <title>Ejemplo de alerta</title>

      <mediaobject>
        <imageobject>
          <imagedata fileref="images/windows-alert-information.png" width="251" depth="123" format="PNG"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/windows-alert-information.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Ejemplo de una alerta, mostrando el texot «Tiene una cita con Jorge Castro en 15 minutos», y con un botón «Aceptar» para descartar la ventana.</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!--<remark>FIXME: need to redo the spacing and icons in the alert shots. I think I have a glade file for these somewhere. -Seth</remark>-->

    <formalpara>
      <title>Formato del título</title>

      <para>Las ventanas de las alertas no tienen título ya que, generalmente, el título duplicaría innecesariamente el texto principal de la alerta. De este modo, los usuarios puede leer y responder a las alertas más rápidamente ya que hay menos ruido visual y menos texto confuso.</para>
    </formalpara>

    <remark>NO TRADUCIR</remark>

    <remark>NO TRADUCIR</remark>

    <remark>NO TRADUCIR</remark>

    <remark>NO TRADUCIR</remark>

    <formalpara>
      <title>Redimensionando</title>

      <para>Las ventanas de alerta no son redimensionables. Si el usuario necesita redimensionar su alerta, entonces probablemente el texto no es suficientemente conciso.</para>
    </formalpara>

    <formalpara>
      <title>Comandos de ventana:</title>

      <para>Ninguno</para>
    </formalpara>

    <caution>
      <title>Las alertas deben mostrarse por encima de sus padres</title>

      <para>Alerts do not appear in the system window list. Consequently, take
      care to ensure that alerts stay above their parent window. Otherwise,
      users will be likely to lose the alert and find your application
      unresponsive for no apparent reason. Modal windows should always stay
      above the window(s) they block.</para>
    </caution>

    <!--    
    <para role="library-problem">Buttons in GTK dialogues end up the same size (sized to the button with the longest text label). This is wrong, and looks bad.</para>
    <para role="library-problem">Automatic wrapping of labels happens at funny places and ends up looking wrong. Labels should wrap before the last whole word that does not fit in the allotted space.</para> 
      -->

    <!--
  <para>FIXME - reduced or no frame; one or two buttons: <guibutton>OK</guibutton> for informing alerts, and effectively <guibutton>Cancel</guibutton> and <guibutton>OK</guibutton> for confirmation. No other controls: especially not the "Do not show this again" checkbutton. Perhaps locally modal, rarely globally modal.</para>
    -->

    <sect2 id="alert-text">
      <title>Texto de alerta</title>

      <para>Una alerta puede contener texto primario y secundario. El texto primario describe brevemente la situación. El texto secundario proporciona información adicional.</para>

	<para>Haga que tanto el texto primario como el secundario sean seleccionables. Esto hace que sea más fácil para el usuario copiar y pegar el texto en otra ventana, tal como un correo electrónico.</para>

      <figure id="alert-text-figure">
        <title>Ubicación de texto primario y secundario</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-alert-text.png" width="446" depth="178" format="PNG"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-alert-text.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Captura de pantalla de una alerta mostrando un ejemplo de texto primario en negrita y texto secundario en una tipografía más pequeña, debajo.</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <formalpara>
        <title>Texto primario</title>

        <para>The primary text provides the user with a one sentence summary
        of the information or suggested action. This summary should concisely
        contain the essential details of the problem or suggestion. Every
        alert has primary text, displayed in a bold font slightly larger than
	the default. The primary text is punctuated in 'newspaper headline'
	style, that is, it has no terminating period, but it may have a 
	terminating question mark.</para>
      </formalpara>

      <para role="technical-note">Note el texto primario con el marcado pango: <programlisting>&lt;span weight="bold"
      size="larger"&gt;<replaceable>Texto primario</replaceable>&lt;/span&gt;</programlisting></para>

      <formalpara>
        <title>Texto secundario</title>

        <para>Secondary text provides a more in-depth description of the
        problem and suggested action, including possible side effects.
        Secondary text can also provide information that may be helpful in
        allowing the user to make an informed decision. In most situations the
        user should only need the primary text to make a quick decision, but
        they may read the secondary text if they are unsure of the proper
        course of action, or require extra details. Secondary text is
        optional, but if used, place it one text line height beneath the
        primary text using the default font size and weight.</para>
      </formalpara>
    </sect2>

    <sect2 id="alert-button-order">
      <title>Botones de alerta</title>

      <para>Give all alerts an affirmative button that dismisses the alert and
      performs the action suggested in the primary text. Provide a
      <guibutton>Cancel</guibutton> button for all alerts displayed in
      response to a user actions, such as <guimenuitem>Quit</guimenuitem>. If
      the alert warns of a technical problem or other situation that could
      result in data loss, provide a <guibutton>Help</guibutton> button that
      provides more information on the particular situation and explains the
      user's options. You may also provide buttons to perform alternate
      actions that provide another possible solution, fix potential problems,
      or launch related dialogs or programs.</para>

      <figure id="alert-buttons-figure">
        <title>Ordenación de botones y ubicación de alertas</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-alert-buttons.png" format="PNG" width="425" depth="62"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-alert-buttons.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Captura de pantalla mostrando ordenación y ubicación de los botones de alerta: botón de ayuda en la parte inferior izquierda, y botones de cambio, cancelación y aprobación en la parte inferior derecha.</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <formalpara>
        <title>Texto en los botones</title>

        <para>Write button labels as imperative verbs, for example
        <guibutton>Save</guibutton>, <guibutton>Print</guibutton>. This allows
        users to select an action with less hesitation. An active phrase also
        fits best with the button's role in initiating actions, as
        contrasted with a more passive phrase. For example
        <guibutton>Find</guibutton> and <guibutton>Log In</guibutton> are
        better buttons than <guibutton>Yes</guibutton> and
        <guibutton>OK</guibutton>.</para>
      </formalpara>

      <itemizedlist>
        <listitem>
          <formalpara>
            <title>Botón afirmativo</title>

            <para>Place the affirmative button in the lower right corner of
            the alert. The affirmative button accepts the action proposed by
            the alert, or simply dismisses the alert if no action is suggested
            (as is the case with an <link linkend="alerts-information">information
            alert</link>).</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Botón Cancelar</title>

            <para>If the alert was produced in response to a user's action,
            place a <guibutton>Cancel</guibutton> button immediately to the
            left of the affirmative button. This provides an escape route for
            users to stop an action in response to new information, or just if
            they clicked accidentally. Clicking the <guibutton>Cancel</guibutton>
            button reverts the application to its state prior to the user
            action.</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Botón Ayuda</title>

            <para>A <guibutton>Help</guibutton> button may be used to clarify
            alerts that present potentially destructive options. Place the
            <guibutton>Help</guibutton> button in the lower left corner of the
            alert. When clicked, launch a help window clarifying the
            situation, detailing the actions performed by the other buttons,
            and explaining any side-effects that each action may have.</para>
          </formalpara>
        </listitem>

        <listitem>
          <formalpara>
            <title>Botones de cambio</title>

            <para>Extra buttons may be used to provide alternates to the
            primary action proposed by the alert text. Place these buttons to
            the left of the <guibutton>Cancel</guibutton> button, or the
            affirmative button if <guibutton>Cancel</guibutton> is not
            present. An example of a common alternate action would be a
            <guibutton>Quit without Saving</guibutton> button in a save
            confirmation alert. This is an alternative to the primary
            suggested action <guibutton>Save</guibutton> and the
            <guibutton>Cancel</guibutton> button.</para>
          </formalpara>
        </listitem>
      </itemizedlist>
    </sect2>

    <sect2 id="alert-spacing">
      <title>Espaciado y posicionamiento dentro de las alertas</title>

      <para>Usar espaciado limpio y consistente en las alertas hace que el mensaje sea más fácil de leer y entender así como más obvias las reacciones.</para>

      <figure id="alert-spacing-figure">
        <title>Espaciado dentro de una alerta</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-alert-spacing.png" format="PNG" width="530" depth="250"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-alert-spacing.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Diagramas mostrando el espaciado correcto que usar entre controles y botones en una ventana de alerta. Está detallado en las guías de debajo.</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <itemizedlist>
        <title>Guías</title>

        <listitem>
          <para>El borde alrededor de todos los bordes de la alerta y de su espaciado entre el icono y el texto es de 12 píxeles.</para>
        </listitem>

        <listitem>
          <para>El espaciado horizontal entre los botones es de 6 píxeles.</para>
        </listitem>

        <listitem>
          <para>Añada un salto de línea del tamaño estándar de tipografía debajo de los textos primario y secundario, o 24 píxeles si está usando Glade.</para>
        </listitem>

        <listitem>
          <para>Alinee la parte superior del icono con la parte superior del texto primario.</para>
        </listitem>

        <listitem>
          <para>Alinee a la izquierda el mensaje de texto para configuraciones regionales occidentales.</para>
        </listitem>
      </itemizedlist>

      <tip>
        <title>Detalles técnicos para una disposición adecuada</title>

        <para>Create a new GtkDialog window specifying the number of buttons
        you wish the alert to contain (and a help button if appropriate). The
        GtkDialog will contain a GtkVBox with an empty upper row, and a lower
        row containing a GtkButtonBox with buttons in it. In the empty upper
        row, place a new GtkHBox. In the left column of the GtkHBox place a
        GtkImage. In the right column of the GtkHBox place a GtkLabel. Inside
        the GtkLabel place <replaceable>Primary Text</replaceable> first
        (using the appropriate Pango markup, see <xref linkend="alert-text"/>),
        then put two linebreaks (return), then place
        <replaceable>Secondary Text</replaceable>. Now change the properties
        for each control according to these tables:</para>

        <table frame="topbot" pgwide="0">
          <title>Propiedades para el GtkDialog</title>

          <tgroup align="left" cols="2" colsep="0" rowsep="0">
            <thead>
              <row valign="top">
                <entry>Propiedad</entry>

                <entry>Valor</entry>
              </row>
            </thead>

            <tbody>
              <row>
                <entry>Título</entry>

                <entry>(ninguna)</entry>
              </row>

              <row>
                <entry>Anchura del borde</entry>

                <entry>6</entry>
              </row>

              <row>
                <entry>Tipo</entry>

                <entry>Nivel superior</entry>
              </row>

              <row>
                <entry>Redimensionable</entry>

                <entry>No</entry>
              </row>

              <row>
                <entry>Tiene separador</entry>

                <entry>No</entry>
              </row>
            </tbody>
          </tgroup>
        </table>

        <table frame="topbot" pgwide="0">
          <title>Propiedades para la GtkVBox (incluidas en el diálogo de manera predeterminada)</title>

          <tgroup align="left" cols="2" colsep="0" rowsep="0">
            <thead>
              <row valign="top">
                <entry>Propiedad</entry>

                <entry>Valor</entry>
              </row>
            </thead>

            <tbody>
              <row>
                <entry>Espaciado</entry>

                <entry>12</entry>
              </row>
            </tbody>
          </tgroup>
        </table>

        <table frame="topbot" pgwide="0">
          <title>Propiedades para GtkHBox</title>

          <tgroup align="left" cols="2" colsep="0" rowsep="0">
            <thead>
              <row valign="top">
                <entry>Propiedad</entry>

                <entry>Valor</entry>
              </row>
            </thead>

            <tbody>
              <row>
                <entry>Espaciado</entry>

                <entry>12</entry>
              </row>

              <row>
                <entry>Anchura del borde</entry>

                <entry>6</entry>
              </row>
            </tbody>
          </tgroup>
        </table>

        <table frame="topbot" pgwide="0">
          <title>Propiedades para GtkImage</title>

          <tgroup align="left" cols="2" colsep="0" rowsep="0">
            <thead>
              <row valign="top">
                <entry>Propiedad</entry>

                <entry>Valor</entry>
              </row>
            </thead>

            <tbody>
              <row>
                <entry>Alineación Y</entry>

                <entry>0.00</entry>
              </row>

              <row>
                <entry>Tamaño de icono</entry>

                <entry>Diálogo</entry>
              </row>
            </tbody>
          </tgroup>
        </table>

        <table frame="topbot" pgwide="0">
          <title>Propiedades para GtkLabel</title>

          <tgroup align="left" cols="2" colsep="0" rowsep="0">
            <thead>
              <row valign="top">
                <entry>Propiedad</entry>

                <entry>Valor</entry>
              </row>
            </thead>

            <tbody>
              <row>
                <entry>Usar marcado</entry>

                <entry>Sí</entry>
              </row>

              <row>
                <entry>Ajustar texto</entry>

                <entry>Sí</entry>
              </row>

              <row>
                <entry>Alineación Y</entry>

                <entry>0.00</entry>
              </row>
            </tbody>
          </tgroup>
        </table>
      </tip>
    </sect2>

    <sect2 id="alerts-information">
      <title>Alertas de información</title>

      <para>Use una alerta de información cuando el usuario deba conocer la información presentada antes de continuar, o si ha solicitado específicamente esa información. Presente la información menos importante de otra manera, como puede ser un mensaje en la barra de estado.</para>

      <figure id="information-alert-figure">
        <title>Una alerta de información</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="123" fileref="images/windows-alert-information.png" format="PNG" width="251"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-alert-information.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase/>
          </textobject>
        </mediaobject>
      </figure>

      <itemizedlist>
        <title>Una alerta de información...</title>

        <listitem>
          <para>usa el icono de información del almacén.</para>
        </listitem>

        <listitem>
          <para>presenta un mensaje seleccionable y un botón <guibutton>Aceptar</guibutton>. El botón se sitúa en la esquina inferior derecha de la alerta. Al pulsar <keysym>Intro</keysym> o <keysym>Esc</keysym> se descarta la alerta.</para>
        </listitem>

        <listitem>
          <para>may present a convenience button to give access to a relevant
          object. For example, a <guibutton>Details</guibutton> button in an
          appointment reminder alert that opens the appointment's property
          window. Place this button to the left of the affirmative button.</para>

          <!-- FIXME: Reword -->
        </listitem>
      </itemizedlist>

      <formalpara>
        <title>Comandos de ventana:</title>

        <para>Enrollar/desenrollar, minimizar (si la alerta no tiene ventana padre), cerrar</para>
      </formalpara>
    </sect2>

    <sect2 id="alerts-error">
      <title>Alertas de error</title>

      <para>Display an error alert when a user-requested operation cannot be
      sucessfully completed. Present errors caused by operations not requested
      by the user by another means, unless the error could result in data loss
      or other serious problems. For example, an error encountered during an
      email check initiated by the user clicking a toolbar button should
      present an error alert. However, an error encountered in an automated
      periodic email check would more appropriately report failure with a
      statusbar message.</para>

      <figure id="error-alert-figure">
        <title>Una alerta de error</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-alert-error.png" width="287" depth="156" format="PNG"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-alert-error.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase/>
          </textobject>
        </mediaobject>
      </figure>

      <itemizedlist>
        <title>Una alerta de error...</title>

        <listitem>
          <para>usa el icono de error del almacén.</para>
        </listitem>

        <listitem>
          <para>presenta un mensaje seleccionable con un botón <guibutton>Aceptar</guibutton>. El botón se ubica en la esquina inferior derecha de la alerta. Pulsar <keysym>Intro</keysym> puede descartar la alerta de error.</para>
        </listitem>

        <listitem>
          <para>may present a convenience button to allow immediate handling
          of the error. For example, a <guibutton>Format...</guibutton> button
          in a "This disk is not formatted" alert. Place this button
          to the left of the affirmative button.</para>
        </listitem>
      </itemizedlist>

      <formalpara>
        <title>Comandos de ventana:</title>

        <para>Enrollar/desenrollar</para>
      </formalpara>
    </sect2>

    <sect2 id="alerts-confirmation">
      <title>Alertas de confirmación</title>

      <para>Presenta una alerta de confirmación cuando el usuario peude destruir sus datos, generar un riesgo para la seguridad o si conlleva al usuario más de 30 segundos para arreglarlo si se seleccionó por error.</para>

      <figure id="confirmation-alert-figure">
        <title>Una alerta de confirmación</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-alert-confirmation.png" contentwidth="450" contentdepth="162" format="PNG"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-alert-confirmation.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase/>
          </textobject>
        </mediaobject>
      </figure>

      <itemizedlist>
        <title>Una alerta de confirmación...</title>

        <listitem>
          <para>usa el icono de advertencia del almacén.</para>
        </listitem>

        <listitem>
          <para>presenta un mensaje seleccionable y un botón etiquetado con un verbo o con una frase que describa la acción que confirmar, o la etiqueta <guilabel>Aceptar</guilabel> si la frase ocupa más de tres palabras. Este botón se coloca en la esquina inferior derecha de la alerta.</para>
        </listitem>

        <listitem>
          <para>presenta un botón <guibutton>Cancelar</guibutton> que evitará la ejecución del comando del usuario. Este botón se coloca justo a la izquierda del botón <guibutton>Aceptar</guibutton> o equivalente.</para>
        </listitem>

        <listitem>
          <para>puede presentar un botón de acción alternativo o un botón de conveniencia. Ubique este botón a la izquierda del botón <guibutton>Cancelar</guibutton>.</para>
        </listitem>
      </itemizedlist>


      <formalpara>
        <title>Comandos de ventana:</title>

        <para>Enrollar/desenrollar</para>
      </formalpara>

      <sect3 id="save-confirmation-alerts">
        <title>Alertas de confirmación de guardado</title>

        <para>Las alertas de confirmación de guardado ayudan a asegurarse de que los usuarios no pierden los cambios en los documentos cuando cierran las aplicaciones. Esto hace que cerrar aplicaciones sea una operación menos peligrosa.</para>

        <figure id="save-alert-figure">
          <title>Una alerta de confirmación de guardado</title>

          <mediaobject>
            <imageobject>
              <imagedata fileref="images/windows-alert-save.png" width="500" depth="194" format="PNG"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/windows-alert-save.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Alerta de confirmación de guardado: "[ Cerrar sin guardar ] [ Cancelar ] [[ Guardar ]] "</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <formalpara>
          <title>Texto primario</title>

          <para>¿Quier guardar los cambios en el documento <replaceable>Nombre del documento</replaceable> antes de cerrar?</para>
        </formalpara>

        <para>Puede reemplazar <quote>documento</quote> con una descripción más adecuada, por ejemplo <quote>imagen</quote> o <quote>diagrama</quote> si el documento en cuestión no es principalmente de texto.</para>

        <formalpara>
          <title>Texto secundario</title>

          <para>Si cierra sin guardar, se perderán los cambios de los últimos <replaceable>periodo de tiempo</replaceable></para>
        </formalpara>

        <para role="explanation">El texto secundario proporciona al usuario cierto contexto acerca del número de cambios sin guardar.</para>

        <formalpara>
          <title>Botones</title>

          <para><guibutton>Cerrar sin guardar</guibutton>, <guibutton>Cancelar</guibutton>, <guibutton>Guardar</guibutton></para>
        </formalpara>
      <para>
When a confirmation alert is needed,
present it immediately. If the user confirms closing without saving,
hide the alert and the document or application  window immediately, 
before doing any necessary internal clean-up.
If the user chooses to save before
closing, hide the alert immediately but show the document window until the document is
saved, in case an error occurs.  Then hide the document window immediately after it has been saved successfuly.
	</para>
      </sect3>
    </sect2>

    <sect2 id="alerts-authentication">
      <title>Alertas de autenticación</title>

      <para>Las alertas de autenticación socilitan al usuario la información necesaria para obtener acceso a recursos protegidos, como su nombre y su contraseña. Las alertas de autenticación son un tipo especial de alertas porque son generalmente inveitables. Cada intento se debe hacer para mantener la información introducida en la alerta de autenticación, siempre que sea posible sin restricciones de la seguridad.</para>

      <figure id="authentication-alert-figure">
        <title>Una alerta de autenticación</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-alert-authentication.png" width="460" depth="279" format="PNG"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-alert-authentication.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase/>
          </textobject>
        </mediaobject>
      </figure>

      <para><itemizedlist><title>Guías</title><listitem><para>Usar el botón de autenticación del almacén</para></listitem><listitem><para>Muestre un campo etiquetado para cada elemento de información necesario. Los campos sugeridos son <guilabel>Nombre de usuario</guilabel> y <guilabel>Contraseña</guilabel> (en ese orden), donde sea apropiado.</para></listitem><listitem><para>If it is
      secure to retain the username longer than the password, pre-fill the
      username field and give focus to the password field when the alert is
      displayed.</para></listitem><listitem><para>Show a button labelled with
      a verb or verb phrase describing the authentication action, or
      <guilabel>OK</guilabel> if there is no appropriate phrase or such a
      phrase would be longer than three words. Place this button in the bottom
      right corner of the alert.</para></listitem><listitem><para>No active el botón <guibutton>Aceptar</guibutton> o equivalente hasta que el usuario no haya rellenado todos los campos necesarios. Recuerde que, sin embargo, no todos los campos pueden requerir que se escriba algo. Por ejemplo, una contraseña vacía puede ser válida en varias aplicaciones</para></listitem><listitem><para>Muestre un botón <guibutton>Cancelar</guibutton> que evitará la autenticación y cerrará la alerta. Coloque este botón justo a la izquierda del botón <guibutton>Aceptar</guibutton> o equivalente.</para></listitem><listitem><para>Ubique cualquier acción alternativa o botón conveniente a la izquierda del botón <guibutton>Cancelar</guibutton>.</para></listitem><listitem><para>Cuando el usuario pulse <keycap>Intro</keycap> en el último campo, active el botón predeterminado. Cuando el usuario pulse <keycap>Intro</keycap> en otro campo, mueva el foco al siguiente campo.</para></listitem></itemizedlist></para>

      <formalpara>
        <title>Comandos de ventana:</title>

        <para>Enrollar/desenrollar</para>
      </formalpara>
    </sect2>
  </sect1>

  <sect1 id="windows-progress">
    <title>Ventanas de progreso</title>

    <para>Se puede usar una ventana de progreso para proporcionar <link linkend="feedback">información</link> durante una operación que dura más de un segundo. Consulte la <xref linkend="controls-progress-bars"/> para obtener más detalles sobre el uso adecuado de las barras de progreso.</para>
		
    <para>A progress window should always appear as an independent window in a window list.
	If progress of a task makes a window temporarily unusable, do not present a modal dialog-like progress window in front of it.
	Instead, present progress somewhere in the original window, making all its other elements temporarily insensitive.
	This helps reduce visual clutter.</para>

    <figure id="example-progress-figure">
      <title>Ejemplo de una ventana de progreso</title>

      <mediaobject>
        <imageobject>
          <imagedata fileref="images/windows-progress.png" width="425" depth="159" format="PNG"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/windows-progress.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Ejemplo de una ventana de progreso</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <formalpara>
      <title>Formato del título</title>

      <para>Las ventanas de progreso deben tener un título que represente la operación completa, por ejemplo: <guilabel>Copiando archivos</guilabel>, <guilabel>Instalando</guilabel>, o <guilabel>Llamando</guilabel>. Al igual que con otros títulos de ventanas, no termine los títulos de las ventanas de progreso con puntos suspensivos.</para>
    </formalpara>

    <formalpara>
      <title>Redimensionando</title>

      <para>Las ventanas de progreso deben ser redimensionables si contienen información no estática que el usuario pueda querer copiar (por ejemplo, el URL de origen en una ventana de descarga). Si no es así, no deben ser redimensionables.</para>
    </formalpara>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>A menudo es mejor usar la barra de progreso que tienen muchas barras de estado de la ventana principal en lugar de una ventana de progreso. Consulte la <xref linkend="progress-windows-vs-status-bar"/> para obtener más detalles o para elegir entre las dos.</para>
      </listitem>

      <listitem>
        <para>Las ventanas de progreso deben usar un texto primario y secundario como una alerta. Consulte la <xref linkend="alert-text"/>.</para>
      </listitem>

      <listitem>
        <para>El texto de la barra de progreso deber proporcionar una idea de cuánto trabajo se ha completado. Es mejor proporcionar información específica que porcentajes. Por ejemplo, «rotadas 13 de 19 imágenes» o «descargados 12.1 de 30 MB» en lugar de «13% completado».</para>
      </listitem>

      <listitem>
        <para>If possible, an estimate of the time left until the operation is
        complete should also be included in the progress bar text. Indicate
        that the "time left" is an estimate using the word
        "about".</para>
      </listitem>

      <listitem>
        <para>Immediately beneath the progress bar, place italicized text
        indicating the current sub-operation being performed. This might be a
        step in a sequence, "Contacting control tower for permission to
        land", or it could be the current object being operated on in a
        bulk operation, "Rotating MonaLisa.png", "Rotating
        StarryNight.png".</para>
      </listitem>

      <listitem>
        <para>If the operation in progress is potentially hazardous
        (destructive, costly, etc) or heavily taxes a limited resource for
        more than ten seconds (network bandwidth, hard disk, CPU, etc),
        consider placing a <guibutton>Pause</guibutton> <link linkend="controls-toggle-buttons">toggle button</link> to the right of
        the <guibutton>Cancel</guibutton> button. When paused, the italicized
        current sub-operation text should have " (Paused)" appended.
        This will allow users to perform important tasks requiring that
        resource, or give them time to think whether they want to procede with
        a dangerous operation they inadvertantly triggered.</para>
      </listitem>
    </itemizedlist>

    <figure id="example-complex-progress-figure">
      <title>Una ventana de progreso para una operación de copia de un archivo</title>

      <mediaobject>
        <imageobject>
          <imagedata fileref="images/windows-progress-copy-file.png" width="408" depth="227" format="PNG"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/windows-progress-copy-file.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Una ventana de progreso para las operaciones de copia</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <sect2 id="progress-window-checklists">
      <title>Ventanas de listas de comprobación</title>

      <para>Occasionally a procedure is comprised of a series of user
      performable actions. In these cases, particularly when it is desirable
      that the user acquire some familiarity with the actions involved in a
      procedure, checklist windows may be used.</para>

      <example>
        <title>Asistente de configuración del cortafuegos</title>

        <para>A personal firewall setup wizard might install the firewall
        package, add entries for the firewall to /etc/xinetd.conf, restart the
        internet super-daemon, and configure the user's web browser to
        operate through the firewall. It may be desirable that the user is
        exposed to the series of actions involved in setting up the firewall to
        increase the chances that they will be sucessful in making
        modifications later, if they so desire.</para>
      </example>

      <figure id="example-checklist-start-figure">
        <title>An example checklist window (Ready to Start)</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-progress-checklist-start.png" width="422" depth="249" format="PNG"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-progress-checklist-start.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Una ventana de lista de comprobación</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <figure id="example-checklist-in-progress-figure">
        <title>Un ejemplo de ventana de lista de comprobación (en progreso)</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-progress-checklist.png" width="336" depth="220" format="PNG"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-progress-checklist.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Una ventana de lista de comprobación</phrase>
          </textobject>
        </mediaobject>
      </figure>
      
      <figure id="example-checklist-done-figure">
        <title>Un ejemplo de ventana de lista de comprobación (terminada)</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-progress-checklist-done.png" width="356" depth="223" format="PNG"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-progress-checklist-done.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Una ventana de lista de comprobación</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <itemizedlist>
        <title>Guías</title>

        <listitem>
          <para>If knowing the series of steps in an operation isn't that
          useful to the user, just use a regular progress window. Remember
          that you are probably more interested in the information than most
          users, many of whom will find the technical steps confusing rather
          than helpful.</para>
        </listitem>

        <listitem>
          <para>Unlike regular progress windows, checklist windows should not
          close automatically when the operation is complete and should
          require explicit user input before they begin. This is because one
          of their purposes is to inform the user concerning an
          operation's contingent steps.</para>
        </listitem>

        <listitem>
          <para>The progress bar indicates progress in the overall operation,
          not each step. While this is more difficult to program, it is the
          information most useful to the user. Just estimate how long each of
          the steps takes relative to each other and assign each step a fixed
          ratio of the progress bar's progress accordingly.</para>
        </listitem>

        <listitem>
          <para>Do <emphasis>not</emphasis> use a checklist window for a
          series of internal programmatic steps, use a regular progress
          window. For example "Connect to mail server",
          "Authenticate with mail server", "Download
          messages", "Disconnect" would <emphasis>not</emphasis>
          be an appropriate series of steps for a checklist window, but would
          be appropriate sub-operation steps for a regular progress window.</para>
        </listitem>
      </itemizedlist>
    </sect2>
  </sect1>

  <sect1 id="windows-dialog">
    <title>Diálogos</title>

    <para>A dialog provides an exchange of information, or dialog, between the
    user and the application. Use a dialog to obtain additional information
    from the user that is needed to carry out a particular command or task.</para>
	<para>Un diálogo no debe aparecer en la lista de ventanas del panel. Cualquier diálogo abierto se debe elevar por encima de la aplicación cuando su ventana se seleccione en la lista de ventanas.</para>

    <figure>
      <title>Ejemplo de diálogo</title>

      <mediaobject>
        <imageobject>
          <imagedata fileref="images/windows-dialog-tabbed.png" width="357" depth="322" format="PNG"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/windows-dialog-tabbed.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Un ejemplo de diálogo en pestañas: el diálogo de impresión de GNOME</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <formalpara>
      <title>Formato del título:</title>

      <para><replaceable>Nombre del comando que abrió el diálogo</replaceable> (sin puntos suspensivos)</para>
    </formalpara>

    <formalpara>
      <title>Comandos de ventana:</title>

      <para>Minimizar, enrollar/desenrollar</para>
    </formalpara>

    <formalpara>
      <title>Botones:</title>

      <para>Siga la guía para los Botones de alerta, consulte la <xref linkend="alert-button-order"/>.</para>
    </formalpara>

    <para>Your dialog may specify a default button, that is activated when the
    user presses the <keycap>Return</keycap> key. See <xref linkend="default-buttons"/> for guidance on choosing an appropriate
    default button.</para>

    <sect2 id="dialog-buttons">
      <title>Botones adicionales</title>

      <para>You can include other buttons in a dialog's main button area
      in addition to the affirmative button and <guibutton>Cancel</guibutton>,
      but any more than one or two such buttons will make the dialog appear
      complicated and difficult to use. As with any other button, keep the
      labels as concise as possible to minimize this effect.</para>

      <itemizedlist>
        <title>Guías</title>

        <listitem>
          <para>Place buttons that apply to the dialog as a whole in the main
          button area row at the bottom of the dialog, to the left of the
          <guibutton>Cancel</guibutton> button.</para>
        </listitem>

        <listitem>
          <para>Place buttons that apply to one or a few controls next to
          their associated controls. For instance, place a
          <guibutton>Browse...</guibutton> button at the trailing edge of the
          text field it fills in.</para>
        </listitem>
      </itemizedlist>
    </sect2>

    <sect2 id="dialog-layout">
      <title>Distribución</title>

      <para>A clean, logical dialog layout helps the user to quickly
	understand what information is required from them.</para>

      <itemizedlist><title>Guías</title>

      <listitem><para>
      Arrange controls in your dialog in the direction that people read.
      In western locales, this is generally left-to-right, top-to-bottom.
      Position the main controls with which the user will interact as close to
      the upper left corner as possible. Follow similar guidelines for
      arranging controls within groups in the dialog, and for specifying the
      order in which controls are traversed using the <keycap>Tab</keycap>
      key.</para></listitem>

      <listitem><para>
    	When opening a dialog, provide initial keyboard focus to the
      component that you expect users to operate first. This focus is
      especially important for users who must use a keyboard to navigate your
      application.</para></listitem>

      <listitem><para>Provide and show sensible default values for as many of the
      controls in your dialog as possible when it is opened, so the user does
      not have to generate the information from scratch. These defaults may
      come from system settings (for example, hostname or IP address), or from
      information that the user has previously entered in this or another
      application (for example, email address or network proxy).</para></listitem>
	</itemizedlist>

      <para>Consulte la <xref linkend="design"/> para obtener información más detallada sobre cómo colocar controles en los diálogos.</para>

      <para>Consulte la <xref linkend="controls-notebooks"/> para obtener información sobre cómo usar controles en pestañas en los diálogos.</para>
    </sect2>

    <sect2 id="common-dialogs">
      <title>Diálogos comunes</title>

      <para>The gtk and GNOME libraries provide standard dialogs for many
      common tasks, including opening and saving files, choosing fonts and
      colors, and printing. Always use these when the user is performing one
      of these tasks. You may modify the dialogs to reflect the needs of your
      particular application (for example, adding preview
      <guibutton>Play</guibutton> and <guibutton>Stop</guibutton> buttons to
      the Open File dialog in an audio application), but do not change or
      remove features so much as to make them unrecognizable.</para>
    </sect2>
  </sect1>

  <sect1 id="windows-assistant">
    <title>Asistentes</title>

    <!--<remark>FIXME: need to finish this section</remark>-->

    <para>An assistant is a secondary window that guides the user through an
    operation by breaking it into sequential steps. Assistants are useful for
    making complex operations less intimidating, as they restrict the
    information visible to the user at any given moment.</para>

    <para>Because assistants provide a relatively small number of controls on
    the screen at any given time, they have sufficient space for inline
    documentation. Therefore, do not include a <guibutton>Help</guibutton>
    button in an assistant window. If you cannot make an operation
    sufficiently clear in an assistant without resorting to a
    <guibutton>Help</guibutton> button, you need to simplify it further.</para>

    <para>Assistants do have major downsides. After using an assistant
    it is often hard to figure out where the individual settings aggregated
    into the assistant are stored. Often people will resort to re-running
    the assistant, re-entering many settings that they don't want to change.
    <remark>Why do they need to re-enter anything? The assistant should
	be populated with the exisiting settings whenever it is run.</remark>
    </para>

    <warning><para>Assistants are often used in situations where a better
    solution would be to simplify, or even better automate, the process.
    Before using an assistant to step people through a complex operation,
    consider if the operation can be fundamentally simplified so an
    assistant is unnecessary.</para></warning>
    

    <formalpara>
      <title>Comandos de ventana:</title>

      <para>Cerrar, minimizar/restaurar, enrollar/desenrrollar</para>
    </formalpara>

    <sect2 id="assistant-first-page">
      <title>Página de introducción</title>

      <para>The first page provides the user with the "big picture".
      Place the title of the assistant in the window's title bar and the
      assistant's title area, along with an optional picture. Beneath
      this, state the goal of the assistant, and, if it is not obvious, where
      the user can find the information the assistant will be asking for.</para>

      <formalpara>
        <title>Formato del título:</title>

        <para><replaceable>Título del asistente</replaceable></para>
      </formalpara>

      <formalpara>
        <title>Botones:</title>

        <para><guibutton>Cancelar</guibutton>, <guibutton>Adelante</guibutton></para>
      </formalpara>

      <figure>
        <title>Ejemplo de la primera página de un asistente</title>

        <mediaobject>
          <imageobject>
            <imagedata fileref="images/windows-assistant-first-page.png" format="PNG" width="502" depth="318"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-assistant-first-page.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Captura de pantalla que muestra la primera página de un asistente para crear una cuenta de correo-e nueva.</phrase>
          </textobject>
        </mediaobject>
      </figure>
    </sect2>

    <sect2 id="assistant-middle-page">
      <title>Páginas de contenido</title>

      <para>Content pages contain the actual settings of the assistant.
      Summarize the type of setting present on each content page in its title
      area. For example, <guilabel>Mail Server</guilabel>.</para>

      <formalpara>
        <title>Formato del título:</title>

        <para><replaceable>Título del asistente</replaceable> - (<replaceable>Página actual</replaceable> de <replaceable>Páginas en total</replaceable>)</para>
      </formalpara>

      <formalpara>
        <title>Botones:</title>

        <para><guibutton>Cancelar</guibutton>, <guibutton>Atrás</guibutton>, <guibutton>Adelante</guibutton></para>
      </formalpara>

<!--
      <figure>
        <title>Example of a middle page of an assistant</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="341" fileref="images/windows-assistant-middle-page.png"
            format="PNG" width="452" />
          </imageobject>

          <imageobject>
            <imagedata fileref="images/windows-assistant-middle-page.eps" format="EPS" />
          </imageobject>

          <textobject>
            <phrase>Screenshot showing the third page of an email account
            assistant, asking for mail server information</phrase>
          </textobject>
        </mediaobject>
      </figure>
-->
    </sect2>

    <sect2 id="assistant-last-page">
      <title>Última página</title>

      <para>La última página debería resumir las configuraciones que el asistente ha cambiado y cómo puede el usuario modificarlas más tarde.</para>

      <formalpara>
        <title>Formato del título:</title>

        <para>Terminar es <replaceable>Título del asistente</replaceable></para>
      </formalpara>

      <formalpara>
        <title>Botones:</title>

        <para><guibutton>Cancelar</guibutton>, <guibutton>Atrás</guibutton>, <guibutton>Terminar</guibutton></para>
      </formalpara>
    </sect2>
  </sect1>
</chapter>


  <chapter id="menus">
    <title>Menús</title>

<remark>NO TRADUCIR</remark>
<remark>Posición de la barra de menú</remark>
<remark> Menu bar hiding </remark>

    <para>Menus present the whole range of an application's commands to the user, and often a subset of its preferences.  When designing a new application, place common menu items in the same locations as they appear in other applications, as this makes it much easier for the user to learn.</para>
  
    <para>In most applications, only primary windows should have a menubar. <link linkend="windows-utility">Utility windows</link> and <link linkend="windows-dialog">dialogs</link> should be simple enough that their functions can be provided by controls such as buttons placed within the window.</para>

    <para>Occasionally, however, a utility window or dialog is so complex that there would be too many such controls. In this case, you may use a menubar provided that:</para>

    <itemizedlist>
      <listitem><para>los menús siguen la misma distribución estándar descrita en la <xref linkend="menus-standard"/></para></listitem>
      <listitem><para>the window does not include a dialog button area or any buttons that dismiss it, such as <guibutton>OK</guibutton>, <guibutton>Close</guibutton> or <guibutton>Cancel</guibutton>.  Place these commands on the <guimenu>File</guimenu> menu or equivalent instead.</para></listitem>
    </itemizedlist>

	<itemizedlist><title>Guías</title>
      <listitem><para>Label menu items with verbs for commands and adjectives for settings, according to the rules in <xref linkend="layout-capitalization"/>.</para></listitem>

	<listitem><para>Make a menu item insensitive when its command is unavailable. For example, the <menuchoice><guimenu>Edit</guimenu> <guimenuitem>Copy</guimenuitem></menuchoice> item, which issues the command to copy selected data to the clipboard, should not be active when there is no data selected.</para></listitem>

    <listitem><para>Provide an access key for every menu item.  You may use the same access key on different menus in your application, but avoid duplicating access keys on the same menu.  Note that unlike other controls, once a menu is displayed, its access keys may be used by just typing the letter; it is not necessary to press the <keysym>Alt</keysym> key at the same time.</para></listitem>

      <listitem><para>Design your menu structure to avoid more than one level of submenus.  Deep menu hierarchies are harder to memorize and physically difficult to navigate.</para></listitem>

	<listitem><para>Do not have menus with less than three items on them (except the standard <guimenu>Help</guimenu> menu, which has only two items by default).  If you have a submenu with fewer than three items on it, move them into their parent menu.  If you have a top-level menu with fewer than three items on it, find another suitable menu to add them to, or find suitable items from other menus to add to it.</para></listitem>

	</itemizedlist>


	<sect1 id="menus-menubar">
	  <title>La barra de menú</title>

	<figure id="example-menu-bar">
	<title>Una barra de menú típica</title>
	<mediaobject>
	<imageobject><imagedata fileref="images/menus-application.png" width="454" depth="27" format="PNG"/></imageobject>
	<imageobject><imagedata fileref="images/menus-application.eps" format="EPS"/></imageobject>
	<textobject><phrase>Una barra de menú típica con los menús Archivo, Editar, Ver, Insertar, Formato, Ir, Marcadores. Herramientas, Ventanas y Ayuda</phrase></textobject>
	</mediaobject>
      </figure>

	  <para>La barra de menús proporciona una serie de menús desplegables. Sólo se muestran los títulos de los menús, hasta que el usuario pulsa en uno de ellos.</para>

	<para>Normalmente, la barra de menú está visible todo el tiempo y es accesible desde el teclado, por lo que debe hacer que todos los comandos disponibles en su aplicación estén disponibles desde la barra de menú.</para>

	<note><title>Modo a pantalla completa</title><para>When your application is running in full screen mode, hide the menubar by default.  However, make its menus and items accessible from the keyboard as usual. Pressing <keycap>ESC</keycap> should cause the application to leave full screen mode. A <guibutton>Leave Fullscreen</guibutton> button should be placed in the upper right hand corner of the window. The button should disappear after the mouse is unused for 5 seconds, and should appear again when the moused is moved. Alternately, in applications where the mouse is used frequently in full screen mode, all but a two pixel row of the button may be slid off the top of the screen. The button should slide back on the screen when the mouse moves near it.</para></note>

	<itemizedlist><title>Guías</title>

		<listitem><para>Proporciona una barra de menú en cada ventana principal de la aplicación que contenga al menos los elementos <guimenu>Archivo</guimenu> y <guimenu>Ayuda</guimenu>.</para></listitem>

      		<listitem><para>Organize menu titles in the standard order— see <xref linkend="menus-standard"/></para></listitem>

		 <listitem><para>Do not disable menu titles. Allow the user to explore the menu, even though there might be no available items on it at that time.</para></listitem>

		  <listitem><para>Menu titles on a menubar are single words with their first letter capitalized.  Do not use spaces in menu titles, as this makes them easily-mistaken for two separate menu titles.  Do not use compound words (such as <guimenu>WindowOptions</guimenu>) or hyphens (such as <guimenu>Window-Options</guimenu>) to circumvent this guideline.</para></listitem>

		<listitem><para>Do not provide a mechanism for hiding the menubar, as this may be activated accidentally. Some users will not be able to figure out how to get the menu bar back in this case.</para></listitem>
	
	</itemizedlist>

	</sect1>

   <sect1 id="menus-types">
      <title>Tipos de menús</title>


	<sect2 id="menu-type-drop-down">
	  <title>Menús desplegables</title>
	<figure id="drop-down-menu">
	<title>Un menú desplegable típico</title>
	<mediaobject>
	  <imageobject><imagedata fileref="images/menus-dropdown.png" format="PNG" width="166" depth="300"/></imageobject>
	  <imageobject><imagedata fileref="images/menus-dropdown.eps" format="EPS"/></imageobject>
	  <textobject><phrase>Captura de pantalla de un menú desplegable típico</phrase></textobject>
	</mediaobject>
      </figure>

	  <para>A drop-down menu appears when the user clicks on its title in a menubar, or focuses the title and presses <keycap>Return</keycap>.</para>

<remark>NO TRADUCIR</remark>
<remark>CFB: I've just reworded everything to avoid the use of "post"</remark>

    <itemizedlist><title>Guías</title>

	<listitem><para>Only place items on a menu that relate to that menu's title.</para></listitem>

      <listitem><para>Organize menu items in the standard order— see <xref linkend="menus-standard"/>.  For application-specific items where there is no standard order, arrange in numerical or other logical order (for example, <guimenuitem>50%</guimenuitem>, <guimenuitem>100%</guimenuitem>, <guimenuitem>200%</guimenuitem>), task order (for example, <guimenuitem>Compile</guimenuitem> followed by <guimenuitem>Debug</guimenuitem>) or by expected frequency of use.</para></listitem>

      <listitem><para>Limit top-level menus to a maximum of about 15 items. If you have any more items than this, consider moving a functionally-related subset of the items into a submenu or a new top-level menu.</para></listitem>

      <listitem><para>Do not add or remove individual menu items while the application is running, make them insensitive instead. Entire menus may be added or removed from the menubar at runtime, however, for example in component-based applications.</para></listitem>

      <listitem><para>Immediately update menu items that are edited directly or indirectly by the user, such as those on the <guisubmenu>Open Recent</guisubmenu> submenu and the <guimenu>Bookmarks</guimenu> menu.</para></listitem>


    </itemizedlist>
  <remark>CB-Ed: As in JLFDG AT p. 33, perhaps provide a table of common access keys, or "mnemonics."</remark>
  <remark>CFB: the keyboard navigation chapter already does so</remark>


	</sect2>

	<sect2 id="menu-type-submenu">
	  <title>Submenús</title>

	<figure id="submenu">
	<title>Un menú desplegable con un submenú</title>
	<mediaobject>
	  <imageobject><imagedata fileref="images/menus-submenu.png" format="PNG" width="352" depth="264"/></imageobject>
	  <imageobject><imagedata fileref="images/menus-submenu.eps" format="EPS"/></imageobject>
	  <textobject><phrase>Screenshot of a drop-down menu with a submenu</phrase></textobject>
	</mediaobject>
      </figure>

	  <para>A submenu appears when the user clicks its title, which is indicated by a small arrow symbol beside its label.  You can save space on long menus by grouping related commands onto a single submenu.</para>

	<itemizedlist><title>Guías</title>

		<listitem><para>Use submenus sparingly, as they are physically difficult to navigate and make it harder to find and reach the items they contain.</para></listitem>

		<listitem><para>Do not create submenus with fewer than three items, unless the items are added dynamically (for example the <menuchoice><guimenu>File</guimenu><guimenuitem>New Tab</guimenuitem></menuchoice> submenu in <application>gnome-terminal</application>).</para></listitem>

		<listitem><para>Do not nest submenus within submenus.  More than two levels of hierarchy are difficult to memorize and navigate.</para></listitem>
		
	</itemizedlist>

<remark>CB-Ed/Fig: In JLFDG AT, p. 41, the Most Recently Used (MRU) list is recommended to contain no more than 10 items. Add a figure here, with callouts to point out this rule, among others, if any are developed.</remark> 

	</sect2>

	<sect2 id="menu-type-popup">
	  <title>Menús emergentes</title>

	<figure id="popup-menu">
	<title>Un menú emergente para una carpeta de correo</title>
	<mediaobject>
	  <imageobject><imagedata fileref="images/menus-popup.png" format="PNG" width="251" depth="233"/></imageobject>
	  <imageobject><imagedata fileref="images/menus-popup.eps" format="EPS"/></imageobject>
	  <textobject><phrase>Screenshot of a popup menu for a mail folder, listing the actions that can be performed on that folder</phrase></textobject>
	</mediaobject>
      </figure>

	<para>Popup menus provide shortcuts to those menu items that are applicable only to the currently selected object.  As such, they are sometimes known as "context menus" or "shortcut menus".  A popup menu is shown when the user right-clicks on an object, or selects the object and presses <keycombo><keycap>Shift</keycap><keycap>F10</keycap></keycombo>.</para>

	<para>Be aware that popup menus are used primarily by intermediate and advanced users.  Even some users who have used graphical desktops for many years do not know about popup menus until somebody shows them.</para>

	<itemizedlist><title>Guías</title>
		<listitem><para>Provide a popup menu for every object, selectable part, and text input target such as entry fields.</para></listitem>
		<listitem><para>Provide an access key for each item.  However, to enhance their spatial efficiency and readability, do not show keyboard shortcuts in popup menus.</para></listitem>
		
		<listitem><para>Since the user may not be aware of their presence, do not provide functions that are only accessible from popup menus unless you are confident that your target users will know how to use popup menus.</para>
		<remark>Pero consulte http://bugzilla.mozilla.org/show_bug.cgi?id=34357</remark>
		</listitem>

		<listitem><para>Order items on a popup menu as follows:</para>
		<itemizedlist>
			<listitem><para>the double-click action for object, when it exists</para></listitem>
			<listitem><para>other commands and settings in expected frequency-of-use order</para></listitem>
			<listitem><para>transfer commands such as <command>Cut</command>, <command>Copy</command>, and <command>Paste</command></para></listitem>
			<listitem><para><guimenuitem>Input Methods</guimenuitem>, where applicable. <guimenuitem>Input Methods</guimenuitem> is provided by GTK+ for supporting alternatives to the keyboard for input (such as used for Japanese, Chinese, and some accessibility technologies).</para></listitem>
		</itemizedlist>
		</listitem>

	 	<listitem><para>Popup menus need to be as simple as possible to maximize their efficiency.  Do not place more than about ten items on a popup menu, and do avoid submenus.</para></listitem>

	</itemizedlist>

<remark>NO TRADUCIR</remark>
<remark>NO TRADUCIR</remark>
<remark>NO TRADUCIR</remark>
	</sect2>
	</sect1>

	<sect1 id="menus-design">
	<title>Diseñar un menú</title>

	<sect2 id="menu-grouping">
	  <title>Agrupar elementos de menú</title>

	<figure id="menu-separators">
	<title>Elementos agrupados en un menú con separadores</title>
	<mediaobject>
	  <imageobject><imagedata fileref="images/menus-dropdown.png" format="PNG" width="166" depth="300"/></imageobject>
	  <imageobject><imagedata fileref="images/menus-dropdown.eps" format="EPS"/></imageobject>
	  <textobject><phrase>Screenshot of a menu divided into five logical groups with menu separators</phrase></textobject>
	</mediaobject>
      </figure>

	  <para>Menu separators are the horizontal dividing lines that visually separate groups of related items on a drop-down menu, submenu, or popup menu.  For example, the separators in <xref linkend="menu-separators"/> divide the menu into five functionally-related groups.  Good use of separators helps to "chunk" the information on a menu and make it easier to scan and memorize.</para>
	  
	  <itemizedlist><title>Guías</title>

	    <listitem><para>The best size for a group is around 2-5 items.  Single-item groups are best placed at the top or bottom of a menu, otherwise try to group them with other single items of the same type on the same menu.</para></listitem>

	    <listitem><para>Order items within a group logically, numerically, in task order or by expected frequency of use, as appropriate.</para></listitem>

	    <listitem><para>Only place one type of menu item in each group— <link linkend="menu-item-type-command">command</link>, <link linkend="menu-item-type-mutable">mutable</link>, <link linkend="menu-item-type-check">check box</link> or <link linkend="menu-item-type-radio">radio button</link>.  For example, do not place commands (such as <menuchoice><guimenu>View</guimenu><guimenuitem>Reload</guimenuitem></menuchoice>) and settings (such as. <menuchoice><guimenu>View</guimenu><guimenuitem>Toolbar</guimenuitem></menuchoice>) in the same group.</para></listitem>

	    </itemizedlist>	  
	</sect2>

	<sect2 id="menu-item-types">
	<title>Tipos de elementos de menú</title>
	
	<sect3 id="menu-item-type-command">
	  <title>Elementos de comando</title>

	<figure id="command-items-figure"><title>Un grupo de elementos de comando en un menú</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-command-group.png" format="PNG" width="253" depth="105"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-command-group.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Screenshot of a group on a menu containing only command items: Save, Save As, and Revert</phrase></textobject>
	  </mediaobject>
	</figure>

	  <para>Command items are menu items that initiate a command or perform an action, such as <guimenuitem>Save</guimenuitem>, <guimenuitem>Print</guimenuitem> or <guimenuitem>Quit</guimenuitem>. They may act on the currently active document in a document based application, or on the application itself.</para>

	<itemizedlist><title>Guías</title>

		<listitem><para>Provide a keyboard shortcut for standard or frequently used command items.  See <xref linkend="shortcuts"/> for more information on choosing shortcut keys.</para></listitem>
	  <!-- <para>Shortcuts consist of the <keysym>Control</keysym> key and an alphanumeric key, or of one of the keys <keysym>F1</keysym>-<keysym>F12</keysym>, <keysym>Insert</keysym>, <keysym>Delete</keysym>, <keysym>Home</keysym>, <keysym>End</keysym>, <keysym>Page Up</keysym> or <keysym>Page Down</keysym>. The <keysym>Shift</keysym> key may be used as an additional modifier for commands which are related to or the opposite of the command accessed without the <keysym>Shift</keysym> key.  See <xref linkend="shortcuts"/> for more information.</para> -->
	  
	<listitem><para>Do not remove command items from the menu when they are unavailable, make them insensitive instead.  This allows the user to infer what functionality the application provides even if it is not currently available, and keeping the menu structure static makes it easier to memorize.</para></listitem>

	  <listitem><para>Label the menu item with a trailing ellipsis ("...")  only if the command requires further input from the user before it can be performed. Do not add an ellipsis to items that only present a confirmation dialog (such as <guimenuitem>Delete</guimenuitem>), or that do not <emphasis>require</emphasis> further input (such as <guimenuitem>Properties</guimenuitem>, <guimenuitem>Preferences</guimenuitem> or <guimenuitem>About</guimenuitem>).</para></listitem>

	</itemizedlist>
	<remark>
	  Should we reserve <keysym>Alt</keysym> as a modifier for window manager operations? Should we state this here?
	</remark>


<remark>NO TRADUCIR</remark>
	</sect3>

	<sect3 id="menu-item-type-mutable">
	  <title>Mutable Command Items</title>
	  <para>A mutable command item changes its label when selected.  For example, <menuchoice><guimenu>View</guimenu><guimenuitem>Reload</guimenuitem></menuchoice> in a browser may change to <guimenuitem>Stop</guimenuitem> to allow the user to interrupt the operation if it is taking a long time.</para>

	  <para>Note that mutable menu items can be problematic because the user never sees the menu item changing, so it is not obvious that a different function has become available. </para>

	<itemizedlist><title>Guías</title>
		<listitem><para>If your mutable menu items are <link linkend="menu-item-type-command">command items</link>, and you have sufficient space on your menu, consider providing two adjacent menu items for the commands instead.  Then make the items sensitive or insensitive as the situation demands.  This also makes it easier for the user to tell when different shortcuts are available for each of the commands, for example <keycombo><keycap>Ctrl</keycap><keycap>R</keycap></keycombo> for <guimenuitem>Reload</guimenuitem>, and <keycap>Esc</keycap> for <guimenuitem>Stop</guimenuitem>.</para></listitem>

		<listitem><para>Do not use mutable menu items to toggle a two-state setting (for example, <guimenuitem>Show Toolbar</guimenuitem> and <guimenuitem>Hide Toolbar</guimenuitem>).  Present such items as a single <link linkend="menu-item-type-check">check box item</link> instead.</para></listitem>
	</itemizedlist>

	</sect3>
	<sect3 id="menu-item-type-check">
	  <title>Checkbox Items</title>

	<figure id="checkbox-items-figure"><title>A group of check box items on a menu</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-checkbox-group.png" format="PNG" width="231" depth="112"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-checkbox-group.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Screenshot of group on a View menu containing four check box items: Main Toolbar, Side Pane, Location Bar and Status Bar</phrase></textobject>
	  </mediaobject>
	</figure>

	  <para>A check box menu item shows the current state of a two-state setting, and allows the user to toggle it by selecting the menu item.</para>

	<itemizedlist><title>Guías</title>
	  
	  	<listitem><para>Use a check box menu item only when it is obvious from the label what the set and unset states mean.  This usually means that the two states are logical or natural opposites, such as "on" and "off".  If this is not the case, use two <link linkend="menu-item-type-radio">radio button items</link> instead.</para></listitem>
		  <listitem><para>Never change the label of a check box menu item in response to the user selecting the item.</para></listitem>

	</itemizedlist>

	</sect3>
	<sect3 id="menu-item-type-radio">
	  <title>Radio Button Items</title>

	<figure id="radiobutton-items-figure"><title>A group of radiobutton items on a menu</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-radiobutton-group.png" format="PNG" width="167" depth="117"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-radiobutton-group.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Screenshot of group on a menu containing three radiobutton items: view as icons, view as list and view details</phrase></textobject>
	  </mediaobject>
	</figure>

	  <para>Radio button menu items show which of two or more mutually-exclusive settings are currently selected, and allow the user to choose a different setting by selecting its menu item.</para>

	<itemizedlist>

	  	<listitem><para>If you need to offer a choice of two mutually-exclusive settings to the user,  use a group of two radio button items instead of a single check box menu item if the settings are not clearly opposites.  For example, represent <guimenuitem>View as Icons</guimenuitem> and <guimenu>View as List</guimenu> as two radio button items.</para></listitem>

	  <listitem><para>Never change the label of a radio button menu item in response to the user selecting or deselecting the item.</para></listitem>

	</itemizedlist>

<remark>
	Adam notes that this whole section can be a significant source of
	nastiness in a UI. We need explicit recommendations here on how to
	represent different states of a toggled menu item via icons in the UI.
	We also need to make recommendations to avoid some common mistakes,
	including:
	
	* Confusing menu items acting as radio buttons in a group with menu
          items acting as check boxes.
	* Ambiguous names for check box/toggle menu items which make it
	  difficult to establish the current system state by looking at
	  the menu.
</remark>

	</sect3>
	
      </sect2>

    </sect1>

    <sect1 id="menus-standard">
      <title>Menús estándar</title>
      <para>Most applications have many functions in common, such as <guimenu>Cut</guimenu>, <guimenu>Copy</guimenu>, <guimenu>Paste</guimenu> and <guimenu>Quit</guimenu>.  To aid learning and memorability, these menu items, and the menus on which they appear, must appear with the same labels and in the same order in every application.  The same commands must also behave the same way in different applications, to avoid surprising the user.</para>

	<para>This section details the most common menus, menu items and their behaviors.  You will not need all of these menus or menu items in every application you write, but do preserve the order of the menu titles and of the menu items that you do use.</para>

	<itemizedlist><title>Guías</title>
		<listitem><para>Place application-specific menus after the <guimenu>Format</guimenu> menu and before the <guimenu>Go</guimenu> menu</para></listitem>

		<listitem><para>Place application-specific menu items towards the middle of a standard menu, unless they logically fit with one of the standard groups already on the menu.</para></listitem>

	</itemizedlist>

        
    <remark>What is the best way to present menus given the known variants? Multiple shots? Segments?</remark>

      <figure id="generic-menu-bar">
	<title>Una barra de menú que muestra los títulos estándar del menú en el orden correcto</title>
	<mediaobject>
	  <imageobject><imagedata fileref="images/menus-application.png" width="454" depth="27" format="PNG"/></imageobject>
	  <imageobject><imagedata fileref="images/menus-application.eps" format="EPS"/></imageobject>
	  <textobject>
	    <simplelist type="horiz" columns="9">
	      <member><guimenu><accel>F</accel>ile</guimenu></member>
	      <member><guimenu><accel>E</accel>dit</guimenu></member>
	      <member><guimenu><accel>V</accel>iew</guimenu></member>
	      <member><guimenu><accel>I</accel>nsert</guimenu></member>
	      <member><guimenu>For<accel>m</accel>at</guimenu></member>
	      <member><guimenu><accel>G</accel>o</guimenu></member>
	      <member><guimenu><accel>B</accel>ookmarks</guimenu></member>
	      <!--<member><guimenu><accel>T</accel>ools</guimenu></member>-->
	      <member><guimenu><accel>W</accel>indows</guimenu></member>
	      <member><guimenu><accel>H</accel>elp</guimenu></member>
	    </simplelist>
	  </textobject>
	</mediaobject>
      </figure>
      
      <sect2 id="the-file-menu">
	<title>Archivo</title>
		<para>The <guimenu>File</guimenu> menu contains commands that operate on the current document. It is the left-most item in the menubar because of its importance and frequency of use, and because it is a relevant menu in many applications. Historically, because most applications already had this menu, and because the distinction between closing documents and closing windows became blurred over time, the <guimenu>File</guimenu> menu has also become the standard location for <guimenuitem>Quit</guimenuitem>.</para>

		  <para>The items on the <guimenu>File</guimenu> menu are generally ordered by locality, closest first.  That is, items to save or load from file, followed by printing, followed by sending to a remote user.  Try to maintain this ordering if you have to add new items to the menu.</para>

	        <para>If your application does not operate on documents, name this item for the type of object it displays.  For example, many games should have a <guimenu>Game</guimenu> instead of a <guimenu>File</guimenu> menu.  However, place the <guimenuitem>Quit</guimenuitem> menu item last on this menu nonetheless.</para>
		
<remark>GJM: Quit should be deprecated. Close is often sufficient; especially when
the application saves state as it should.</remark>

	<figure id="generic-file-menu"><title>Un menú «Archivo» genérico</title>
	<mediaobject>
	  <imageobject><imagedata fileref="images/menus-file.png" width="290" depth="454" format="PNG"/></imageobject>
	  <imageobject><imagedata fileref="images/menus-file.eps" format="EPS"/></imageobject>
	  <textobject>
<literallayout>
<guimenu>Archivo</guimenu>
<guimenuitem><accel>N</accel>ew                  Ctrl+N</guimenuitem>
<guimenuitem><accel>O</accel>pen...              Ctrl+O</guimenuitem>

---
<guimenuitem><accel>S</accel>ave                 Ctrl+S</guimenuitem>
<guimenuitem>Save <accel>A</accel>s...     Shift+Ctrl+S</guimenuitem>
<guimenuitem>Sa<accel>v</accel>e a Copy...               </guimenuitem>
<guimenuitem><accel>R</accel>evert                     </guimenuitem>
---
<guimenuitem>Page Set<accel>u</accel>p                 </guimenuitem>
<guimenuitem>Print Previe<accel>w</accel>  Shift+Ctrl+P</guimenuitem>
<guimenuitem><accel>P</accel>rint...             Ctrl+P</guimenuitem>
<guimenuitem><accel>S</accel>end To...              Ctrl+M</guimenuitem>
---
<guimenuitem>Proper<accel>t</accel>ies                 </guimenuitem>
---
<guimenuitem><accel>1</accel>. Recent Document                 </guimenuitem>
<guimenuitem><accel>2</accel>. Recent Document                </guimenuitem>
<guimenuitem><accel>3</accel>. Recent Document                </guimenuitem>
<guimenuitem><accel>4</accel>. Recent Document                </guimenuitem>
---
<guimenuitem><accel>C</accel>lose               Ctrl+W</guimenuitem>
<guimenuitem><accel>Q</accel>uit                 Ctrl+Q</guimenuitem>
</literallayout>
	    </textobject>
	  </mediaobject>
	</figure>

        
	<sect3>
	  <title>Creation and Opening Operations</title>
	<remark>Adam noted in the last review that we don't make any suggestions for applications  that do not edit document/files. In an OOUI, the Game
	  menu would have items such as (modulo phraeseology) Open New Game, Open Game Settings, High Scores.</remark>
	<remark>&gt;For non-game UI there would be at the very least, Open as ... and Open Settings.</remark>

	<table frame="all"> 
	  <title>Creation and Opening operation menu items </title> 

	  <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
	      	<entry><guimenuitem><accel>N</accel>ew</guimenuitem></entry>
	       <entry><keycombo><keycap>Ctrl</keycap><keycap>N</keycap></keycombo></entry>
		<entry>Creates a new document. Open a new primary window, with the title <replaceable>Nombre del documento</replaceable>, containing a blank document.  How this window is displayed, e.g. as a tab or a separate window, is up to the window manager.
			<para>If your application can create a number of different types of document, you can make the <guimenuitem><accel>N</accel>ew</guimenuitem> item a submenu, containing a menu item for each type. Label these items <guimenuitem>New <replaceable>document type</replaceable></guimenuitem>, make the first entry in the submenu the most commonly used document type, and give it the <keycombo><keycap>Ctrl</keycap><keycap>N</keycap></keycombo> shortcut.</para>
			<para>Note: A blank document will not necessarily be completely blank. For example, a document created from a template may already contain some data.</para>
		</entry>
		</row>

		<row>
		      <entry><guimenuitem><accel>O</accel>pen...</guimenuitem></entry>
	      		<entry><keycombo><keycap>Ctrl</keycap><keycap>O</keycap></keycombo></entry>
			<entry>Opens an existing document in a new window. Present the user with a standard Open File dialog  from which they can choose an existing file. If the chosen file is already open in the application, raise that window instead of opening a new one. 
		<remark>If your application provides more than two ways to open an object, place all the Open ... items in a submenu, including Recent Files. This keeps the menu less cluttered and in some ways presents a better inteface as the list of recent files is presented in the same menu, and near, the regular open commands. Users hate having to go to the bottom of the file menu to open recent files; the cause of this is that, in the workplace, it is far more common to sort out other peoples already written and saved crap than it is to have to write your own. Most of the users of office application, surveyed in both card sorts and online presentations of speculative menus, do not want or do not even notice when the New... items are absent.</remark>
		  <remark>&gt;Problem to be solved. It may be desirable to open a second read-only view of the same document. How should this be provided? Non-OOUI are particularly nasty in this regard, as in many others. A "Clone Window" command seems quite nasty.</remark>
		  <remark>&gt;As I noted in the first review, the blank window should be kept available; in an OOUI this is a more obvious a way of working.</remark>
			</entry>
		</row>

	  <!-- I think this is totally broken, I'm moving back to having recent files on the main menu itself. -Seth
		<row>
			<entry>Recent Files</entry>
			<entry>none</entry>	
			<entry>Allows the user to open a recently used file. The application should maintain a history of recently opened documents and these should be accessible via a submenu. Selecting one of these files should open that file in the same way that <guimenuitem><accel>O</accel>pen</guimenuitem> does.
			<para>Provide at least ten of the most recent files in the menu; fewer only according to user preferences or absence of recent files.</para>
			</entry>
		</row>
	  -->
		</tbody>
		</tgroup>
	</table>
	</sect3>


	<sect3>
	  <title>Saved State Operations</title>
	    <remark>This section needs a review with an eye to what can actually be done programmatically.</remark>

	<table>
	  <title>Saved State Operation menu items</title>
	  <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
		<entry><guimenuitem><accel>S</accel>ave</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo></entry>
		<entry>Saves the document with its current filename. If the document already has a filename associated with it, save the document immediately without any further interaction from the user. If there are any additional options involved in saving a file (eg. DOS or UNIX-style line endings in a text file), prompt for these first time the document is saved, but subsequently use the same values each time until the user changes them.
		<para>If the document has no current filename or is read-only, selecting this item should be the same as selecting <guimenuitem>Save As</guimenuitem>.</para>
		</entry>
		</row>

		<row>
		      <entry><guimenuitem>Save <accel>A</accel>s...</guimenuitem></entry>
	      		<entry><keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>S</keycap></keycombo></entry>
			<entry>Saves the document with a new filename. Present the user with the standard Save As dialog, and save the file with the chosen file name. </entry>

		</row>
		<row>
	      		<entry><guimenuitem>S<accel>a</accel>ve a Copy...</guimenuitem></entry>
	      		<entry>Ninguno</entry>
			<entry>Prompts the user to enter a filename, with which a copy of the document is then saved.  Do not alter either the view or the filename of the original document.  All subsequent changes are still made to the original document until the user specifies otherwise, for example by choosing the <guimenuitem>Guardar como</guimenuitem> command.
		<para> Like the <guimenuitem>Save As</guimenuitem> dialog, the <guimenuitem>Save a Copy</guimenuitem> dialog may present different ways to save the data. For example, an image may be saved in a native format or as a PNG.</para></entry>
	      </row>

	    <row>
	      	<entry><guimenuitem><accel>R</accel>evert</guimenuitem></entry>
	      <entry>Ninguno</entry>
		<entry>Reverts the document to the last saved state. Present the user with a warning that all changes will be lost, and offer the option of cancelling before reloading the file.</entry>

		</row>

		<row>
		      <entry><guimenuitem>Save <accel>V</accel>ersion...</guimenuitem></entry>
	      		<entry>Ninguno</entry>
			<entry>An alternative to the <guimenuitem>Guardar una copia</guimenuitem> command.  Only use this item in conjunction with the <guimenuitem>Restaurar versión</guimenuitem>.  <remark>Unless we can describe exactly what this ought to do, should we remove it for now?</remark>command.</entry>
	      </row>

		<row>
		      <entry><guimenuitem>R<accel>e</accel>store Version...</guimenuitem></entry>
	      		<entry>Ninguno</entry>
			<entry>Prompts the user for a version of the current document to be restored. Present the user with with a warning that all changes will be lost, and offer the option of cancelling before restoring the version. Only use this item in conjunction with the <guimenuitem>Guardar versión</guimenuitem> command.</entry>
		</row>
	
		<row>
		      <entry><guimenuitem><accel>V</accel>ersions...</guimenuitem></entry>
	      		<entry>Ninguno</entry>
			<entry>An alternative to the <guimenuitem>Guardar versión</guimenuitem> and <guimenuitem>Restaurar versión</guimenuitem> commands. Use this when more utilities, such as a diff, are available.</entry>
	      </row>

		</tbody>
		</tgroup>

	</table>
	</sect3>

	<sect3>
	  <title>Exportar operaciones</title>

	<table>
	  <title>Export Operation menu items</title>
	  <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
	      	<entry><guimenuitem>Page Set<accel>u</accel>p</guimenuitem></entry>
		<entry>Ninguno</entry>
	      	<entry>Allows the user to control print-related settings. Present the user with a dialog allowing the user to set such options as portrait or landscape format, margins, and so on. <remark>We should have a standard dialog for this.</remark></entry>
	      </row>

		<row>
		      <entry><guimenuitem>Print Previe<accel>w</accel></guimenuitem></entry>
	      		<entry><keycombo><keycap>Mayús</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 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>
	    	<entry><guimenuitem><accel>P</accel>rint...</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>P</keycap></keycombo></entry>
	        <entry>Prints the current document. Present the user with a dialog allowing them to set options like the page range to be printed, the printer to be used, and so on. The dialog must contain a button labelled <guibutton>Imprimir</guibutton> that starts printing and closes the dialog.  The <filename>libgnomeprintui</filename> library provides a standard Print dialog that you should use if possible.</entry>
	    </row>

	    <row>
	      <entry><guimenuitem>S<accel>e</accel>nd To...</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>M</keycap></keycombo></entry>
	      <entry>Provides the user a means to attach or send the current document as an email or email attachment, depending on its format.
		<para>You may provide more than one <guimenuitem>Send</guimenuitem> item depending on which options are available. If there are more than two such items, move them into a submenu. For example, if only <guimenuitem>Send by Email</guimenuitem> and <guimenuitem>Send by Fax</guimenuitem> are available, leave them on the top-level menu  If there is a third option, such as <guimenuitem>Send by FTP</guimenuitem>, place all the options in a <guimenuitem>Send</guimenuitem> submenu.</para>
	      </entry>
	    </row>
	</tbody>
	</tgroup>
	</table>
	</sect3>
	
	<sect3>
	  <title>Propiedades del archivo</title>
	<table>
	  <title>Elementos del menú de propiedades</title>
	  <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
		<entry><guimenuitem>Proper<accel>t</accel>ies</guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>Intro</keycap></keycombo></entry>
	        <entry>Opens the document's <guilabel>Propiedades</guilabel> window.  This may contain editable information, such as the document author's name, or read-only information, such as the number of words in the document, or a combination of both. The <keycombo><keycap>Alt</keycap><keycap>Intro</keycap></keycombo> shortcut should not be provided where <keycap>Intro</keycap> is most frequently used to insert a new line.</entry>
	    </row>
	  </tbody>
	</tgroup>
	</table>
	</sect3>
	

	<sect3>
	  <title>Operaciones de cierre</title>
	<table>
	  <title>Elementos del menú de operaciones de cierre</title>
	  <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
		<entry><guimenuitem><accel>C</accel>lose</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>W</keycap></keycombo></entry>
	        <entry>Closes the current document. If it has unsaved changes, present the user with a <link linkend="alerts-confirmation">alerta de confirmación</link> giving the option to save changes, discard them, or cancel the action without closing or saving the document.
		<para>If the window you are closing is the last open document in the application, the correct action depends on your application type:</para>
		<itemizedlist>
			<listitem><para>Single document interface: close the application</para></listitem>
			<listitem><para>Controlled single document interface: leave only the control window open</para></listitem>
			<listitem><para>Multiple document interface: close the current document and create a new blank document</para></listitem>
		</itemizedlist>		
		  <remark>As mentioned on the usability list, Control+W is an Emacs shortcut for Cut. This has already proven deleterious for some users so we should consider dropping the shortcut.  But see also <ulink url="http://bugzilla.gnome.org/show_bug.cgi?id=76761">http://bugzilla.gnome.org/show_bug.cgi?id=76761</ulink></remark>
	      </entry>
	    </row>
	    
	    <row>
	      <entry><guimenuitem><accel>Q</accel>uit</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>Q</keycap></keycombo></entry>
	      <entry><para>Closes the application. If there are unsaved changes in any open documents, present the user with a <link linkend="alerts-confirmation">confirmation alert</link> for each affected document, giving the option to save the changes, discard them, or cancel. If there are no unsaved changes, close the application immediately without presenting any further messages or dialogs.</para>
		<!-- This para in response to bug #73618--><para>In particular, non-document based applications, for example a game or a calculator, should save their state and exit immediately.  This state should be restored the next time the application is started.</para> 
		  <remark>Kathy had suggested not providing a shortcut key to Quit. I can find no discussion of this. (And I think it should go away.)</remark>
	      </entry>
	    </row>
	  </tbody>
	</tgroup>
	</table>
	</sect3>
	
      </sect2>
      <sect2 id="menu-standard-edit">
	<title>Editar</title>

	<para>The <guimenu>Edit</guimenu> menu contains items relating to editing both the document (clipboard handling, search and replace, and inserting special objects) and the user's preferences.  Preferences are edited here rather than on a <guimenu>Settings</guimenu> menu, because:</para>

	<itemizedlist>
		<listitem><para>most applications' preferences windows are accessed via a single menu item, and single-item menus offer poor usability</para></listitem>
		<listitem><para>most applications already contain a suitable <guimenu>Edit</guimenu> menu.</para></listitem>
	</itemizedlist>

	<remark>NO TRADUCIR</remark>

	<figure id="generic-edit-menu">
	  <title>Un menú «Editar» genérico</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-edit.png" width="226" depth="417" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-edit.eps" format="EPS"/></imageobject>
	    <textobject>
<literallayout class="monospaced">
<guimenu><accel>E</accel>dit</guimenu>
<guimenuitem><accel>U</accel>ndo                 Ctrl+Z</guimenuitem>
<guimenuitem><accel>R</accel>edo           Shift+Ctrl+Z</guimenuitem>
-
<guimenuitem>Cu<accel>t</accel>                  Ctrl+X</guimenuitem>
<guimenuitem><accel>C</accel>opy                 Ctrl+C</guimenuitem>
<guimenuitem><accel>P</accel>aste                Ctrl+V</guimenuitem>
<guimenuitem>Paste <accel>S</accel>pecial...                Shift+Ctrl+V</guimenuitem>
<guimenuitem><accel>D</accel>elete               Del</guimenuitem>
<guimenuitem><accel>S</accel>elect All           Ctrl+A</guimenuitem>
<guimenuitem>Du<accel>p</accel>licate           Ctrl+U</guimenuitem>
<guimenuitem>Dese<accel>l</accel>ect All   Shift+Ctrl+A</guimenuitem>
-
<guimenuitem><accel>F</accel>ind...              Ctrl+F</guimenuitem>
<guimenuitem>Find Ne<accel>x</accel>t            Ctrl+G</guimenuitem>
<guimenuitem>Find Pre<accel>v</accel>ious  Shift+Ctrl+G</guimenuitem>
<guimenuitem>R<accel>e</accel>place...              Ctrl+R</guimenuitem>
-
<guimenuitem><accel>I</accel>nsert...              </guimenuitem>
-
<guimenuitem>Pr<accel>e</accel>ferences</guimenuitem>
</literallayout>
	    </textobject>
	  </mediaobject>
	</figure>


	<sect3>
	  <title>Histórico de modificaciones</title>
	  <para>Document-based applications should maintain a history of modifications to a document and the state of the document between each action. The <guimenuitem>Undo</guimenuitem> and <guimenuitem>Redo</guimenuitem> commands move backwards and forwards through this history.</para>

	<remark>We'd like to see the action name included on the Undo/Redo menu items, but this is currently not easy to do in gtk.</remark>

	<table frame="all"> 
	  <title>Elementos de menú del histórico de modificaciones</title> 

	  <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
	  	<entry><guimenuitem><accel>U</accel>ndo <replaceable>acción</replaceable></guimenuitem></entry>
	       <entry><keycombo><keycap>Ctrl</keycap><keycap>Z</keycap></keycombo></entry>
		<entry>Undoes the effect of the previous action in the undo history list. Revert the document to its state before the previous action was performed. If your application supports undo, and the user undoes all changes since it was last saved, treat the document as unmodified.
		<para>Note: provide a separate <guimenuitem>Undo</guimenuitem> and <guimenuitem>Redo</guimenuitem> menu item even if your application only supports one level of undo.</para></entry>
	      </row>

		<row>
	      	  <entry><guimenuitem><accel>R</accel>edo <replaceable>acción</replaceable></guimenuitem></entry>
			<entry><keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>Z</keycap></keycombo></entry>
	      		<entry>Performs the next action in the undo history list, after the user has moved backwards through the list with the <guimenuitem>Deshacer</guimenuitem> command.  Move the user one step forwards again, restoring the document to the state it was in after that action was originally performed.
			<para>Note: provide a separate <guimenuitem>Undo</guimenuitem> and <guimenuitem>Redo</guimenuitem> menu item even if your application only supports one level of undo.</para></entry>
	      </row>
		</tbody>
		</tgroup>
	</table>
	</sect3>

	<sect3>
	  <title>Manipular datos seleccionados</title>

	<table frame="all"> 
	  <title>Selected Data Manipulation menu items </title> 

	  <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
		<entry><guimenuitem>Cu<accel>t</accel></guimenuitem></entry>
	      	<entry><keycombo><keycap>Ctrl</keycap><keycap>X</keycap></keycombo></entry>
		<entry>Removes the selected content and places it onto the clipboard. Visually, remove the content from the document in the same manner as <guimenuitem><accel>D</accel>elete</guimenuitem>.</entry>
	      </row>

		<row>
	    		<entry><guimenuitem><accel>C</accel>opy</guimenuitem></entry>
	      		<entry><keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo></entry>
			<entry>Copia el contenido seleccionado al portapapeles.</entry>
	      </row>
	    
	    <row>
		<entry><guimenuitem><accel>P</accel>aste</guimenuitem></entry>
	      <entry><keycombo><keycap>Ctrl</keycap><keycap>V</keycap></keycombo></entry>
		<entry>Inserts the contents of the clipboard into the document.  If there is no current selection, use the caret as the insertion point.  If there is a current selection, replace it with the clipboard contents.</entry>
	    </row>
	    
	    <row>
		<entry><guimenuitem>Paste <accel>S</accel>pecial...</guimenuitem></entry>
	      <entry><keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>V</keycap></keycombo></entry>
		<entry>Inserts a non-default representation of the clipboard contents into the document.  Open a dialog presenting a list of the available formats from which the user can select.  For example, if the clipboard contains a PNG file copied from a file manager, the image may be embedded in the document, or a link to the file inserted so that changes to the image on disk are always reflected in the document.</entry>
	    </row>

	    <row>
		<entry><guimenuitem>Du<accel>p</accel>licate</guimenuitem></entry>
	      <entry><keycombo><keycap>Ctrl</keycap><keycap>U</keycap></keycombo></entry>
		<entry>Creates a duplicate copy of the selected object.  Do not prompt for a name for the duplicate object, but give it a sensible default (for example, <filename>Copia de ListaCompra.abw</filename>) and allow the user to change it later.  Place the duplicate copy as near the original as possible without overlapping it, even if this means breaking the current sort order within the container, so the user sees it immediately.</entry>
	    </row>

		<row>
			<entry><guimenuitem><accel>D</accel>elete</guimenuitem></entry>
		      <entry><keycap>Eliminar</keycap></entry>
			<entry>Removes the selected content without placing it on the clipboard.
		      <remark>Should Delete be provided on a menu? The command is as obvious as using the arrow keys to move about.</remark></entry>
	      </row>

		<row>
		      <entry><guimenuitem>Select <accel>A</accel>ll</guimenuitem></entry>
	      		<entry><keycombo><keycap>Ctrl</keycap><keycap>A</keycap></keycombo></entry>
			<entry>Selecciona todo el contenido del documento actual.</entry>
	    	</row>
	    
		<row>
		  <entry><guimenuitem><accel>D</accel>eselect All</guimenuitem></entry>
	      	  <entry><keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>A</keycap></keycombo></entry>
		<entry>Deselects all content in the current document. Only provide this item in situations when no other method of undoing selection is possible or apparent to the user.  For example, in complex graphics applications where selection and deselection is not usually possible simply by using the cursor keys.
		<para>Note: Do not provide <guimenuitem>Deselect All</guimenuitem> in text entry fields, as <keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keysym>hex digit</keysym></keycombo> is used to enter unicode characters so its shortcut will not work.</para></entry>
	      </row>

	    </tbody>
	  </tgroup>
	 </table>
	</sect3>

	<sect3>
	  <title>Buscar y reemplazar</title>

	<table frame="all"> 
	  <title>Search and Replace menu items </title> 

	  <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
	      <entry>Buscar…</entry>
	      <entry><keycombo><keycap>Ctrl</keycap><keycap>F</keycap></keycombo></entry>
		<entry>Opens a window or dialog allowing the user to search for specific content in the current document.  Highlight each match in-place.
		<para>If the command allows the user to search for content in places other than the current document, for example other open documents, other documents on disk, or a remote network location, label this item <guimenuitem>Search</guimenuitem> instead of <guimenuitem>Find</guimenuitem>.</para></entry>
	      </row>

	    <row>
	      <entry><guimenuitem>Find Ne<accel>x</accel>t</guimenuitem></entry>
	      <entry><keycombo><keycap>Ctrl</keycap><keycap>G</keycap></keycombo></entry>
	      <entry>Selects the next instance of the last Find term in the current document.  <remark>What to do if there is no next instance?  Disable the menu item, which could be confusing, or pop up an annoying alert saying 'no matches found'?</remark></entry>
	      </row>

		<row>
		      <entry><guimenuitem>Find Pre<accel>v</accel>ious</guimenuitem></entry>
	      		<entry><keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>G</keycap></keycombo></entry>
			<entry>Selects the previous instance of the last Find term in the current document.</entry>
	      </row>

		<row>
		      <entry><guimenuitem><accel>R</accel>eplace...</guimenuitem></entry>
	      		<entry><keycombo><keycap>Ctrl</keycap><keycap>H</keycap></keycombo></entry>
			<entry>Opens a window or dialog allowing the user to search for specific content in the current document, and replace each occurrence with new content. 	    
		 	<remark>Replace is not always descriptive of what the user may do with the utility window. Formatting a section is also a possibility. Ideally, these would all be merged into a simple utility window</remark>
		</entry>
	      </row>
		</tbody>
		</tgroup>
	</table>
	</sect3>


	<sect3>
	  <title>Insertar objetos especiales</title>
	  <para>Where applicable, provide items on the <guimenu>Edit</guimenu> menu that insert special objects such as images, links, GUI controls or the current date and time. </para>

	<para>If you have up to three types of object that can be inserted, add them as individual items to this menu, for example <guimenuitem>Insert Image</guimenuitem>, or <guimenuitem>Insert External Link</guimenuitem>.  If you have between three and six types, place them on an <menuchoice><guimenu>Edit</guimenu><guimenuitem>Insert</guimenuitem></menuchoice> submenu.  If you have more than six, add a separate <link linkend="menu-standard-insert"><guimenu>Insert</guimenu> menu</link> to the menubar.</para>

	</sect3>


	<sect3>
	  <title>Preferencias del usuario</title>

	<table>
	<title>Elementos del menú de preferencias del usuario</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
		      <entry><guimenuitem>Pr<accel>e</accel>ferences</guimenuitem></entry>
	      		<entry>Ninguno</entry>
			<entry>Opens a <link linkend="preference-windows">ventana de preferencias</link> allowing the user to change preferences for the whole application.  Changes will apply to all running and subsequent instances of the application.</entry>
		</row>
		</tbody>
		</tgroup>
	</table>
	</sect3>

      </sect2>
      <sect2 id="menu-standard-view">
	<title>Ver</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 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>Un menú «Ver» genérico</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-view.png" width="166" depth="300" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-view.eps" format="EPS"/></imageobject>
	    <textobject>
	      <literallayout class="monospaced">
<guimenu><accel>V</accel>iew</guimenu>
<guimenuitem><accel>T</accel>oolbar</guimenuitem>
<guimenuitem><accel>S</accel>tatusbar</guimenuitem>
---
<guimenuitem><accel>I</accel>cons</guimenuitem>
<guimenuitem><accel>L</accel>ista</guimenuitem>
<guimenuitem><accel>D</accel>etails</guimenuitem>
---
<guimenuitem><accel>S</accel>ort By...</guimenuitem>
<guimenuitem><accel>F</accel>ilter...</guimenuitem>
---
<guimenuitem><accel>Z</accel>oom in       Ctrl++</guimenuitem>
<guimenuitem>Zoom <accel>O</accel>ut  Ctrl+-</guimenuitem>
<guimenuitem><accel>N</accel>ormal Size   Ctrl+=</guimenuitem>
<guimenuitem><accel>B</accel>est Fit    </guimenuitem>
---
<guimenuitem><accel>R</accel>efresh     Ctrl+R</guimenuitem>

	      </literallayout>
	    </textobject>
	  </mediaobject>
	</figure>


	<sect3>
	<title>Barra de herramientas y barra de estado</title>
	<table>
	<title>Toolbar and Statusbar menu items</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
	      <row>
	 	      <entry><guimenuitem><accel>T</accel>oolbar</guimenuitem></entry>
	      		<entry>Ninguno</entry>
			<entry>Shows or hides the application's toolbar.  This is a <link linkend="menu-item-type-check">check box menu item</link>. Include this item in every application that has a single toolbar.  See <xref linkend="toolbars-controlling-display"/> for information on how to deal with multiple toolbars.</entry>
		</row>

		<!-- Suggest removing this for now, see bug #????
		<row>
			<entry><guimenuitem><accel>S</accel>tatusbar</guimenuitem></entry>
			<entry>None</entry>
			<entry>Shows or hides the application's statusbar.  This is a <link linkend="menu-item-type-check">check box menu item</link>.  Include this item in every application that has a statusbar.</entry>
		</row>
		-->

		</tbody>
		</tgroup>
	</table>
	</sect3>

	<sect3>
	<title>Content Presentation</title>
	<table>
	<title>Content Presentation menu items</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">

		<row>
			<entry><guimenuitem><accel>I</accel>cons</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Shows the contents of the selected container as rows and columns of large icons, each with its name underneath.  This is a <link linkend="menu-item-type-radio">radio button menu item</link>.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>L</accel>ista</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Shows the contents of the selected container as a list of small icons, possibly in multiple columns, each with its name on its right-hand side.  This is a <link linkend="menu-item-type-radio">radio button menu item</link>.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>D</accel>etails</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Shows the contents of the selected container as single column of small icons, each with its name on its right-hand side.  Additional columns give extra information about the object each icon represents, for example the size and modification date of files in a file manager.  This is a <link linkend="menu-item-type-radio">radio button menu item</link>.
			<para>If your application has no need for both <guimenu>List</guimenu> and <guimenu>Details</guimenu> modes, use the <guimenu>List</guimenu> item for whichever of the two modes you support.</para></entry>
		</row>

		<row>
			<entry><guimenuitem>S<accel>o</accel>rt By...</guimenuitem></entry>
			<entry>Ninguno</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>
			<entry><guimenuitem><accel>F</accel>ilter...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Hides objects that are not of interest to the user.  Open a dialog allowing the user to choose from a list of types of object they want to display, or to enter their own criteria (for example, a regular expression matched against a particular property of the objects).</entry>
		</row>


		<row>
			<entry><guimenuitem><accel>Z</accel>oom In</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>+</keycap></keycombo></entry>
			<entry>Zooms into the document.  Make the center of the new view the same as the center of the previous view. <remark>Should probably encourage apps to support Ctrl+= as well.</remark></entry>
		</row>

		<row>
			<entry><guimenuitem>Zoom <accel>O</accel>ut</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>-</keycap></keycombo></entry>
			<entry>Zooms out of the document.  Make the center of the new view the same as the center of the previous view.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>N</accel>ormal Size</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>0</keycap></keycombo></entry>
			<entry>Resets the zoom level back to the default value, normally 100%.  Make the center of the new view the same as the center of the previous view.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>B</accel>est Fit</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Makes the document fill the window.  Show the document, or the current page of the document, at as high a zoom level as will fit in the window whilst allowing the whole document or page to be visible without scrolling.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>R</accel>efresh</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>R</keycap></keycombo></entry>
			<entry>Redraws the current view of the document from local storage.  For example, in a web browser application, this would redraw the page from the browser page cache.</entry>
		</row>
		<row>
			<entry><guimenuitem><accel>R</accel>eload</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>R</keycap></keycombo></entry>

			<entry>Redraws the current view of the document, checking the data source for changes first.  For example, checks the web server for updates to the page before redrawing it.
			<para>If your application requires both <guimenuitem>Reload</guimenuitem> and <guimenuitem>Refresh</guimenuitem>, use <keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>R</keycap></keycombo> as the shortcut for <guimenuitem>Reload</guimenuitem>.</para></entry>
		</row>

		</tbody>
		</tgroup>
	</table>
	</sect3>
      </sect2>

      <sect2 id="menu-standard-insert">
	<title>Insertar</title>
	<para>The <guimenuitem>Insert</guimenuitem> menu lists the type of special objects that can be inserted into the document at the current caret position, for example images, links, page breaks or GUI objects.  Only provide this menu if you have more than about six types of object that can be inserted, otherwise place individual items for each type on the <link linkend="menu-standard-edit"><guimenu>Edit</guimenu> menu</link>.</para>

	<figure id="generic-insert-menu">
	  <title>Un menú «Insertar» genérico</title>
	  <mediaobject>
	  <imageobject><imagedata fileref="images/menus-insert.png" width="118" depth="245" format="PNG"/></imageobject>
	  <imageobject><imagedata fileref="images/menus-insert.eps" format="EPS"/></imageobject>
	    <textobject>
	      <literallayout class="monospaced">
<guimenu><accel>P</accel>age Break</guimenu>
<guimenuitem><accel>D</accel>ate and Time...</guimenuitem>
<guimenuitem><accel>S</accel>ymbol...</guimenuitem>
---
<guimenuitem><accel>S</accel>heet...</guimenuitem>
<guimenuitem><accel>R</accel>ows...</guimenuitem>
<guimenuitem><accel>C</accel>olumns...</guimenuitem>
---
<guimenuitem><accel>I</accel>mage...</guimenuitem>
<guimenuitem><accel>G</accel>raph...</guimenuitem>
---
<guimenuitem><accel>F</accel>rom File...</guimenuitem>
<guimenuitem>E<accel>x</accel>ternal Link...</guimenuitem>

	      </literallayout>
	    </textobject>
	  </mediaobject>
	</figure>
	
	<para>The types of object will vary between applications, but the table below shows some common types that may be applicable.</para>

	<table>
	<title>Insertar elementos de menú</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">

		<row>
			<entry><guimenuitem><accel>P</accel>age Break</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Inserts a page break at the caret position.  Show the page break visually, for example as a dotted line across the page, unless the user has specifically requested not to see them.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>D</accel>ate and Time...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Inserts the current date and/or time at the caret position.  Open a dialog giving a choice of date and time formats.  If applicable, also offer the choice to insert either as plain text, so the specified date and time will always appear in the document, or as a special field that will updated every time the document is opened, refreshed or printed.</entry>
			</row>

		<row>
			<entry><guimenuitem>Sy<accel>m</accel>bol...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Inserts a special symbol, such as a mathematical symbol or foreign character, at the caret position.  Open a dialog showing all the available symbols as a table, from which the user can choose.  The user must be able to add multiple symbols to the document at one time without having to close and re-open the dialog.</entry>
			</row>

		<row>
			<entry><guimenuitem><accel>S</accel>heet...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Adds a new sheet to the current workbook.  Do not prompt for a name, but choose a sensible default (such as <guilabel>Sheet-2</guilabel>) and allow the user to change it later.</entry>
			</row>

		<row>
			<entry><guimenuitem><accel>R</accel>ows...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Adds new rows to a table in which one or more rows or cells are currently selected.  Open a dialog asking whether to insert rows above or below the current selection, and for any other required information.  Copy the row format from the last or first row of the current selection respectively, unless the user specifies otherwise.</entry>
			</row>

		<row>
			<entry><guimenuitem><accel>C</accel>olumns...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Adds new columns to a table in which one or more columns or cells are currently selected.  Open a dialog asking whether to insert columns to the left or right of the current selection, and for any other required information.  Copy the column format from the right- or left-most column of the current selection respectively, unless the user specifies otherwise.</entry>
			</row>

		<row>
			<entry><guimenuitem><accel>I</accel>mage...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Inserts an image into the document from a file.  Present a standard Open File dialog filtered on acceptable file types, from which the user can choose an image file to insert.</entry>
			</row>

		<row>
			<entry><guimenuitem><accel>G</accel>raph...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Inserts a graph into the document.  Open a dialog or assistant that allows the user to build (or open from a file) a graph of their choice, using the current selection as an indication of which values, axis labels and data labels to use.</entry>
			</row>

		<row>
			<entry><guimenuitem><accel>F</accel>rom FIle...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Inserts an object from any acceptable file type, for example plain text, formatted text, or an image.  Present a standard Open File dialog filtered on acceptable file types, from which the user can choose a file to insert.</entry>
			</row>

		<row>
			<entry><guimenuitem>E<accel>x</accel>ternal Link...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Inserts a link to an object stored in a different file, or on a remote system.  The object is not embedded in or saved with the document, only a link to it.  Open a dialog in which the user can type or choose the name of the object, for example a filename or a webpage URL.  Show the link in the document in as informative way as possible.  For example, show a link to an image as a thumbnail of that image, unless the user specifies otherwise.</entry>
			</row>

		</tbody>
		</tgroup>
	</table>


      </sect2>


      <sect2 id="menu-standard-format">
	<title>Formato</title>

		<para>A <guimenu>Format</guimenu> menu contains commands to change the visual appearance of the document.  For example, changing the font, color, or line spacing of a text selection.</para>
		<para>The difference between these commands and those on the <link linkend="menu-standard-view"><guimenuitem>View</guimenuitem> menu</link> is that changes made with Format commands are persistent and saved as part of the document, for example as HTML or RTF tags.</para>

	<figure id="generic-format-menu">
	  <title>Un menú «Formato» genérico</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-format.png" width="163" depth="265" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-format.eps" format="EPS"/></imageobject>
	    <textobject>
	      <literallayout class="monospaced">
<guimenu><accel>S</accel>tyle...</guimenu>
---
<guimenuitem><accel>F</accel>ont...</guimenuitem>
<guimenuitem><accel>P</accel>aragraph...</guimenuitem>
---
<guimenuitem><accel>B</accel>old	Ctrl+B</guimenuitem>
<guimenuitem><accel>I</accel>talic	Ctrl+I</guimenuitem>
<guimenuitem><accel>U</accel>nderline	Ctrl+U</guimenuitem>
---
<guimenuitem><accel>C</accel>ells...</guimenuitem>
<guimenuitem><accel>L</accel>ist...</guimenuitem>
---
<guimenuitem>L<accel>ayer</accel>...</guimenuitem>
<guimenuitem>P<accel>a</accel>ge...</guimenuitem>

	      </literallayout>
	    </textobject>
	  </mediaobject>
	</figure>


	<para>Items found on the <guimenu>Format</guimenu> will be very application-specific, but some common items are listed in the table below.</para>

	<table>
	<title>Format menu items</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">

		<row>
			<entry><guimenuitem><accel>S</accel>tyle...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Sets the style attributes of the selected text or objects either individually or to a named, predefined style.  Open a dialog allowing the user to set attributes such as bold, italic, size and spacing individually, and to create their own named styles where applicable.</entry>

		</row>

		<row>
			<entry><guimenuitem><accel>F</accel>ont...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Sets the font properties of the selected text or objects.  Open a dialog allowing the user to choose font, size, style, color, or whatever other attributes are applicable.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>P</accel>aragraph...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Sets the properties of the selected paragraph.  Open a dialog allowing the user to choose style, line spacing, tabulation, or whatever other attributes are applicable.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>B</accel>old</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>B</keycap></keycombo></entry>
			<entry>Toggles the boldness of the current text selection on or off.  If some of the selection is currently bold and some is not, this command should bolden the selected text.</entry>

		</row>

		<row>
			<entry><guimenuitem><accel>I</accel>talic</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>I</keycap></keycombo></entry>
			<entry>Toggles the italicisation of the current text selection on or off.  If some of the selection is currently italicised and some is not, this command should italicise the selected text.</entry>

		</row>

		<row>
			<entry><guimenuitem><accel>U</accel>nderline</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>U</keycap></keycombo></entry>
			<entry>Toggles underlining of the current text selection.  If some of the selection is currently underlined and some is not, this command should underline the selected text.</entry>

		</row>

		<row>
			<entry><guimenuitem><accel>C</accel>ells...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Sets the properties of the selected table cells.  Open a dialog allowing the user to choose alignment, borders, shading, text style, number format, or whatever other attributes are applicable.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>L</accel>ist...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Sets the properties of the selected list, or turns the selected paragraphs into a list if they are not already formatted as such.  Open a dialog allowing the user to choose number or bullet style, spacing, tabulation, or whatever other attributes are applicable.</entry>
		</row>


		<row>
			<entry><guimenuitem>Laye<accel>r</accel>...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Sets the properties of all or selected layers of a multi-layered document.  Open a dialog allowing the user to choose name, size, visibility, opacity, z-ordering, or whatever other attributes are applicable.</entry>
		</row>


		<row>
			<entry><guimenuitem>P<accel>a</accel>ge...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Sets the properties of all or selected pages of the document.  Open a dialog allowing the user to choose paper size, orientation, columns, margins, or whatever other attributes are applicable.</entry>
		</row>

		</tbody>
		</tgroup>
	</table>

      </sect2>


      <sect2 id="menu-standard-bookmarks">
	<title>Marcadores</title>

	<para>Provide a <guimenu>Bookmarks</guimenu> menu in any application that allows the user to browse files and folders, help documents, web pages or any other large information space.</para>
	<note><title>Iconos</title><para>Show icons for bookmark entries on the Bookmarks menu that indicate the type of the bookmark, even if the user has globally turned off icons for other menu items on the desktop.</para></note>

	<figure id="generic-bookmarks-menu">
	  <title>Un menú «Marcadores» genérico</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-bookmarks.png" width="190" depth="49" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-bookmarks.eps" format="EPS"/></imageobject>
	    <textobject>
	      <literallayout class="monospaced">
<guimenu><accel>B</accel>ookmarks</guimenu>
<guimenuitem><accel>A</accel>dd Bookmark   </guimenuitem><keycombo><keycap>Ctrl</keycap><keycap>D</keycap></keycombo>
<guimenuitem><accel>E</accel>dit Bookmarks </guimenuitem><keycombo><keycap>Ctrl</keycap><keycap>B</keycap></keycombo>
	      </literallayout>
	    </textobject>
	  </mediaobject>
	</figure>

	<table>
	<title>Bookmark menu items</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">

		<row>
			<entry><guimenuitem><accel>A</accel>dd Bookmark</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>D</keycap></keycombo></entry>
			<entry>Adds a bookmark for the current document to the default bookmark list.  Do not pop up a dialog asking for a title or location for the bookmark, instead choose sensible defaults (such as the document's title or filename as the bookmark name) and allow the user to change them later using the <guimenuitem>Editar marcadores</guimenuitem> feature.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>E</accel>dit Bookmarks</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>B</keycap></keycombo></entry>
			<entry>Allows the user to edit the application's bookmark list.  Open a window in which the user can arrange bookmarks into a hierarchy, move, copy, and delete bookmarks, and change their properties.</entry>
		</row>
		<row>
			<entry><emphasis>Lista de marcadores</emphasis></entry>
			<entry>Ninguno</entry>
			<entry>The user's current list of bookmarks for the application.</entry>
		</row>
		</tbody>
		</tgroup>
	</table>

      </sect2>
      <sect2 id="menu-standard-go">

	<title>Ir</title>

	<para>A <guimenu>Go</guimenu> menu provides commands for quickly navigating around a document or collection of documents, or an information space such as a directory structure or the web.</para>

	<para>The contents of the menu will vary depending on the type of application.  Different standard menus are presented here for browser-based and document-based applications , but your application may require a combination of both.</para>

	<figure id="generic-browser-go-menu">
	  <title>Un menú «Ir» genérico para un examinador</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-go-browser.png" width="178" depth="127" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-go-browser.eps" format="EPS"/></imageobject>
	    <textobject>
<literallayout class="monospaced">
<guimenu><accel>G</accel>o</guimenu>
<guimenuitem><accel>B</accel>ack       Alt+Left</guimenuitem>
<guimenuitem><accel>F</accel>orward	Alt+Right    </guimenuitem>
<guimenuitem><accel>U</accel>p		Alt+Up         </guimenuitem>
---
<guimenuitem><accel>H</accel>ome	Alt+Home       </guimenuitem>
<guimenuitem><accel>L</accel>ocation...  Ctrl+L</guimenuitem>
</literallayout>
	    </textobject>
	  </mediaobject>
	</figure>


	<table>
	<title>Go menu items for a browser application</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">

		<row>
			<entry><guimenuitem><accel>B</accel>ack</guimenuitem></entry>
			<entry><keycombo><keycap>Alt</keycap><keycap>Izquierda</keycap></keycombo></entry>
			<entry>Navega al documento anterior en el histórico.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>F</accel>orward</guimenuitem></entry>
			<entry><keycombo><keycap>Alt</keycap><keycap>Derecha</keycap></keycombo></entry>
			<entry>Navega al siguiente documento en el histórico.</entry>		
		</row>

		<row>
			<entry><guimenuitem><accel>U</accel>p</guimenuitem></entry>
			<entry><keycombo><keycap>Alt</keycap><keycap>Arriba</keycap></keycombo></entry>
			<entry>Navigates to the current document's (or folder's) parent document (or folder).  For a document browser, such as an online help viewer, this usually means navigating to the enclosing sub-section, section, chapter or contents page.</entry>		
		</row>
	
		<row>
			<entry><guimenuitem><accel>H</accel>ome</guimenuitem></entry>
			<entry><keycombo><keycap>Alt</keycap><keycap>Inicio</keycap></keycombo></entry>
			<entry>Navega a la página inicial definida por el usuario o la aplicación.</entry>
		</row>


		<row>
			<entry><guimenuitem><accel>L</accel>ocation...</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>L</keycap></keycombo></entry>
			<entry>Navigates to a user-specified URI.  Open a dialog into which the user can type a suitable URI, or select one from a list where applicable (for example, a file selection dialog for applications that can handle file:// URIs).</entry>		
		</row>

			</tbody>
		</tgroup>
	</table>

	<figure id="generic-document-go-menu">
	  <title>Un menú «Ir» genérico para aplicaciones basadas en documentos</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-go-document.png" width="206" depth="127" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-go-document.eps" width="210" depth="121" format="EPS"/></imageobject>
	    <textobject>
<literallayout class="monospaced">
<guimenu><accel>G</accel>o</guimenu>
<guimenuitem><accel>P</accel>revious Page 	PgUp </guimenuitem>
<guimenuitem><accel>N</accel>ext Page      		PgDn</guimenuitem>
<guimenuitem><accel>G</accel>o to Page...</guimenuitem>
-
<guimenuitem><accel>F</accel>irst Page    		Ctrl+Home </guimenuitem>
<guimenuitem><accel>L</accel>ast Page		Ctrl+End</guimenuitem>
</literallayout>
	    </textobject>
	  </mediaobject>
	</figure>

	<table>
	<title>Go menu items for a document-based application</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">

		<row>
			<entry><guimenuitem><accel>P</accel>revious Page</guimenuitem></entry>
			<entry><keycap>RePág</keycap></entry>
			<entry>Navega a la página anterior en el documento.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>N</accel>ext Page</guimenuitem></entry>
			<entry><keycap>AvPág</keycap></entry>
			<entry>Navega a la siguiente página en el documento.</entry>		
		</row>

		<row>
			<entry><guimenuitem><accel>G</accel>o to Page...</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Navigates to a user-specified page number.  Open a dialog into which the user can type a page number.
			<para>Text-based applications may also include a <guimenuitem>Go  to Line...</guimenuitem> menu item, which allows the user to jump to a specified line number.</para></entry>		
		</row>
	
		<row>
			<entry><guimenuitem><accel>F</accel>irst Page</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>Inicio</keycap></keycombo></entry>
			<entry>Navega hasta la primera página del documento.</entry>
		</row>


		<row>
			<entry><guimenuitem><accel>L</accel>ast Page</guimenuitem></entry>
			<entry><keycombo><keycap>Ctrl</keycap><keycap>Fin</keycap></keycombo></entry>
			<entry>Navega hasta la última página del documento.</entry>		
		</row>

			</tbody>
		</tgroup>
	</table>

      </sect2>

<!-- CFB Commenting out until we have anything to go on it :/
      <sect2 id="menu-standard-tools">
	<title>Tools</title>
	<figure id="generic-tools-menu">
	  <title>A generic Tools menu</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/generic-tools-menu.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/generic-tools-menu.eps" format="EPS"/></imageobject>
	    <textobject>
	      <literallayout class="monospaced">
<guimenu><accel>T</accel>ools</guimenu>
	      </literallayout>
	    </textobject>
	  </mediaobject>
	</figure>
	<para>FIXME</para>
      </sect2>

-->

      <sect2 id="application-windows-menu">
	<title>Ventanas</title>
		<para>The Windows menu contains commands that apply to all of the application's open windows.  Only use a Windows menu in <link linkend="mdi">multiple document interface</link> (MDI) applications.</para>

      <note><title>Aplicaciones MDI</title><para>The use of MDI is discouraged, as they have a number of inherent usability problems.</para></note>
	
		<para>You may also label this menu <guimenu><accel>D</accel>ocuments</guimenu>, <guimenu><accel>B</accel>uffers</guimenu>, or similar according to the type of document handled by your application.</para>
	
	<para>The last items on this menu are a numbered list of the application's primary windows, for example <guimenuitem><accel>1</accel>shoppinglist.abw</guimenuitem>.  Selecting one of these items raises the corresponding window.</para>

	<figure id="generic-windows-menu">
	  <title>Un menú «Ventanas» genérico</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-windows.png" width="151" depth="172" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-windows.eps" format="EPS"/></imageobject>
	    <textobject>
	      <literallayout class="monospaced">
<guimenu><accel>W</accel>indows</guimenu>
<guimenuitem><accel>S</accel>ave All</guimenuitem>
<guimenuitem><accel>C</accel>lose All</guimenuitem>
	      </literallayout>
	    </textobject>
	  </mediaobject>
	</figure>
	

<table>
	<title>Windows menu items</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">
		<row>
			<entry><guimenuitem><accel>S</accel>ave All</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Saves all open documents.  If any documents have no current filename, prompt for a filename for each one in turn using the standard Save dialog.</entry>		
		</row>

		<row>
			<entry><guimenuitem><accel>C</accel>lose All</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Closes all open documents.  If there are any unsaved changes in any documents, post a <link linkend="alerts-confirmation">alerta de confirmación</link> for each one in turn.</entry>
		</row>
		<row>
			<entry><guimenuitem><accel>1</accel>. <replaceable>first open window title</replaceable></guimenuitem>
			<para><guimenuitem><accel>2</accel>. <replaceable>second open window title</replaceable></guimenuitem></para>
			<para>etc.</para></entry>
			<entry>Ninguno</entry>
			<entry>Raises the corresponding window to the top of the window stack.</entry>
		</row>
			</tbody>
		</tgroup>
	</table>

	
      </sect2>
      <sect2 id="menu-standard-help">
	<title>Ayuda</title>
	<para>The <guimenu>Help</guimenu> menu provides access to all online documentation for your application.  This includes both the user guide, and the <guimenuitem>About</guimenuitem> window which includes a brief description of your application's functionality.</para>

	<figure id="generic-help-menu">
	  <title>Un menú de ayuda genérico</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/menus-help.png" width="118" depth="45" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/menus-help.eps" format="EPS"/></imageobject>
	    <textobject>
	      <literallayout class="monospaced">
<guimenu><accel>H</accel>elp</guimenu>
<!--<guimenuitem><accel>S</accel>earch</guimenuitem>-->
<guimenuitem><accel>C</accel>ontents      F1</guimenuitem>
<guimenuitem><accel>A</accel>bout</guimenuitem>
	      </literallayout>
	    </textobject>
	  </mediaobject>
	</figure>

	<table>
	<title>Elementos del menú «Ayuda»</title>
	 <tgroup cols="3" align="left">
	    <thead> 
	      <row> 
		<entry>Etiqueta</entry> 
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
		</row>
	      </thead>
	    <tbody valign="top">

		<row>
			<entry><guimenuitem><accel>C</accel>ontents</guimenuitem></entry>
			<entry><keycap>F1</keycap></entry>
			<entry>Opens the default help browser on the contents page for the application.</entry>
		</row>

		<row>
			<entry><guimenuitem><accel>A</accel>bout</guimenuitem></entry>
			<entry>Ninguno</entry>
			<entry>Opens the About dialog for the application.  Use the standard dialog provided by the GNOME libraries, which contains the name and version number of the application, a short description of the application's functionality, author contact details, copyright message and a pointer to the licence under which the application is made available.</entry>		
		</row>

			</tbody>
		</tgroup>
	</table>

	<remark>We originally wanted a Search item on here too, but it's not technically possible to implement it right now.</remark>

      </sect2>
    </sect1>
  </chapter>



<chapter id="toolbars">
  <title>Barras de herramientas</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 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>
  -->
    
  <figure id="mail-toolbar-example">
    <title>Ejemplo de barra de herramientas de una sencilla aplicación de correo-e</title>
    <mediaobject>
      <imageobject><imagedata fileref="images/toolbars-mail.png" format="PNG" width="428" depth="48"/></imageobject>
      <imageobject><imagedata fileref="images/toolbars-mail.eps" format="EPS"/></imageobject>
      <textobject><phrase>Ejemplo de barra de herramientas de una aplicación de correo-e</phrase></textobject>
    </mediaobject>
  </figure>

  <!-- Notes from GJM:
  Text-on-the-side toolbars are now part of Gtk+.
  Stock items have mnemonics/access keys. I don't think they should.
  -->
 
  <!-- CFB: Assuming for now therefore that we ought to be recommending Gtk toolbars, but trying to keep the text as widget-neutral as possible
  <note>
  <title>For discussion</title>
  <para>A few people only want to recommend one type of toolbar.  Which should it be?  We can't really recommend the GAL one because it's not part of core GNOME.  On the other hand, the Gtk one is somewhat clunky, and projects like Evo, AbiWord etc. are unlikely to switch to it anyime soon.</para>
  </note>
  -->
    
  <para>Careful and consistent toolbar design speeds up the user's task by giving direct access to functions that would otherwise be hidden on a menu.  Use them only for the most important functions, however.  Having too many toolbar controls reduces their efficiency by making them harder to find, and too many rows of toolbars reduces the amount of screen space available to the rest of the application.</para>
    
  <sect1 id="toolbars-appearance">
    <title>Apariencia y contenido</title>
      
    <para>The effectiveness of toolbars is increased by maintaining a level of consistency between different applications.  The toolbar is one of the first parts of your application that a user will see the first time they run it, so by providing a toolbar that looks familiar to them, you can immediately make them feel comfortable about using your application.</para>
      
    <para>As well as following the recommendations and examples given in this section, look at the toolbars in other well-designed GNOME 2.0 applications for guidance when deciding what— and what not— to put on your application's toolbar.</para>
      
    <para>However many toolbars or <link linkend="toolbox-windows">toolbox windows</link> your application offers, provide one main toolbar by default that contains a representative subset of the application's overall functionality.  Many of the buttons on this toolbar will be the same regardless of the type of application.</para>
      
    <para>For example, the main toolbar in an office application will nearly always have <guilabel>New</guilabel>, <guilabel>Open</guilabel> and <guilabel>Save</guilabel> as its first three toolbar buttons.  Similarly, the first few buttons in a browser application should always include <guilabel>Back</guilabel>, <guilabel>Forward</guilabel>, <guilabel>Stop</guilabel> and <guilabel>Reload</guilabel>, in that order.</para>
      
    <!-- CB-Fig: A composite figure for all the listitems might be useful. --> 
    <itemizedlist><title>Guías</title>
	
      <listitem><para>Place only the most commonly-used application functions on your toolbars.  Don't just add buttons for every menu item.</para></listitem>
		
      <listitem><para>De manera predeterminada, haga que sus barras de herramientas aparezcan justo debajo de la barra de menú principal</para></listitem>
	
      <listitem><para>Allow toolbars to be turned on and off in your application's <guilabel>Preferences</guilabel> dialog and by using the <menuchoice><guimenu>View</guimenu><guimenuitem>Toolbar</guimenuitem></menuchoice> menu item.  If there is more than one toolbar, they are turned on and off by individual entries in the <menuchoice><guimenu>View</guimenu><guimenuitem>Toolbar</guimenuitem></menuchoice> submenu.</para></listitem>
	
      <listitem><para>All functions that appear on your toolbars must also accessible via the main menu bar, either directly (i.e. an equivalent menu item) or indirectly (e.g. in the <menuchoice><guimenu>Options</guimenu><guimenuitem>Settings</guimenuitem></menuchoice> dialog).</para></listitem>
	
      <listitem><para>Arrange toolbar buttons in the same order and groupings as their equivalents on the main menu bar. In particular, always group sets of mutually-exclusive toolbar buttons.</para></listitem>
	
      <listitem><para>Don't add buttons for <guilabel>Help</guilabel>, <guilabel>Close</guilabel> or <guilabel>Quit</guilabel> to your toolbar by default, as these are rarely used and the space is better used for more useful controls.  Similarly, only provide buttons for <guilabel>Undo</guilabel>, <guilabel>Redo</guilabel> and the standard clipboard functions if there is space on the toolbar to do so without sacrificing more useful, application-specific controls.</para></listitem>
	
      <listitem><para>Provide options to show toolbar buttons as text, graphics or both— see <xref linkend="view-toolbar"/> for the menus to use for controlling toolbar display.  Also provide an option to return all toolbars in your application to the control center default for this setting.</para></listitem>
	
      <listitem><para>Allow users to configure toolbars to contain their own selection of commands, in whatever order they choose.  Provide an option in the configuration dialog to return the toolbars to their default configuration.</para></listitem>
	
      <listitem><para>Save your application's toolbar position and contents as part of the application configuration, and restore them when the application is restarted.</para></listitem>
	
    </itemizedlist>
      
    <sect2 id="vertical-toolbars">
      <title>Barras de herramientas verticales</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 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> 
	
      <itemizedlist>

	<listitem><para>the configuration of the application window means there would be a lot of wasted space if a horizontal toolbar was used instead, or</para></listitem>
	<listitem><para>your application would otherwise require three or more rows of toolbars to appear below the main menu bar by default.  Note however that in this situation, the better alternative is usually to display fewer toolbars by default.</para></listitem>

      </itemizedlist>

      <para>If you must use a vertical toolbar, ensure the user can configure it to appear horizontally if they prefer.</para>
      
    </sect2>

	<sect2 id="toolbars-media">
		<title>Barras de herramientas del reproductor multimedia</title>
		<para>Many applications are able to play sound or video clips.  For consistency, always present the buttons that control playback in the same order and with the same stock icons.</para>
		<itemizedlist><title>Guías</title>
			<listitem><para>Show separate Stop and Pause buttons. Do not change Play to Pause while the clip is playing.</para></listitem>
		</itemizedlist>
		<para><remark>Suggested order: prev,rew,rec,play,stop,pause,fwd,next,eject.</remark></para>
		<para><remark>gtk still doesn't have stock media icons, but CD player, sound recorder etc. all register icons with media-* IDs, should mention that here.</remark></para>
		<para><remark>Should maybe also suggest here how to show volume and timeline controls.</remark></para>
	</sect2>

  </sect1>
    
  <sect1 id="toolbars-controlling-display">
    <title>Controlling Display and Appearance</title>
      
    <para>For each toolbar in your application, the user should be able to choose whether or not to show that toolbar, and whether to show its contents as icons only, text only or both.</para>
                  
    <itemizedlist><title>Guías</title>
	
      <listitem><para>Allow the user to override the control center toolbar defaults for your particular application in the application's <guilabel>Preferences</guilabel> dialog.  In particular, ensure that the user can:</para>
	  
	<itemizedlist>
	    
	  <listitem><para>separately choose to show each toolbar in your application as icons only, text only, or both</para></listitem>
	    
	  <listitem><para>return the icon/text/both status for all toolbars in your application to the system default</para></listitem>

	  <listitem><para>choose to show text labels either to the side of some or below all toolbar icons, and to return this setting to the system default</para></listitem>
	    
	  <listitem><para>return the layout and ordering of all toolbars in your application to the application default</para></listitem>
	    
	</itemizedlist>
	  
      </listitem>
	
      <listitem><para>If your application has a single toolbar, allow the user to turn it on or off with a <menuchoice><guimenu>View</guimenu><guimenuitem>Toolbar</guimenuitem></menuchoice> check box menu item.</para></listitem>
	
      <listitem><para>If your application has two or three toolbars, allow the user to turn them on or off individually by placing a menu item for each one on the application's <guimenu>View</guimenu> menu.  For example, <guimenuitem>Main Toolbar</guimenuitem>, <guimenuitem>Drawing Toolbar</guimenuitem>, <guimenuitem>Formatting Toolbar</guimenuitem>. Place the items together in a single group on the menu, with <guimenuitem>Main Toolbar</guimenuitem> first (if your application has one), followed by the others in alphabetical order.</para></listitem>
	
      <listitem><para>If your application has more than three toolbars, allow the user to turn them on or off individually by placing a menu item for each one in a <guisubmenu>Toolbars</guisubmenu> sub-menu on the application's <guimenu>View</guimenu> menu.  Place the <guimenuitem>Main Toolbar</guimenuitem> item first (if your application has one), followed by the others in alphabetical order.</para>
	  
	<figure id="view-toolbar">
	  <title>Example View menu fragments for applications with one toolbar (left), two or three toolbars (middle), or four or more toolbars (right)</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/toolbars-configure-menu.png" format="PNG" width="488" depth="135"/></imageobject>
	    <imageobject><imagedata fileref="images/toolbars-congfigure-menu.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Example View menu for application with single toolbar</phrase></textobject>
	  </mediaobject>
	</figure>
	  
      </listitem>
	
    </itemizedlist>

  </sect1>
  <sect1 id="toolbars-labels-tooltips">
    <title>Etiquetas y consejos</title>
      
    <para>Most controls that appear on your toolbar will require a text label that appears on, below or beside it.  Keep this description as short as possible, preferably a single verb.  For example, <guibutton>Open</guibutton> or <guibutton>Undo</guibutton>.</para>
      
    <para>Every control that appears on your toolbar should have a tooltip, whether or not that control has an associated text label.  The tooltip should be a concise description of the control, but should provide more information than its text label where possible.  For example, <guilabel>Open an existing document</guilabel>, or <guilabel>Undo last operation</guilabel>.</para>
            
    <itemizedlist><title>Guías</title>

      <listitem><para>For buttons that correspond directly to menu items, make the text label the same as the menu item, but without any trailing ellipsis.  For example, <guibutton>Open</guibutton>, <guibutton>Save</guibutton>.</para></listitem>

      <listitem><para>Do not provide access keys for toolbar buttons.  Since toolbars are in the same keyboard focus context as the menubar, it would be too difficult to provide unique access keys for every menu title and toolbar control.  Toolbars are primarily intended as a shortcut for mouse users, although they are keyboard-navigable for accessibility reasons.</para></listitem>
	
      <listitem><para>If your toolbar is configured to show labels below button icons, show a label for every control on the toolbar.  For example:</para>
	  
	<figure>
	  <title>Barra de herramientas con etiquetas debajo de todos los botones</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/toolbars-labels-below.png" format="PNG" width="381" depth="56"/></imageobject>
	    <imageobject><imagedata fileref="images/toolbars-labels-below.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Barra de herramientas con etiquetas debajo de todos los botones</phrase></textobject>
	  </mediaobject>
	</figure>

      </listitem>
	
      <listitem><para>If your toolbar is configured to show labels beside button icons rather than below them (using the "priority text" setting), do not show labels for every button.  Show labels only for the buttons that will be most-frequently used.  Choose no more than four such icons on any one toolbar, otherwise the effect will be diluted and the toolbar will become very wide.  For example:</para>
	  
	<figure>
	  <title>Toolbar with "priority text" labels beside the first few buttons only</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/toolbars-labels-beside.png" format="PNG" width="459" depth="35"/></imageobject>
	    <imageobject><imagedata fileref="images/toolbars-labels-beside.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Toolbar with "priority text" labels beside the first few items only</phrase></textobject>
	  </mediaobject>
	</figure>

	<para>If you are unsure which buttons will be most frequently used, choose the first few buttons on your toolbar and provide labels for those only.</para>
      </listitem>
	
      <listitem><para>Ensure all toolbar controls have tooltips. The tooltip should be more descriptive than the corresponding menu item, if it has one, but still concise.  For example, <guilabel>Create new document</guilabel> for the <guibutton>Open</guibutton> toolbar button.  Use sentence capitalization for tooltips—see <xref linkend="layout-capitalization"/> for more information.</para></listitem>
	
    </itemizedlist>
      
  </sect1>
    
  <!-- Removed for now until we decide how much/little specific guidance to give for application types
    
  <sect2>
  <title>Default Toolbar Layout— Office Application</title>
    
  <para>However many toolbars or palette windows your application provides, by default there should be one main toolbar that provides a subset of the application's overall functionality.  Many of the buttons on this toolbar will be the same regardless of the type of application.</para>
    
  <para>The following operations should be included on the main toolbar in the following order, if your application supports them.  Application-specific functions should be slotted onto the toolbar according to the position on which they appear on the main menu bar.  For functions that don't appear on the <guimenu>File</guimenu>, <guimenu>Edit</guimenu> or <guimenu>Help</guimenu> menus, this means they will normally appear between the <guibutton>Replace</guibutton> and <guibutton>Help</guibutton> buttons.</para>
    
  <figure>
  <title>Buttons that should appear on the main toolbar of an office application.</title>
  <mediaobject>
  <imageobject><imagedata fileref="images/GtkToolbar_productivitydefault.png" format="PNG" width="720" depth="54"/></imageobject>
  <imageobject><imagedata fileref="images/GtkToolbar_productivitydefault.eps" format="EPS"/></imageobject>
  <textobject>
  <phrase>New-Open-Save|Print|Undo-Redo|Find-Replace|Cut-Copy-Paste-Delete</phrase>
  </textobject>
  </mediaobject>
  </figure>
    
  <para>If your application supports all of these functions and you want to simplify your toolbar, consider leaving off the <guibutton>Undo</guibutton> and <guibutton>Redo</guibutton> buttons, or the <guibutton>Cut</guibutton>, <guibutton>Copy</guibutton>, <guibutton>Paste</guibutton> and <guibutton>Delete</guibutton> buttons, as most users prefer to use keyboard or menu for these functions.  However, you should include an option to re-add these buttons in your <menuchoice><guimenu>Toolbars</guimenu><guimenuitem>Customize</guimenuitem></menuchoice>... menu.</para>
    
  <para>If you wish to add a <guibutton>Help</guibutton> toolbar button, it should be placed last (rightmost, in western locales) on the main toolbar.  However, adding a <guibutton>Help</guibutton> button to the toolbar is not generally recommended, as usability studies suggest that it will be rarely used.  (N.B. This finding applies only to toolbars, not <guibutton>Help</guibutton> buttons in dialogs).</para>
    
    
    
  </sect2>
    
  <sect2>
  <title>Default Toolbar Layout— Browser Applications</title>
    
  <para>Applications for browsing documents or other objects, such as web, file, help or documentation browsers, should use the following layout for their main toolbar:</para>
    
  <para>Back Forward [Other Navigation] Stop Reload | Home | [Other App-Specific]</para>
    
  <para>Application-specific buttons (other than navigation buttons) should be placed in the button group following <guibutton>Home</guibutton>, in the order that they appear on the main menu bar.</para>
    
  <para>Following this model, some current GNOME browser apps would have their toolbars re-ordered as follows:</para>
    
  <figure>
  <title>Nautilus 1.0 toolbar rearranged to follow recommended standard toolbar layout for browser applications</title>
  <mediaobject>
  <imageobject><imagedata fileref="images/GtkToolbar_browserdefault.png" format="PNG" width="486" depth="58"/></imageobject>
  <imageobject><imagedata fileref="images/GtkToolbar_browserdefault.eps" format="EPS"/></imageobject>
	    <textobject>
	      <phrase>Back Forward Up Stop Reload | Home | WebSearch Services</phrase>
	    </textobject>
	  </mediaobject>
	</figure>
	
	<table>
	  <title>Proposed toolbar re-ordering for Nautilus</title>
	  <tgroup cols='2' align='left'>
	    	    
	    <tbody>
	      <row>
		<entry>Nautilus (1.0.x)</entry>
		<entry>Back Forward Up Refresh Home WebSearch Services Stop</entry>
	      </row>
	      <row>
		<entry>Nautilus (proposed)</entry>
		<entry>Back Forward Up Stop Reload | Home | WebSearch Services </entry>
	      </row>
	    </tbody>
	  </tgroup>
	</table>

	<table>
	  <title>Proposed toolbar re-ordering for Galeon</title>
	  <tgroup cols='2' align='left'>

	    <tbody>
	      <row>
		<entry>Galeon (0.12.x)</entry>
		<entry>Back Forward Reload Home Stop Zoom [URL] Go</entry>
	      </row>
	      <row>
		<entry>Galeon (proposed)</entry>
		<entry>Back Forward Stop Reload | Home | Zoom [URL] Go </entry>
	      </row>
	    </tbody>
	  </tgroup>
	</table>
	
	<table>
	  <title>Proposed toolbar re-ordering for GNOME Help (deprecated, for illustration purposes only)</title>
	  <tgroup cols='2' align='left'>

	    <tbody>
	      <row>
		<entry>GNOME Help (0.4)</entry>
		<entry>Back Forward Refresh Index History Bookmarks Help</entry>
	      </row>
	      <row>
		<entry>GNOME Help (proposed)</entry>
		<entry>Back Forward Stop Reload | Index History Bookmarks</entry>
	      </row>
	    </tbody>
	  </tgroup>
	</table>

	<para>Note: In browser applications, use <guilabel>Reload</guilabel> rather than <guilabel>Refresh</guilabel> when the data will be actually re-read from its original source, rather than just re-painted on the screen.</para>


      </sect2>
-->

  </chapter>
  <!-- Note from GJM: I think palettes should go with toolboxes/utility windows. -->
  <!--
<sect1 id="toolbars-palettes">
<title>TODO : Palettes</title>
  
<para>A palette is much like a floating toolbar.  However, its size and shape is usually more customizable, and it typically has a titlebar of its own and appears in the GNOME task list.</para>
  
</sect1>
</chapter>
  -->
  


<chapter id="controls">
  <title>Controles</title>

  <sect1 id="controls-usage">
    <title>Using Controls Effectively</title>

    <para>GNOME provides a set of controls, also known as widgets, which allow
    users to interact with your applications. Using these controls
    appropriately and not altering their standard behavior is important. This
    allows users to predict the effects of their actions, and thus learn to
    use your application more quickly and efficiently. Controls that behave in
    non-standard ways break the user's mental model of how your
    application works, and dilute the meaning of the interface's visual
    language.</para>
  </sect1>

  <sect1 id="controls-terminology">
    <title>Terminología</title>

    <para>Although they are known as "widgets" in the GNOME APIs and
    developer documentation, do not use this term in your user interface or
    user documentation. Refer to them by their specific names (for example,
    "buttons" or "menus"), or by the generic name
    "controls".</para>
  </sect1>

  <sect1 id="controls-sensitivity">
    <title>Sensibilidad</title>

    <!--      <remark>Do we really want to include GTK calls here? -Seth</remark> -->

    <!--	 CFB have removed the GTK calls for the basic stuff, although left it in for the 
		 more obscure things that hackers currently aren't doing -->

    <para>Sometimes it does not make sense to allow the user to interact with
    a control in the current context, for example, to press a
    <guilabel>Paste</guilabel> button when the clipboard is empty. At these
    times, make the control insensitive 
    to minimize the risk of user error. While a control is insensitive, it
    will appear dimmed and will not be able to receive the focus, although
    assistive technologies like screenreaders will still be able to detect and
    report it.</para>

    <para>It is usually better to make a control insensitive than to hide it
    altogether. This way, the user can learn about functionality they may be
    able to use later, even if it is not available right now.</para>

    <figure>
      <title>Two check boxes: sensitive (top) and insensitive (bottom)</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="76" fileref="images/controls-sensitivity.png" format="PNG" width="258"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-sensitivity.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Screenshot showing the visual appearance of sensitive and
          insensitive check box controls</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!--
      <para>Sometimes, however, a large group of controls always become insensitive or sensitive simultaneously as the direct result of user action, such as checking a box or pressing a button.  In this case it is sometimes better to hide or show the controls (for example, using the <ulink url="http://developer.gnome.org/doc/API/2.0/gtk/gtkwidget.html#GTK-WIDGET-SHOW"><function>gtk_widget_show()</function></ulink> and <ulink url="http://developer.gnome.org/doc/API/2.0/gtk/gtkwidget.html#GTK-WIDGET-HIDE"><function> gtk_widget_hide()</function></ulink> functions, for GTK controls) rather than making them sensitive or insensitive.  For example, if all the controls on a <link linkend="controls-notebooks">notebook tab</link> are insensitive, it is usually better to hide the tab altogether.</para>
-->

    <!-- CB-Ed: Hmm. Not sure about the preceding paragraph and the suggestion it makes.  Usually you don't want to change an interface as drastically as removing an entire tab when a user clicks a button - it's jarring, first of all, and secondly, you want to keep the UI as consistent as possible: one of the reasons for disabling, say, a menu item, and not just making it disappear when it is unavailable, is to train the user's eye and behavior to know where certain things are located. You may want to back this up or verify the suggestion's strength before finalizing the HIG. -->

    <sect2 id="controls-locked">
      <title>Controles bloqueados</title>

      <para>In a network-managed environment, like a computer lab, system
      administrators usually want to "lock down" the values of certain
      settings, or remove them from the user interface altogether. This makes
      it easier for them to troubleshoot any problems that their users may
      encounter. In GNOME, the correct way for the system administrator to do
      this is by restricting write access to the GConf keys corresponding to
      those settings.</para>

      <para>When you are designing your application, consider which settings a
      system administrator might want to make unavailable to users. These may
      typically include:</para>

      <itemizedlist>
        <listitem>
          <para>Settings that, if set wrongly, could prevent the application
          from functioning at all. For example, proxy settings in a network
          application.</para>
        </listitem>

        <listitem>
          <para>Settings that could refer to networked resources. For example,
          the Templates directory in an office application, where shared
          stationery such as fax cover sheets might be stored.</para>
        </listitem>

        <listitem>
          <para>Settings that customize the user interface, other than those
          required for accessibility. For example, certain menu, keyboard or
          toolbar customization options.</para>
        </listitem>
      </itemizedlist>

      <para>Your application needs to decide every time these controls are
      displayed whether or not they are available for editing, depending on
      the writeable state of the GConf key that holds its value. In the
      simplest case, your code for each control could look like that in the
      example below.</para>

      <!-- CB-Ed: Again, reconsider who your readers are.  Some may not be comfortable with terms such as "runtime."  Use language that is more inclusive; you may reword the first sentence to say "...decide when you start up your machine whether..." or something along those lines. -->

      <example>
        <title>Sample code fragment showing how to make a GConf-locked control
        insensitive</title>

        <programlisting>if (!gconf_key_is_writable (http_proxy))
        gtk_widget_set_sensitive (http_proxy_field, FALSE);</programlisting>
      </example>

      <para>Include a section for system administrators in your user guide,
      explaining which settings they can lock, and their corresponding GConf
      keys.</para>

      <para>Explain to the user why these controls cannot be edited at this
      time. You can do this with static text, tooltips or online help,
      depending on the situation. For example:</para>

      <figure>
        <title>Example of a dialog with locked controls</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="216" fileref="images/controls-locked.png" format="PNG" width="475"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/controls-locked.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Screenshot showing disabled proxy controls in a web
            browser's property dialog, under the caption "Only the
            system administrator can change these settings"</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <!-- CB-Fig: Figure is good, add callouts, taking some text from the caption, and make caption more succinct: "Dialog with locked settings/controls."  When referring to figures, use the figure number, preferably with the following format: chapter_no - figure_no so that figures can be referred to from outside its housing chapter. -->

      <para>Note that although they cannot be edited, the settings are still
      visible and selectable, and may be copied to the clipboard.</para>

      <!-- CB-Ed: Second sentence in above paragraph: "In some cases?"  Please provide solid examples and reasons for why you suggest such a thing as hiding "affected controls."  -->
    </sect2>
  </sect1>

  <sect1 id="controls-entry">
    <title>Campos de entrada de texto</title>

    <para>Text entry fields are used for entering one or more lines of plain
    text. In GTK 2, the <ulink url="http://developer.gnome.org/doc/API/2.0/gtk/gtkentry.html">GtkEntry</ulink>
    control is used for single-line text entry, and <ulink url="http://developer.gnome.org/doc/API/2.0/gtk/gtktextview.html">GtkTextView</ulink>
    for multiple-line text entry.</para>

    <!-- CB-Ed: The second and third sentences are baffling.  It seems to be just directed at the developer; it is not inclusive to readers who are not coders.  This probably isn't what you want to get people like visual/UI designers to read and use this guide. -->

    <figure>
      <title>Single and multi-line entry fields</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="153" fileref="images/controls-text.png" format="PNG" width="545"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-text.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Screenshot of part of a dialog, containing both single and
          multi-line entry fields</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!-- CB-Fig: Dialog "fragment?"  Use callouts.  Succinct caption: "Text fields." or "Single and Multi-line Entry Fields"-->

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Label the entry field with a text label above it or to its left,
        using <link linkend="layout-capitalization">sentence capitalization</link>.
        Provide an access key in the label that allows the user to give focus
        directly to the entry field.</para>
      </listitem>

      <listitem>
        <para>Right-justify the contents of entry fields that are used only
        for numeric entry, unless the convention in the user's locale
        demands otherwise. This is useful in windows where the user might want
        to compare two numerical values in the same column of controls. In
        this case, ensure the right edges of the relevant controls are also
        aligned.</para>
      </listitem>

      <listitem>
        <para>When the user gives focus to an entry field using the keyboard,
        place the text cursor at the end of the existing text and highlight
        its contents (but don't overwrite the existing PRIMARY clipboard
        selection). This makes it
        easy to immediately overtype or append new text, the two most common
        operations performed on entry fields.</para>
      </listitem>

      <listitem>
        <para>Size text entry fields according to the likely size of the
        input. This gives a useful visual cue to the amount of input expected,
        and breaks up the dialog making it easier to scan. Don't make all
        the fields in the dialog the same width just to make everything line
        up nicely.</para>
      </listitem>

      <!-- CB-Ed: Try to cluster input text fields so that fields of similar "types" end up together, and end up having uniform sizes.  Usually you want to size text entry fields to the width of the largest input expected in each clustering.  A clean and orderly visual flow is indeed important for the user; that is, line things up so that "everything line[s] up nicely" where possible.  The figure (3) actually shows this well. -->

      <listitem>
        <para>In an instant-apply <link linkend="windows-utility">property or
        preference window</link>, validate the contents of the entry field
        when it loses focus or when the window is closed, not after each keypress. 
	Exception: if the field accepts only a fixed
        number of characters, such as a hexadecimal color code, validate and
        apply the change as soon as that number of characters have been entered.</para>
      </listitem>

      <listitem>
        <para>Provide a static text prompt for text boxes that require input
        in a particular format or in a particular unit of measurement. For
        example:</para>

        <figure>
          <title>Text entry field with static text prompt</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="31" fileref="images/controls-text-prompt.png" format="PNG" width="130"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-text-prompt.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>A text entry field in which the user must input a time,
              with the label "hh:mm" beside it to indicate the
              required format</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <!-- CB-Fig: Good fig, provide callouts to "static text prompt," shorten caption and fix fig no. -->
      </listitem>

      <listitem>
        <para>Where possible, provide an additional or alternative control
        that limits the required input to the valid range. For example,
        provide a <link linkend="controls-spin-boxes">spinbox</link> or <link linkend="controls-sliders">slider</link> if the required input is one
        of a fixed range of integers, or provide access to a <ulink url="http://developer.gnome.org/doc/API/2.0/gtk/gtkcalendar.html">GtkCalendar</ulink>
        control if the user has to enter a valid date:</para>

        <figure>
          <title>Text entry field requiring a date as input, with a button
          beside it to pop up a GtkCalendar control to simplify the task</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="41" fileref="images/controls-text-choose.png" format="PNG" width="298"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-text-choose.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>A text entry field in which the user must input a date,
              with a button labelled "Choose" beside it that opens a
              GtkCalendar control to simplify the task</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <!-- CB-Fig: Provide a larger image including examples of "spinbox" or "slider." Same comments apply here as to all figuers in the HIG: callouts, shorter caption, figure number. -->

        <para>This is less error-prone than expecting the user to format their
        text input in some arbitrary format. You may still want to provide the
        entry field control as well, however, for expert users who are
        familiar with the required format.</para>
      </listitem>

      <listitem>
        <para>If you implement an entry field that accepts only keystrokes
        valid in the task context, such as digits, play the system warning
        beep when the user tries to type an invalid character. If the user
        types three invalid characters in a row, display an <link linkend="windows-alert">alert</link> that explains the valid inputs
        for that textfield.</para>
      </listitem>

      <listitem>
        <para>The cursor blink rate is globally defined by the XSettings
        "gtk-cursor-blink" and "gtk-cursor-blink-time".
        Standard toolkit controls use these and they must 
        not be altered in applications by any means. New controls with text
        cursors must respect these global values.</para>
      </listitem>
    </itemizedlist>

    <sect2 id="controls-text-return">
      <title>Comportamiento de la tecla «Intro»</title>

      <para>Normally, pressing <keycap>Return</keycap> in a dialog should
      activate the dialog's default button, unless the focused control
      uses <keycap>Return</keycap> for its own purposes. You should therefore
      set the <ulink url="http://developer.gnome.org/doc/API/2.0/gtk/gtkentry.html#GTK-ENTRY-SET-ACTIVATES-DEFAULT"><function>activates-default</function></ulink>
      property of most entry fields to TRUE. (Note that GtkTextView does not
      have such a setting— pressing <keycap>Return</keycap> always inserts a
      new line.).</para>

      <para>However, if your dialog contains several entry fields that are
      usually filled out in order, for example <guilabel>Name</guilabel>,
      <guilabel>Address</guilabel> and <guilabel>Telephone Number</guilabel>,
      consider setting the <function>activates-default</function> property on
      those entry fields to FALSE. Pressing <keycap>Return</keycap> should
      then move focus on to the next control instead. 
      
      Doing this will help prevent the user from accidentally closing the
      window before they have entered all the information they wanted to.</para>

      <para>As a further safeguard, remember not to set the default button in
      a dialog until the minimum amount of required information has been
      entered, for example, both a username and a password in a login dialog.
      Again, in this case you should move focus to the next control when the
      user presses <keycap>Return</keycap>, rather than just ignoring the
      keypress.</para>

      <para>If you need to provide a keyboard shortcut that activates the
      default button while a GtkTextView control has focus, use
      <keycombo><keycap>Ctrl</keycap><keycap>Return</keycap></keycombo>.</para>

      <note>
        <title>Nota</title>

        <para>Gtk does not currently move focus to the next control when
        <keycap>Return</keycap> is pressed and either <function>activates-default=FALSE</function>,
        or there is no default button in the window. For now,
        <keycap>Return</keycap> does nothing in these situations, so remember
        to implement the focus change behavior yourself.</para>
      </note>
    </sect2>

    <sect2 id="controls-text-tab">
      <title>Comportamiento de la tecla «Tab»</title>

      <para>Normally, pressing <keycap>Tab</keycap> in a single-line entry
      field should move focus to the next control, and in a multi-line entry
      field it should insert a tab character. Pressing <keycombo><keycap>Ctrl</keycap><keycap>Tab</keycap></keycombo>
      in a multi-line entry field should move focus to the next control.</para>

      <para>If you need to provide a keyboard shortcut that inserts a tab
      character into a single line entry field, use <keycombo><keycap>Ctrl</keycap><keycap>Tab</keycap></keycombo>.
      You are unlikely to find many situations where this is useful, however.</para>

      <remark>There is a patch in bugzilla (bugid=<ulink url="http://bugzilla.gnome.org/show_bug.cgi?id=53763">53763</ulink>)
      that adds an <function>allow_tab_characters</function> function to
      GtkEntry controls. This allows you to specify on a per-control basis
      whether <keycap>Tabulador</keycap> should insert a tab character or not. It is
      currently not known whether this patch is likely to make it into a
      future version of gtk.</remark>
    </sect2>
  </sect1>

  <sect1 id="controls-spin-boxes">
    <title>Spin Boxes</title>

    <para>A spin box is a text box that accepts a range of values. It
    incorporates two arrow buttons that allow the user to increase or decrease
    the current value by a fixed amount.</para>

    <figure>
      <title>Example of a spin box</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="32" fileref="images/controls-spin-box.png" format="PNG" width="204"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-spin-box.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>A simple spin box used to specify the spacing between
          applets on a panel</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!-- CB-Fig: Callout, shorten caption, fig no -->

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Use spin boxes for numerical input only. Use a list or option
        menu when you need the user to select from fixed data sets of other
        types.</para>
      </listitem>

      <listitem>
        <para>Use a spin box if the numerical value is meaningful or useful
        for the user to know, and the valid input range is unlimited or fixed
        at one end only. For example, a control for specifying the number of
        iterations of some action, or a timeout value. If the range is fixed
        at both ends, or the numerical values are arbitrary (for example, a
        volume control), use a slider control instead.</para>
      </listitem>

      <listitem>
        <para>Label the spin box with a text label above it or to its left,
        using <link linkend="layout-capitalization">sentence capitalization</link>.
        Provide an access key in the label that allows the user to give focus
        directly to the spin box.</para>
      </listitem>

      <listitem>
        <para>Right-justify the contents of spin boxes, unless the convention
        in the user's locale demands otherwise. This is useful in windows
        where the user might want to compare two numerical values in the same
        column of controls. In this case, ensure the right edges of the
        relevant controls are also aligned.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="controls-sliders">
    <title>Deslizadores</title>

    <para>A slider allows the user to quickly select a value from a fixed,
    ordered range, or to increase or decrease the current value. The control
    looks like the type of slider that you might find on an audio mixing desk
    or a hi-fi's graphic equalizer. In gtk, you implement a slider using
    the GtkHScale or GtkVScale controls, for horizontal or vertical sliders
    respectively.</para>

    <figure id="controls-slider-figure">
      <title>Un deslizador simple</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="27" fileref="images/controls-slider.png" format="PNG" width="208"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-slider.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>A slider control used to change the stereo audio balance
          between left and right speakers</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Use un deslizador cuando:</para>

        <itemizedlist>
          <listitem>
            <para>adjusting the value relative to its current value is more
            important than choosing an absolute value. For example, a volume
            control: the average user will usually think about turning the
            volume up or down to make a sound louder or quieter, rather than
            setting the peak output to a specific decibel value.</para>
          </listitem>

          <listitem>
            <para>it is useful for the user to control the rate of change of
            the value in real time. For example, to monitor the effects of a
            color change in a live preview window as they drag the RGB
            sliders.</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Label the slider with a text label above it or to its left,
        using <link linkend="layout-capitalization">sentence capitalization</link>.
        Provide an access key in the label that allows the user to give focus
        directly to the slider.</para>
      </listitem>

      <listitem>
        <para>Mark significant values along the length of the slider with text
        or tick marks. For example the left, right and center points on an
        audio balance control in <xref linkend="controls-slider-figure"/>.</para>
      </listitem>

      <listitem>
        <para>For large ranges of integers (more than about 20), and for
        ranges of floating point numbers, consider providing a text box or
        spin box that is linked to the slider's value. This allows the
        user to quickly set or fine-tune the setting more easily than they
        could with the slider control alone.</para>

        <figure>
          <title>Slider controls with linked spin boxes</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="85" fileref="images/controls-slider-spinbox.png" format="PNG" width="356"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-slider-spinbox.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Three slider controls used to change RGB values, each
              with a spinbox beside them to facilitate direct numeric entry</phrase>
            </textobject>
          </mediaobject>
        </figure>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="controls-buttons">
    <title>Botones</title>

    <para>A button initiates an action when the user clicks it.</para>

    <figure>
      <title>Botones típicos en un diálogo modal</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="47" fileref="images/controls-buttons.png" format="PNG" width="190"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-buttons.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>OK and Cancel buttons as found in a modal dialog</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Label all buttons with imperative verbs, using <link linkend="layout-capitalization">header capitalization</link>. For
        example, <guilabel>Save</guilabel>, <guilabel>Sort</guilabel> or
        <guilabel>Update Now</guilabel>. Provide an access key in the label
        that allows the user to directly activate the button from the
        keyboard.</para>
      </listitem>

      <listitem>
        <para>After pressing a button, the user should expect to see the
        result of their action within 1 second. For example, closing the
        window or opening another. See <xref linkend="feedback"/> for
        guidance on what to do if your application cannot respond this
        quickly.</para>
      </listitem>

      <!-- CB-Ed: Do you use ms in other parts of the HIG?  Might want to just use ms and not s as a measure, to keep things consistent and in case you need to finer granualarity than this later -->

      <listitem>
        <para>Use an ellipsis (...) at the end of the label if the action
        requires further input from the user before it can be carried out. For
        example, <guilabel>Save As...</guilabel> or <guilabel>Find...</guilabel>.
        Do not add an ellipsis to commands like <guilabel>Properties</guilabel>,
        <guilabel>Preferences</guilabel>, or <guilabel>Settings</guilabel>, as
        these open windows that do not <emphasis>require</emphasis> further
        input.</para>
      </listitem>

      <listitem>
        <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 inefficient,
        especially for users relying on assistive technologies.</para>
      </listitem>

      <listitem>
        <para>If your button can display text, an icon, or both, choose which
        label to display at runtime according to the user's preference in
        the GNOME Menus and Toolbars Preferences dialog. However, you may
        over-ride this preference when there is no suitable icon to describe
        the button's action graphically, for example.</para>
      </listitem>

      <listitem>
        <para>Do not use more than one or two different widths of button in
        the same window, and make all of them the same height. This will help
        give a pleasing uniform visual appearance to your window that makes it
        easier to use.</para>
      </listitem>

      <listitem>
        <para>Do not assign actions to double-clicking or right-clicking a
        button. Users are unlikely to discover these actions, and if they do,
        it will distort their expectations of other buttons on the desktop.</para>
      </listitem>

      <listitem>
        <para>Make invalid buttons insensitive, rather than popping up an
        error message when the user clicks them.</para>
      </listitem>
    </itemizedlist>

    <para>In a dialog, one button may be made the default button, which is
    shown with a different border and is activated by pressing
    <keycap>Return</keycap>. Often this will be the <guibutton>OK</guibutton>
    or equivalent button. However, if pressing this button by mistake could
    cause a loss of data, do not set a default button for the window. Do not
    make <guibutton>Cancel</guibutton> the default button instead. See <xref linkend="default-buttons"/> for more information.</para>

    <!-- CB-Fig: Add a figure here to illustrate a default button. -->

    <para>If it does not make sense to have a default button until several
    fields in the dialog have been correctly completed—for example, both the
    <guilabel>Username</guilabel> and <guilabel>Password</guilabel> fields in
    a login dialog—do not set the default button until they have both been
    completed.</para>
  </sect1>

  <sect1 id="controls-check-boxes">
    <title>Check Boxes</title>

    <para>Check boxes are used to show or change a setting. Its two states,
    set and unset, are shown by the presence or absence of a checkmark in the
    labelled box.</para>

    <figure>
      <title>Un grupo típico de casillas</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="140" fileref="images/controls-check-boxes.png" format="PNG" width="143"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-check-boxes.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Un grupo típico de cinco casillas en un diálogo</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!-- CB-Fig: callouts. -->

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Do not initiate an action when the user clicks a check box.
        However, if used in an instant-apply <link linkend="windows-utility">property
        or preference window</link>, update the setting represented by the
        check box immediately.</para>
      </listitem>

      <listitem>
        <para>Clicking a check box should not affect the values of any other
        controls. It may sensitize, insensitize, hide or show other controls,
        however.</para>
      </listitem>

      <listitem>
        <para>If toggling a check box affects the sensitivity of other
        controls, place the check box immediately above or to the left of the
        controls that it affects. This helps to indicate that the controls are
        dependent on the state of the check box.</para>
      </listitem>

      <listitem>
        <para>Use <link linkend="layout-capitalization">sentence
        capitalization</link> for check box labels, for example
        <guilabel>Use custom font</guilabel>.</para>
      </listitem>

      <listitem>
        <para>Label check boxes to clearly indicate the effects of both their
        checked and unchecked states, for example, <guilabel>Show icons in
        menus</guilabel>. Where this proves difficult, consider using two
        radio buttons instead so both states can be given labels. For example:</para>

        <figure>
          <title>Ambiguous check box (top), radio buttons work better in this
          case (bottom)</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="70" fileref="images/controls-check-box-ambiguous.png" format="PNG" width="279"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-check-box-ambiguous.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Two images: one showing a single check box ambiguously
              labelled "Progress bar in left of statusbar", the other
              making the choice explicit with radio buttons labelled
              "Left" and "Right" under the heading "Status
              bar progress indicator position:"</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <para>The single check box in this example is ambiguous, as it is not
        clear where the "progress indicator" will go if the box is
        unchecked. Two radio buttons are better in this case, as they make the
        options clear.</para>
      </listitem>

      <!-- CB-Fig: Again, callouts, shorten caption.  The callouts should include other bullet points as well (e.g., access keys).  The referring bullet item is badly phrased.  Perhaps make this the one check box images for the bullets, with different callouts for different bullet points.  -->

      <listitem>
        <para>Provide an access key in all check box labels that allows the
        user to set or unset the check box directly from the keyboard.</para>
      </listitem>

      <listitem>
        <para>If the check box represents a setting in a multiple selection
        that is set for some objects in the selection and unset for others,
        show the check box in its mixed state. For example:</para>

        <figure>
          <title>Check boxes (right) showing properties for a multiple
          selection of files in Nautilus (left)</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="170" fileref="images/controls-check-boxes-mixed.png" format="PNG" width="223"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-check-boxes-mixed.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Check boxes showing the Hidden, Readable and Writeable
              states of two selected files in Nautilus. Both files are hidden,
              neither are writeable, but one is readable. The Readable check
              box is therefore shown in its mixed state.</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <para>In this example, both selected files are hidden (since their
        filenames start with "."), and the emblems on their icons show
        that neither file is writeable, but one is readable. The
        <guilabel>Readable</guilabel> check box is therefore shown in its
        mixed state. <remark>At time of writing, the exact visual appearance
        of a mixed state check box in gtk was undecided</remark>.</para>

        <para>When a check box is in its mixed state:</para>

        <itemizedlist>
          <listitem>
            <para>clicking the box once should check the box, applying that
            setting (when confirmed) to all the selected objects</para>
          </listitem>

          <listitem>
            <para>clicking the box a second time should uncheck the box,
            removing that setting (when confirmed) to all the selected objects</para>
          </listitem>

          <listitem>
            <para>clicking the box a third time should return the box to its
            mixed state, restoring each selected object's original value
            for that setting (when confirmed)</para>
          </listitem>
        </itemizedlist>

        <!-- CB-Ed: Mixed state check boxes are a polemic-ridden issue.  Data to back this up? -->
      </listitem>

      <listitem>
        <para>Label a group of check boxes with a descriptive heading above or
        to the left of the group.</para>
      </listitem>

      <listitem>
        <para>Use a frame around the group if necessary, but remember that
        blank space often works just as well and results in a less
        visually-cluttered dialog.</para>
      </listitem>

      <listitem>
        <para>Do not place more than about eight check boxes under the same
        group heading. If you need more than eight, try to use blank space,
        heading labels or frames to divide them into smaller groups.
        Otherwise, consider using a check box list instead— but you probably
        also need to think about how to simplify your user interface.</para>
      </listitem>

      <listitem>
        <para>Try to align groups of check boxes vertically rather than
        horizontally, as this makes them easier to scan visually. Use
        horizontal or rectangular alignments only if they greatly improve the
        layout of the window.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="controls-radio-buttons">
    <title>Botones de radio</title>

    <para>Radio buttons are used in groups to select from a mutually exclusive
    set of options. Only one radio button within a group may be set at any one
    time. As with check boxes, do not use radio buttons to initiate actions.</para>

    <figure>
      <title>Un grupo típico de botones de radio</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="105" fileref="images/controls-radio-buttons.png" format="PNG" width="352"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-radio-buttons.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Un grupo típico de tres botones de radio en un diálogo</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Only use radio buttons in groups of at least two, never use a
        single radio button on its own. To represent a single setting, use a
        check box or two radio buttons, one for each state.</para>
      </listitem>

      <listitem>
        <para>Exactly one radio button should be set in the group at all
        times. The only exception is when the group is showing the properties
        of a multiple selection, when one or more of the buttons may be in
        their mixed state.</para>
      </listitem>

      <listitem>
        <para>Do not initiate an action when the user clicks a radio button.
        However, if used in an instant-apply <link linkend="windows-utility">property
        or preference window</link>, update the setting represented by the
        radio button immediately.</para>
      </listitem>

      <listitem>
        <para>Clicking a radio button should not affect the values of any
        other controls. It may sensitize, insensitize, hide or show other
        controls, however.</para>
      </listitem>

      <listitem>
        <para>If toggling a radio button affects the sensitivity of other
        controls, place the radio button immediately to the left of the
        controls that it affects. This helps to indicate that the controls are
        dependent on the state of the radio button.</para>
      </listitem>

      <listitem>
        <para>Use <link linkend="layout-capitalization">sentence
        capitalization</link> for radio button labels, for example
        <guilabel>Switched movement</guilabel>. Provide an access key in the
        label that allows the user to set the radio button directly from the
        keyboard.</para>
      </listitem>

      <!-- CB-Fig: "guilabel" may need to be more generic, like: Button Label, so that people don't get confused when scanning text about literals, particularly because you guys are using a lot of code references and lingo. -->

      <listitem>
        <para>If the radio button represents a setting in a multiple selection
        that is set for some objects in the selection and unset for others,
        show the radio button in its mixed state. For example:</para>

        <figure>
          <title>Radio buttons (right) showing properties for a multiple
          selection of shapes in a drawing application (left)</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="105" fileref="images/controls-radio-button-mixed.png" format="PNG" width="314"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-radio-button-mixed.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Radio buttons showing the Thick, Thin and Dashed drawing
              styles of two selected shapes in a drawing application. One
              shape is drawn in the thick style, the other in the dashed
              style. The Thick and Dashed radio buttons are therefore shown in
              their mixed state, and the Thin radio button is unset.</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <!-- 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>. 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
        radio button to its mixed state by clicking on it. Provide a
        <guibutton>Reset</guibutton> button or equivalent in the window that
        allows the previous mixed settings to be restored without closing the
        window or cancelling the dialog.</para>
      </listitem>

      <listitem>
        <para>Label a group of radio buttons with a descriptive heading above
        or to the left of the group.</para>
      </listitem>

      <listitem>
        <para>Use a frame around the group if necessary, but remember that
        blank space often works just as well and results in a less
        visually-cluttered dialog.</para>
      </listitem>

      <listitem>
        <para>Do not place more than about eight radio buttons under the same
        group heading. If you need more than eight, consider using a
        single-selection <link linkend="controls-lists">list</link> instead—
        but you probably also need to think about how to simplify your user
        interface.</para>
      </listitem>

      <listitem>
        <para>Try to align groups of radio buttons vertically rather than
        horizontally, as this makes them easier to scan visually. Use
        horizontal or rectangular alignments only if they greatly improve the
        layout of the window.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="controls-toggle-buttons">
    <title>Botones conmutadores</title>

    <para>Toggle buttons look similar to regular <link linkend="controls-buttons">Buttons</link>, but are used to show or change
    a state rather than initiate an action. A toggle button's two states,
    set and unset, are shown by its appearing "pushed in" or
    "popped out" respectively.</para>

    <figure>
      <title>Un típico grupo de botones conmutadores</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="46" fileref="images/controls-toggle-buttons.png" format="PNG" width="137"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-toggle-buttons.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>A group of four toggle buttons representing a choice of
          measurement units: inches, centimeters, feet and meters</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!-- CB-Fig: callouts -->

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Do not use groups of toggle buttons in dialogs unless space
        constraints force you to do so, or you need to provide consistency
        with a toolbar in your application. <link linkend="controls-check-boxes">Check boxes</link> or <link linkend="controls-radio-buttons">radio buttons</link> are usually
        preferable, as they allow more descriptive labels and are less
        easily-confused with other types of control.</para>
      </listitem>

      <listitem>
        <para>Only use toggle buttons in groups, so they are not mistaken for
        regular buttons. Make the group behave like either a group of check
        boxes or a group of radio buttons, as required.</para>
      </listitem>

      <listitem>
        <para>Provide an access key in the label of all toggle buttons that
        allows the user to set or unset the button directly from the keyboard.</para>
      </listitem>

      <listitem>
        <para>Label a group of toggle buttons with a descriptive heading above
        or to the left of the group, as you would with a group of check boxes
        or radio buttons.</para>
      </listitem>

      <listitem>
        <para>Use a frame around the group of buttons if necessary, but
        remember that blank space often works just as well and results in a
        less visually-cluttered dialog.</para>
      </listitem>

      <listitem>
        <para>Try to align groups of toggle buttons horizontally rather than
        vertically. This is how toggle buttons normally appear on a toolbar,
        so the user will be more familiar with this arrangement.</para>
      </listitem>

      <listitem>
        <para>Do not leave any space between toggle buttons in a group,
        otherwise they may look unrelated or may be mistaken for regular
        buttons.</para>
      </listitem>

      <listitem>
        <para>Use <link linkend="layout-capitalization">header capitalization</link>
        for toggle button labels, for example <guibutton>No Wallpaper</guibutton>,
        <guibutton>Embossed Logo</guibutton>.</para>
      </listitem>

      <listitem>
        <para>If your toggle button can display text, an icon, or both, choose
        which to display at runtime according to the user's setting in the
        GNOME Menus and Toolbars preference dialog.</para>
      </listitem>

      <listitem>
        <para>Use the same text or graphical label for a toggle button whether
        it is set or unset.</para>
      </listitem>

      <listitem>
        <para>If the toggle button represents a setting in a multiple
        selection that is set for some objects in the selection and unset for
        others, show the button in its mixed state. For example:</para>

        <figure>
          <title>Toggle buttons (right) showing properties for a multiple
          selection of shapes in a drawing application (left)</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="108" fileref="images/controls-toggle-button-mixed.png" format="PNG" width="467"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-toggle-button-mixed.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Toggle buttons showing the Thick, Thin and Dashed
              drawing styles of two selected shapes in a drawing application.
              One shape is drawn in the thick style, the other in the dashed
              style. The Thick and Dashed toggle buttons are therefore shown
              in their mixed state, and the Thin toggle button is unset.</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <!-- CB-Fig: There's probably a better figure for fig 16 than this one. Also, my 2 cents on the mixed state visual issue: mixed state MUST be visually DISTINCT from "set." What I see here isn't enough (I know this isn't set yet.) -->

        <remark>At time of writing, the exact visual appearance of mixed state
        toggle buttons was undecided. A mixed state toggle button should
        behave exactly as a mixed state check box or radio button, depending
        on whether the toggle button choices are independent or mutually
        exclusive, respectively.</remark>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="controls-option-menus">
    <title>Listas desplegables</title>

    <para>Drop-down lists are used to select from a mutually exclusive set of
    options. They can be useful when there is insufficient space in a window
    to use a group of radio buttons or a single-selection list, with which
    they are functionally equivalent.</para>

    <figure>
      <title>A drop-down list showing current selection (left) and the list of
      available choices when clicked on (right)</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="178" fileref="images/controls-option-menu.png" format="PNG" width="377"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-option-menu.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Two images, one of a drop-down list displaying its current
          setting, and the other showing its popup menu of available choices
          when clicked on</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!-- CB-Fig: Callouts, shortened caption.  This can probably be collapsed into one snapshot. -->

    <para>Recomendaciones:</para>

    <itemizedlist>
      <listitem>
        <para>Do not use drop-down lists with fewer than three items, or more
        than about ten. To offer a choice of two options, use <link linkend="controls-radio-buttons">radio buttons</link> or <link linkend="controls-toggle-buttons">toggle buttons</link>. To offer a
        choice of more than ten options, use a <link linkend="controls-lists">list</link>.</para>
      </listitem>

      <listitem>
        <para>Do not initiate an action when the user selects an item from an
        drop-down list. However, if used in an instant-apply <link linkend="windows-utility">property or preference window</link>, update
        the setting that the menu represents immediately.</para>
      </listitem>

      <listitem>
        <para>Selecting an item from a drop-down list should not affect the
        values of any other controls. It may sensitize, insensitize, hide or
        show other controls, however.</para>
      </listitem>

      <listitem>
        <para>Label the drop-down list with a text label above it or to its left,
        using <link linkend="layout-capitalization">sentence capitalization</link>.
        Provide an access key in the label that allows the user to give focus
        directly to the drop-down list.</para>
      </listitem>

      <listitem>
        <para>Use <link linkend="layout-capitalization">sentence
        capitalization</link> for drop-down list items, for example
        <guilabel>Switched movement</guilabel></para>
      </listitem>

      <!-- CB-Ed: Change guilabel to something less literal-seeming: Menu item. -->

      <listitem>
        <para>Assign an access key to every drop-down list item. Ensure each
        access key is unique within the enclosing window or dialog, not just
        within the menu.</para>
      </listitem>

      <listitem>
        <para>Do not assign shortcut keys to drop-down list items by default. The
        user may assign their own shortcut keys in the usual way if they wish,
        however.</para>
      </listitem>

      <listitem>
        <para>Do not use a drop-down list in a situation where it may have to
        show a property of a multiple selection, as drop-down lists have no
        concept of mixed state. Use a group of radio or toggle buttons
        instead, as these can show set, unset or mixed states.</para>
      </listitem>

      <!-- CB-Fig: The bullet points probably could be illustrated in a main drop-down lists figure (17 would work) -->

      <listitem>
        <para>No use un submenú en una lista desplegable.</para>
      </listitem>
    </itemizedlist>

    <para>You should normally use <link linkend="controls-radio-buttons">radio
    buttons</link> or a <link linkend="controls-lists">list</link> instead of
    drop-down lists, as those controls present all the available options at once
    without any further interaction. However, drop-down lists may be preferable
    in a window where:</para>

    <itemizedlist>
      <listitem>
        <para>hay poco espacio disponible</para>
      </listitem>

      <listitem>
        <para>the list of options may change over time</para>
      </listitem>

      <listitem>
        <para>the contents of the hidden part of the menu are obvious from its
        label and the one selected item. For example, if you have an option
        menu labelled "Month:" with the item "January"
        selected, the user might reasonably infer that the menu contains the
        12 months of the year without having to look.</para>
      </listitem>
    </itemizedlist>

    <para>Drop-down lists can also be useful on toolbars, to replace a group of
    several mutually-exclusive toggle buttons.</para>
  </sect1>

  <sect1 id="controls-combo-boxes">
    <title>Drop-down Combination Boxes</title>

    <!-- 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>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 drop-down list is displayed</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="200" fileref="images/controls-combo.png" format="PNG" width="304"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-combo.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Two images, one of a drop-down combination box entry field displaying its
          current selection, and the other showing its drop-down list of
          available choices when clicked on</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!-- CB-Fig: callouts, shorten caption. -->

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Only use a drop-down combination box instead of a list, drop-down list or radio
        button group when it is important that the user be able to enter a new
        value that is not already amongst the list of pre-defined choices.</para>
      </listitem>

      <listitem>
        <para>Do not initiate an action when the user selects an item from the
        list in a drop-down combination box. If used in an instant-apply <link linkend="windows-utility">property or preference window</link>, update
        the setting represented by the drop-down combination box immediately if possible. If
        this isn't possible due to the contents of the entry field being
        invalid while the user is still typing into it, update the related
        setting when the drop-down combination box loses focus instead.</para>
      </listitem>

      <listitem>
        <para>If the user types a value into the drop-down combination box that is not already
        in the drop-down list, add it to the list when the drop-down combination box loses
        focus so they can select it next time.</para>
      </listitem>

      <listitem>
        <para>Interpret user input into a drop-down combination box in a case-insensitive way.
        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 drop-down list, unless your application makes a distinction
        between the different forms (which is usually a bad idea).</para>
      </listitem>

      <listitem>
        <para>Label the drop-down combination box with a text label above it or to its left,
        using <link linkend="layout-capitalization">sentence capitalization</link>.
        Provide an access key in the label that allows the user to give focus
        directly to the drop-down combination box.</para>
      </listitem>

      <listitem>
        <para>Use <link linkend="layout-capitalization">sentence
        capitalization</link> for the drop-down list items, for example
        <guilabel>Switched movement</guilabel>.</para>
      </listitem>

      <!-- CB-Ed: Make guilabel less literal: "List item." -->
    </itemizedlist>
  </sect1>

  <sect1 id="controls-scrollbars">
    <title>Barras de desplazamiento</title>

    <para>Often an object (such as a document or a list) will not be fit within
    the confines of its viewer control. In these cases a scrollbar can be affixed
    to the viewer control. The scrollbar alters which part of the object is
    currently visible inside the viewer control: it slides the view across the object
    in one axis (horizontal or vertical).</para>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Only display scrollbars when they are required for sliding the view. If
        an object fits inside the viewer control, don't draw scrollbars. If you are
        using a GtkScrolledWindow, call <function>gtk_scrolled_window_set_policy</function>
        setting the appropriate axis (or axes) to GTK_POLICY_AUTOMATIC.</para>
      </listitem>

      <listitem>
        <para>Do <emphasis>not</emphasis> use scrollbars as a replacement for a 
        <link linkend="controls-sliders">slider</link>. Scrollbars should only be
        used affixed to a view that they actively alter, not used as a generic
        continuous input control.</para>
      </listitem>

      <listitem>
        <para>Affix scrollbars to the right side of a viewer control (to slide the view
        vertically), or to the bottom side (to slide the view horizontally). Do <emphasis>not</emphasis>
        affix scrollbars on the top or left sides of a viewer control.</para>
      </listitem>

      <listitem>
        <para>Scrollbars should be aligned in both directions with the view they are
        affixed to on the axis they control. In other words, horizontal scrollbars
        should span the full length of the viewer control, and vertical scrollbars
        should span the full height of the viewer control.</para>
      </listitem>

      <listitem>
        <para>If both horizontal and vertical scrollbars are acting upon a view,
        alignment will require that small rectangle in the lower right corner where
        the horizontal and vertical scrollbars meet will be blank. This is OK.</para>
      </listitem>
       
      <listitem>
        <para>Scrollbars should affect the view to which they are affixed in realtime:
        as the user drags or clicks the view should change. Time lag will be
        disconcerting and negatively impact a users ability to navigate content inside
        the view.</para>
      </listitem>
    </itemizedlist>
  </sect1>



  <sect1 id="controls-lists">
    <title>Listas</title>

    <para>A list control allows the user to inspect, manipulate or select from
    a list of items. Lists may have one or more columns, and contain text,
    graphics, simple controls, or a combination of all three.</para>

    <!-- CB-Fig: Looks like a table, to me, complete with table row striping and column headers.  Lists are usually one column, scrollable... lists! Of text or, rarely, graphics which can be selected in order to be manipulated. Sorting also happens in tables, not lists, from my experience. -->

    <!-- CFB: It's not a table because there is no way to select or manipulate individual cells, only complete rows. -->

    <figure>
      <title>Una simple lista de dos columnas</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="149" fileref="images/controls-list.png" format="PNG" width="179"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-list.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Picture of list control containing two unsorted columns of
          text</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Always give list controls a label, positioned above or to the
        left of the list, in <link linkend="layout-capitalization">sentence
        capitalization</link>. Provide an access key in the label that allows
        the user to give focus directly to the list.</para>
      </listitem>

      <listitem>
        <para>Make the list control large enough that it can show at least
        four items at a time without scrolling. For lists of ten or more
        items, increase this minimum size as appropriate.</para>
      </listitem>

      <listitem>
        <para>If the list appears in a dialog or utility window, consider
        making the window and the list within it resizable so that the user
        can choose how many list items are visible at a time without
        scrolling. Each time the user opens this dialog, set its dimensions to
        those that the user last resized it to.</para>
      </listitem>

      <listitem>
        <para>Do not use lists with less than about five items, unless the
        number of items may increase over time. Use <link linkend="controls-check-boxes">check boxes</link>, <link linkend="controls-radio-buttons">radio buttons</link> or an <link linkend="controls-option-menus">drop-down list</link> if there are fewer
        items.</para>
      </listitem>

      <listitem>
        <para>Use cabeceras de columnas solo cuando:</para>

        <itemizedlist>
          <listitem>
            <para>la lista tiene más de una columna, o</para>
          </listitem>

          <listitem>
            <para>the list has only one column, but the user may wish to
            re-order the list. (This is rarely useful with single column
            lists).</para>
          </listitem>
        </itemizedlist>

        <para>In most other situations, column headers take up unnecessary
        space, and the extra label adds visual clutter.</para>
      </listitem>

      <listitem>
        <para>Always label column headers when used. If the column is too
        narrow for a sensible label, provide a tooltip for the column instead.
        Apart from its obvious use, this will help ensure that assistive
        technologies can describe the use of the column to visually impaired
        users.</para>
      </listitem>

      <listitem>
        <para>Consider using a check box list for multiple-selection lists, as
        these make it more obvious that multiple selection is possible:</para>

        <figure>
          <title>A simple check box list</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="133" fileref="images/controls-list-checkbox.png" format="PNG" width="160"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-list-checkbox.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Picture of list control with two columns. The first
              column consists of check boxes showing whether or not the
              corresponding item in the second column is selected for further
              action.</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <para>If you do this, you should normally set the list control itself
        to be single-selection, but this depends on the particular task for
        which it will be used.</para>
      </listitem>

      <listitem>
        <para>For multiple selection lists, show the number of items currently
        selected in a static text label below the list, for example,
        <guilabel>Names selected: 3</guilabel>. Such a label also makes it
        more obvious that multiple selection is possible.</para>
      </listitem>

      <listitem>
        <para>Consider providing <guibutton>Select All</guibutton> and
        <guibutton>Deselect All</guibutton> buttons beside multiple selection
        lists, if appropriate.</para>
      </listitem>
    </itemizedlist>

    <sect2 id="controls-lists-sortable">
      <title>Listar ordenables</title>
      <para>Users often prefer to sort long lists, either alphabetically or
	      numerically, to make it easier to find items. Allow users
	      to sort long or multi-column lists by clicking on the column
	      header they want to sort.
      </para>
      <itemizedlist><title>Guías</title>
	      <listitem><para>
		Indicate which column is currently sorted by showing an
		upward or downward facing arrow in its header:</para>
	  <informaltable frame="all">
            <tgroup align="left" cols="2">
                <thead>
	              <row>
		      <entry>Sort Order</entry>
                      <entry>Dirección de la flecha</entry>
		      <entry>Ejemplo</entry>
                    </row>
                </thead>
            <tbody>
                  <row>
		  <entry>Natural</entry>
		  <entry>Abajo</entry>
		 <entry>Alphabetical; smallest number first;
			  earliest date first; checked items first</entry>
                </row>
                  <row>
		  <entry>Invertido</entry>
		  <entry>Arriba</entry>
		  <entry>Reverse alphabetical; largest number first;
		  	most recent date first; unchecked items first)</entry>
                </row>
            </tbody>
             </tgroup>
              </informaltable>
      </listitem>
      <listitem><para>Clicking an unsorted column header sorts the 
		      column in natural order, indicated by showing a
		      down arrow in its header.</para></listitem>

      <listitem><para>Clicking a column header sorted in natural order
		      re-sorts it in reverse order, indicated by
		      showing an up arrow in its header.</para>
	      
		      <note><title>Un-sorting lists</title>
	    		<para> Occasionally, 
		      an unsorted state may be useful, for example to
		      show items in the order in which the user added 
		      them to the list.
		      In such cases, clicking a column sorted in reverse
		      order should un-sort it, indicated by removing the
		      arrow from the column header.</para>
	    	      <para>Usually, however,
		      this is better achieved by adding an extra column
		      that the user can sort in the usual way, such as a 
		      sequence
		      number column in this example.
      		</para></note>
	</listitem>

	</itemizedlist>

    </sect2>
  </sect1>

  <sect1 id="controls-trees">
    <title>Árboles</title>

    <para>A tree control allows the user to inspect, manipulate or select from
    a hierarchichal list of items. Trees may have one or more columns, and
    contain text, graphics, simple controls, or a combination of all three.</para>

    <tip>
      <title>Use los árboles con cuidado.</title>

      <para>Because of their complexity compared to other controls, novice and
      some intermediate users often have problems using and understanding tree
      controls. If your application is designed for that type of user, you
      might want to consider alternative ways of presenting the information,
      such as the Nautilus list or icon view, or the hierarchical browser
      lists found in <ulink url="http://www.gnustep.it/enrico/gworkspace/viewer.html">GNUstep's
      File Viewer</ulink>.</para>
    </tip>

    <figure>
      <title>A simple tree control with one level of hierarchy</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="277" fileref="images/controls-tree.png" format="PNG" width="343"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-tree.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Picture of tree control showing months of the year as top
          level nodes, and public holidays in those months as their children</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!-- CB-Fig: Trees are usually used for navigation, so it's probably best to illustrate a tree in that context (GnomeCC, for example). -->

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Always give tree controls a label, positioned above or to the
        left of the tree, in <link linkend="layout-capitalization">sentence
        capitalization</link>. Provide an access key in the label that allows
        the user to give focus directly to the tree.</para>
      </listitem>

      <listitem>
        <para>Use cabeceras de columna cuando:</para>

        <itemizedlist>
          <listitem>
            <para>el árbol tiene más de una columna</para>
          </listitem>

          <listitem>
            <para>the tree has only one column, but the user may wish to
            re-order the tree. This should rarely be true of single column
            trees.</para>
          </listitem>
        </itemizedlist>

        <para>In most other situations, column headers take up unnecessary
        space, and the extra label adds visual clutter.</para>
      </listitem>

      <listitem>
        <para>Always label column headers when used. If the column is too
        narrow for a sensible label, provide a tooltip for the column instead.
        Apart from its obvious use, this will help ensure that assistive
        technologies can describe the use of the column to visually impaired
        users.</para>
      </listitem>

      <listitem>
        <para>Consider using a check box tree for multiple-selection trees, as
        these make it more obvious that multiple selection is possible:</para>

        <figure>
          <title>A simple check box tree</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="297" fileref="images/controls-tree-checkbox.png" format="PNG" width="349"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-tree-checkbox.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Picture of tree control with two columns. The first
              column consists of check boxes showing whether or not the
              corresponding item in the second column is selected for further
              action.</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <para>If you do this, you should normally set the tree control itself
        to be single-selection, but this depends on the particular task for
        which it will be used.</para>
      </listitem>

      <listitem>
        <para>For multiple selection trees, show the number of items currently
        selected in a static text label below the tree, for example,
        <guilabel>Names selected: 3</guilabel>. Such a label also makes it
        more obvious that multiple selection is possible.</para>
      </listitem>

      <listitem>
        <para>Consider providing <guibutton>Select All</guibutton> and
        <guibutton>Deselect All</guibutton> buttons beside multiple selection
        trees, if appropriate to the task.</para>
      </listitem>
    </itemizedlist>

    <sect2 id="controls-trees-sortable">
	    <title>Árboles ordenables</title>
	    <para>As with lists, the user may find it useful to sort long or
	    multi-column trees. See the guidelines in 
	    <xref linkend="controls-lists-sortable"/> for 
	    more information.</para>
    </sect2>
  </sect1>

  <sect1 id="controls-notebooks">
    <title>Cuadernos de notas con pestaña</title>

    <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 analogous to the divider tabs in a ring binder or a file
    cabinet.</para>

    <figure>
      <title>Un control típico de cuaderno de notas con tres pestañas</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="270" fileref="images/controls-notebook.png" format="PNG" width="341"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-notebook.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Picture of notebook control with three tabs</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!-- CB-Fig: Maybe I'm off, so if I am, then just ignore, but I'm concerned with terminology in the HIG at this point; maybe it's just one of those wizard/druid issues that are just here to stay because GNOME is GNOME, but I think people are more familiar with the term "Tabs" instead of the term "Pages," and "Tabbed pane" instead of "notebooks."  That's what they are called in JLF, anyway.   Callouts would also be nice here. -->

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Do not put too many pages in the same notebook. If you cannot
        see all the tabs without scrolling or splitting them into multiple
        rows, you are probably using too many and should use a list control
        instead. See the <link linkend="controls-too-many-tabs">example below</link>.</para>
      </listitem>

      <listitem>
        <para>Label tabs with <link linkend="layout-capitalization">header
        capitalization</link>, and use nouns rather than verbs, for example
        <guilabel>Font</guilabel> or <guilabel>Alignment</guilabel>. Try to
        keep all labels in a notebook the same general length.</para>
      </listitem>

      <listitem>
        <para>Do not assign access keys to tab labels, as this means you
        cannot use those access keys for any other control on
        <emphasis>any</emphasis> of the notebook pages without conflict. Even
        if you are able to assign access keys that would not conflict, it is
        better not to as it may be impossible to avoid the conflict when your
        application is translated to other languages. Assign an access key to
        every other control on each page, however.</para>
      </listitem>

      <listitem>
        <para>Do not design a notebook such that changing controls on one page
        affects the controls on any other page. Users are unlikely to discover
        such dependencies.</para>
      </listitem>

      <listitem>
        <para>If a control affects only one notebook page, place it on that
        notebook page. If it affects every page in the notebook, place it
        outside the notebook control, for example beside the window's
        <guibutton>OK</guibutton> and <guibutton>Cancel</guibutton> buttons.</para>
      </listitem>

      <listitem>
        <para>Use tabs that are proportional to the width of their labels.
        Don't just set all the tabs to the same width, as this makes them
        harder to scan visually, and limits the number of tabs you can fit
        into the notebook without scrolling. For example:</para>

        <figure>
          <title>Fixed- and proportional-width tabs (preferred)</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="92" fileref="images/controls-notebook-tabs.png" format="PNG" width="475"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-notebook-tabs.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>Side-by-side comparison of one notebook whose tabs are
              all the same width, and one whose tabs are only wide enough to
              accommodate the tab labels. The latter takes up around 33% less
              screen space.</phrase>
            </textobject>
          </mediaobject>
        </figure>
      </listitem>

      <!-- CB-Fig: callouts, shorter caption -->

      <listitem>
        <para>Although the contents of each page in a notebook will take up a
        different amount of space, do not use larger than normal spacing
        around the controls in the "emptier" pages, and do not center
        the controls on the page.</para>
      </listitem>

      <listitem>
        <para>If your tab labels include icons, choose whether or not to show
        the icons at runtime based on the user's preference in the GNOME
        Menus and Toolbars desktop preferences dialog. Always show the text
        part of the label, however.</para>
      </listitem>
    </itemizedlist>

    <para>If you have more than about six tabs in a notebook, use a list
    control instead of tabs to switch between the pages of controls. For
    example:</para>

    <figure id="controls-too-many-tabs">
      <title>Use of list control where there would be too many tabs to fit
      comfortably in a notebook</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="200" fileref="images/controls-notebook-list.png" format="PNG" width="370"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-notebook-list.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Part of a window including a list control with 7 items, each
          item representing a category of settings such as
          "Appearance" and "Navigation". The controls in the
          rest of the window change depending on which item is selected in the
          list.</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <para>As in this example, place the list control on the left-hand side of
    the window, with the dynamic portion of the window immediately to its
    right. <remark>Should this be reversed for right-to-left locales?</remark></para>

	<sect2 id="controls-tab-status">
	  <title>Indicadores de estado</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 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>

  <sect1 id="controls-progress-bars">
    <title>Barras de progreso</title>

    <para>Progress bars are visual indicators of the progress of a task being
    carried out by the application, and provide important <link linkend="feedback-types">feedback</link>. For information on using a
    progress bar within a progress window, see <xref linkend="windows-progress"/>.</para>

    <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 three types of measured
    progress bars.</para>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Always use a measured progress bar when the length of a task can
        be precisely or approximately predicted. Otherwise, use an <link linkend="indeterminate-progress">indeterminate progress indicator</link>
        or a <link linkend="progress-checklists">checklist window</link>.</para>
      </listitem>

      <listitem>
        <para>Ensure that a measured-progress bar measures an operation's
        total time or total work, not just that of a single step. An exception
        is a progress bar that measures the total time or work of the current
        step in a progress checklist.</para>
      </listitem>
    </itemizedlist>

    <sect2 id="time-remaining">
      <title>Time-remaining Progress Indicator</title>

      <para>An animation consisting of a bar whose changing length indicates
      how much time remains in an operation, and text stating how much time
      remains before the operation will be complete. Time-remaining bars are
      the most useful type of progress bar.</para>

      <figure>
        <title>Una sencilla barra de progreso de «tiempo restante»</title>

        <mediaobject>
          <imageobject>
            <imagedata width="386" fileref="images/controls-progress-time.png" format="PNG" depth="38"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/controls-progress-time.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Un sencillo diálogo de progreso de tiempo restante</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <para>Use a time-remaining bar if your application will display an
      initial estimate of an operation's remaining time and then
      periodically display updated estimates. Each updated estimate should be
      based on changes that have occurred and that will cause the operation to
      finish more quickly or more slowly. If the operation will finish more
      slowly, your application can display an updated estimate that is greater
      than the estimate previously displayed.</para>
    </sect2>

    <sect2 id="typical-time">
      <title>Typical-time Progress Indicator</title>

      <para>A bar whose changing length indicates how much time remains if an
      operation takes as long as it typically does. Typical-time bars are the
      least precise type of measured-progress bar, but they are more useful
      than indeterminate-progress bars.</para>

      <figure>
        <title>A simple 'typical time remaining' progress bar</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="32" fileref="images/controls-progress-typical.png" format="PNG" width="385"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/controls-progress-typical.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>A simple 'typical time remaining' progress dialog</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <para>For some operations, you cannot estimate the time remaining or the
      proportion of work completed. However, if you can estimate the typical
      time for that operation, you can provide feedback with a typical-time
      bar.</para>

      <para>If your application overestimates the completed amount of work,
      the length of the bar can indicate "almost complete" until the
      operation is complete. If your application underestimates how much work
      is complete, the application can fill the remaining portion of the bar
      when the operation is complete.</para>
    </sect2>

    <sect2 id="indeterminate-progress">
      <title>Indeterminate-progress indicator</title>

      <para>An animated bar indicating only that an operation is ongoing, not
      how long it will take. One example is the "throbber" in a web
      browser. Indeterminate-progress bars are the least precise type of
      progress bar.</para>

      <figure>
        <title>A simple 'indeterminate time' progress bar; the slider
        moves from left-to-right and back again until the operation is
        complete</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="210" fileref="images/controls-progress-indeterminate.png" format="PNG" width="409"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/controls-progress-indeterminate.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>A simple 'indeterminate time' progress dialog,
            showing a slider moving back and forth until the operation is
            complete</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <!-- CB-Fig: Above figure may benefit from showing the slider away from the right or left edge; otherwise it looks like the other progress bars, slightly modified. -->

      <para>Use an indeterminate-progress bar to provide feedback only for
      operations whose duration you cannot estimate at all.</para>
    </sect2>
  </sect1>

  <sect1 id="controls-status-bars">
    <title>Barras de estado</title>

    <para>A statusbar is an area at the bottom of a window that can be used
    to display brief information about the status of the application.</para>

    <figure>
      <title>Una simple barra de estado</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="53" fileref="images/controls-status-bar.png" format="PNG" width="244"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-status-bar.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>A statusbar at the bottom of a document window, showing
          current zoom level and a status message indicating that the document
          has been modified since it was last saved</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!-- CB-Fig: callouts -->

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Use statusbars only in application or document windows. Do not
        use them in dialogs, alerts or other secondary windows.</para>
      </listitem>

      <listitem>
        <para>Only place a statusbar along the bottom of a window.</para>
      </listitem>

      <listitem>
        <para>Only use statusbars to display non-critical information. This
        might include:</para>

        <itemizedlist>
          <listitem>
            <para>general information about the document or application. For
            example, current connection status in a network application, or
            the size of the current document in a text editor.</para>
          </listitem>

          <listitem>
            <para>information about the task the user is currently performing.
            For example, while using the selection tool in a drawing
            application, "Hold Shift to extend the selection"</para>
          </listitem>

          <listitem>
            <para>progress of a background operation. For example,
            "Sending to printer", "Printing page 10 of 20",
            "Printing Complete".</para>
          </listitem>

          <listitem>
            <para>a description of the control or area of the window under the
            mouse pointer. For example, "Drop files here to upload
            them"</para>
          </listitem>
        </itemizedlist>

        <para>Remember that statusbars are normally in the user's
        peripheral vision, and can even be turned off altogether using the
        application's <menuchoice><guimenu>View</guimenu><guimenuitem>Status
        Bar</guimenuitem></menuchoice> menu item. The user may therefore never
        see anything you display there, unless they know when and where to
        look for it.</para>
      </listitem>

      <listitem>
        <para>When there is no interesting status to report, leave a status
        bar panel blank rather than displaying something uninformative like
        "Ready". This way, when something interesting does appear in
        the statusbar, the user is more likely to notice it.</para>
      </listitem>

      <listitem>
        <para>If you want to make all or part of your statusbar interactive,
        use the following conventions:</para>

        <itemizedlist>
          <!--<listitem><para>Raised or button-like appearance for areas that respond to a single click</para></listitem>-->

          <listitem>
            <para>Inlaid appearance for areas that respond to a double click</para>
          </listitem>

          <listitem>
            <para>Apariencia plana para áreas que no son interactivas</para>
          </listitem>
        </itemizedlist>

        <!-- CB-Ed: I have never seen a button in a statusbar area before.  I'll bet this is deprecated, or should be.  Do you have data to back this up?  And doesn't this conflict with one of the previous bullet points: Only use statusbars to display non-critical information?  A cancel button is certainly not trivial. -->

        <!-- CFB: removed this recommendation for now -->

        <para>In <xref linkend="status-bar-figure"/>, the appearance
        indicates that the left area would respond to a double click (perhaps
        by saving the document), and the progress indicator on the right is
        non-interactive.</para>

        <figure id="status-bar-figure">
          <title>Una barra de estado interactiva</title>

          <mediaobject>
            <imageobject>
              <imagedata depth="58" fileref="images/controls-status-bar-interactive.png" format="PNG" width="461"/>
            </imageobject>

            <imageobject>
              <imagedata fileref="images/controls-status-bar-interactive.eps" format="EPS"/>
            </imageobject>

            <textobject>
              <phrase>A statusbar with a text panel that responds to a double
              click, a button that responds to a single click, and a
              non-interactive progress area</phrase>
            </textobject>
          </mediaobject>
        </figure>

        <para>Ensure that double-clicking in the status area does not provide
        any functionality that is not also available in the main application
        menu bar, or by some other accessible means.</para>
      </listitem>

      <listitem>
        <para>Provide a drag handle in the bottom right corner of the status
        bar of resizeable windows. Subclasses of GtkStatusbar should use the
        drag handle provided by that class. A reimplementation of a status
        bar, which is discouraged, should also reimplement the GtkStatusbar
        drag handle in both appearance and function.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="controls-frames">
    <title>Marcos y separadores</title>

    <para>A frame is a box with a title that you can draw around controls to
    organise them into functional groups. A separator is a single horizontal
    or vertical line that you can use to divide windows into functional
    groups.</para>

    <para>Frames with a border around their perimeter have traditionally been
    used for denoting groups of related controls. This is advantageous because
    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>

    <para>Rather than using bordered frames, use frames without borders, bold
    labels to make the categories stand out, and indented contents. This,
    combined with good layout and spacing, is usually a better alternative to
    bordered frames.</para>

    <figure>
      <title>Preferred frame style, using bold labels, spacing and indentation</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="256" fileref="images/controls-frames.png" format="PNG" width="288"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-frames.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Frame showing the preferred style described above</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <figure>
      <title>Traditional frame style, using borders (deprecated)</title>

      <mediaobject>
        <imageobject>
          <imagedata depth="275" fileref="images/controls-old-frames.png" format="PNG" width="296"/>
        </imageobject>

        <imageobject>
          <imagedata fileref="images/controls-old-frames.eps" format="EPS"/>
        </imageobject>

        <textobject>
          <phrase>Frame showing the traditional style described above</phrase>
        </textobject>
      </mediaobject>
    </figure>

    <!--    <para>See <xref linkend="window-layout-spacing"/> for technical details on implementing the preferred frame style in gtk.</para> -->

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Before you add a frame with a visible border or separator to any
        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
        alignment.</para>
      </listitem>

      <listitem>
        <para>Do not mix framed and unframed groups in the same window.</para>
      </listitem>

      <listitem>
        <para>Do not nest one frame inside another. This results in visual
        clutter.</para>
      </listitem>

      <listitem>
        <para>If all the items in a group are disabled, disable the group title too.</para>
      </listitem>

    </itemizedlist>
  </sect1>
</chapter>


<chapter id="feedback">
  <title>Comentarios</title>

  <sect1 id="feedback-responsiveness">
    <title>Characteristics of Responsive Applications</title>

    <para>Although highly responsive applications can differ widely from one
    another, they share the following characteristics:</para>

    <itemizedlist>
      <listitem>
        <para>They give immediate feedback to users, even when they cannot
        fulfill their requests immediately.</para>
      </listitem>

      <listitem>
        <para>They handle queued requests as users would expect, discarding
        requests that are no longer relevant and reordering requests according
        to users' probable priorities.</para>
      </listitem>

      <listitem>
        <para>They let users do other work while long operations proceed to
        completion— especially operations not requested by users— such as
        reclaiming unused memory or other "housekeeping" operations.</para>
      </listitem>

      <listitem>
        <para>They provide enough feedback for users to understand what they
        are doing, and organize feedback according to users' abilities to
        comprehend and react to it.</para>
      </listitem>

      <listitem>
        <para>They let users know when processing is in progress.</para>
      </listitem>

      <listitem>
        <para>They let users know or estimate how long lengthy operations will
        take.</para>
      </listitem>

      <listitem>
        <para>They let users set the pace of work, when possible, and they let
        users stop requested tasks that have started but not finished.</para>
      </listitem>
    </itemizedlist>

    <!-- CB-Ed: Collapse some of the items in the list above, they are similar or have lots of overlap.  -->

    <para>Highly responsive applications put users in control by quickly
    acknowledging each user request, by providing continuous feedback about
    progress toward fulfilling each request, and by letting users complete
    tasks without unacceptable delays.</para>

    <para>Even applications with attractive, intuitive user interfaces can
    lack responsiveness. Typically, unresponsive applications have at least
    one of the following problems:</para>

    <itemizedlist>
      <listitem>
        <para>They provide late feedback— or no feedback— for users'
        requests, leaving users wondering what the application has done or is
        doing.</para>
      </listitem>

      <listitem>
        <para>When performing extended operations, they prevent users from
        doing other work or cancelling the extended operation.</para>
      </listitem>

      <listitem>
        <para>They fail to display estimates of how long extended operations
        will last, forcing users to wait for unpredictable periods.</para>
      </listitem>

      <listitem>
        <para>They ignore users' requests while doing unrequested
        "housekeeping", forcing users to wait at unpredictable times—
        often without feedback.</para>
      </listitem>
    </itemizedlist>

    <para>You can sometimes possible to improve an application's
    responsiveness without speeding up the application's code. For tips on
    how to make such improvements, see <xref linkend="feedback-responding-to-user"/>.</para>
  </sect1>

  <sect1 id="feedback-response-times">
    <title>Tiempos de respuesta aceptables</title>

    <para>Some user interface events require shorter response delays than
    others. For example, an application's response to a user's mouse
    click or key press needs to be much faster than its response to a request
    to save a file. The table below shows the maximum acceptable response
    delay for typical interface events.</para>

    <table frame="all">
      <title>Maximum acceptable response times for typical events</title>

      <tgroup align="left" cols="2">
        <thead>
          <row>
            <entry>Evento de IU</entry>

            <entry>Maximum Acceptable Response Time</entry>
          </row>
        </thead>

        <tbody>
          <row>
            <entry>Mouse click, pointer movement, window movement or resizing,
            keypress, button press, drawing gesture, other UI input event
            involving hand-eye co-ordination</entry>

            <entry>0.1 segundos</entry>
          </row>

          <row>
            <entry>Displaying progress indicators, completing ordinary user
            commands (e.g. closing a window), completing background tasks
            (e.g. reformatting a table)</entry>

            <entry>1.0 segundo</entry>
          </row>

          <row>
            <entry>Displaying a graph or anything else a typical user would
            expect to take time (e.g. displaying a new list of all a
            company's financial transactions for an accounting period)</entry>

            <entry>10.0 segundos</entry>
          </row>

          <row>
            <entry>Accepting and processing all user input to any task</entry>

            <entry>10.0 segundos</entry>
          </row>
        </tbody>
      </tgroup>
    </table>

    <para>Make each response delay in your application as short as possible,
    unless users need time to see the displayed information before it is
    erased. The acceptable response delay for each event is based on a typical
    user's sense that the event is a logical point at which to stop or
    pause. The greater that sense is, the more willingly the user will wait
    for a response. Verify that your application responds to users'
    requests within the limits listed in the table above. If your application
    cannot respond within those limits, it probably has one or more general
    problems caused by a particular algorithm or module.</para>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Verify that your application provides feedback within 100
        milliseconds (0.1 second) after each key press, movement of the mouse,
        or other physical input from the user.</para>
      </listitem>

      <listitem>
        <para>Verify that your application provides feedback within 100
        milliseconds (0.1 second) after each change in the state of controls
        that react to input from the user— for example, displaying menus or
        indicating drop targets.</para>
      </listitem>

      <listitem>
        <para>Verify that your application takes no longer than 1 second to
        display each progress indicator, complete each ordinary user command,
        or complete each background task.</para>
      </listitem>

      <listitem>
        <para>Verify that your application takes no longer than 10 seconds to
        accept and process all user input to any task—including user input to
        each step of a multistep task, such as a wizard.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="feedback-responding-to-user">
    <title>Respuesta a peticiones de usuario</title>

    <para>If your application takes too long to respond, users will become
    frustrated. Use these techniques to improve the responsiveness of your
    application.</para>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Display feedback as soon as possible.</para>
      </listitem>

      <listitem>
        <para>If you cannot display all the information that a user has
        requested, display the most important information first.</para>
      </listitem>

      <listitem>
        <para>Save time by displaying approximate results while calculating
        finished results.</para>
      </listitem>

      <listitem>
        <para>If users are likely to repeat a time-consuming command in rapid
        succession, save time by faking the command's effects instead of
        repeatedly processing the command. For example, if a user adds several
        rows to a table stored in a database, you might display each new row
        immediately but delay actually creating each new row in the database
        until the user finished adding all the rows.</para>
      </listitem>

      <listitem>
        <para>Work ahead. Prepare to perform the command that is most likely
        to follow the current command. That is, use idle time to anticipate
        users' probable next requests. For example, as the user of an
        email application reads the currently displayed new message, the
        application might prepare to display the next new message.</para>
      </listitem>

      <listitem>
        <para>Use background processing. Perform less important tasks —such as
        housekeeping— in the background, enabling users to continue working.</para>
      </listitem>

      <listitem>
        <para>Delay work that is not urgent. Perform it later, when more time
        is available.</para>
      </listitem>

      <listitem>
        <para>Discard unnecessary operations. For example, to move back
        several pages in a web browser, a user might click the browser's
        <guibutton>Back</guibutton> button several times in rapid succession.
        To display the final requested page more quickly, the browser might
        not display the pages visited between the current page and that final
        page.</para>
      </listitem>

      <listitem>
        <para>Use dynamic time management. At run time, change how your
        application prioritizes user input and other processing, based on the
        application's current state. For example, if a user is typing text
        in one word-processing document while printing another, the
        word-processing application might delay the printing task if the user
        shifts to an editing task (such as cutting and pasting text) that
        requires greater resources.</para>
      </listitem>

      <listitem>
        <para>In your application, display an estimate of how long each
        lengthy operation will take.</para>

        <itemizedlist>
          <listitem>
            <para>If a command might take longer than 5 seconds to complete
            its work on an object, allow users to interact with any parts of
            the object and parts of the application that are not directly
            affected by the command.</para>
          </listitem>

          <listitem>
            <para>If a command provides lengthy output, show partial results
            as they become available. Scroll the results (if necessary) until
            the user moves input focus to a component (e.g. a scrollbar or
            text area) involved in the scrolling.</para>
          </listitem>
        </itemizedlist>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="feedback-types">
    <title>Types of Visual Feedback</title>

    <para>You can use two types of visual feedback for operations in your
    application— pointer feedback and progress animations.</para>

    <sect2 id="pointer-feedback">
      <title>Pointer Feedback</title>

      <para>Pointer feedback changes the shape of the pointer. For example, a
      busy pointer indicates that an operation is in progress and that the
      user cannot do other tasks. A busy-interactive pointer indicates that an
      operation is in progress but the window is still interactive.</para>

      <figure>
        <title>Busy pointer (left) and Busy-Interactive pointer (right)</title>

        <mediaobject>
          <imageobject>
            <imagedata depth="28" fileref="images/feedback-pointers-busy.png" format="PNG" width="58"/>
          </imageobject>

          <imageobject>
            <imagedata fileref="images/feedback-pointers-busy.eps" format="EPS"/>
          </imageobject>

          <textobject>
            <phrase>Busy pointer (left) and busy-interactive pointer (right)</phrase>
          </textobject>
        </mediaobject>
      </figure>

      <!-- CB-Fig: Replace above figure with one that is cleaned up.  -->
    </sect2>

    <sect2 id="progress-animations">
      <title>Animaciones de progreso</title>

      <para>Progress animations show either how much of an operation is
      complete, or only that an operation is ongoing. Normally, these take the
      form of either a progress bar or a progress checklist.</para>

      <itemizedlist>
        <title>Guías</title>

        <listitem>
          <para>When displaying a progress animation, open it as soon as
          possible after you know it is required, and close it automatically
          as soon as the associated operation is complete.</para>
        </listitem>

        <listitem>
          <para>Use a measured-progress bar if your application can estimate
          either how long the operation will take, or what proportion of the
          operation is complete.</para>
        </listitem>

        <listitem>
          <para>If your application can make neither estimate, and the
          operation only has one step, use an <link linkend="indeterminate-progress">indeterminate-progress bar</link>.
          For operations with two or more steps, use a <link linkend="progress-checklists">progress checklist</link> that
          dynamically displays a check mark for each completed step.</para>
        </listitem>
      </itemizedlist>

      <sect3 id="progress-bars">
      <title>Barras de progreso</title>
      <para>For information on different types of progress bars and when to use
            them see <xref linkend="controls-progress-bars"/>.</para>

        <sect4 id="progress-windows-vs-status-bar">
          <title>Progress Windows vs. the Statusbar</title>

          <para>In an application where the <link linkend="windows-primary">primary
          windows</link> contain a <link linkend="controls-status-bars">status
          bar</link> (which in turn contains a progress bar), it will often be
          the case that an operation's feedback could be presented in
          either the statusbar or a <link linkend="windows-progress">progress
          window</link>. A rule of thumb is to use the statusbar when an
          operation is expected to take fewer than ten seconds, otherwise use
          a progress window. However, do consider the following when choosing
          between the two:</para>

          <itemizedlist>
            <listitem>
              <para>Opening a new window, particularly when an operation is
              short, can needlessly disrupt the user's workflow.</para>
            </listitem>

            <listitem>
              <para>Progress windows can convey more information.</para>
            </listitem>

            <listitem>
              <para>Multiple progress windows can be open at once, whereas
              only a single operation can be presented in a statusbar.</para>
            </listitem>

            <listitem>
              <para>Progress windows provide a <guibutton>Cancel</guibutton>
              button.</para>
            </listitem>
          </itemizedlist>
        </sect4>
      </sect3>

      <sect3 id="progress-checklists">
        <title>Ventanas de listas de comprobación</title>

        <para>A checklist window shows the sequence of stages in an operation.
        See <xref linkend="progress-window-checklists"/>.
	
	<figure><title>A Checklist Window</title>
	
	<mediaobject>
		<imageobject><imagedata fileref="images/feedback-checklist-running.png" format="PNG" width="336" depth="220"/></imageobject>
	<textobject><phrase>A
        checklist window showing a sequence of steps</phrase></textobject>
	
	<imageobject>
            <imagedata fileref="images/feedback-checklist-running.eps" format="EPS"/>
          </imageobject>
        </mediaobject>
	  
	  </figure></para>
      </sect3>
    </sect2>
  </sect1>

  <sect1 id="feedback-choosing">
    <title>Choosing Appropriate Feedback</title>

    <para>To determine which type of visual feedback to provide for a
    particular operation, consider these factors:</para>

    <itemizedlist>
      <listitem>
        <para>Whether your application can provide an estimate of the
        operation's progress.</para>
      </listitem>

      <listitem>
        <para>Whether the operation blocks the user from issuing further
        commands in your application.</para>
      </listitem>

      <listitem>
        <para>Whether your application has a dedicated space, such as a status
        bar, for indicating the status of operations.</para>
      </listitem>
    </itemizedlist>

    <para>The table below shows which type of feedback to provide for
    operations that usually take at least 1 second to finish. In the
    "Appropriate Feedback" column, "Internal progress
    animations" means progress animations displayed in an
    application's dedicated status area, and "External progress
    animations" means progress animations displayed somewhere other than
    in a dedicated status area— typically, in an alert box.</para>

    <table frame="all">
      <title>Visual feedback types for operations that take at least 1 second</title>

      <tgroup align="left" cols="4">
        <thead>
          <row>
            <entry>Typical Duration &gt; 5 seconds?</entry>

            <entry>User blocked from issuing further commands?</entry>

            <entry>Application has dedicated status area?</entry>

            <entry>Appropriate feedback</entry>
          </row>
        </thead>

        <tbody>
          <row>
            <entry>Sí</entry>

            <entry>Sí</entry>

            <entry>Sí</entry>

            <entry>Internal animation plus pointer feedback</entry>
          </row>

          <row>
            <entry>Sí</entry>

            <entry>Sí</entry>

            <entry>No</entry>

            <entry>Pointer feedback</entry>
          </row>

          <row>
            <entry>Sí</entry>

            <entry>No</entry>

            <entry>Sí</entry>

            <entry>Animación interna</entry>
          </row>

          <row>
            <entry>No</entry>

            <entry>Sí</entry>

            <entry>Sí</entry>

            <entry>Internal animation plus pointer feedback</entry>
          </row>

          <row>
            <entry>No</entry>

            <entry>Sí</entry>

            <entry>No</entry>

            <entry>External animation plus pointer feedback</entry>
          </row>

          <row>
            <entry>No</entry>

            <entry>No</entry>

            <entry>Sí</entry>

            <entry>Animación interna</entry>
          </row>

          <row>
            <entry>No</entry>

            <entry>No</entry>

            <entry>No</entry>

            <entry>Animación externa</entry>
          </row>
        </tbody>
      </tgroup>
    </table>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Use a busy pointer whenever users are blocked from interaction
        with your application for 1 second or longer. Display the busy pointer
        less than 1 second after the operation begins.</para>
      </listitem>

      <listitem>
        <para>If a command will likely take 10 seconds or longer to finish,
        provide a <guibutton>Stop</guibutton> or <guibutton>Cancel</guibutton>
        button, which can also be activated by pressing <keycap>Esc</keycap>,
        that lets users terminate the command's processing even if your
        application cannot undo the command's effects. See <xref linkend="feedback-interrupting"/>.</para>
      </listitem>

      <listitem>
        <para>When using an external animation, leave the window containing
        the animation on-screen for at least 1 second after the operation has
        completed, with a successful completion message. Change the
        <guibutton>Stop</guibutton> or <guibutton>Cancel</guibutton> button to
        an <guibutton>OK</guibutton> button during this period— pressing this
        button should close the window immediately.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="feedback-interrupting">
    <title>Permitir interrupciones</title>

    <para>Users sometimes need to stop a command— for example, because it is
    taking too long. Your application should let users stop commands in
    progress, even if stopping a command cannot undo or "roll back"
    all the command's effects.</para>

    <itemizedlist>
      <title>Guías</title>

      <listitem>
        <para>Place a <guibutton>Stop</guibutton> or <guibutton>Cancel</guibutton>
        button, which can also be activated by pressing <keycap>Esc</keycap>,
        near the progress animation for the interruptable command.</para>
      </listitem>

      <listitem>
        <para>Label the button <guibutton>Cancel</guibutton> if the whole
        operation can be cleanly abandoned with no side effects, leaving the
        system in the state it was in prior to the operation beginning.
        Terminate the command immediately when the user presses this button.</para>
      </listitem>

      <listitem>
        <para>Label the button <guibutton>Stop</guibutton> if the command can
        be interrupted, but its effects up to that point cannot (or should
        not) be reversed. When the user presses this button, open an alert box
        that warns of the potential side effects of stopping the command. The
        alert box should have only two buttons: one for continuing the
        command's processing, and one for immediately terminating it.</para>
      </listitem>

      <!-- CB-Fig: Figure here showing example alertbox in context (overlaying the progress animation in a dialog, etc.) with sample alerbox text. JLFDG AT p. 107 shows this. (Fig 66) -->
    </itemizedlist>

    <para>Alternatively, you can place the <guibutton>Stop</guibutton> or
    <guibutton>Cancel</guibutton> button near the control with which the user
    issued the command that needs to be stopped. Place the button here only
    if:</para>

    <itemizedlist>
      <listitem>
        <para>There is no progress animation for the command, or</para>
      </listitem>

      <listitem>
        <para>The progress animation is in a window's status area or in
        another location that lacks space for a <guibutton>Stop</guibutton> or
        <guibutton>Cancel</guibutton> button.</para>
      </listitem>
    </itemizedlist>

    <para>In the alert box that appears after pressing a
    <guibutton>Stop</guibutton> button, ensure the message and button labels
    in the alert box are specific and precise. Ambiguous button labels can
    cause users to terminate or continue a command unintentionally. For
    example, use:</para>

    <para><screen>Continue deleting files? <guibutton>[Continue Deleting]</guibutton>
    <guibutton>[Stop Deleting]</guibutton></screen></para>

    <para>rather than</para>

    <para><screen>Operation interrupted, continue? <guibutton>[Yes]</guibutton>
    <guibutton>[No]</guibutton></screen></para>

    <para>since in the latter example, it is not clear whether pressing
    <guibutton>Yes</guibutton> would continue the operation or continue the
    interruption (i.e. cancel the operation).</para>
  </sect1>
</chapter>



<chapter id="design">

  <title>Diseño visual</title>

  <para>Visual design is not just about making your application look pretty.  Good visual design is about communication.  A well-designed application will make it easy for the user to understand the information that is being presented, and show them clearly how they can interact with that information.  If you can achieve all that, your application <emphasis>will</emphasis> look good to the user, even if it doesn't have any fancy graphics or spinning logos!</para>
  <!-- GJM: This kind of folksy remark really is not appropriate at all. -->
  <!-- TODO:
  - More than any other section this needs to be liberally sprinkled with examples
  -->

  <!-- Color section based on Coleen's HTML draft -->

  <sect1 id="design-color">
    <title>Color</title>

    <para>El color es una buena herramienta para comunicar información en una interfaz de usuario. Por ejemplo, se puede usar para:</para>

    <itemizedlist>
      <listitem><para>strengthen a desktop's look and feel by enhancing a theme</para></listitem>
      <listitem><para>accent a dynamic alert in a system management application</para></listitem>
      <listitem><para>emphasize an element in a long list to expedite scanning</para></listitem>
      <listitem><para>add aesthetically pleasing details to an icon</para></listitem>
    </itemizedlist>

    <para>However, color should always be regarded as a useful addition to your design, not as a necessity. Never depend upon colors alone to display important information, and keep in mind that if colors cannot be perceived correctly (for example, the user has an 8-bit system, or is color-blind), your application should still be usable. </para>

    <sect2 id="Palette">
      <title>Paleta</title>
      
      <!-- primary contributor to the href="http://primates.ximian.com/~tigert/new_stock_project/" GNOME stock icon repository -->
      
      <para>A 32-color palette has been developed for the GNOME desktop. The palette may be downloaded from <ulink url="http://developer.gnome.org/projects/gup/images/ximian-palette">http://developer.gnome.org/projects/gup/images/ximian-palette</ulink>. To use it in The GIMP, save it to your <filename>~/.gimp_1.2/palettes</filename> folder, and restart The GIMP. A single, consistently-used palette helps give a unified look and feel to the desktop while minimizing visual distractions. If you need a color that is darker or lighter than the colors in this basic palette (e.g., for anti-aliasing), choose a color that is closest to the hue you need, then darken or lighten as required.</para>

      <figure><title>The basic GNOME 32-color palette</title>
	<mediaobject>
	  <imageobject><imagedata fileref="images/visdes-palette.png" format="PNG"/></imageobject>
	  <imageobject><imagedata fileref="images/visdes-palette.eps" format="EPS"/></imageobject>
	  <textobject><phrase>The basic GNOME 32-color palette</phrase></textobject>
	</mediaobject>
      </figure>
      
      <table frame="none"> 
	<title>RGB and hexadecimal values for the basic palette</title> 
	<tgroup cols="8" colsep="1" rowsep="0" align="left">
	  <thead> 
	    <row rowsep="1" valign="top"> 
	      <entry>Color</entry> 
	      <entry>Descripción</entry>
	      <entry>RGB</entry>
	      <entry>Hex</entry>
	      <entry>Color</entry>
	      <entry>Descripción</entry>
	      <entry>RGB</entry>
	      <entry>Hex</entry>
	    </row>
	  </thead>
	  <tbody valign="middle">
	    <row>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-1.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-1.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Basic 3D Hilight</entry>
	      <entry>234 232 227</entry>
	      <entry>#EAE8E3</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-2.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-2.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Basic 3D Medium</entry>
	      <entry>186 181 171</entry>
	      <entry>#BAB5AB</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-3.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-3.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Basic 3D Dark</entry>
	      <entry>128 125 116</entry>
	      <entry>#807D74</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-4.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-4.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Sombra 3D</entry>
	      <entry>86 82 72</entry>
	      <entry>#565248</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-5.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-5.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Green Hilight</entry>
	      <entry>197 210 200</entry>
	      <entry>#C5D2C8</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-6.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-6.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Green Medium</entry>
	      <entry>131 166 127</entry>
	      <entry>#83A67F</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-7.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-7.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Green Dark</entry>
	      <entry>93 117 85</entry>
	      <entry>#5D7555</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-8.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-8.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Green Shadow</entry>
	      <entry>68 86 50</entry>
	      <entry>#445632</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-9.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-9.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Red Hilight</entry>
	      <entry>224 182 175</entry>
	      <entry>#E0B6AF</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-10.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-10.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Red Medium</entry>
	      <entry>193 102 90</entry>
	      <entry>#C1665A</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-11.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-11.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Red Dark</entry>
	      <entry>136 70 49</entry>
	      <entry>#884631</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-12.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-12.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Red Shadow</entry>
	      <entry>102 56 34</entry>
	      <entry>#663822</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-13.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-13.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Purple Hilight</entry>
	      <entry>173 167 200</entry>
	      <entry>#ADA7C8</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-14.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-14.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Purple Medium</entry>
	      <entry>136 127 163</entry>
	      <entry>#887FA3</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-15.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-15.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Purple Dark</entry>
	      <entry>98 91 129</entry>
	      <entry>#625B81</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-16.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-16.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Purple Shadow</entry>
	      <entry>73 64 102</entry>
	      <entry>#494066</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-17.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-17.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Blue Hilight</entry>
	      <entry>157 184 210</entry>
	      <entry>#9DB8D2</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-18.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-18.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Blue Medium</entry>
	      <entry>117 144 174</entry>
	      <entry>#7590AE</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-19.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-19.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Blue Dark</entry>
	      <entry>75 105 131</entry>
	      <entry>#4B6983</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-20.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-20.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Blue Shadow</entry>
	      <entry>49 78 108</entry>
	      <entry>#314E6C</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-21.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-21.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Face Skin Hilight</entry>
	      <entry>239 224 205</entry>
	      <entry>#EFE0CD</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-22.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-22.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Face Skin Medium</entry>
	      <entry>224 195 158</entry>
	      <entry>#E0C39E</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-23.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-23.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Face Skin Dark</entry>
	      <entry>179 145 105</entry>
	      <entry>#B39169</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-24.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-24.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Face Skin Shadow</entry>
	      <entry>130 102 71</entry>
	      <entry>#826647</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-25.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-25.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Accent Red</entry>
	      <entry>223 66 30</entry>
	      <entry>#DF421E</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-26.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-26.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Accent Red Dark</entry>
	      <entry>153 0 0</entry>
	      <entry>#990000</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-27.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-27.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Accent Yellow</entry>
	      <entry>238 214 128</entry>
	      <entry>#EED680</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-28.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-28.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Accent Yellow Dark</entry>
	      <entry>209 148 12</entry>
	      <entry>#D1940C</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-29.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-29.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Accent Green </entry>
	      <entry>70 160 70</entry>
	      <entry>#46A046</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-30.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-30.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Accent Green Dark</entry>
	      <entry>38 199 38</entry>
	      <entry>#267726</entry>
	    </row>
	    <row> 
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-31.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-31.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Blanco</entry>
	      <entry>255 255 255</entry>
	      <entry>#ffffff</entry>
	      <entry><mediaobject>
		  <imageobject><imagedata fileref="images/visdes-palette-32.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-palette-32.eps" format="EPS"/></imageobject>
		</mediaobject></entry>
	      <entry>Negro</entry>
	      <entry>0 0 0</entry>
	      <entry>#000000</entry>
	    </row>
	  </tbody>
	</tgroup>
      </table>
      
    </sect2>
    
    <sect2 id="hsv">
      <title>Tono, brillo, contraste</title>
      
      <para>Users with vision disorders, such as color-blindness or low vision, require alternatives to default settings. A good user interface anticipates these needs by providing customizable preferences and support for accessible themes. Even better is an application that is already configured with carefully-chosen color and contrast defaults.</para>

      <para>An estimated 11% of the world population has some sort of color-blindness.  Those affected typically have trouble distinguishing between certain hues such as red and green (deuteranopia or protanopia), or blue and yellow (tritanopia). Therefore it is necessary to allow the user to customize colors in any part of your application that conveys important information. This means that your application must effectively convey information using just the colors from any theme that the user chooses.</para>
      
      <para>A useful tool for reviewing information about color-blindness and checking legibility of images for color-blind users is <ulink url="http://www.vischeck.com/">Vischeck</ulink>, an online tool that simulates the way an image or a website might appear to a user who has deuteranopia, protanopia, or tritanopia. </para>

      <figure><title>How the earth looks to a user with normal color vision (left), deuteranopia (middle), and tritanopia (right). (Images from <ulink url="http://www.vischeck.com">http://www.vischeck.com</ulink>).</title>
	
	<informaltable frame="none">
	  <tgroup cols="3" align="center">
	    <tbody valign="top">
	      <row>
		<entry>
	          <mediaobject>
		    <imageobject><imagedata fileref="images/visdes-colorblind-normal.png" format="PNG"/></imageobject>
		    <imageobject><imagedata fileref="images/visdes-colorblind-normal.eps" format="EPS"/></imageobject>
		    <textobject><phrase>Photo of earth as a normally-sighted user would see it</phrase></textobject>
		  </mediaobject>
	        </entry>
		
		<entry>
	          <mediaobject>
		    <imageobject><imagedata fileref="images/visdes-colorblind-deutan.png" format="PNG"/></imageobject>
		    <imageobject><imagedata fileref="images/visdes-colorblind-deutan.eps" format="EPS"/></imageobject>
		    <textobject><phrase>Photo of earth as a user with red-green color-blindness would see it</phrase></textobject>
		  </mediaobject>
	        </entry>
		<entry>
	          <mediaobject>
		    <imageobject><imagedata fileref="images/visdes-colorblind-tritan.png" format="PNG"/></imageobject>
		    <imageobject><imagedata fileref="images/visdes-colorblind-tritan.eps" format="EPS"/></imageobject>
		    <textobject><phrase>Photo of earth as a user with blue-yellow color-blindness would see it</phrase></textobject>
		  </mediaobject>
	        </entry>
	      </row>
	    </tbody>
	  </tgroup>
	</informaltable>
      </figure>


      <para>Other users have more problems with contrast levels rather than hue on their screen. Some users require a high level of contrast between background and foreground colors, such as black on white, white on black, or some other high-contrast combination. Others can experience discomfort unless they use low-contrast settings, such as gray text on a lighter gray background.</para>

      <para>You can meet these needs by ensuring your application supports the accessible GNOME themes (found in the gnome-themes module in cvs), which include high and low contrast themes, and large print themes. This means you must supply default and large sizes of high-, low- and regular-contrast icon sets with your application. </para>

      <itemizedlist><title>Guías</title>
	<listitem><para>Use the GNOME color palette. If you need a darker or lighter shade, start from one of the colors from the palette and darken or lighten as needed.</para></listitem>

	<listitem><para>Do not use color as the only means to distinguish items of information. All such information should be provided by at least one other method, such as shape, position or textual description.</para></listitem>

	<listitem><para>Ensure your application is not dependent on a particular theme. Test it with different themes, especially high and low contrast accessibility themes, which use fewer colors, to ensure your application respects the settings. For example, all text should appear in the foreground color against the background color specified in the chosen theme.</para></listitem>

	<listitem><para>Select colors carefully.  When they need to be recognizably different, select the light colors from orange, yellow, green or blue-green, and darker colors from blue, violet, purple or red, as most people affected by color-blindness already see blue, violet, purple and red as darker than normal.</para></listitem>

      </itemizedlist>

    </sect2>
  </sect1>

  <sect1 id="design-window">
    <title>Disposición de ventana</title>
    
    <sect2>
      <title>General</title> 

      <para>El emplazamiento de componentes visuales en una aplicación es importante porque las relaciones entre los elementos se indican por sus posiciones. Esto se llama «disposición» en el diseño de interfaces.</para>

      <para>Un diseño limpio es vital para crear un buen flujo visual de la información para el usuario. En esta sección se describe la colocación adecuada de los componentes y el espacio para su uso en aplicaciones GNOME. Los componentes principales que tratar serán las etiquetas, los iconos, botones de radio y casillas de verificación, campos de texto, botones de comandos y los menús desplegables.</para>

    </sect2>

    <sect2 id="layout-dialogs">
      <title>Diálogos</title>
      
      <para>When a user is scanning a complex preferences dialog consisting of many labels and corresponding check boxes, text fields, and drop-down combination boxes, it is easy to see how she can quickly become hindered by poor layout in the visual design. For information on laying out Alerts, see <xref linkend="alert-spacing"/></para>

      <figure id="improved-layout-figure"><title>Disposición de la ventana mejorada</title>
	
	<informaltable frame="none">
	  <tgroup cols="2" align="center">
	    <tbody valign="top">
	      <row>
		<entry>
	          <mediaobject>
		    <imageobject><imagedata fileref="images/visdes-layout-poor.png" format="PNG"/></imageobject>
		    <imageobject><imagedata fileref="images/visdes-layout-poor.eps" format="EPS"/></imageobject>
		    <textobject><phrase>Initial layout with poor alignment and limited use of white space</phrase></textobject>
		  </mediaobject>
	        </entry>
		
		<entry>
	          <mediaobject>
		    <imageobject><imagedata fileref="images/visdes-layout-good.png" format="PNG"/></imageobject>
		    <imageobject><imagedata fileref="images/visdes-layout-good.eps" format="EPS"/></imageobject>
		    <textobject><phrase>Improved layout with fewer alignment points, frames removed to relieve clutter, and clearer grouping with use of white space</phrase></textobject>
		  </mediaobject>
	        </entry>
	      </row>
	    </tbody>
	  </tgroup>
	</informaltable>
      </figure>

      <!-- picture here of a complex preferences dialog, badly designed: right-aligned similar length labels, very little spacing between elements (vertically), varying spaces between elements (horizontally) -->

      <para>In <xref linkend="improved-layout-figure"/>, the dialog on the left presents labels which are not left-aligned. The user's eye is not given a proper anchor to scan the dialog quickly.</para>

      <para>As the labels are all similar in length, they should be left-aligned. Now the user has a firm left margin to anchor the eye and scan the list of items vertically more easily. If most of the labels in a group greatly differ in length, right-align them instead, so that the controls do not end up too far away from their corresponding labels.</para>

      <para>Using frames with visible borders to separate groups within a window is deprecated. Use spacing and bold headers instead. This is more effective because there are fewer gratuitous lines to distract the user from the main content in the window. See <xref linkend="controls-frames"/> for more details.</para>

      <para>Try to keep components consonant with each other in terms of size and alignment. This is particularly important within a group of controls, so that the user's ability to quickly scan information is not sacrificed.  Minimize as much as possible the need for the user's eye to jump around when scanning a layout.</para>
      
      <figure id="layout-callouts-figure"><title>Especificaciones de la disposición</title>
	
	<mediaobject>
	  <imageobject><imagedata fileref="images/visdes-layout-annotated.png" format="PNG"/></imageobject>
	  <imageobject><imagedata fileref="images/visdes-layout-annotated.eps" format="EPS"/></imageobject>
	  <textobject><phrase>Improved layout with fewer alignment points, frames removed to relieve clutter, and clearer grouping with use of white space</phrase></textobject>
	</mediaobject>
      </figure>
      
      <!-- Figure here of the above paragraph, giving examples -->

      <itemizedlist> <title>Guías</title>
	<listitem><para>Leave a 12-pixel border between the edge of the window and the nearest controls.</para></listitem>
	<listitem><para>Leave a 12-pixel horizontal gap between a control and its label.  (The gap may be bigger for other controls in the same group, due to differences in the lengths of the labels.)</para></listitem>
	<listitem><para>Labels must be concise and make sense when taken out of context.  Otherwise, users relying on screenreaders or similar assistive technologies will not always be able to immediately understand the relationship between a control and those surrounding it.</para></listitem>
	<!--		<listitem><para>Assign access keys to all editable controls.  Ensure that labels immediately precede their associated control in the tab order, so that the access key will focus to or activate the correct control when pressed.</para></listitem>
	<remark>GJM: I almost missed this instance of this error which is repeated below; except that it says mnemonic instead of access key. This entire section is a repeat, it seems. Adding restated listitem.</remark>
	-->
	<listitem><para>Assign access keys to all editable controls. Ensure that using the access key focuses its associated control.</para></listitem>
      </itemizedlist>

    </sect2>

<!-- 
I'm commenting out this section for the HIG 2.8 release pending "still needs more work" -Seth

    <sect2 id="layout-window-size">
	<title>Size</title>
	<remark>This section taken from Alan's draft in bug #111772, still needs some work</remark>
	<para>GNOME is used on by many different people on a wide variety of
different hardware.  This includes people with older hardware and 
small displays.  Laptop users and users of other portable devices also
need to be able to work on smaller screens. Users who require large fonts, or assistive technologies that take over part of the screen, also have a correspondingly smaller area in which to display application windows and dialogs.</para> 

<para>While these space restrictions are intended primarily to allow people
with smaller displays to use Gnome it is also good discipline to keep
windows and dialogs clear with not to many concepts all at once. 
<remark>The sentiment of this
paragraph might be useful although it would need to be massively
rephrased-AH.</remark></para>

	<itemizedlist><title>Guidelines</title>

	<listitem><para>Try to ensure that the size of a window is no larger than 480 pixels
wide and 640 pixels hight in the default theme (including window
decorations).  Ideally your application should be usable at 600 by 400
pixels which leaves enough room for both top and bottom Panels.</para></listitem>  

	<listitem><para>The Ratio of the screen width to height is 2:3 and things will look
aesthetically pleasing if we can keep (near to) this proportion. <remark>This ratio isn't always the case these days, with widescreen monitors and PDA-type devices becoming more common-CB</remark>.  
<remark> The
space take by window decorations largely spoils this idealism-AH.</remark>
Dialogs [like a properties dialog] should [probably] be 300 by 400.  
Message Dialogs should be 600 by 200.<remark> I'm not sure specifying pixel dimensions for anything we don't really have to is such a good plan- perhaps just stick to the 'golden ratio' guideline that currently lives in next section?- CB.</remark></para></listitem>
	</itemizedlist>

	</sect2>

-->

    <sect2 id="window-layout-spacing">
      <title>Espaciado y alineación</title>
      
      <para>Provide adequate space between controls and groups of controls. This white space will make it easier for the user to find the information they need.</para>

      <itemizedlist><title>Guías</title>

	<listitem><para>As a basic rule of thumb, leave space between user interface components in increments of 6 pixels, going up as the relationship between related elements becomes more distant. For example, between icon labels and associated graphics within an icon, 6 pixels are adequate. Between labels and associated components, leave 12 horizontal pixels. For vertical spacing between groups of components, 18 pixels is adequate. A general padding of 12 pixels is recommended between the contents of a dialog window and the window borders.</para></listitem>
	
	<listitem><para>Break long lists of choices into smaller groups. For lists of less than about eight items, use radio buttons or check boxes. For longer lists, use a list control or drop-down list.</para></listitem>
	
	<listitem><para>Try to keep elements of the same type left-aligned with each other. For instance, in <xref linkend="layout-callouts-figure"/>, the group titles (<guilabel>General</guilabel> and <guilabel>Actions</guilabel>) are left-aligned and justified with each other.</para></listitem>

	<listitem><para>Indent group members 12 pixels to denote hierarchy and association.</para></listitem>
	<listitem><para>Minimize the number of alignment points in your window. An alignment point is an imaginary vertical or horizontal line through your window that touches the edge of one or more labels or controls in the window.</para></listitem>

	<listitem><para>Right-justification within groups or the overall window (as indicated by the line labelled "justification" in <xref linkend="layout-callouts-figure"/> is pleasing to the eye, but not crucial.</para></listitem>
	
	<listitem><para>Lay out components left-to-right, top-to-bottom. Generally, the first element the user is meant to encounter should be in the top-left, and the last in the bottom right. Keep in mind that when localized for non-western locales, interfaces may be reversed so that they read from right to left.</para></listitem>
	
	<listitem><para>Using "white" or blank spacing and indentation to delineate groups is cleaner and preferable to using graphical separators such as frames.
	  </para></listitem>
	
	<listitem><para>Align controls in your layout <emphasis>exactly</emphasis>. The eye is very sensitive to aligned and unaligned objects. If nothing lines up with anything else in a window, it will be very hard for the user to scan the contents and find the information he wants. Two things that almost line up, but not quite, are equally distracting.</para></listitem>
	
	<listitem><para>Be consistent. Use the same spacing, alignment, and component sizes in all dialogs appearing in your application. The <guibutton>OK</guibutton> and <guibutton>Cancel</guibutton> buttons, for example, should all appear exactly 12 vertical and horizontal pixels from the lower right corner of every dialog window.</para></listitem>
	
	<listitem><para>Ensure that light and dark areas as well as spacing are equally distributed around the window. Keep in mind that every control or group of controls in your window has a visual "weight," depending on its overall size, color, and how much white space it includes. Darker, larger areas are "heavier," while paler, smaller areas are "lighter."</para></listitem>
	
	<listitem><para>Do not design windows that are more than 50% longer in one dimension than in the other. People are more comfortable looking at windows and dialogs whose dimensions stay within the golden ratio (about 1.6 to 1), a ratio that artists and architects have used to create aesthetically-pleasing paintings and buildings for thousands of years.</para></listitem>
	
	<!-- <para><listitem>Do not resize components to fit arbitrary or uncommon layout needs. Make it a practice to use GtkTables, GtkVBox and GtkHBox container widgets at their default /* Calum, is there such a thing? */ row, column and border sizes. This will help ensure that a lot of layout and alignment work is done for you automatically.</para></listitem>-->
	
      </itemizedlist>
      <!--
      <note id="frame-layout-tech"><title>Technical Details for Proper Layout</title>
      <para>Set <property>Border Width</property> for the GtkDialog to <userinput>12</userinput>. Place a GtkVBox containing as many rows as you wish to have categories inside the control area of the GtkDialog, and set the <property>Spacing</property> for the GtkVBox to <userinput>18</userinput>.</para>
      <para>In turn, each category should be composed of a GtkVBox with two rows. Set the <property>Spacing</property> to <userinput>6</userinput>.
      <itemizedlist>
      <listitem><para>In the top row, place a label for the category header. Make the label bold using the Pango markup <programlisting>&lt;span weight="bold"&gt;<replaceable>Category Header</replaceable>&lt;/span&gt;</programlisting> Set the label property <property>Use Markup</property> to <userinput>Yes</userinput>, and <property>X Align</property> to <userinput>0.0</userinput> to left align the label.</para></listitem>
      <listitem><para>Place a 2-columned GtkHBox in the lower row of the top-level GtkVBox.
      <itemizedlist>
      <listitem><para>In the left column, place a label containing four space characters. This will serve to indent the category contents.</para></listitem>
      <listitem><para>In the right column, place a GtkVBox containing a row per control you wish to place in the category. Set the <property>Spacing</property> to <userinput>6</userinput>.
      <itemizedlist>
      <listitem><para>For left-side labelled controls such as text boxes, drop-down lists, and many others, place a 2 columned GtkHBox inside the row with a label in the left column and the corresponding control in the right. Set the <property>Spacing</property> on the GtkHBox to <userinput>6</userinput>. Place all labels such as this (for the whole window) in the same GtkSizeGroup (there is currently no way to do this using only Glade, you will have to use code as well). This will align the controls to their right, even between categories, which is important for allowing quick visual scans.</para></listitem>
      <listitem><para>For right-side labelled controls such as check boxes and radio buttons, simply place them directly in the row.</para></listitem>
    </itemizedlist>
    </para></listitem>
    </itemizedlist>
    </para></listitem>
    </itemizedlist>
    </para>
    </note>
      -->
    </sect2>
    
  </sect1>

  <sect1 id="design-text-labels">
    <title>Etiquetas de texto</title>
    
    <para>To a user with normal vision, textual output provides the majority of the information and feedback in most applications. To a visually-impaired user who may not be able to see or understand any additional graphical output, clear textual output is critical. You must therefore choose and position text carefully on the screen, and leave the choice of fonts and sizes to the user, to ensure that all users are able to use your application effectively.</para>

    <sect2 id="layout-label-position">
      
      <title>Espaciado y alineación</title>

      <para>Use spacing and alignment of text uniformly throughout your application. A basic rule of thumb is to put space between user interface components in increments of 6 pixels, going up as the relationship between related elements becomes more distant.</para>

      <table id="label-placement-example">
	<title>ALineación y espaciado para diferentes elementos de texto</title>
	<tgroup cols="3" align="left">
	  <thead>
	    <row>
	      <entry>Elemento</entry>
	      <entry>Posicionamiento</entry>
	      <entry>Ejemplo</entry>
	    </row>
	  </thead>
	  
	  <tbody>
	    <row>
	      <entry>Iconos grandes (navegador de archivos)</entry>
	      <entry>Horizontally centered with and (6 pixels, if specification necessary)below large icon</entry>
	      <entry align="center" valign="middle">
		<mediaobject>
		  <imageobject><imagedata fileref="images/visdes-large-icon-label.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-large-icon-label.eps" format="EPS"/></imageobject>
		  <textobject><phrase>Large icon with text label centered below</phrase></textobject>
		</mediaobject>
	      </entry>
	    </row>
	    
	    <row>
	      <entry>Iconos pequeños (barra de herramientas)</entry>
	      <entry>Vertically centered with and (6 pixels, if specification necessary) to the right of small icons</entry>
	      <entry align="center" valign="middle">
		<mediaobject>
		  <imageobject><imagedata fileref="images/visdes-small-icon-label.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-small-icon-label.eps" format="EPS"/></imageobject>
		  <textobject><phrase>Small icon with text label to the right</phrase></textobject>
		</mediaobject>
	      </entry>
	    </row>
	    
	    <row>
	      <entry>List control label</entry>
	      <entry>6 pixels above and horizontally left aligned with list control or 12 pixels to the left of and horizontally top aligned with list control</entry>
	      <entry align="center" valign="middle">
		<mediaobject>
		  <imageobject><imagedata fileref="images/visdes-list-label.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-list-label.eps" format="EPS"/></imageobject>
		  <textobject><phrase>List control with text label horizontally aligned above</phrase></textobject>
		</mediaobject>
	      </entry>
	    </row>

	    <row>
	      <entry>Radio button and check box labels</entry>
	      <entry>6 pixels to the right of and vertically center aligned with radio button</entry>
	      <entry align="center" valign="middle">
		<mediaobject>
		  <imageobject><imagedata fileref="images/visdes-radiobutton-label.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-radiobutton-label.eps" format="EPS"/></imageobject>
		  <textobject><phrase>Radio button with text label to its right</phrase></textobject>
		</mediaobject>
	      </entry>

	    </row>

	    <row> 
	      <entry>Etiquetas de campo de texto</entry>
	      <entry>6 pixels to the left of and vertically center aligned with textfield control</entry>
	      <entry align="center" valign="middle">
		<mediaobject>
		  <imageobject><imagedata fileref="images/visdes-textbox-label.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-textbox-label.eps" format="EPS"/></imageobject>
		  <textobject><phrase>Textbox with text label to its left</phrase></textobject>
		</mediaobject>
	      </entry>
	    </row>
	    
	    <row>
	      <entry>Etiquetas de botón</entry>
	      <entry>12 pixels of padding to either side of centered text (and any accompanying graphic). If appearing in a group of buttons, longest button label sets button size, center all other button labels and accompanying graphics in same-sized buttons</entry>
	      <entry align="center" valign="middle">
		<mediaobject>
		  <imageobject><imagedata fileref="images/visdes-button-label.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-button-label.eps" format="EPS"/></imageobject>
		  <textobject><phrase>Botones con texto centrado</phrase></textobject>
		</mediaobject>
	      </entry>
	    </row>
	    <row> 
	      <entry>Other component labels (e.g., spin boxes, text fields </entry>
	      <entry>12 pixels between the longest text label and its associated component, all other text labels in component grouping left aligned with the longest label. All labels vertically center aligned with associated components</entry>
	      <entry align="center" valign="middle">
		<mediaobject>
		  <imageobject><imagedata fileref="images/visdes-other-labels.png" format="PNG"/></imageobject>
		  <imageobject><imagedata fileref="images/visdes-other-labels.eps" format="EPS"/></imageobject>
		  <textobject><phrase>Drop-down list with label to its left</phrase></textobject>
		</mediaobject>
	      </entry>
	    </row>
	  </tbody>
	</tgroup>
      </table>

      

      <itemizedlist><title>Guías</title>
	<listitem><para>If the label precedes the control it is labelling, end the label with a colon. For example, <guilabel>Email:</guilabel> to label a text field into which the user should type their email address. This helps identify it as a control's label rather than an independent item of text.  Some assistive technology screen review utilities may also use the presence of a colon to identify text as a control label.</para></listitem>
	
	<!--	<listitem><para>When you use static text to label a control, ensure that the label immediately precedes that control in the Tab order. This will ensure that the access key (underlined character) you assign to the label will move focus to or activate the correct control when pressed.</para></listitem> 
	<remark>GJM: This is just wrong. Glade may have an "auto" target for labels with mnemonics that
	works this way, but it isn't part of GTK+. Adding the next listitem, though it could be better written.</remark>
	-->
	<listitem><para>Ensure that a label with a mnemonic is associated with the control it labels.</para></listitem>

	<listitem><para>Left-align components and labels, unless all the labels in a group have very different lengths. If they do, right-align the labels instead, to ensure that no controls end up too far away from their corresponding labels.</para></listitem>

	<listitem><para>Choose label names carefully. Label objects with names that make sense when taken out of context. Users relying on screenreaders or similar assistive technologies will not always be able to immediately understand the relationship between a control and those surrounding it.</para></listitem>

	<listitem><para>Be consistent with label usage and semantics. For example, if you use the same label in different windows, it will help if it means the same thing in both windows. Equally, don't use labels that are spelled differently but sound the same, e.g., "Read" and "Red", as this could be confusing for users relying on screenreaders.</para></listitem>

	<listitem><para>Don't use the same label more than once in the same window.  This makes life difficult for users relying on tools like magnifiers or screen readers, which cannot always convey surrounding context to the user.</para></listitem>
	
	<listitem><para>Do not hard-code font styles and sizes. The user should be able to adjust all sizes and typefaces.</para></listitem>
	
	<listitem><para>Do not use more than two or three different fonts and sizes in your application, and choose visually distinct rather than similar-looking fonts in one window. Too many font sizes and styles will make the interface look cluttered and unprofessional, and be harder to read. In general, always use fonts from the current theme, and specify relative rather than absolute sizes.</para></listitem>
	
	<listitem><para>Do not use graphical backdrops or "watermarks" behind text, other than those specified by the user's chosen theme. These interfere with the contrast between the text and its background.  This can cause difficulty for users with visual impairments, who will therefore normally choose themes that always use plain backdrops.</para></listitem>
	
      </itemizedlist>
      
    </sect2>
    
    
    <sect2 id="layout-capitalization">
      
      <title>Capitalización</title>

      <para>Two styles of capitalization are used in GNOME user interface elements: 
	<variablelist> 
	  <varlistentry> 
	    <term>Header capitalization</term> 
	    <listitem> 
	      <para>Capitalize all words in the element, with the following exceptions:
		
		<itemizedlist> 
		  <listitem> 
		    <para>Articles: <emphasis>a</emphasis>, <emphasis>an</emphasis>, <emphasis>the</emphasis>.</para>
		  </listitem> 
		  <listitem> 
		    <para>Conjunciones: <emphasis>y</emphasis>, <emphasis>pero</emphasis>, <emphasis>para</emphasis>, <emphasis>no</emphasis>, <emphasis>por</emphasis>, <emphasis>ya</emphasis> ...</para>
		  </listitem> 
		  <listitem> 
		    <para>
		      Prepositions of three or fewer letters:
		      <emphasis>at</emphasis>, <emphasis>for</emphasis>, <emphasis>by</emphasis>,
		      <emphasis>in</emphasis>, <emphasis>to</emphasis> ... 
		    </para>
		  </listitem> 
		</itemizedlist> 
	      </para>
	    </listitem> 
	  </varlistentry> 
	  <varlistentry> 
	    <term>Capitalización de frase</term> 
	    <listitem> 
	      <para>
		Capitalize the first letter of the first word, and any other words
		normally capitalized in sentences, such as application names. 
	      </para>
	    </listitem> 
	  </varlistentry> 
	</variablelist> 
      </para>
     
	<para>
	The following table indicates the capitalization style to use for each type
	of user interface element. 
      </para>

      <table frame="topbot"> 
	<title>Capitalization Style Guidelines for User Interface
	  Elements</title> 
	<tgroup cols="2" colsep="0" rowsep="0" align="left">
	  <thead>
	    <row rowsep="1" valign="top"> 
	      <entry colname="col1" align="left" valign="top">Elemento</entry> 
	      <entry colname="col2" valign="top" align="left">Estilo</entry>
	    </row> 
	  </thead> 
	  <tbody> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top">
		
		Check box labels 
		
	      </entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top">Etiquetas de botón de comando</entry> 
	      <entry colname="col2" valign="top">Cabecera</entry> 
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top">Etiquetas de cabecera de columna</entry> 
	      <entry colname="col2" valign="top">Cabecera</entry> 
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">
		
		Desktop background object labels 
		
	      </entry>
	      <entry colname="col2" valign="top">Cabecera</entry>
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">Mensajes de diálogo</entry>
	      <entry colname="col2" valign="top">Frase</entry>
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top">
		
		Drop-down combination box labels 
		
	      </entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top">
		
		Drop-down list box labels 
		
	      </entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top">Etiquetas de campo</entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">Nombres de archivo</entry>
	      <entry colname="col2" valign="top">Frase</entry>
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">
		
		Graphic equivalent text: for example, Alt text on web pages 
		
	      </entry>
	      <entry colname="col2" valign="top">Frase</entry>
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top"> 
		
		Group box or frame labels 
		
	      </entry> 
	      <entry colname="col2" valign="top">Cabecera</entry> 
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top"> 
		
		Items in drop-down combination boxes, drop-down list boxes, and
		list boxes 
		
	      </entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top"> 
		
		List box labels 
		
	      </entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">Elementos de menú</entry>
	      <entry colname="col2" valign="top">Cabecera</entry>
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">Elementos de menú en aplicaciones</entry>
	      <entry colname="col2" valign="top">Cabecera</entry>
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">Títulos de menú en aplicaciones</entry>
	      <entry colname="col2" valign="top">Cabecera</entry>
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top">Etiquetas de botón de radio</entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top"> 
		
		Slider labels 
		
	      </entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row> 
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top"> 
		
		Spin box labels 
		
	      </entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row> 
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top"> 

		Tabbed section titles 
		
	      </entry>
	      <entry colname="col2" valign="top">Cabecera</entry>
	    </row>
	    <row valign="top"> 
	      <entry colname="col1" align="left" valign="top">
		
		Text box labels 
		
	      </entry> 
	      <entry colname="col2" valign="top">Frase</entry> 
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">
		
		Titlebar labels 
		
	      </entry>
	      <entry colname="col2" valign="top">Cabecera</entry>
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">Etiquetas de los botones de la barra de herramientas</entry>
	      <entry colname="col2" valign="top">Cabecera</entry>
	    </row>
	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">Consejos</entry>
	      <entry colname="col2" valign="top">Frase</entry>
	    </row>

	    <row valign="top">
	      <entry colname="col1" align="left" valign="top">
		
		Webpage titles and navigational elements 
		
	      </entry>
	      <entry colname="col2" valign="top">Cabecera</entry>
	    </row> 
	  </tbody> 
	</tgroup> 
      </table> 
	 <note><title>Guías de capitalización para otros idiomas</title>
	<para>Languages other than English may have different rules about capitalization.  For example, Swedish has no concept of Header capitalization. Contact the <ulink url="http://developer.gnome.org/projects/gtp/contact.html">GNOME Translation Project</ulink> if you are in doubt about how to capitalize labels in a particular language.</para>
	</note>

    </sect2>
  </sect1>

  <sect1 id="design-fonts">
    <title>Tipografías</title>
    <para>Only use the fonts that the user has specified in their theme, and in sizes relative to the default size specified in their theme.  This will ensure maximum legibility and accessibility for all users.</para>
    <para>Do not mix more than two or three font sizes and styles (underlined, bold, italicized) in one window, as this will look unprofessional and distract the user from the information being conveyed.</para>
    <para>Provide alternatives to WYSIWYG where applicable. Some users may need to print text in a small font but edit in a larger screen font, for example. Possible alternatives include displaying all text in the same font and size (both of which are chosen by the user); a "wrap-to-window" option that allows you to read all the text in a window without scrolling horizontally; a single column view that shows the window's contents in a single column even if they will be printed in multiple columns; and a text-only view, where graphics are shown as placeholders or text descriptions.</para>
  </sect1>
  </chapter>



<chapter id="icons">
  <title>Iconos</title>
  <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 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>
  </para>

  <sect1 id="icons-style">
    <title>Estilo</title>
    
    <para>GNOME uses a soft, three-dimensional look. This style is achieved by using antialiasing, shading and highlighting techniques. The <ulink url="http://developer.ximian.com/articles/tutorials/icons/"><citetitle>Gnome Icons</citetitle></ulink> tutorial details how one of GNOME's leading artists creates some of these effects.</para>
    <para>Components of an icon style can be broken down into several categories such as perspective, dimentionality, lighting effects and palette. These components play an important part in giving a group of icons a collectively distinctive look. For instance, the Java Look and Feel is recognizable by its use of a primary eight-color palette, interior highlighting and diagonal gradients. The Macintosh Aqua style is recognizable by its use of a cool palette based on blue, lighting effects mimicking reflectivity and antialiasing. The GNOME style exhibits a subdued thirty-two color palette, soft drop shadows and a mix between cartoonish and photorealistic graphics.</para>
    <table frame="topbot" pgwide="1">
      <title>A globe in different icon styles</title>
      
      <tgroup cols="3" colsep="0" rowsep="0" align="center">
	<thead>
	  <row valign="top">
	    <entry>Java Metal</entry>
	    <entry>MacOS/X Aqua</entry>
	    <entry>GNOME</entry>
	  </row>
	</thead>
	<tbody>
	  <row valign="middle">
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-style-java.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-style-java.eps" format="EPS"/></imageobject>
		<textobject><phrase>Java globe</phrase></textobject>
	      </mediaobject>
	    </entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-style-aqua.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-style-aqua.eps" format="EPS"/></imageobject>
		<textobject><phrase>Aqua globe</phrase></textobject>
	      </mediaobject>
	    </entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-style-gnome.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-style-gnome.eps" format="EPS"/></imageobject>
		<textobject><phrase>GNOME globe</phrase></textobject>
	      </mediaobject>
	    </entry>
	  </row>
	</tbody>
      </tgroup>
    </table>

    <sect2 id="icon_style_perspective">
      <title>Perspectiva</title>
      <remark>NO TRADUCIR</remark>
      <formalpara>
	<title>Perspectiva de tabla</title>
	<para>Presents objects as if they were sitting on a table or desk in front of the user.</para>
      </formalpara>
      <figure>
	<title>Illustration of the table perspective</title>
	<mediaobject>
	  <imageobject><imagedata fileref="images/icons-perspective-table.png" format="PNG"/></imageobject>
	  <imageobject><imagedata fileref="images/icons-perspective-table.eps" format="EPS"/></imageobject>
	  <textobject><phrase>illustration of the table perspective</phrase></textobject>
	</mediaobject>
      </figure>
      <formalpara>
	<title>Shelf perspective</title>
	<para>Presents objects as if they were propped up on a shelf at eye level. Make it look like a police line-up.</para>
      </formalpara>
      <figure>
	<title>Illustration of the shelf perspective</title>
	<mediaobject>
	  <imageobject><imagedata fileref="images/icons-perspective-shelf.png" format="PNG"/></imageobject>
	  <imageobject><imagedata fileref="images/icons-perspective-shelf.eps" format="EPS"/></imageobject>
	  <textobject><phrase>illustration of the shelf perspective</phrase></textobject>
	</mediaobject>
      </figure>
    </sect2>

    <sect2 id="icon_style_lighting">
      <title>Iluminación</title>
      <remark>NO TRADUCIR</remark>
      <formalpara>
	<title>Superior izquierda</title>
	<para>Design as if there is lighting coming from the upper left corner, with a soft drop-shadow cast within the icon's 48x48 (original design size) borders (120 degrees, 4 pixel distance, 4 pixel blur).</para>
      </formalpara>
      <formalpara>
	<title>Overhead</title>
	<para>Design as if there is a light source placed above the "camera", casting a shadow down.  </para>
      </formalpara>
    </sect2>

    <sect2 id="icon_style_palette">
      <title>Paleta</title>
      <remark>NO TRADUCIR</remark>
      <para>Icons should use colors based on the basic thirty-two color palette, darkening or lightening the colours to achieve the desired look. See <xref linkend="Palette"/></para>
    </sect2>

  </sect1>

  <sect1 id="icons-types">
    <title>Tipos de iconos</title>
    <table frame="all" pgwide="1" id="icon_specifications">
      <title>Especificaciones para los diferentes tipos de iconos usados en GNOME</title>
      <tgroup cols="4" colsep="1" rowsep="1" align="center">
	<thead>
	  <row>
	    <entry>Tipo del icono</entry>
	    <entry>Tamaños (píxeles)</entry>
	    <entry>Perspectiva</entry>
	    <entry>Fuente de luz</entry>
	    <entry>Ejemplos</entry>
	  </row>
	</thead>
	<tbody>
	  <row>
	    <entry>Objetos/iconos de documento</entry>
	    <entry>24x24, 48x48*, 96x96</entry>
	    <entry>Tabla</entry>
	    <entry>Superior Izquierda</entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-objects.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-objects.eps" format="EPS"/></imageobject>
		<textobject><phrase>variety of object icons</phrase></textobject>
	      </mediaobject>
	    </entry>
	  </row>
	  <row>
	    <entry>Iconos de aplicación</entry>
	    <entry>24x24, 48x48*</entry>
	    <entry>Tabla</entry>
	    <entry>Superior Izquierda</entry>
	    <entry>	
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-applications.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-applications.eps" format="EPS"/></imageobject>
		<textobject><phrase>variety of application icons</phrase></textobject>
	      </mediaobject>
	    </entry>
	  </row>
	  <row>
	    <entry>Iconos de barra de herramientas</entry>
	    <entry>24x24*, 48x48</entry>
	    <entry>Estantería</entry>
	    <entry>Overhead</entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-toolbar.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-toolbar.eps" format="EPS"/></imageobject>
		<textobject><phrase>variety of toolbar icons</phrase></textobject>
	      </mediaobject>
	    </entry>
	  </row>
	  <row>
	    <entry>Iconos de menú</entry>
	    <entry>16x16</entry>
	    <entry>Estantería</entry>
	    <entry>Overhead</entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-menu.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-menu.eps" format="EPS"/></imageobject>
		<textobject><phrase>variedad de iconos de menú</phrase></textobject>
	      </mediaobject>
	    </entry>
	  </row>
	</tbody>
      </tgroup>
    </table>
    <para>(* denotes the primary size for this kind of icon)</para>

    <sect2 id="document_icons">
      <title>Iconos de documentos</title>
      <para>If possible, document icons should convey the type of the file using a physical object. For example a good icon for MPEG video would be a movie reel. Failing the existence of an appropriate object, when a document type corresponds to a specific application, another option is to use a piece of paper with the corresponding application's icon overlayed it as the document icon. This may be appropriate for a document type such as an application's settings files.</para>
      <itemizedlist>
	<listitem><para>Do <emphasis>not</emphasis> display a piece of paper behind a document icon unless the document type has a use correspondence with physical paper (or a suitable object was not found and you are using the application icon). For example, the final state of most word processing documents is a piece of paper, so it is appropriate to use a piece of paper in the icon. On the other hand, a movie on the computer has little association with a piece of paper, so a piece of paper behind the movie reel primarily introduces <link linkend="icon_problems_extraneous_information">visual noise</link>. The use of a piece of paper in most or all document types creates an additional problem: it is harder to scan large numbers of icons because they do not possess <link linkend="icon_design_silhouettes">distinct outlines</link>. A useful technique for creating a subtle difference between document types with similar roles (for example, between "JPEG", "PNG", "GIF", etc) is to use different colours. Expert users who need to make this distinction frequently will become accustomed to these differences.</para></listitem>
	<listitem><para>Do <emphasis>not</emphasis> include a file extension in the icon. The document icon's job is not to convey such precise information but to allow for rapid visual distinction between documents. Additionally, this text will not be displayed in the user's preferred font and size. Because many document types are associated with multiple file extensions, a file extension embedded in the icon will also frequently be wrong. In a context where the file extension is actually useful, the application should composite the information onto the icon at runtime (thereby using the correct font and size, as well as getting the extension right).</para></listitem>
	<listitem><para>Do <emphasis>not</emphasis> customize document icons to a particular Nautilus theme. Document icons are likely to be used in conjunction with a variety of different icon themes, and should work well with all of them.</para></listitem>
      </itemizedlist>
    </sect2>

    <sect2 id="application_icons">
      <title>Iconos de aplicación</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>
    </sect2>

    <sect2 id="toolbar_icons">
      <title>Iconos de barra de herramientas</title>
      <para>The idea of a toolbar as a shelf filled with tools should be reflected in toolbar icons. Toolbar icons should have the perspective of being viewed head on, as if they were actually sitting on a shelf at eye-level. Some design guides refer to this perspective as "flush".</para>
      <itemizedlist>
	<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 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>

    <sect2 id="menu_icons">
      <title>Iconos de menú</title>
      <para>Principles of toolbar icon design should be followed with menu icons, just at a smaller size. Where a corresponding toolbar icon exists, a menu icon should mirror its design.</para>
    </sect2>
  </sect1>

  <sect1 id="icons-design">
    <title>Designing Effective Icons</title>
    <para>
      <tip><title>Rule of Thumb for Icon Metaphors</title><para>"If you have to think about an icon to 'get it', the metaphor is too complex"</para></tip>
    </para>
	
    <itemizedlist>
      <listitem>
	<formalpara>
	  <title>Design Functionally Suggestive Icons</title>
	  <para>Icons should be suggestive of the functionality with which they are associated. The best icon will suggest to the user the primary purpose of the program or operation without having to read accompanying text. Users recognize functionally suggestive icons more rapidly than other forms because they directly associate with a physical object or action.</para>
	</formalpara>
	<figure>
	  <title>Un icono funcional y sugerente para un procesador de textos</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icons-word-processor.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icons-word-processor.eps" format="EPS"/></imageobject>
	    <textobject><phrase>A document with a pencil writing on it</phrase></textobject>
	  </mediaobject>
	</figure>
	<figure>
	  <title>Un icono funcional y sugerente para subrayado</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icons-underline-text.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icons-underline-text.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Un carácter subrayado</phrase></textobject>
	  </mediaobject>
	</figure>
      </listitem>
      <listitem id="icon_design_silhouettes">
	<formalpara>
	  <title>Make Icon Silhouettes Distinct</title>
	  <para>It is important to make it easy to visually distinguish icons that will be used together, for example toolbar icons and document icons. The human visual system is excellent at making rapid distinctions between items based on shape, thus a good way to help your users sort through a large number of icons is to use different shapes. You can see the shape of an icon most clearly by turning it into a silhouette: blacken all areas of the icon which are not transparent.</para>
	</formalpara>
	<example>
	  <title>Distinct silhouettes from the GNOME icon theme</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icons-silhouette.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icons-silhouette.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Silhouettes of various toolbar icons</phrase></textobject>
	  </mediaobject>
	</example>
      </listitem>
    </itemizedlist>

    <!-- CB-Ed: Much of this section has good substance, but is communicated poorly.  There seem to be a lot of blanket statements, and the tone is subjective (e.g., text describing figure 12, the Gnumeric icon.  Stick just to the facts, or try to stay closely to objective language, and language that will not be presenting things in a way that can be argued with or questioned. -->
    <!-- Seth: Objective language does not present the entire picture. While its better for laying down hard and fast guidelines, it does not assist designers in understanding the motivation behind various decisions. This document covers the design *philosophy* as well as providing specific guidelines. This is in fact one of my major complaints about the Java guidelines relative to the MacOS guidelines. Java guidelines attempt to maintain a facade of scientific objectivity and in doing so fail to educate designers as well as failing to communicate the real dynamics of good design. Dealing with more subjective issues is particularly important because many of the readers of the GNOME guidelines will not be professional icon artists, or even graphic designers. -->
    

    <!-- FIXME: we need a short section that talks about finding useful metaphors and images for icons -->
    
    <sect2 id="icon_design_process">
      <title>Suggested Design Process For Toolbar and Menu Icons</title>
      <para>For accessibility reasons, you should create high and low contrast and large print versions of all icons, in addition to the regular size and contrast icon. A suggested process for conveniently integrating this into your icon design is as follows:</para>
      <orderedlist>
	<listitem>
	  <para>Draw the basic outline as close to 48x48 pixels as possible:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-1.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-1.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
	<listitem>
	  <para>Fill in with black and white to create detail. Do not add gratuities such as drop shadows or anti-aliasing:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-2.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-2.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
	<listitem>
	  <para>Use the finished image as the large print high contrast icon:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-3.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-3.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
	<listitem>
	  <para>GNOME will automatically scale it down to create the 24x24 high contrast icon:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-4.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-4.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
	<listitem>
	  <para>Or you may hand-create a 24x24 version, which will be superior in contrast and sharpness:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-5.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-5.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
	<listitem>
	  <para>Add color and anti-aliasing to the large print high contrast icon:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-6.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-6.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
	<listitem>
	  <para>Add gradients for a smooth, realistic effect:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-7.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-7.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
	<listitem>
	  <para>Add a drop shadow (120 degree global angle, 4 pixel distance, 4 pixel blur, 40% opacity), and use the finished image as the large print regular contrast icon:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-8.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-8.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
	<listitem>
	  <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>
	  </mediaobject>
	</listitem>
	<listitem>
	  <para>Create a layer with the large print regular contrast icon's same outline and size then overlay that on the color icon. Give the overlay layer 40% opacity, and use the finished image as the large print low contrast icon:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-10.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-10.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
	<listitem>
	  <para>GNOME will automatically scale it down to create the 24x24 low contrast icon:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-11.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-11.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
      <listitem>
	  <para>Or you may hand-create a 24x24 version, which will be superior in contrast and sharpness:</para>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/icon-design-process-12.png" format="PNG"/></imageobject>
	    <imageobject><imagedata fileref="images/icon-design-process-12.eps" format="EPS"/></imageobject>
	  </mediaobject>
	</listitem>
      </orderedlist>
    </sect2>

    <sect2 id="icon_problems">
      <title>Problemas que evitar</title>
      <itemizedlist>
	<listitem>
	  <formalpara>
	    <title>Avoid name suggestive icons</title>
	    <para>Some icons, such as the original Nautilus file manager icon, do not suggest the program's purpose, but instead suggest the program's name. This is less desirable than a functionally suggestive icon, because an extra layer of abstraction is added (rather than associating file management with an icon representing files, they have to associate file management with nautilus with an image of a nautilus shell). Additionally it makes it difficult for new users who may not know what "Nautilus" is, and hence will not recognize a shell icon as the file manager.</para>
	  </formalpara>
	  <figure>
	    <title>The original, name suggestive icon for Nautilus</title>
	    <mediaobject>
	      <imageobject><imagedata fileref="images/icons-nautilus.png" format="PNG"/></imageobject>
	      <imageobject><imagedata fileref="images/icons-nautilus.eps" format="EPS"/></imageobject>
	      <textobject><phrase>A picture of a nautilus shell</phrase></textobject>
	    </mediaobject>
	  </figure>
	</listitem>
	<listitem>
	  <formalpara>
	    <title>Do <emphasis>not</emphasis> include meaningful text in icons</title>
	    <para>Icons that contain the text of the program name in the icon. They effectively contain no metaphor or picture for the user to identify with, and are probably harder to read than the accompanying caption. Since icons draw the eyes, an icon that is harder to identify than text is potentially worse than no icon at all. Hence "text icons" should not be used. Moreover, text should be avoided in icons because it makes the icons difficult to translate. If there is text in icons it should not form words in your native language, a good metric for ensuring that the particular text is not lending to the meaning of the icon.</para>
	  </formalpara>
	  <figure>
	    <title>Text in the original GEdit icon</title>
	    <mediaobject>
	      <imageobject><imagedata fileref="images/icons-gedit.png" format="PNG"/></imageobject>
	      <imageobject><imagedata fileref="images/icons-gedit.eps" format="EPS"/></imageobject>
	      <textobject><phrase>The original GEdit icon, a rectangle containing the word "GEdit".</phrase></textobject>
	    </mediaobject>
	  </figure>
	</listitem>
	<listitem>
	  <formalpara>
	    <title>Do <emphasis>not</emphasis> rely on information your users will not have</title>
	    <para>Random icons appear to have no association with the application (except perhaps some odd connection in the mind of the developer). These icons should <emphasis>never</emphasis> be used and will likely serve to confuse the user more than help them. The icon's purpose should not be to "look pretty"; this is merely a very desirable side effect.</para>
			</formalpara>
	    <para>The SodiPodi project logo is a squirrel, which is used as the application icon. However, because the logo has no obvious connection <emphasis>to a user</emphasis>, it is a poor icon. Make sure that you are not relying on information that users won't necessarily possess.</para>
	  <figure>
	    <title>A seemingly random icon for SodiPodi</title>
	    <mediaobject>
	      <imageobject><imagedata fileref="images/icons-sodipodi.png" format="PNG"/></imageobject>
	      <imageobject><imagedata fileref="images/icons-sodipodi.eps" format="EPS"/></imageobject>
	      <textobject><phrase>Una ardilla</phrase></textobject>
	    </mediaobject>
	  </figure>
	</listitem>
	<listitem id="icon_problems_extraneous_information">
	  <formalpara>
	    <title>Do <emphasis>not</emphasis> include extraneous information</title>
	    <para>Remember that icons will often be viewed in a smaller form. Too much information may render the icon unintelligible when it is shrunk in size (e.g. to be placed on a panel, or in the tasklist). Too much information also makes it easier for users confuse the purpose of the application. For example, in user testing many users thought an older version of the Evolution icon (below) would launch a word processor. They were misled by the pencil and the paper, which could be seen as extraneous information: it is implicit that the mail program will allow you to write messages as well as receive them. A better icon might have been a simple envelope. Foremost in the icon designer's mind should be a consideration of the minimal visual elements necessary to express the purpose of the program.</para>
	  </formalpara>
	  <figure>
	    <title>Extraneous information - the Evolution icon</title>
	    <mediaobject>
	      <imageobject><imagedata fileref="images/icons-evolution.png" format="PNG"/></imageobject>
	      <imageobject><imagedata fileref="images/icons-evolution.eps" format="EPS"/></imageobject>
	      <textobject><phrase>El icono de Evolution</phrase></textobject>
	    </mediaobject>
	  </figure>
	  <para>
	    This Gnumeric icon (below) is a great icon except for the introduction of extra visual noise. The extra sheet of paper with the 'g' on it behind the spreadsheet and chart adds no significant value to the icon and provides extra visual distraction. In this case the contribution of the extraneous element to the appearance of the icon is negative. Simple, well-balanced icons look more attractive than cluttered icons. An improved icon might contain only the spreadsheet and chart; larger because they can use all of the space in the icon, and hence more visually distinct.
	  </para>
	  <figure>
	    <title>Extraneous information - the old Gnumeric icon</title>
	    <mediaobject>
	      <imageobject><imagedata fileref="images/icons-gnumeric.png" format="PNG"/></imageobject>
	      <imageobject><imagedata fileref="images/icons-gnumeric.eps" format="EPS"/></imageobject>
	      <textobject><phrase>El icono de Gnumeric</phrase></textobject>
	    </mediaobject>
	  </figure>
	</listitem>
	<listitem>
	  <formalpara>
	    <title>Do <emphasis>not</emphasis> include body parts in the icon</title>
	    <para> Because GNOME aims to be an international desktop, it needs to avoid imagery that is potentially offensive or crass to other cultures. A prime source of offensive imagery is various body parts in a number of different configurations. Aside from offensive gestures with the hands, arms or fingers; body parts that are considered "clean" in one culture (such as eyes), will be considered tasteless or gross to another (such as a nose). Based on a survey of icons in GNOME, body parts frequently appear in the least communicative icons (often "pointing" at some element in the icon); they are being used as an ineffective crutch for poor metaphor. In these situations body parts should <emphasis>not</emphasis> be used. Even in situations where the metaphor is appropriate (for example an eye representing the sawfish appearance capplet) it is better to avoid using a body part. Often body parts have been used in GNOME to suggest a human "choosing" or "using" something. This is normally an unnecessary point for the icon designer to make. People naturally attempt to understand objects in reference to themselves (show someone a bat and they will think of hitting something with the bat, show someone a tool and they will think of using it, etc). For example, the font selector shows a finger pointing to an "F" suggesting the user choosing between a series of fonts. A better icon would be the text "Aa" presented in an ornate font (calling attention to the font rather than the text). The user doesn't need to be told that they are "choosing" the font, they can infer that easily.</para>
	  </formalpara>
	  <figure>
	    <title>Using body parts - the font selector icon</title>
	    <mediaobject>
	      <imageobject><imagedata fileref="images/icons-font-selection-poor.png" format="PNG"/></imageobject>
	      <imageobject><imagedata fileref="images/icons-font-selection-poor.eps" format="EPS"/></imageobject>
	      <textobject><phrase>El icono selector de tipografía original</phrase></textobject>
	    </mediaobject>
	  </figure>	    
	  <figure>
	    <title>Un icono mejor para el selector de tipografía</title>
	    <mediaobject>
	      <imageobject><imagedata fileref="images/icons-font-selection-good.png" format="PNG"/></imageobject>
	      <imageobject><imagedata fileref="images/icons-font-selection-good.eps" format="EPS"/></imageobject>
	      <textobject><phrase>A simple replacement icon showing an ornate "Aa"</phrase></textobject>
	    </mediaobject>
	  </figure>
	</listitem>
	<listitem>
	  <formalpara>
	    <title>Do <emphasis>not</emphasis> base icons off word puns</title>
	      <para>This should be avoided for a couple reasons, the most obvious of which is that puns do not translate well. For example, representing the "system log monitor" as a log will likely be uncommunicative in languages other than English. Additionally, most users do not comprehend the word play until it is too late for the icon to assist them. Even after being familiar with the "system log monitor" being represented as a log, users do not form the association fast enough for the icon to assist through in scanning through menu entries. A popular instance of this problem was the proliferation of icons representing the "World Wide Web" as a spider web in the mid 1990s. Part of the value of icons is that they bypass linguistic comprehension and hence are complementary to captions, allowing users to utilize more areas of the mind than linguistic recognition (already used in scanning for captions) when they hunt for items.</para>
	  </formalpara>
	  <figure>
	    <title>Word play - System Log Monitor icon</title>
	    <mediaobject>
	      <imageobject><imagedata fileref="images/icons-system-log.png" format="PNG"/></imageobject>
	      <imageobject><imagedata fileref="images/icons-system-log.eps" format="EPS"/></imageobject>
	      <textobject><phrase>A tree log</phrase></textobject>
	    </mediaobject>
	  </figure>
	</listitem>
	<listitem>
	  <formalpara>
	    <title>Do <emphasis>not</emphasis> employ violent imagery</title>
	    <para>Just as words like "kill" and "slay" are inappropriate in interfaces, violent or destructive icons should be avoided. The "shut down" icon uses the image of an explosive detonation switch, presumably trying to convey the idea of ending something abruptly. However, this icon is likely to intimidate some users of the computer who will not want to click on the icon for fear of breaking something.</para>
	  </formalpara>
	  <figure>
	    <title>Destructive-looking Shutdown icon</title>
	    <mediaobject>
	      <imageobject><imagedata fileref="images/icons-shut-down.png" format="PNG"/></imageobject>
	      <imageobject><imagedata fileref="images/icons-shut-down.eps" format="EPS"/></imageobject>
	      <textobject><phrase>Un botón de detonación explosiva</phrase></textobject>
	    </mediaobject>
	  </figure>
	</listitem>
      </itemizedlist>
    </sect2>
    </sect1>

    <sect1 id="icons-design-accessible">
       <title>Diseñar iconos accesibles</title>
       <para>
	       The GNOME desktop includes accessible themes that make the desktop and the applications running on it accessible to users with a range of visual impairments. By default, these are:</para>
       <itemizedlist>
	       <listitem><para>un tema de alto contraste</para></listitem>
	       <listitem><para>un tema de alto contraste invertido</para></listitem>
	       <listitem><para>a large print theme</para></listitem>
       </itemizedlist>
       <para>Los siguientes temas de accesibilidad también están disponibles:</para>
       <itemizedlist>
	       <listitem><para>a high contrast large print theme</para></listitem>
	       <listitem><para>an inverse high contrast large print theme</para></listitem>
	       <listitem><para>un tema de bajo contraste</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
	       themes is used.</para>
	<tip><title>Iconos de bajo contraste</title>
	<para>Low contrast icon themes were deprecated in GNOME 2.22. It is no longer necessary to deliver low contrast icon equivalents. </para></tip>
       <sect2 id="icons-design-highcontrast">
	<title>Iconos de alto contraste</title>
	<para>
		High contrast icons are greatly simplified versions of an application's existing regular icons. They are drawn with two colors, black and white, and thicker borders. This style allows high contrast icons to be distinguishable when viewed by a user with a visual impairment. Below is an approximation of what well-designed high contrast icons look like when viewed by someone with a visual impairment.</para>
    <table frame="topbot" pgwide="1">
	    <title>Simulation of low vision user viewing high contrast icons</title>
      
      <tgroup cols="3" colsep="0" rowsep="0" align="center">
	<thead>
	  <row valign="top">
	    <entry>Descripción</entry>
	    <entry>Icono de alto contraste</entry>
	    <entry>Apariencia simulada</entry>
	  </row>
	</thead>
	<tbody>
	  <row valign="top">
		<entry>Libro</entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-hc-book.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-hc-book.eps" format="EPS"/></imageobject>
		<textobject><phrase>Icono de libro</phrase></textobject>
	      </mediaobject>
	    </entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-hc-book-blur.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-hc-book-blur.eps" format="EPS"/></imageobject>
		<textobject><phrase>Blurred Book icon</phrase></textobject>
	      </mediaobject>
	    </entry>
	  </row>
	  <row valign="top">
		<entry>CD-ROM</entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-hc-cdrom.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-hc-cdrom.eps" format="EPS"/></imageobject>
		<textobject><phrase>Icono CD-ROM</phrase></textobject>
	      </mediaobject>
	    </entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-hc-cdrom-blur.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-hc-cdrom-blur.eps" format="EPS"/></imageobject>
		<textobject><phrase>Blurred CD-ROM icon</phrase></textobject>
	      </mediaobject>
	    </entry>
	  </row>
	  <row valign="top">
		<entry>Copiar</entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-hc-copy.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-hc-copy.eps" format="EPS"/></imageobject>
		<textobject><phrase>Copiar icono</phrase></textobject>
	      </mediaobject>
	    </entry>
	    <entry>
	      <mediaobject>
		<imageobject><imagedata fileref="images/icons-hc-copy-blur.png" format="PNG"/></imageobject>
		<imageobject><imagedata fileref="images/icons-hc-copy-blur.eps" format="EPS"/></imageobject>
		<textobject><phrase>Blurred Copy icon</phrase></textobject>
	      </mediaobject>
	    </entry>
	  </row>
	</tbody>
      </tgroup>
    </table>

	<para>
		If a regular icon uses a simple, straightforward metaphor the corresponding high contrast icon can often use the same metaphor. In many cases the same metaphor will need to be drawn differently to create a simplified high contrast icon.
	</para>
	 <figure>
		 <title>Simplified representation of metaphors for high contrast icons</title>
	         <mediaobject>
			 <imageobject><imagedata fileref="images/icons-hc-metaphors.png" format="PNG"/></imageobject>
			 <imageobject><imagedata fileref="images/icons-hc-metaphors.eps" format="EPS"/></imageobject>
			 <textobject><phrase>Comparison of photorealistic style of regular icons with the simpler, line-art style of high contrast icons</phrase></textobject>
								               </mediaobject>
									             </figure>

	<para>High contrast icons are created in a vector drawing program. Black and white shapes are layered to create a simplified icon. The process feels like layering black and white pieces of construction paper, as if you were assembling a collage.</para>
	 <figure>
		<title>Layered technique for high contrast icons</title>
	         <mediaobject>
			 <imageobject><imagedata fileref="images/icons-floppy-dissected.png" format="PNG"/></imageobject>
		             <imageobject><imagedata fileref="images/icons-floppy-dissected.eps" format="EPS"/></imageobject>
			     <textobject><phrase>Exploded view of layers used in high contrast floppy disk icon</phrase></textobject>
								               </mediaobject>
									             </figure>

	<tip><title>Reuse existing shapes</title>
		<para>Often shapes from existing high contrast icons can be resized and reused to more quickly build up a new icon.</para></tip>

	<tip><title>No olvide el borde.</title>
		<para>It is useful to design high contrast icons over a temporary background color so you don't forget to draw the external white border.</para></tip>
     </sect2>
     <sect2 id="icons-design-lowcontrast">
	     <title>Iconos de bajo contraste</title>

		<tip><title>Iconos de bajo contraste</title>
		<para>Low contrast icon themes were deprecated in GNOME 2.22. It is no longer necessary to deliver low contrast icon equivalents. </para></tip>
	     <para>
		     The goal of low contrast themes is to eliminate, as much as possible, light values (e.g. a large 'V' value in HSV). To achieve this, the colors in low contrast icons are compressed toward the middle value range, i.e. dark colors are lightened and light colors are darkened.
	     </para>
	     <para>
		     Low contrast icons are generated from the existing regular icons by adjusting the levels in GIMP. The Input Levels are set to 100, 1.25, 200 and the Output Levels are set to 100, 160, as shown in the Levels dialog below. Large numbers of regular icons can be quickly converted to low contrast by using GIMP's scripting facilities.</para>
	      <figure>
	        <title>Levels dialog in GIMP showing correct levels for generating low contrast icons</title>
		<mediaobject>
		  <imageobject><imagedata fileref="images/icons-lowcontrast-levels.png" format="PNG"/></imageobject>
                  <imageobject><imagedata fileref="images/icons-lowcontrast-levels.eps" format="EPS"/></imageobject>
		  <textobject><phrase>Levels dialog in GIMP showing input levels set to 100, 1.25, 200, and output levels set to 100 and 160.</phrase></textobject>
		 </mediaobject>
	      </figure>

     </sect2>
  </sect1>
</chapter>

<!-- Keep this comment at the end of the file
Local variables:
mode: xml
sgml-omittag:nil
sgml-shorttag:nil
sgml-namecase-general:nil
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:("/usr/lib/sgml/catalog")
sgml-local-ecat-files:("ECAT" "~/sgml/ECAT" "/usr/lib/sgml/ECAT" "/usr/local/lib/sgml/ECAT")
End:
-->



<chapter id="input">
<title>Entrada del usuario</title>
  <sect1 id="input-mouse">
    <title>Interacción del ratón</title>
    
    <sect2 id="mouse-buttons">
      <title>Botones</title>

	<figure> <title>A plethora of pointing devices: mouse, trackball, foot-operated mouse, joystick, trackpad, and a finger-mounted pointing device.</title>
	  <mediaobject>
	  <imageobject><imagedata fileref="images/input-pointing-devices.png" format="PNG" width="480" depth="80"/></imageobject>
	  <imageobject><imagedata fileref="images/input-pointing-devices.eps" format="EPS"/></imageobject>
	  <textobject><phrase>Pictures of different types of pointing device, including mouse, trackball, foot-operated mouse and joystick.</phrase></textobject>
	  </mediaobject>
	</figure>
      
<!-- CB-Ed: The following paragraphs are VERY GOOD because they lay out terms and definitions for the reader clearly and unequivocally. -->

      <para>For most users, the mouse provides the main way of interacting with graphical user interfaces.  The term "mouse" is used in this chapter to include other pointing devices that can be used to move the pointer around the screen, such as trackballs, trackpads, spaceballs, graphics tablets, or assistive technology devices that emulate a mouse.</para>
	
      <para>For right-handed users, the left button on a conventional mouse is used for the majority of mouse actions. We therefore call it the <mousebutton>left button</mousebutton> here, even though that may not physically be the case.  For this reason, you may sometimes see this button referred to in code or documentation as "Button 1" or the "Selection Button".</para>

      <para>Similarly for right-handed users, the right button on a conventional mouse is used for operations involving pop-up menus. We therefore call it the <mousebutton>right button</mousebutton> in this chapter.  You may sometimes see this button referred to in code or documentation as "Button 3" or the "Menu Button".</para>

      <para>A conventional mouse with three buttons normally has its third button (or a scrollwheel that acts as a button when pushed) between the left and right buttons.  We therefore call it the <mousebutton>middle button</mousebutton>, but you may sometimes see this referred to in code or documentation as "Button 2" or the "Transfer Button".</para>

	<itemizedlist><title>Guías</title>
	  
	  <listitem><para>Your application uses left button gestures for selecting, activating components, dragging, and the display of drop-down menus.</para></listitem>
	  
	  <listitem><para>Your application uses right button gestures to display and select actions from a popup menu.</para></listitem>  
	  
	  <listitem><para>Your application uses the middle button to paste the current PRIMARY (usually the last-highlighted) selection at the pointer position, as follows:</para>
	    
	    <table frame="all">
	      <title>Effect of modifier keys on a <mousebutton>middle button</mousebutton> transfer operation</title>
	      <tgroup cols="2" align="left">
		<thead>
		  <row>
		    <entry>Modificador</entry>
		    <entry>Función</entry>
		  </row>
		</thead>
		<tbody>
		  <row>
		    <entry>No modificado</entry>
		    <entry>Copiar la selección</entry>
		  </row>
		  <row>
		    <entry><keycap>Ctrl</keycap></entry>
		    <entry>Copiar la selección</entry>
		  </row>
		  <row>
		    <entry><keycap>Mayús</keycap></entry>
		    <entry>Mover la selección</entry>
		  </row>
		  <row>
		    <entry><keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap></keycombo></entry>
		    <entry>Crear vínculo, atajo o alias para la selección</entry>
		</row>

		</tbody>
	      </tgroup>
	    </table>

	<para>Do not over-ride this functionality in any part of your user interface where the transfer action is likely to be useful.  If you do intend to use the middle button for a different purpose somewhere, only do so as a shortcut for experienced users, and only for operations that can also be performed without using the <mousebutton>right button</mousebutton> or <mousebutton>middle button</mousebutton>.</para></listitem>

	<listitem><para>If present on the mouse, the scrollwheel should scroll the window or control under the pointer, if it supports scrolling. Initiating scrolling in this way should not move keyboard focus to the window or control being scrolled. <remark>If it supports both horizontal and vertical scrolling, perhaps suggest unmodified scrollwheel should scroll vertically, and <keycombo><keycap>Shift</keycap><mousebutton>scrollwheel</mousebutton></keycombo> should scroll horizontally.</remark></para></listitem>

	<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 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>

	<listitem><para>Do not warp the mouse pointer, or restrict mouse movement to part of the screen. This can interfere with assistive technologies, and is usually confusing even for users who do not rely on assistive technologies.</para></listitem>

	<listitem><para>Do not require the use of chording (pressing multiple mouse buttons simultaneously) for any operations.</para></listitem>

	<listitem><para>Do not require the use of multiple (triple- or quadruple-) clicking actions for any operations, unless you also provide an accessible alternative method of performing the same action.</para></listitem>

	<listitem><para>Allow all mouse operations to be cancelled before their completion. Pressing the Esc key should cancel any mouse operation in progress, such as dragging and dropping a file in a file manager, or drawing a shape in a drawing application.</para></listitem>

	<listitem><para>Do not assign any actions exclusively to the middle button of a three-button mouse, as not all mice have one.</para></listitem>

	<listitem><para>Do not hard-code mouse target sizes, or make them too small. Define any mouse targets to be at least as large as the arrow button in a GtkSpinBox in the current gtk theme. Bear in mind that a user with impaired dexterity or vision may be using a theme that results in considerably larger widgets than the default theme.</para></listitem>

	<listitem><para>Do not refer to particular mouse buttons in your interface unless absolutely necessary.  Not everybody will be using a conventional mouse with left, middle and right buttons, so any text or diagrams that refer to those may be confusing.</para></listitem>

      </itemizedlist>
      
    </sect2>

    <sect2 id="selection">
      <title>Seleccionar objetos</title>
      <sect3 id="mouse-keyboard-equivalents">
	<title>Equivalentes del ratón y el teclado</title>

	<para>For controls or windows that contain a number of objects that the
user can select, either singly or multiply, ensure the following mechanisms are in place to allow selections to be made using either the mouse or the keyboard.</para>
	
	<table frame="all" pgwide="1">
	  <title>Standard mouse and keyboard selection mechanisms</title>
	  <tgroup cols="3" align="left">
	    <thead>
	      <row>
		<entry/>
		<entry>Ratón</entry>
		<entry>Teclado</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry>Seleccionar elemento, quitar la selección de todos los demás</entry>
		<entry>Click</entry>
		<entry><keysym>Espacio</keysym></entry>
	      </row>
	      <row>
		<entry>Añadir/quitar elemento de la selección</entry>
		<entry><keycap>Ctrl</keycap> click (toggles item's selected state)</entry>
		<entry><keycombo><keycap>Ctrl</keycap><keysym>Espacio</keysym></keycombo> (toggles focused item's selected state)</entry>
	      </row>
	      <row>
		<entry>Extender selección</entry>
		<entry><keycap>Mayús</keycap> click</entry>
		<entry><keycombo><keycap>Mayús</keycap><keysym>Espacio</keysym></keycombo>, <keycombo><keycap>Mayús</keycap><keycap>Inicio</keycap></keycombo>, <keycombo><keycap>Mayús</keycap><keycap>Fin</keycap></keycombo>, <keycombo><keycap>Mayús</keycap><keycap>RePág</keycap></keycombo>, o <keycombo><keycap>Mayús</keycap><keycap>AvPág</keycap></keycombo></entry>
	      </row>
	      <row>
		<entry>Mover el foco</entry>
		<entry>Pulse en el elemento apropiado para seleccionarlo</entry>
		<entry>Cursor keys, <keycap>Inicio</keycap>, <keycap>Fin</keycap>, <keycap>RePág</keycap>, and <keycap>AvPág</keycap> move focus and selection simultaneously.
		<para><keycombo><keycap>Ctrl</keycap><keysym>cursor keys</keysym></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>Home</keycap></keycombo>,<keycombo><keycap>Ctrl</keycap><keycap>End</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>PageUp</keycap></keycombo>, and <keycombo><keycap>Ctrl</keycap><keycap>PageDown</keycap></keycombo> move focus without affecting current selection.</para></entry>
	      </row>
	      <row>
		<entry>Seleccionar todo</entry>
		<entry>Click first item, then <keycap>Mayús</keycap> click last item</entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>A</keycap></keycombo></entry>
	      </row>
	      <row>
		<entry>Deseleccionar todas</entry>
		<entry>Click container background</entry>
		<entry><keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>A</keycap></keycombo></entry>
	      </row>
	      <row>
		<entry>Activar selección</entry>
		<entry>Double-click to activate a single selection.  <keycap>Mayús</keycap> or <keycap>Ctrl</keycap> double-clicking extends or adds item to selection first before activating the entire selection.</entry>
		<entry><keysym>Intro</keysym> activates entire selection.  If nothing is currently selected, selects currently-focused item first.</entry>
	      </row>
	      <row>
		<entry>Invertir selección</entry>
		<entry>Sin ratón equivalente</entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>I</keycap></keycombo></entry>
	      </row>
	    </tbody>
	  </tgroup>
	</table>
      </sect3>

      <sect3 id="bounding-box-selection">
	<title>Bounding Box Selection</title>

	<para>For a container whose objects may be arranged in two dimensions, for example the icon view in a file manager, allow multiple selection by dragging a bounding box (sometimes called a "rubber band") around one or more objects.  <keycombo action="other" otheraction="drag"><keycap>Shift </keycap><mousebutton>left button</mousebutton></keycombo> <action>drag</action> should add all the objects within the bounding box to the existing selection.  <keycombo action="other" otheraction="drag"><keycap>Ctrl </keycap><mousebutton>left button</mousebutton></keycombo> <action>drag</action> should toggle the selected state of all the objects within the bounding box.</para>

	<itemizedlist><title>Guías</title>

		<listitem><para><remark>This guideline needs to be so much better worded :) </remark>Allow a bounding box selection to begin only if the initial mouse button press is made:</para>
		
			<itemizedlist>
				<listitem><para>Within the bounds of the container's background, and</para></listitem>
				<listitem><para>outside the bounds of any another object in the same container that can be dragged.</para></listitem>
			</itemizedlist>
			
		<para>In a drawing application, for example, this means that a bounding box click and drag could start on a blank area of the canvas, or within a shape that had been locked down to prevent accidental editing, but not in an active shape which would itself be dragged instead.</para></listitem>
		
		<listitem><para>Select any objects that lie wholly or partly within the bounding box when the mouse button is released. <remark>This is different from 1.0 advice, need to update figure 10.2 accordingly.</remark></para></listitem>

		<listitem><para>Use dynamic highlighting during the drag to show which objects will be selected.  Do not wait until the mouse button is released.  This avoids any uncertainty about which objects will be selected by the bounding box.</para></listitem>

		<listitem><para>When a bounding box is being dragged out within a scrollable window, support automatic scrolling of that window when the box is dragged near the window's edges.</para></listitem>

	</itemizedlist>

	<figure> <title>Examples illustrating dynamic selection highlighting during bounding box selection.  In the first example, the folder color and label highlighting changes to indicate selection.  In the second, selection is indicated by the addition of resizing handles to selected objects.</title>
	  <mediaobject>
	    <imageobject><imagedata fileref="images/input-drag-select-files.png" format="PNG" width="509" depth="166"/></imageobject>
	    <imageobject><imagedata fileref="images/input-drag-select-files.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Example illustrating dynamic selection highlighting during bounding box selection</phrase></textobject>
	  </mediaobject>

	  <mediaobject>
	    <imageobject><imagedata fileref="images/input-drag-select-graphics.png" format="PNG" width="598" depth="147"/></imageobject>
	    <imageobject><imagedata fileref="images/input-drag-select-graphics.eps" format="EPS"/></imageobject>
	    <textobject><phrase>Example illustrating dynamic selection highlighting during bounding box selection</phrase></textobject>
	  </mediaobject>
	  
	</figure>

      </sect3>
    </sect2>

    <sect2 id="drag-drop">
      <title>Arrastrar y soltar</title>

      <para>Drag and drop is a direct manipulation technique, where you perform actions on selected objects by moving them around the screen with the mouse.  You "drag" an object by clicking it, then holding the button while you move the pointer to the object's target location.  The object is "dropped" at that location by releasing the mouse button.</para>
      
      <itemizedlist><title>Guías</title>

      	<listitem><para>Use drag and drop only where the user can reasonably guess what the effect might be.  The most common uses are:</para>
		<itemizedlist>
		<listitem><para>to move or copy objects from one place to another</para></listitem>
		<listitem><para>para enlazar un objeto a otro</para></listitem>
		<listitem><para>to perform an action on the objects by dropping them onto an icon representing that action, such as a trash can or printer icon.</para></listitem>
		</itemizedlist>
	</listitem>
      
      	<listitem><para>Provide visual feedback throughout a drag and drop operation. Highlight valid targets and change the mouse pointer as it passes over them.  Use the "no drop" mouse pointer when passing over invalid drop targets. See also <xref linkend="drag-drop-pointers"/>.</para></listitem>	

	<listitem><para>Augment the mouse pointer with a representation of the objects being dragged.  Keep this representation small or make it translucent, so as not to obscure possible drop targets underneath it. See also <xref linkend="drag-drop-pointers"/>.</para>

		<figure>
		<title>Example of copy pointer augmented by an icon representing the file being copied</title>
		<mediaobject>
		<imageobject><imagedata fileref="images/input-drag-cursor.png" format="PNG" width="101" depth="129"/></imageobject>
		<imageobject><imagedata fileref="images/input-drag-cursor.eps" format="EPS"/></imageobject>
		<textobject><phrase>Copy pointer superimposed on icon representing a file being copied, to form a "copy file" pointer</phrase></textobject>
		</mediaobject>
		</figure>
	  
	    	<remark>The pointer shapes shown here aren't actually the current GTK defaults, they're the current KDE (and Windows) defaults.  Should we try and persuade GTK to change?</remark>
	</listitem>

	<listitem><para>Only allow objects to be copied between applications, not moved.  This avoids any confusion about which application's <guimenuitem>Undo</guimenuitem> function reverses the operation.</para></listitem>

	<listitem><para>Allow the user to cancel a drag and drop operation by all of these methods:</para> 
		<itemizedlist>
		<listitem><para>pulsando <keycap>Esc</keycap> antes de soltar el botón del ratón</para></listitem>
		
		<listitem><para>arrastrando el objeto a su ubicación original</para></listitem>
		
		<listitem><para>performing a <action>query drag</action> and selecting <guimenuitem>Cancel</guimenuitem> on the pop-up menu (see <xref linkend="drag-drop-query"/>)</para></listitem>
		
		<listitem><para>arrastrando el objeto a un objetivo de arrastre no válido</para></listitem>
		</itemizedlist>
	</listitem>
	
	<listitem><para>Allow the user to undo the effects a drag and drop operation by selecting <menuchoice><guimenu>Edit</guimenu><guimenuitem>Undo</guimenuitem></menuchoice>.</para></listitem>
	
      	<listitem><para>Allow multiple objects to be dragged by <keycap>Shift</keycap> or <keycap>Ctrl</keycap> selecting them, then dragging any one of the selected objects.</para></listitem>

	<listitem><para>Ensure that keyboard users can replicate all drag and drop actions using only menu items or keyboard shortcuts, such as <guimenuitem>Copy</guimenuitem> (<keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo>) and <guimenuitem>Paste</guimenuitem> (<keycombo><keycap>Ctrl</keycap><keycap>V</keycap></keycombo>).</para></listitem>

	<listitem><para>When an item is being dragged within or into a scrollable window, support automatic scrolling of that window when the mouse is moved near its edges.</para></listitem>
	
	<listitem><para>Pop up a menu when the user attemps to drop multiple objects on a target that only accepts single objects.  On the menu, list all the objects being dragged, and a <guimenuitem>Cancel</guimenuitem> item.</para></listitem>

	<!-- CFB commenting this one out for now because it doesn't mean much the way it's written, and we'd ideally like to aim for more consistency than this anyway
	
	<listitem><para>Move selected objects when the user drags them within a container.  Copy or link to selected objects when the user drags them between containers.  A "container" may be a boundary imposed by the user interface (e.g. a top-level application window), or a user interface representation of a physical container (e.g. a mail server or disk partition).</para>
	
	<para><remark>The whole "dragging between containers" thing concerns me, as it's not always obvious to users what constitues a "container", especially when it gets down to physical details that the user may not even know or care about (e.g. different disk partitions). This is why the right mouse drag menu we're now discrediting came into existence in the first place.  There are also exceptions to the rule, e.g. dragging anything into Trash should presumably move it rather than copy it.</remark></para></listitem>
	-->
	
      </itemizedlist>

	
      
      <sect3 id="drag-drop-override"><title>Overriding drag and drop behavior</title>
      
      	<sect4 id="drag-drop-modifiers"><title>Modificadores de teclado</title>
      	<para>Allow the user to force the behavior of a drag and drop operation by holding the <keycap>Ctrl</keycap>, <keycap>Shift</keycap> or both keys throughout.  If the user changes modifier keys after they have started the drag, change the mouse pointer immediately and perform the new action when the mouse button is released.</para>

	<table frame="all">
	  <title>Effect of modifier keys during a drag and drop operation</title>
	  <tgroup cols="2" align="left">
	    <thead>
	      <row>
		<entry>Modificador</entry>
		<entry>Función</entry>
	      </row>
	    </thead>
	    <tbody>
	    <row>
	      <entry><keycap>Ctrl</keycap></entry>
	      <entry>Copiar</entry>
	    </row>
	    <row>
	      <entry><keycap>Mayús</keycap></entry>
	      <entry>Mover</entry>
	    </row>
	    <row>
	      <entry><keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap></keycombo></entry>
	      <entry>Crear enlace, atajo o alias</entry>
	    </row>
	  </tbody>
	</tgroup>
      </table>
      </sect4>
      
      <sect4 id="drag-drop-query"><title>Query Drag</title>
      
      	<para>Allow the user to drag objects with the <mousebutton>middle button </mousebutton>, or with <keycap>Alt</keycap><mousebutton> left button</mousebutton>. Pop up a menu when the mouse button is released, offering the choice of <guimenuitem>Copy</guimenuitem>, <guimenuitem>Move</guimenuitem> and <guimenuitem>Link</guimenuitem> (or whichever subset of those actions is available), and <guimenuitem>Cancel</guimenuitem>.  Dragging in this way is known as <action>query drag</action> because it prompts the user before changing anything.</para>

      </sect4>
      
      </sect3>

	<sect3 id="drag-drop-pointers">
	  <title>Mouse Pointers to Use for Drag and Drop</title>
	  
	  <para>Use the default GTK drag and drop pointers for the standard transfer operations listed below.  This consistency helps ensure the user will know exactly what to expect when they release the mouse button.  If you have to design a pointer for a non-standard transfer action not listed here, follow the style of the standard pointers.</para>

	  <table frame="all">
	    <title>Mouse Pointers for Drag and Drop</title>
	    <tgroup cols="2" align="left">
	      <thead>
		<row>
		  <entry>Pointer Shape</entry>
		  <entry>Significado</entry>
		</row>
	      </thead>
	      
	      <tbody>
		<row>
		  <entry>
	            <mediaobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-move.png" format="PNG" width="31" depth="32"/></imageobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-move.eps" format="EPS"/></imageobject>
	              <textobject><phrase>Puntero «Mover»</phrase></textobject>
	             </mediaobject>
                  </entry>
		  
		  <entry>Move selection. The dragged selection will be moved to the drop location, removing it from its previous location.</entry>
		</row>
		
		<row>
		  <entry>
                    <mediaobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-copy.png" format="PNG" width="33" depth="30"/></imageobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-copy.eps" format="EPS"/></imageobject>
	              <textobject><phrase>Puntero «Copiar»</phrase></textobject>
	             </mediaobject>
                  </entry>
		  <entry>Copy selection.  The dragged selection will be copied to the drop location, leaving the original intact.</entry>
		</row>
		<row>
		  <entry>
                    <mediaobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-link.png" format="PNG" width="37" depth="33"/></imageobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-link.eps" format="EPS"/></imageobject>
	              <textobject><phrase>Puntero «Enlazar»</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 original selection, for example.</entry>
		</row>

		<row>
		  <entry>
                    <mediaobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-query.png" format="PNG" width="28" depth="32"/></imageobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-query.eps" format="EPS"/></imageobject>
	              <textobject><phrase>"Query drop" pointer</phrase></textobject>
	             </mediaobject>
                   </entry>
		   <entry>Middle button or Alt-left button drag.  A pop-up menu will be posted at the drop location to ask whether the user wants to Move, Copy, or Link the selection, or Cancel the operation.</entry>
		  </row>
	
		<row>
		  <entry>
                     <mediaobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-nodrop.png" format="PNG" width="28" depth="32"/></imageobject>
		      <imageobject><imagedata fileref="images/input-drag-cursor-nodrop.eps" format="EPS"/></imageobject>
	              <textobject><phrase>"Can't drop here" pointer</phrase></textobject>
	             </mediaobject>
</entry>
		  <entry>Can't drop here.  Show this pointer while the mouse is over an area where the selection cannot be dropped.</entry>
		</row>
	      </tbody>
	    </tgroup>
	  </table>


	</sect3>
	</sect2>
	
	<sect2 id="mouse-interaction-applets">
	  
	  <title>Mouse Interaction with Panel Applications (Applets)</title>

	  <para>All objects on the desktop must behave consistently.  Despite their specialized nature, applets are no exception.</para>
	  
	  <itemizedlist><title>Guías</title>
	    <listitem><para>The unmodified left mouse button must be sufficient to operate all your applet's controls.  Applets are meant to be simple enough that modified clicking, or clicking with other mouse buttons (except to pop up the applet's menu) is never required.</para>
	      <remark>Suggestion: Clicking and dragging anywhere within the applet window whilst holding down the <keycap>Ctrl</keycap> and/or <keycap>Mayús</keycap> keys could reposition the applet as if dragging with the middle mouse button (<keycombo action="other" otheraction="drag"><keycap>Ctrl</keycap><mousebutton>izquierda</mousebutton></keycombo> <action>arrastrar</action>=copy, if moving to another panel; <keycombo action="other" otheraction="drag"><keycap>Mayús</keycap><mousebutton>izquierda</mousebutton></keycombo> <action>arrastrar</action>=move, if moving to another panel).</remark></listitem>
	    
	    <listitem><para>Clicking the right button <emphasis>anywhere</emphasis> within the applet's enclosing window must display either the popup menu for the whole applet, or the popup menu for the control under the mouse pointer.  Do not have "dead areas" in your applet that do not respond to a right click.</para></listitem>
	    
	    <listitem><para>Do not use the middle button for anything except dragging the applet to a new location.  Middle-clicking and dragging anywhere within the applet window must move the applet, do not require a drag bar or similar device.</para>
		<para><keycombo action="other" otheraction="drag"><keycap>Ctrl</keycap><mousebutton>left button</mousebutton></keycombo> <action>drag</action> should copy the applet, if moving to another panel; unmodified drag or <keycombo action="other" otheraction="drag"><keycap>Shift</keycap><mousebutton>left button</mousebutton></keycombo> <action>drag</action> should move the applet, if moving to another panel.  If moving within same panel, <keycap>Ctrl</keycap>=switched movement, <keycap>Shift</keycap>=push movement, <keycap>Alt</keycap>=free movement.</para></listitem>

	  </itemizedlist>
	  
	</sect2>
	
    </sect1>
    
    
    <sect1 id="input-keyboard">
      <title>Interacción por teclado</title>
      
      
      <sect2 id="keyboard-navigation">
	<title>Navegación por teclado</title>
	
	<para>A well-designed keyboard user interface plays a key role when you are designing applications. Many power-users prefer to perform most operations with the keyboard rather than the mouse. Visually-impaired users can navigate software more effectively using the keyboard, because using the mouse depends on visual feedback of the mouse pointer location. And mobility impairments can prevent a user from successfully navigating using the mouse, because of the fine motor control skills required.</para>
	
	<para>Make all mouse actions available from the keyboard, and include keyboard access to all toolbars, menus, links and buttons. Every function your application provides must be available using the keyboard alone. Hiding your mouse while you test your application is a great way to test this!</para>
	
	
	<figure>
	  <title>Dialog and menu, with some of their access and shortcut keys indicated</title>
	  <mediaobject>
	  <imageobject><imagedata fileref="images/input-accesskeys-shortcuts.png" format="PNG" width="497" depth="399"/></imageobject>
	  <imageobject><imagedata fileref="images/input-accesskeys-shortcuts.eps" format="EPS"/></imageobject>
	  <textobject><phrase>Screenshot of a dialog and a menu with some of their access keys and shortcut keys highlighted</phrase></textobject>
	  </mediaobject>
	</figure>

	<para>Most functionality is easy to make available from the keyboard, by using access keys and shortcut keys, and the toolkit's built-in keyboard navigation features. All controls with labels should have access keys, and frequently-used menu items should be assigned shortcut keys. However, operations that rely on drag-and-drop, for example, may require more thought to make them keyboard accessible.</para>
		
	<itemizedlist><title>Guías</title>
	  
	  <listitem><para>Provide efficient keyboard access to all application features. In particular, ensure every control on menus and in dialogs are directly focusable using access keys or shortcut keys.</para></listitem>
	  
	  <listitem><para>Use a logical keyboard navigation order. When navigating around a window with the Tab key, keyboard focus should move between controls in a predictable order.  In Western locales, this is normally left to right and top to bottom.</para></listitem>
	  
	  <listitem><para>Ensure correct tab order for controls whose enabled state is dependent on check box, radio button or toggle button state. When such a button is selected, all its dependent controls should be enabled, and all the dependent controls of any other button in the group should be disabled. When the user selects a check box, radio button or toggle button that has dependent controls, do not automatically give focus to the first dependent control, but instead leave the focus on the button.  
</para></listitem>
	  
	  
	  <listitem><para>Do not over-ride existing system-level accessibility features. For example, the MouseKeys feature in the GNOME <guilabel>Keyboard Accessibility</guilabel> preferences dialog allows mouse movement and button clicks to be simulated using the keypad. Therefore you cannot add features to your application that can only be accessed by pressing keys on the keypad, as users relying on the MouseKeys feature will not be able to use them.</para></listitem>
	  
	  <listitem><para>Ensure that any text that can be selected with the mouse can also be selected with the keyboard.  This is a convenience for all users, but especially for those for whom fine control of the mouse is difficult.</para></listitem>
	  
	  <listitem><para>Ensure that objects that can be resized or moved by drag and drop can also be resized or moved with the keyboard. For example, icons and windows on the desktop. Where precision sizing and placement is potentially important, e.g. shapes in a diagram, also consider providing a dialog into which you can type co-ordinates, or a means of snapping objects to a user-definable grid.</para></listitem>
	  
	  <listitem><para>Do not use general navigation functions to trigger operations. For example, do not use basic <keycap>Tab</keycap> keyboard navigation in a dialog to activate any actions associated with a control.</para></listitem>
	  
	  <listitem><para>Show keyboard-invoked menus, windows and tooltips near the object they relate to, but without hiding or obscuring the object to which the menu or tooltip refers,. In GNOME, popup menus are activated with <keycombo><keycap>Shift</keycap><keycap>F10</keycap></keycombo>, and tooltips with <keycombo><keycap>Ctrl</keycap><keycap>F1</keycap></keycombo>.</para></listitem>
	  
	  <listitem><para>Provide more than one method to perform keyboard tasks where possible. Users may find some keys and key combinations easier to use than others.</para></listitem>

	  <listitem><para>Do not assign awkward reaches to frequently performed keyboard operations. Some people may only be able to use one hand on the keyboard, so shortcuts that can be easily used with one hand are preferable for common operations.  In any case, having to frequently perform long or difficult reaches on the keyboard can increase muscle strain for all users, increasing the risk of pain or injury.</para></listitem>
	  
	  <listitem><para>Do not require repetitive use of simultaneous keypresses. Some users are only able to press and hold one key at a time. Assistive technologies such as the GNOME <guilabel>Keyboard Accessibility</guilabel> preferences dialog do allow users to press the keys sequentially rather than simultaneously, but this of course means the operation will take longer for them.</para></listitem>
	</itemizedlist>
	
	  <remark>The point about not having Tab initiate any actions effectively rules out tab completion in dialogs, should we consider/recommend a "hands-free" auto-completion method instead, as offered by OpenOffice.org, Explorer etc.?  What does our new 2.0 file selection dialog do?</remark>
	
	</sect2>

      <sect2 id="choosing-access-keys">
	<title>Elegir teclas de acceso</title>

	<para>Give all labelled components an access key (underlined letter), with the exception of toolbar controls which would use up too many access key combinations.</para>

<!-- Consensus was against giving OK and Cancel additional access keys, but they have them anyway and Owen refuses to remove them...

	<note>
	  <title>For discussion</title>
	  <para>It's been suggested that even OK and Cancel should have access keys, as this is more obvious to newer users.  (KDE does this).  What do we think?  Advantages: means you do not always have to have an Enter-operated default button in dialogs where this might lead you to close the dialog by mistake.  Disadvantages: Adds an extra way for people to do things, potentially adding the "dither" factor; uses up O and C access keys, which could be awkward in larger/tabbed dialogs.</para>
	</note>
-->

	<para>Choose access keys to be as easy to remember as possible.  Normally, this means using the first letter of the label.  However, in complex windows, the choice can become more difficult.  Here are some simple rules:</para>

	<orderedlist>
	    <listitem><para>Assign access keys to the most frequently-used controls first.  If it's not clear which controls will be the most frequently used, assign access keys from left to right, top to bottom (for Western locales).</para></listitem>


	  <listitem><para>Use the first letter of the label, or of one of its other words if it has more than one.  If another letter provides a better association (e.g. "x" in <guilabel>Extra Large</guilabel>) however, consider using that letter instead.</para></listitem>

	  <listitem><para>If the first letter is not available, choose an easy to remember consonant from the label, for example, "p" in <guilabel>Replace</guilabel>.</para></listitem>
 
	  <listitem><para>If no such consonants are available, choose any available vowel from the label.</para></listitem>
	</orderedlist>

	   <para>If duplication of access keys in a window is unavoidable, you should still refrain from duplicating the access keys for any of these buttons that appear in the same window: <guibutton>OK</guibutton>, <guibutton>Cancel</guibutton>, <guibutton>Close</guibutton>, <guibutton>Apply</guibutton> or <guibutton>Help</guibutton>.</para>

	   <para>Also, it is better not to assign access keys to "thin" letters (such as lowercase i or l), or letters with descenders (such as lowercase g or y) unless it is unavoidable.  The underline does not show up very well on those characters in some fonts.</para>


	<para>Applications using a non-Roman writing system in conjunction with a standard keyboard can have control labels prefixed with Roman characters as access keys.</para>
	
	</sect2>
      
      <sect2 id="shortcuts">
	<title>Elegir atajos de teclado</title>

	<para>The tables in <xref linkend="standard-shortcuts"/> summarize the standard shortcut keys to use when your application supports those functions.  Your application will not necessarily support all of these functions, see <xref linkend="menus-standard"/> for more information.  However, use the recommended shortcut keys for those functions you do support.</para> 

	<para>You will probably want to add your own shortcut keys for functions specific to your application.  If so, as well as following the guidelines below, look at any other existing similar applications to see which shortcut keys they have defined.  Your users may already be using those or similar applications, so being consistent where it is possible and sensible to do so will provide a better user experience for them when they begin to use yours.</para>

	<itemizedlist><title>Guías</title>

	  <listitem><para>Use <keycombo><keycap>Ctrl</keycap><keysym>letter</keysym></keycombo> in preference to other combinations when choosing new shortcut keys.</para></listitem>

	  <listitem><para><keycap>Insert</keycap>, <keycap>Delete</keycap>, <keycap>Home</keycap>, <keycap>End</keycap>, <keycap>Page Up</keycap> and <keycap>Page Down</keycap> are acceptable shortcut keys for functions that are closely related to those keys' normal system-defined uses.  Do not assign them to unrelated functions just because you've run out of other shortcut key combinations, however.</para></listitem>

	  <listitem><para>Only assign shortcut keys to the most commonly-used actions in your application.  Do not try to assign a shortcut key to everything.</para></listitem>

	  <listitem><para>Choose new shortcut keys to be as mnemonic as possible, as these will be easier to learn and remember.  For example, <keycombo><keycap>Ctrl</keycap><keycap>E</keycap></keycombo> would be a good shortcut for a menu item called <guimenuitem>Edit Page</guimenuitem>.</para></listitem>

	  <listitem><para>Use <keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>letter</keycap></keycombo> for functions that reverse or extend another function.  For example, <keycombo><keycap>Ctrl</keycap><keycap>Z</keycap></keycombo> and <keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>Z</keycap></keycombo> for <guimenuitem>Undo</guimenuitem> and <guimenuitem>Redo</guimenuitem>.
	<note><title>Unicode entry shortcuts</title><para>Note that you cannot use <keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>A-thru-F</keycap></keycombo> or <keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>0-thru-9</keycap></keycombo> for your own purposes, as these combinations are used to enter unicode characters in text fields.</para></note>
	</para></listitem>
	  
	  <listitem><para>Do not use <keycombo><keycap>Ctrl</keycap><keycap>number</keycap></keycombo> or numbered function keys as shortcut keys, unless the number has some obvious relevance to the action.  For example, <keycombo><keycap>Ctrl</keycap><keycap>2</keycap></keycombo> and <keycombo><keycap>Ctrl</keycap><keycap>3</keycap></keycombo> may be acceptable shortcut keys for <menuchoice><guimenu>View</guimenu><guimenuitem>2D View</guimenuitem></menuchoice> and <menuchoice><guimenu>View</guimenu><guimenuitem>3D View</guimenuitem></menuchoice> in a 3D modelling application.</para></listitem>
	  	  
	  <listitem><para>Do not use <keycombo><keycap>Alt</keycap><keycap>key</keycap></keycombo> combinations for shortcut keys, as these may conflict with window manager or menu access keys.</para></listitem>

	  <listitem><para>Do not use symbols that require <keycap>Shift</keycap> or other modifiers as part of a shortcut, for example <keycombo><keycap>Ctrl</keycap><keycap>%</keycap></keycombo>.  Remember that symbols that can be accessed without a modifier key on your keyboard may be more difficult to access on different international keyboards.</para></listitem>
	  
	  <listitem><para>Do not assign shortcut keys to menu items that change over time, for example a list of open windows on the <guimenu>Window</guimenu> menu, or a recently-used file list on the <guimenu>File</guimenu> menu.  Do assign access keys to these items, however.</para></listitem>
	  <listitem><para>Do not use any of the standard shortcut keys listed in <xref linkend="standard-shortcuts"/> for your own purposes,  even if your application doesn't support those functions.  This helps reinforce consistency between all GNOME applications.</para></listitem>

	</itemizedlist>
   </sect2>	
   
   <sect2 id="standard-shortcuts">
   	<title>Standard Application Shortcut Keys</title>	

	<para>If your application uses any of the standard functions listed in the following tables, use the recommended standard keyboard shortcut for that function.</para>
	
	<table frame="all" pgwide="1">
	  <title>Standard GNOME application shortcut keys and access keys - File menu</title>
	  <tgroup cols="3" align="left">
	    <thead>
	      <row>
		<entry>Función</entry>
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry><guimenuitem><accel>N</accel>ew</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>N</keycap></keycombo></entry>
		<entry>Crear un documento nuevo</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>O</accel>pen</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>O</keycap></keycombo></entry>
		<entry>Abrir un documento</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>S</accel>ave</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo></entry>
		<entry>Guardar el documento actual</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>P</accel>rint</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>P</keycap></keycombo></entry>
		<entry>Imprimir el documento actual</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>C</accel>lose</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>W</keycap></keycombo></entry>
		<entry>Cerrar el documento actual</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>Q</accel>uit</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>Q</keycap></keycombo></entry>
		<entry>Sale de la aplicación</entry>
	      </row>
	    </tbody>
	  </tgroup>
	</table>

	<table frame="all" pgwide="1">
	  <title>Standard GNOME application shortcut keys and access keys - Edit menu</title>
	  <tgroup cols="3" align="left">
	    <thead>
	      <row>
		<entry>Función</entry>
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry><guimenuitem><accel>U</accel>ndo</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>Z</keycap></keycombo></entry>
		<entry>Deshacer la última operación</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>R</accel>edo</guimenuitem></entry>
		<entry><keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>Z</keycap></keycombo></entry>
		<entry>Rehacer la última operación</entry>
	      </row>
	      <row>
		<entry><guimenuitem>Cu<accel>t</accel></guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>X</keycap></keycombo></entry>
		<entry>Cortar el área seleccionada y guardarla en el portapapeles</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>C</accel>opy</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo></entry>
		<entry>Copiar el área seleccionada en el portapapeles</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>P</accel>aste</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>V</keycap></keycombo></entry>
		<entry>Pegar el contenido del portapapeles en la posición del ratón o del cursor</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>D</accel>uplicate</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>U</keycap></keycombo></entry>
		<entry>Duplicate the currently-selected items and add them to the same window, without affecting the clipboard</entry>
	      </row>
	      <row>
		<entry><guimenuitem>Select <accel>A</accel>ll</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>A</keycap></keycombo></entry>
		<entry>Seleccionar todo en el control o la ventana con el foco</entry>
	      </row>

	    <!--  <row>
		<entry><guimenuitem>Deselect All</guimenuitem></entry>
		<entry><keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>A</keycap></keycombo></entry>
		<entry>Deselect everything in focused control or window</entry>
	      </row>-->
	      
	      <row>
		<entry><guimenuitem>In<accel>v</accel>ert Selection</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>I</keycap></keycombo></entry>
		<entry>Select everything in focused control or window that was previously unselected, and deselect everything that was previously selected</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>D</accel>elete</guimenuitem></entry>
		<entry><keycap>Supr</keycap></entry>
		<entry>Eliminar la selección</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>F</accel>ind...</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>F</keycap></keycombo></entry>
		<entry>Find matches in the current document, highlighting them in-place</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>S</accel>earch...</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>F</keycap></keycombo> (see note below)</entry>
		<entry>Search for matches in multiple documents, files or other external sources</entry>
	      </row>
	      <row>
		<entry><guimenuitem>Find Ne<accel>x</accel>t</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>G</keycap></keycombo></entry>
		<entry>Buscar siguiente coincidencia</entry>
	      </row>
<!-- Replace may go depending on response to mpt's comment that Replace should be part of standard Find dialog functionality-->
	      <row>
		<entry><guimenuitem><accel>R</accel>eplace...</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>H</keycap></keycombo></entry>
		<entry>Buscar y reemplazar coincidencias</entry>
	      </row>
		  <row>
		<entry><guimenuitem>R<accel>e</accel>name</guimenuitem></entry>
		<entry><keycap>F2</keycap></entry>
		<entry>Switch the selected item's label into edit mode, allowing user to type in a new name.</entry>
	      </row>
	    </tbody>
	  </tgroup>
	</table>

	<note><title>Buscar</title>
		<para>If your application requires both <menuchoice><guimenu>Edit</guimenu><guimenuitem>Find</guimenuitem></menuchoice> and <menuchoice><guimenu>Edit</guimenu><guimenuitem>Search</guimenuitem></menuchoice> menu items, use <keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>F</keycap></keycombo> as the shortcut for <guimenuitem>Search</guimenuitem>.</para>
	</note>
	
<!--
	<note><title>For discussion</title> -->

<!-- Consensus was for "Deselect All" -->
	  <!-- <para>czr currently proposing "Select None" rather than "Deselect All", which is better?  I prefer the latter because it's more visually distinct on a menu, in English at least.</para> -->
	  <!-- Um, consensus was to be rid of the item, iirc. (GJM) -->
	  <!--<para>Should we call it "Find Next" or "Find Again"?</para> -->

	  <!--<para>czr currently proposing Ctrl+R for "Replace", but this clashes with "Reload" in most browser applications... not a problem until somebody writes a graphical HTML editor that you can also do search/replace in :o)  Ctrl+H is another common shortcut for "Replace", should we use this instead?  (It's not as easy to access with one hand, though, so maybe not).</para> -->

	  <!--<para>mpt suggesting that Replace should be part of Find dialog, so shortcut for Replace may not be required at all.</para>-->

	  <!-- Consensus is to keep Letter-based shortcut keys
	  <para>Kenneth suggests a more F-key-based system, e.g. F5 for Refresh rather than Ctrl+R, as "Ctrl+R" is only memorable if you happen to speak English... what's our view on this?</para>-->

<!--
	  </note>-->

	
	

	<table frame="all" pgwide="1">
	  <title>Standard GNOME application shortcut keys and access keys - View menu</title>
	  <tgroup cols="3" align="left">
	    <thead>
	      <row>
		<entry>Función</entry>
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry><guimenuitem>Zoom <accel>I</accel>n</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keysym>Más</keysym></keycombo></entry>
		<entry>Zoom in on the document <remark>Should probably recommend that Ctrl-Equals work too</remark></entry>
	      </row>
	      <row>
		<entry><guimenuitem>Zoom <accel>O</accel>ut</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keysym>Menos</keysym></keycombo></entry>
		<entry>Zoom out of the document</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>N</accel>ormal Size</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keysym>0</keysym></keycombo></entry>
		<entry>Restore to zoom level to normal size (generally 100%)</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>R</accel>efresh</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>R</keycap></keycombo></entry>
		<entry>Redraw current view of document, without checking if content has changed</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>R</accel>eload</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>R</keycap></keycombo> (see note below)</entry>
		<entry>Reload the current document, updating content from source if necessary</entry>
	      </row>
		  <row>
		<entry><guimenuitem>Pr<accel>o</accel>perties</guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>Intro</keycap></keycombo></entry>
		<entry>Display the selected object's Properties window. May alternatively appear on the <guimenu>Archivo</guimenu> menu if the document itself is the only object in the application whose properties can be inspected.</entry>
	      </row>
	    </tbody>
	  </tgroup>
	</table>

	<note><title>Recargar y actualizar</title>
		<para>If your application requires both <menuchoice><guimenu>View</guimenu><guimenuitem>Reload</guimenuitem></menuchoice> and <menuchoice><guimenu>View</guimenu><guimenuitem>Refresh</guimenuitem></menuchoice> menu items, use <keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>R</keycap></keycombo> as the shortcut for <guimenuitem>Reload</guimenuitem>.</para>
	</note>
	
	<table frame="all" pgwide="1">
	  <title>Teclas de acceso rápido y atajos de teclado estándar de GNOME: Menú marcadores</title>
	  <tgroup cols="3" align="left">
	    <thead>
	      <row>
		<entry>Función</entry>
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry><guimenuitem>Añadir marcador <accel>B</accel></guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>D</keycap></keycombo></entry>
		<entry>Añade un marcador para la ubicación actual</entry>
	      </row>
	      <row>
		<entry><guimenuitem>Editar marcadores... <accel>E</accel></guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>B</keycap></keycombo> (see note below)</entry>
		<entry>Abrir una ventana en la que el usuario puede editar y organizar los marcadores guardados</entry>
	      </row>
	    </tbody>
	  </tgroup>
	</table>
	
	<note><title>Resaltar y editar marcadores</title>
		<para>Si su aplicación requiere los elementos de menú <menuchoice><guimenu>Formatear</guimenu><guimenuitem>Resaltar</guimenuitem></menuchoice> y <menuchoice><guimenu>Marcadores</guimenu><guimenuitem>Editar marcadores...</guimenuitem></menuchoice>, use <keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>D</keycap></keycombo> como atajo para <guimenuitem>Editar marcadores</guimenuitem>.</para>
	</note>

	<table frame="all" pgwide="1">
	  <title>Standard GNOME application shortcut keys and access keys - Go menu</title>
	  <tgroup cols="3" align="left">
	    <thead>
	      <row>
		<entry>Función</entry>
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry><guimenuitem><accel>B</accel>ack</guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keysym>Izquierda</keysym></keycombo></entry>
		<entry>Ir a la siguiente ubicación en la cadena de navegación</entry>
	      </row>
	      <row>
		<entry><guimenuitem>Siguiente <accel>x</accel></guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keysym>Derecha</keysym></keycombo></entry>
		<entry>Ir a la siguiente ubicación en la cadena de navegación</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>U</accel>p</guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keysym>Arriba</keysym></keycombo></entry>
		<entry>Go up one level in the navigation hierarchy</entry>
		  </row>
	    
		  <row>
		<entry><guimenuitem><accel>H</accel>ome</guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keysym>Inicio</keysym></keycombo></entry>
		<entry>Go to the starting page defined by the user or application</entry>
	      </row>
		  <row>
		<entry><guimenuitem><accel>L</accel>ocation...</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keysym>L</keysym></keycombo></entry>
		<entry>Present or focus an entry field into which the user can type a new address or location to view</entry>
		</row>
	    </tbody>
	  </tgroup>
	</table>

	
	<table frame="all" pgwide="1">
	  <title>Standard GNOME application shortcut keys and access keys - Format menu</title>
	  <tgroup cols="3" align="left">
	    <thead>
	      <row>
		<entry>Función</entry>
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry><guimenuitem><accel>B</accel>old</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>B</keycap></keycombo></entry>
		<entry>Cambiar el texto seleccionado actualmente a negrita/normal</entry>
		</row>
	      <row>
		<entry><guimenuitem><accel>U</accel>nderline</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>U</keycap></keycombo></entry>
		<entry>Underline/remove underline from selected text</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>I</accel>talic</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>I</keycap></keycombo></entry>
		<entry>Cambiar el texto seleccionado actualmente a cursiva/normal</entry>
	      </row>  
	    </tbody>
	  </tgroup>
	</table>

<!--	<note><title>For discussion</title>
	  <para>Is it acceptable to specify the same shortcut for <menuchoice><guimenu>Format</guimenu><guimenuitem>Bold</guimenuitem></menuchoice> and <menuchoice><guimenu>Bookmarks</guimenu><guimenuitem>Edit Bookmarks</guimenuitem></menuchoice>, given that the two aren't likely to occur in the same application?  Or could/should we provide a second choice for one of them on the off-chance that they do coincide?</para>
	</note>
-->

	<table frame="all" pgwide="1">
	  <title>Standard GNOME application shortcut keys and access keys - Help menu</title>
	  <tgroup cols="3" align="left">
	    <thead>
	      <row>
		<entry>Función</entry>
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry><guimenuitem><accel>C</accel>ontents</guimenuitem></entry>
		<entry><keycap>F1</keycap></entry>
		<entry>Muestra el contenido de la ayuda para la aplicación actual</entry>
	      </row>
		  
		  <!-- Doesn't appear on menus so probably doesn't belong in this table
	      <row>
		<entry><guimenuitem>(Context Help)</guimenuitem></entry>
		<entry><keycombo><keycap>Shift</keycap><keycap>F1</keycap></keycombo></entry>
		<entry>Show online help for the currently focused control or window</entry>
	      </row>-->
		  
	    </tbody>
	  </tgroup>
	</table>

<!--
	<note>
	  <title>For Discussion</title>
	  <para>Greg suggested Ctrl+H for Search Help... this doesn't seem to me to be an important enough function to tie up Ctrl+H with, though, anyone got any other views/alternative suggestions?</para>
	</note>
-->	  

    <sect3 id="window-manager-navigation">
	<title>Standard Window Manager Shortcut Keys</title>
	<para>Los siguientes atajos de teclado los usan varios gestores de ventanas, y normalmente su aplicación no debería sobreescribirlos.</para>

<table frame="all" pgwide="1">
	  <title>Teclas rápidas y de acceso para el gestor de ventanas estándar</title>
	  <tgroup cols="3" align="left">
	    <thead>
	      <row>
		<entry>Función</entry>
		<entry>Combinación de teclas</entry>
		<entry>Descripción</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry>Cambiar las ventanas principales</entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>Tabulador</keycap></keycombo>, <keycombo><keycap>Mayús</keycap><keycap>Alt</keycap><keycap>Tabulador</keycap></keycombo></entry>
		<entry>Cambiar el foco la siguiente o anterior ventana de nivel superior del escritorio</entry>
	      </row>

	      <row>
		<entry>Cambiar paneles</entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Tabulador</keycap></keycombo>, <keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Tabulador</keycap></keycombo></entry>
		<entry>Cambiar el foco al siguiente o anterior panel en el escritorio</entry>
	      </row>

	      <row>
		<entry>Salir de la sesión</entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Supr</keycap></keycombo></entry>
		<entry>Abrir el diálogo de confirmación de cierre de sesión</entry>
	      </row>

	      <row>
		<entry>Menú de ventana</entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>Espacio</keycap></keycombo></entry>
		<entry>Abrir el menú de ventana</entry>
		</row>
	      <row>
		<entry><guimenuitem><accel>C</accel>lose</guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>F4</keycap></keycombo></entry>
		<entry>Cerrar la ventana con el foco</entry>
	      </row>
	      <row>
		<entry><guimenuitem>Restaurar <accel>R</accel></guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>F5</keycap></keycombo></entry>
		<entry>Restaurar lo que tiene el foco a su tamaño anterior</entry>
	      </row>
		<row>
			<entry><guimenuitem><accel>S</accel> con ventanas secundarias</guimenuitem></entry>
			<entry><keycombo><keycap>Alt</keycap><keycap>F6</keycap></keycombo>, <keycombo><keycap>Mayús</keycap><keycap>Alt</keycap><keycap>F6</keycap></keycombo></entry>
		<entry>Cambiar el foco al siguiente o anterior ventana secundaria asociada con la aplicación (<remark>funcionalidad precisa para metacity TBD, ver el error 94682</remark>)</entry>
		</row>

	      <row>
		<entry><guimenuitem>Mover <accel>M</accel></guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>F7</keycap></keycombo></entry>
		<entry>Mover la ventana con el foco</entry>
	      </row>
	      <row>
		<entry><guimenuitem>Redimensionar <accel>s</accel></guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>F8</keycap></keycombo></entry>
		<entry>Redimensionar la ventana con el foco</entry>
	      </row>
	      <row>
		<entry><guimenuitem>Minimizar <accel>n</accel></guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>F9</keycap></keycombo></entry>
		<entry>Minimizar la ventana que tenga el foco</entry>
	      </row>
	      <row>
		<entry><guimenuitem>Maximizar <accel>x</accel></guimenuitem></entry>
		<entry><keycombo><keycap>Alt</keycap><keycap>F10</keycap></keycombo></entry>
		<entry>Maximizar la ventana que tenga el foco</entry>
	      </row>
	      <row>
		<entry><guimenuitem><accel>F</accel> pantalla completa</guimenuitem></entry>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>F11</keycap></keycombo></entry>
		<entry>Mostrar la ventana en modo a pantalla completa, sin borde, barra de menú, barra de herramientas o barra de estado</entry>
	      </row>

	    </tbody>
	  </tgroup>
	</table>
	</sect3>

      <sect3 id="widget-navigation">
	<title>Teclas rápidas de navegación estándar para los widgets</title>
	<para>Los siguientes atajos de teclado están reservados para la navegación con el teclado usada por varios widgets de GNOME, y normalmente su aplicación no debería sobreescribirlos.</para>

	<table frame="all" pgwide="1">
	  <title>Teclas de navegación estándar de GNOME para widgets</title>
	  <tgroup cols="2" align="left">
	    <thead>
	      <row>
		<entry>Clave</entry>
		<entry>Función</entry>
	      </row>
	    </thead>
	    <tbody>
	      <row>
		<entry><keycap>Tabulador</keycap>, <keycombo><keycap>Mayús</keycap><keycap>Tabulador</keycap></keycombo></entry>
		<entry>Mueve el foto del teclado al siguiente/anterior control</entry>
	      </row>
	      <row>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>Tabulador</keycap></keycombo>, <keycombo><keycap>Mayús</keycap><keycap>Ctrl</keycap><keycap>Tabulador</keycap></keycombo></entry>
		<entry>Moves keyboard focus out of enclosing widget to next/previous control, in those situations where Tab alone has another function (e.g. GtkTextView)</entry>
	      </row>
	      <row>
		<entry><keycombo><keycap>Ctrl</keycap><keycap>F1</keycap></keycombo></entry>
		<entry>Mostrar el consejo para el control actualmente seleccionado</entry>
	      </row>
	      <row>
		<entry><keycombo><keycap>Mayús</keycap><keycap>F1</keycap></keycombo></entry>
		<entry>Mostrar la ayuda sensible a contexto para la ventana o control actualmente con el foco</entry>
	      </row>
	      <row>
		<entry><keycap>F6</keycap>, <keycombo><keycap>Mayús</keycap><keycap>F6</keycap></keycombo></entry>
		<entry>Dar el foco al siguiente/anterior panel en una ventana GtkPaned</entry>
	      </row>
	      <row>
		<entry><keycap>F8</keycap></entry>
		<entry>Dar el foco a la barra agrupadora en la ventana del panel</entry>
	      </row>
	      <row>
		<entry><keycap>F10</keycap></entry>
		<entry>Dar el foco a la barra de menú de la ventana</entry>
	      </row>
	      <row>
		<entry><keycombo><keycap>Mayús</keycap><keycap>F10</keycap></keycombo></entry>
		<entry>Muestra el menú contextual emergente para los objetos actualmente seleccionados</entry>
	      </row>
	      <row>
		<entry><keysym>Espacio</keysym></entry>
		<entry>Conmutar el estado de la casilla de verificación, botón de radio o botón de conmutación con el foco</entry>
	      </row>
	      <row>
		<entry><keysym>Intro</keysym></entry>
		<entry>Activar el botón con el foco, el elemento del menú, etc.</entry>
	      </row>
	      <row>
		<entry><keycap>Inicio</keycap>, <keycap>Fin</keycap></entry>
		<entry>Seleccionar/moverse al primer elemento en el widget seleccionado</entry>
	      </row>
	      <row>
		<entry><keycap>RePág</keycap>, <keycombo><keycap>Ctrl</keycap><keycap>RePág</keycap></keycombo>, <keycap>AvPág</keycap>, <keycombo><keycap>Ctrl</keycap><keycap>AvPág</keycap></keycombo></entry>
		<entry>Desplazar una página la vista seleccionada arriba/izquierda/abajo/derecha</entry>
	      </row>
 	      </tbody>
	  </tgroup>
	</table>
	     
      </sect3>
      
	<sect3 id="additional-widget-navigation">
	  <title>Teclas rápidas de navegación adicionales para los widgets</title>
	  
	  <para>The following emacs-style navigation shortcut keys are still available in GNOME 2.0 text entry fields (by selecting the "emacs" scheme in the GNOME <guilabel>Keyboard Shortcuts</guilabel> preferences dialog), but are disabled by default.  Since some users will still want to use them, do not over-ride them for your own purposes in any situations where a text entry control has focus.</para>

	  <table frame="all" pgwide="1">
	    <title>Teclas de navegación estilo Emacs para los widgets</title>
	    <tgroup cols="2" align="left">
	      <thead>
		<row>
		  <entry>Clave</entry>
		  <entry>Función</entry>
		</row>
	      </thead>
	      <tbody>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keycap>A</keycap></keycombo></entry>
		  <entry>Mover el cursor al principio de la línea</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keycap>D</keycap></keycombo></entry>
		  <entry>Borrar el carácter siguiente/bajo el cursor</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keycap>E</keycap></keycombo></entry>
		  <entry>Mover el cursor al final de la línea</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keycap>K</keycap></keycombo></entry>
		  <entry>Borrar desde el cursor al final de la línea</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keycap>U</keycap></keycombo></entry>
		  <entry>Borrar la línea actual</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keycap>W</keycap></keycombo></entry>
		  <entry>Cortar al portapapeles</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keycap>Y</keycap></keycombo></entry>
		  <entry>Pega desde el portapapeles</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keysym>Espacio</keysym></keycombo></entry>
		  <entry>Establecer marca</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keycap>Supr</keycap></keycombo>, <keycombo><keycap>Alt</keycap><keycap>D</keycap></keycombo></entry>
		  <entry>Borrar desde el cursor al final de la palabra</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Ctrl</keycap><keysym>Retroceso</keysym></keycombo></entry>
		  <entry>Borrar desde el cursor al principio de la palabra</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Alt</keycap><keysym>Espacio</keysym></keycombo></entry>
		  <entry>Elimine todo espacio en blanco alrededor del cursor, reinserte un solo espacio en blanco</entry>
		</row>
		<row>
		  <entry><keycombo><keycap>Alt</keycap><keycap>\</keycap></keycombo></entry>
		  <entry>Borrar todos los espacios en blanco alrededor del cursor</entry>
		</row>
	      </tbody>
	    </tgroup>
	  </table>
	  
	</sect3>
	
      </sect2>
      
      <sect2 id="keynav-applets">
	<title>Interacción del teclado con las aplicaciones del panel (miniaplicaciones)</title>

	<para>Panels have been fully keyboard navigable since GNOME 2.0.  Since your panel application can gain keyboard focus, you must ensure that it is also keyboard navigable.</para>

	<para>Las reglas para la navegación por teclado de las aplicaciones del panel son básicamente las mismas que para otra ventana. No obstante existe una diferencia importante:</para>

	<itemizedlist>
	  <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>
	
      </sect2>
      
  </sect1>
  </chapter>





  <chapter id="language">
    <title>Idioma</title>

    <para>Un etiquetado consistente crea un entorno familiar por el que el usuario puede navegar confortablemente. Cuanto más familiar sea el entorno, más fácil es encontrar información.</para>

    <sect1 id="language-labels">
      <title>Etiquetas</title>
      
      <sect2 id="language-controls"> 
	<title>Controles</title> 
	<para>Clear, consistent and concise labelling of controls helps users to work out the purpose of a window or dialog they have never seen before. To a visually-impaired user, clear labels are even more important. A user who relies on a screenreader has no assistance from icons, layout, or spacing to work out what the controls do, so clear labelling is essential.</para>
	
	<itemizedlist><title>Guías</title> 
	  <listitem><para>Mantenga las etiquetas cortas. Esto: <itemizedlist> 
		<listitem><para>Reduces the expansion of text when translated, and thus minimizes the effort required to localize the UI. Translated English text can expand up to 30% in some languages.</para></listitem> 
		
		<listitem><para>Facilita el uso de motores de traducción.</para></listitem> 
		<listitem><para>Mejora la velocidad de comprensión para el usuario.</para></listitem> 
	      </itemizedlist></para>
	    
	    <para>Do not shorten your labels to the point of losing meaning, however. A three-word label that provides clear information is better than a one-word label that is ambiguous or vague. Try to find the fewest possible words to satisfactorily convey the meaning of your label.</para></listitem> 
	  
	  <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>Aplique reglas de capitalización estándar. Consulte la <xref linkend="layout-capitalization"/> para obtener consejos sobre la capitalización de las etiquetas de la interfaz de usuario</para></listitem> 
	</itemizedlist>

      </sect2> 
      
      <sect2> 
	<title>Consejos</title> 
	
	<sect3>
	  <title>Consejos de la barra de herramientas</title>
	  
	  <para>A toolbar tooltip is the short description of a toolbar control's functionality that the user sees when they mouse over it.</para>

	  <itemizedlist> <title>Guías</title>
	    <listitem><para>Concisely state the purpose of the control.  The tooltip should be more descriptive than the corresponding menu item name, if there is one, but not verbose.  For example, <guilabel>Undo last action</guilabel> for the <guibutton>Undo</guibutton> button.</para></listitem> 

	    <listitem><para>Use sentence capitalization rules. See <xref linkend="layout-capitalization"/>.</para></listitem> 
	  </itemizedlist>            
	  
	</sect3> 
	
	<sect3>
	  <title>Consejos de la aplicación</title> 

	  <para>An application tooltip is the short description of your application that the user sees when they mouse over the launcher or menu item for your application.  It is stored in the <structfield>comment</structfield> field of your application's <filename>desktop</filename> file. See <xref linkend="menu-item-tooltips"/></para>

	  <itemizedlist><title>Guías</title> 
	    <listitem><para>Create short tooltips. Aim to accurately communicate the functionality of an element with the fewest words possible.</para></listitem> 
	    <listitem><para>Use sentence capitalization rules. See <xref linkend="layout-capitalization"/>.</para></listitem> 
	    
	    <listitem><para>Use las reglas de puntuación estándar, con la excepción de que no debe usar el punto al final del consejo o sugerencia.</para></listitem> 
	    
	  </itemizedlist> 
	</sect3> 
      </sect2> 
      
      
      <sect2> 
	<title>Menús</title> 
	
	<itemizedlist> <title>Guías</title>
	
	  <listitem><para>Use the recommended standard labels for menu items and titles, where they exist. Do not use synonyms such as <guimenuitem>Exit</guimenuitem> instead of <guimenuitem>Quit</guimenuitem>. See <xref linkend="menus-standard"/> for a list and descriptions of standard menu items and titles.</para></listitem>

	  <listitem><para>Use reglas de capitalización de la cabecera para todos los elementos del menú y títulos. Para obtener más información consulte la <xref linkend="layout-capitalization"/>.</para></listitem> 
	    
	</itemizedlist> 
	
      </sect2>
      
    </sect1>

    <sect1 id="language-errors">
      <title>Avisos y mensajes de error</title>
	<para>Un buen aviso o mensaje de error contiene dos elementos:</para>
	<orderedlist>
		<listitem><para>Una breve descripción del problema.</para></listitem>
		<listitem><para>Una lista de las formas en las que el usuario puede solucionar el problema.</para></listitem>
	</orderedlist>

	<para>Ambos elementos se deberían presentar en un lenguaje no técnico, libre de jergas, a menos que el público al que está dirigido sea particularmente técnico.</para>

	<para>If your application knows enough about the problem to be able to give all this information to the user, it will often be capable of rectifying the problem itself when the user has decided which course of action they want to take.  For example, if the problem is insufficient memory, tell the user which currently-running application is taking up the most memory, and provide a button to close it for them.  (Do not offer to launch a graphical process manager, however, which is something most users should never see!)</para>

	<para>Consulte la <xref linkend="windows-alert"/> para obtener información más detallada acerca de escribir y presentar errores, avisos y alertas de información.</para>
    </sect1>


    <sect1 id="language-help">
      <title>Ayuda en línea</title>
	<para>Writing online help is a specialized task, and is therefore not covered in any depth here.  Refer to the <ulink url="http://developer.gnome.org/documents/style-guide/index.html">GNOME Documentation Styleguide</ulink> for guidance on writing clear, consistent and helpful documentation for your application.</para>
    </sect1>

  </chapter>





<!-- we can change the title as soon as the content is written
     I want the document to be as usable and correct as possible
     this week -seth

  <chapter id="checklists">
    <title>Checklists</title>
-->


  <chapter id="reality-checks">
    <title>Listas de comprobación</title>
    <sect1 id="checks-yourself">
      <title>Cosas que puede hacer por si mismo</title>
      <sect2>
	<title>Antes de comenzar</title>

	<para>Escriba el tipo de personas que espera que usen su aplicación. Luego escriba algunos «escenarios» para cada tipo de usuario; una pequeña historia que describa las tareas habituales para las que esos usuarios usarán su aplicación. Estas tareas deben seguir estas líneas:</para>

	<blockquote><para>Alfredo necesita encontrar un correo electrónico, que recibió la semana pasada, acerca de widgets</para></blockquote>

<!-- CB: Flow chart diagram.  Boxes with arrows showing flow of user scenario 
example.  An transitional paragraph probably needs to be added after the "right" vs. "wrong" text examples shown, that basically says: You can use a flow chart, as shown below, to sketch out an expected user scenario. -->

	<para>rather than </para>

	<blockquote><para>Alfredo pulsa en el botón <guibutton>Buscar</guibutton> y escribe <userinput>widgets</userinput> en el diálogo.</para></blockquote>

	<para>De esta forma, puede usar los mismos escenarios para comprobar y comprar diferentes diseños de interfaces y describir cualquier funcionalidad que falte.</para>

	<para>Include these user descriptions and scenarios with the documentation you commit to CVS.  This way, other contributors will get to understand your users too, can help to develop the application with that knowledge, and can provide more scenarios of their own.</para>
      </sect2>
      
      <sect2>
	<title>Acceso y foco del teclado</title>

	<para>Cuando empiece a implementar la interfaz, esconda su ratón y asegúrese de que sigue pudiendo hacer todo usando solamente el teclado. Implemente la funcionalidad del teclado al mismo tiempo que implementa la del ratón: no lo deje para el final.</para>

<!-- CB: This is a non-figure comment, I couldn't help myself.  The first sentence in the paragraph directly above, is badly written.  The word "it" is ambiguous in the sentence because it likely refers to the mouse!  Please correct. -->

	<para>Usando solo comandos de teclado, mueva el foco por todas las barras de menú y de herramientas en la aplicación. Confirme también que:</para>
	
<!-- CB-Ed: OK I'll just make all non-figures comments tagged with CB-Ed.  The above paragraph should be part of the bulleted list below. -->

<!-- CB-Fig: All figures comments will be tagged with CB-Fig.  A single figure showing an example GUI with callouts highlighting bulleted points would be great. Perhaps visually box bulleted elements and then "zoom" them out with callout text.  -->
	<itemizedlist>
	  <listitem><para>Los menús de contexto sensitivo muestran correctamente (<keycombo><keycap>Mayús</keycap><keycap>F10</keycap></keycombo>).</para></listitem>
	  <listitem><para>Los consejos o sugerencias se pueden mostrar arriba y abajo para todos los controles que los tienen (<keycombo><keycap>Ctrl</keycap><keycap>F1</keycap></keycombo>, <keycap>Esc</keycap>).</para></listitem>

	  <listitem><para>Todas las funciones listadas en la barra de herramientas se pueden realizar usando el teclado.</para></listitem>

	  <listitem><para>Puede operar completamente todo control en el área del cliente de la aplicación y diálogos.</para></listitem>

	  <listitem><para>El texto y los objetos en el área del cliente se pueden seleccionar.</para></listitem>

	  <listitem><para>Cualquier mejora de teclado o combinación de tecla funciona como se ha diseñado.</para></listitem>

	  <listitem><para>Compruebe que al moverse entre objetivos el indicador del foco visual es fácil de identificar en todo momento.</para></listitem>
	</itemizedlist>
	
      </sect2>
      
      <sect2>
	<title>Temas, colores y contraste</title>

	<para>Pruebe varios temas de GNOME para asegurarse de que su aplicación respeta todos los ajustes disponibles.</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>
	<title>Animación</title>

	<para>Asegúrese de que ha implementado una opción para apagar cualquier animación en su aplicación (por razones de accesibilidad), y de que funciona tal y como está diseñada. Apague la animación. Confirme que toda la información se muestra correctamente.</para>
      </sect2>
    </sect1>
    
    <sect1 id="checks-other-people">
      <title>Lo que puede hacer con otras personas</title>
      <sect2>
	<title>Obtener comentarios rápidamente</title>
	
	<para>It's always tempting, but don't start coding your interface straight away.  Sketch out some ideas on paper first, or in Glade or HTML if you prefer.  (But don't be tempted add any functionality at this point if you do it this way!)</para>

	<para>Show these prototypes to other people— the GNOME mailing lists and IRC are ideal for finding likely candidates.  Ask them to use these prototype interfaces to run through some of the scenarios you came up with earlier.  You'll probably get questions like "how would I do X", "which menu is Y on"... these questions will help you think about the interface from the user's viewpoint.  You'll probably also get a few suggestions about how to do things differently— these ideas may or may not turn out to better than yours, but any idea from a potential user is worth considering!</para>

	<para>You should also consider seeking opinions from the <ulink url="http://developer.gnome.org/projects/gup/">GNOME Usability team</ulink>.  They have designed many user interfaces before and may be able to spot potential problems at this early stage, before you take your design too far to change easily.</para>

	<para>Once you've decided on the basic interface design and have started coding parts of it, find somebody to try it out again— it doesn't have to be the same person.  You'll probably find some more problems that were hard to see on your static paper prototype.  By finding these now, it's usually not too late to fix them without too much trouble.</para>
      </sect2>
      
      
      <sect2>
	<title>Internacionalización y localización</title>

	<para>If you intend your application to be translated into different languages, show draft designs of your application to the <ulink url="http://developer.gnome.org/projects/gtp/contact.html">GNOME Translation Team</ulink>.  They'll help you find potential translation problems, such as not leaving enough space for translated labels, shortcut keys that cause problems on a different keyboard layout, or using new terms in your app that are hard to translate.</para>

	<para>If possible, try out your application with users from the locales you are targeting.  This will help you determine whether users understand how to use the application, if they perceive the graphics and colors the way you intended, and if there are words or images in the application that may cause offence to users of that locale. </para>
      </sect2>

    </sect1>
  </chapter>




  <chapter id="credits">
    <title>Créditos</title>
    <para>(lista en orden alfabético, si se le omitió de forma accidental, escriba un correo-e a los autores o <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=HIG">abra un informe de error</ulink>)</para>
    <sect1 id="credits-active-authors">
      <title>Autores activos</title>
      <para>
	<itemizedlist>
	  <listitem><para>Calum Benson, <email>calum.benson@sun.com</email></para></listitem>
          <listitem><para>Bryan Clark, <email>clarkbw@gnome.org</email></para></listitem>
	  <listitem><para>Seth Nickell, <email>seth@gnome.org</email></para></listitem>
	</itemizedlist>
      </para>
    </sect1>

    <sect1 id="credits-figures">
	<title>Ilustradores adicionales</title>
	<para>
	  <itemizedlist>
	  	<listitem><para>Mihai Anca, <email>ropiku@gmail.com</email></para></listitem>
		<listitem><para>Denis Anisimov, <email>genius@s146.net.ru</email></para></listitem>
		<listitem><para>Wouter Bron, <email>wousser@gmail.com</email></para></listitem>
	  </itemizedlist>
	</para>
    </sect1>

    <sect1 id="credits-inactive-authors">
      <title>Autores inactivos o retirados</title>
      <para>
	<itemizedlist>
	  <listitem><para>Coleen Baik</para></listitem>
	  <listitem><para>Adam Elman</para></listitem>
	  <listitem><para>Colin Z. Robertson</para></listitem>
	  <listitem><para>Maciej Stachowiak</para></listitem>
	</itemizedlist>
      </para>
    </sect1>

    <sect1 id="credits-reviewers-contributors">
      <title>Reviewers and Contributors</title>

      <para>
	<itemizedlist>
	  <listitem><para>Chip Alexander</para></listitem>
	  <listitem><para>Kathy Fernandes</para></listitem>
	  <listitem><para>John Fleck</para></listitem>
	  <listitem><para>Andrea Mankoski</para></listitem>
	  <listitem><para>Nils Pederson</para></listitem>
	  <listitem><para>Sebastian Rittau</para></listitem>
	  <listitem><para>Christian Rose</para></listitem>
	  <listitem><para>Sharon Snider</para></listitem>
	  <listitem><para>Suzanna Smith</para></listitem>
	  <listitem><para>Matthew Thomas</para></listitem>
	</itemizedlist>
      </para>

</sect1>
</chapter>


<bibliography id="bibliography">
  <remark>NO TRADUCIR</remark>
  <para>This bibliography lists books and other resources for software engineers, user interface designers, and human factors specialists, arranged by topic and without a particular ordering. The final section of the bibliography contains information about useful online resources and organizations.</para>
  <bibliodiv>
    <title>General Design</title>
    <bibliomixed id="Dreyfus1967">
      <bibliomset relation="book"><surname>Dreyfuss</surname>, <firstname>Henry</firstname><title role="book">Designing for People</title><address><city>Nueva York</city>, <state>NY</state></address>: <publishername>allworth press</publishername>, <pubdate>2003</pubdate><bibliomisc>A reprint of the 1960s design classic by the designer of everything from the modern airplane cabin to the Bell telephone. Perhaps the best book for introducing the general concerns and thought patterns of design (industrial, product, or interaction), as well as an entertaining read.</bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Mandel1997">
      <bibliomset relation="book"><surname>Mandel</surname>, <firstname>Theo</firstname>. <title role="book">The Elements of User Interface Design</title>. <address><city>Nueva York</city>, <state>NY</state></address>: <publishername>Wiley Computer Publishing</publishername>, <pubdate>1997</pubdate>. <bibliomisc>Un libro útil que cubre todo lo básico y un amplio rango de entornos y nuevos desarrollos como agentes de interfaz, asistentes, interacción de voz, interfaces de usuarios sociales y diseños web.</bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Norman1990">
      <bibliomset relation="book"><surname>Norman</surname>, <firstname>Donald A.</firstname><title role="book">The Design of Everyday Things</title>. <address><city>Nueva York</city>, <state>NY</state></address>: <publishername>Doubleday</publishername>, <pubdate>1990</pubdate>. <bibliomisc>Un libro excepcional y entretenido acerca del diseño detrás de las cosas cotidianas.</bibliomisc></bibliomset>
    </bibliomixed>
  </bibliodiv>
  <bibliodiv>
    <title>Graphical Design</title>
    <bibliomixed id="Horton1994">
      <bibliomset relation="book"><surname>Horton</surname>, <firstname>William</firstname><title role="book">The Icon Book: Visual Symbols for Computer Systems and Documentation</title>. <address><city>Nueva York</city>, <state>NY</state></address>: <publishername>John Wiley &amp; Sons</publishername>, <pubdate>1994</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Misjksenaar1999">
      <bibliomset relation="book"><surname>Misjksenaar</surname>, <firstname>Paul</firstname> y <firstname>Piet</firstname><surname>Westendorpp</surname>. <title role="book">Open Here: The Art of Instructional Design</title>. <address><city>Londres</city>, <country>RU</country></address>: <publishername>Thames &amp; Hudson</publishername>, <pubdate>1999</pubdate><bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Mullet1995">
      <bibliomset relation="book"><surname>Mullet</surname>, <firstname>Kevin</firstname> y <firstname>Darrell</firstname><surname>Sano</surname>. <title role="book">Designing Visual Interfaces: Communication Oriented Techniques</title>. <address><city>Englewood Cliffs</city>, <state>NJ</state></address>: <publishername>Prentice Hall</publishername>, <pubdate>1995</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Rubin1994">
      <bibliomset relation="book"><surname>Rubin</surname>, <firstname>Jeffrey</firstname>. <title role="book">Handbook of Usability Testing: How to Plan, Design and Conduct Effective Tests</title>. <address><city>Nueva York</city>, <state>NY</state></address>: <publishername>John Wiley &amp; Sons</publishername>, <pubdate>1994</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Tufte1990">
      <bibliomset relation="book"><surname>Tufte</surname>, <firstname>Edward R.</firstname><title role="book">Envisioning Information</title>. <address><city>Cheshire</city>, <state>CT</state></address>: <publishername>Graphics Press</publishername>, <pubdate>1990</pubdate><bibliomisc>El segundo clásico trabajo acerca de la previsión del trabajo, por Tufte.</bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Tufte1992">
      <bibliomset relation="book"><surname>Tufte</surname>, <firstname>Edward R.</firstname><title role="book">The Visual Display of Quantitative Information</title>. <edition>Edición de reimpresión</edition>, <address><city>Cheshire</city>, <state>CT</state></address>: <publishername>Graphics Press</publishername>, <pubdate>1992</pubdate><bibliomisc>El primer trabajo clásico acerca de la previsión de la información, por Tufte.</bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Williams1994">
      <bibliomset relation="book"><surname>Williams</surname>, <firstname>Robin</firstname>. <title role="book">The Non-Designer's Design Book: Design and Typographic Principles for the Visual Novice</title>. <address><city>Berkeley</city>, <state>CA</state></address>: <publishername>Peachpit Press</publishername>, <pubdate>1994</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
  </bibliodiv>
  <bibliodiv>
    <title>Usability</title>
    <bibliomixed id="Arlov1997">
      <bibliomset role="book"><surname>Arlov</surname>, <firstname>Laura</firstname>. <title role="book">GUI Design for Dummies</title>. <address><city>Foster City</city>, <state>CA</state></address>: <publishername>IDG Books Worldwide</publishername>, <pubdate>1997</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Cooper2003">
      <bibliomset role="book"><surname>Cooper</surname>, <firstname>Alan</firstname> y <surname>Reimann</surname>, <firstname>Robert</firstname>. <title role="book">Acerca de Face 2.0: The Essentials of User Interface Design</title>. <publishername>John Wiley &amp; Sons</publishername>, <pubdate>2003</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Cooper1999">
      <bibliomset role="book"><surname>Cooper</surname>, <firstname>Alan</firstname>. <title role="book">The Inmates are Running the Asylum : Why High Tech Products Drive us Crazy and How to Restore the Sanity</title>. <publishername>SAMS</publishername>, <pubdate>1999</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Isaacs2001">
      <bibliomset role="book"><surname>Isaacs</surname>, <firstname>Ellen</firstname> y <firstname>Alan</firstname><surname>Walendowski</surname>. <title role="book">Designing from Both Sides of the Screen</title>. <address><city>Indianapolis</city>, <state>IN</state></address>: <publishername>New Riders Publishing</publishername>, <pubdate>2001</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Nielsen1993">
      <bibliomset role="book"><surname>Nielsen</surname>, <firstname>Jakob</firstname>. <title role="book">Usability Engineering</title>. <address><city>San Francisco</city>, <state>CA</state></address>: <publishername>Morgan Kauffman</publishername>, <pubdate>1993</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
    <bibliomixed id="Tog1992">
      <bibliomset role="book"><surname>Tognazzini</surname>, <firstname>Bruce</firstname>. <title role="book">Tog on Interface</title>. <address><city>Reading</city>, <state>MA</state></address>: <publishername>Addison-Wesley</publishername>, <pubdate>1992</pubdate>. <bibliomisc><remark>NO TRADUCIR</remark></bibliomisc></bibliomset>
    </bibliomixed>
  </bibliodiv>
<!--
  <bibliodiv><title>Other Style Guides</title>
    <bibliomixed id="Aqua2002">
      <bibliomset relation="book">
	<corpauthor>Apple Computer, Inc</corpauthor>.
	<title>Inside Mac OS X: Aqua Human Interface Guidelines</title>.
	<address><city>Mountain View</city>, <state>CA</state></address>.
	<publishername>Vervanté</publishername>,
	<pubdate>2002</pubdate>.
	<bibliomisc>[This is a print on demand book also available online from <ulink url="http://developer.apple.com/techpubs/macosx/Essentials/AquaHIGuidelines/">http://developer.apple.com/techpubs/macosx/Essentials/AquaHIGuidelines/</ulink> in HTML and PDF forms.] The style guide to everything Aqua, the Mac OS X user interface. Look here for information on a clean and coherent design.</bibliomisc>
      </bibliomset>
    </bibliomixed>
    <bibliomixed id="IRIX2001">
      <bibliomset relation="book">
	<corpauthor>Silicon Graphics, Inc</corpauthor>.
	<title>IRIX Interactive Desktop User Interface Guidelines</title>.
	<address><city>Lincoln</city>, <state>NE</state></address>.
	<publishername>iUniverse</publishername>,
	<pubdate>2001</pubdate>.
	<bibliomisc>[This book is also available online from <ulink url="http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?cmd=toc&amp;srch=&amp;toccmd=FE&amp;coll=0650&amp;db=bks&amp;pth=/SGI_Developer/UI_Glines">http://techpubs.sgi.com</ulink> in HTML and PDF forms.][This book may be found online at <ulink url="http://techpubs.sgi.com">http://techpubs.sgi.com</ulink> in HTML and PDF forms.] Style guide to the IRIX Interactive Desktop environment. It contains nice concepts, outstanding among them the varios chapters on 3D applications.
	</bibliomisc>
      </bibliomset>
    </bibliomixed>
    <bibliomixed id="Mac1992">
      <bibliomset relation="book">
	<corpauthor>Apple Computer, Inc</corpauthor>.
	<title>Inside Macintosh Human Interface Guidelines</title>.
	<address><city>Reading</city>, <state>MA</state></address>.
	<publishername>Addison-Wesley</publishername>,
	<pubdate>1992</pubdate>.
	<bibliomisc>[This book is also available online from <ulink url="http://developer.apple.com/techpubs/mac/HIGuidelines/HIGuidelines-2.html">http://developer.apple.com/techpubs/mac/HIGuidelines/HIGuidelines-2.html</ulink> in HTML and PDF forms.] The style guide to the classic Macintosh "look and feel".</bibliomisc>
      </bibliomset>
    </bibliomixed>
    <bibliomixed id="Windows1999">
      <bibliomset relation="book">
	<corpauthor>Microsoft Corporation</corpauthor>.
	<title>The Microsoft Windows User Experience</title>.
	<address><city>Redmond</city>, <state>WA</state></address>.
	<publishername>Microsoft Press</publishername>,
	<pubdate>1999</pubdate>.
	<bibliomisc>[This book is also available online from <ulink url="http://msdn.microsoft.com/UI/default.asp">http://msdn.microsoft.com/UI/default.asp</ulink> in HTML form.] The style guide to the Microsoft Windows user interface. Specially good is the chapter on text handling.</bibliomisc>
      </bibliomset>
    </bibliomixed>

  </bibliodiv>
-->
</bibliography>


</book>
