Allan Day
aday@gnome.org
Calum Benson
Adam Elman
Seth Nickell
Colin Robertson
Ekaterina Gerasimova
kittykat3756@gmail.com 2015
Writing text for your user interface, including capitalization rules.
Alex Puchades
alex94puchades@gmail.com 2015
Daniel Mustieles
daniel.mustieles@gmail.com 2011 - 2015
Nicolás Satragno
nsatragno@gnome.org 2013
Benjamín Valero Espinosa
benjavalero@gmail.com 2011
Jorge González
jorgegonz@svn.gnome.org 2009
Rosa Elena Pérez
rozydicemiau@gmail.com 2014
Oscar Rafael Arachi
arachi910@gmail.com 2014 - 2015
Miguel Ajuech
miguel.ann.28@gmail.com 2014
Adrián Pérez Domínguez
adrian@aztli.org 2015
Celina Osorio Ochoa
chelinoska@gmail.com 2015
Dario Amigon Espinoza
daramigon@gmail.com 2015
Yenisei Ramírez Pérez
yeniseirape@gmail.com 2015
José Roberto Ramíres Mendoza
aczella@gmail.com 2015
Bernardo Sánchez Romero
b.sanchez.rom@gmail.com 2015
Emmanuel Márquez Juárez
resident3333@gmail.com 2015
David Romero Serrano
lemi136@hotmail.com 2015
Omar Garcia Guzman
garciag.omar91@gmail.com 2015
Edilberto Huerta Niño
edilberto.huerta0290@gmail.com 2015

# Escribiendo estilos

Text plays an important role in user interfaces. Take the time to ensure that any text you use is clearly written and easy to understand.

# Guías

Your main goal should be to ensure that text is easy to understand and quick to read.

Keep text short and to the point. This improves speed of comprehension for the user. It also reduces the expansion of text when translated (remember that translated English text can expand up to 30% in some languages).

Do not shorten your text to the point of losing meaning. 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.

Use words, phrases, and concepts that are familiar to the people who will be using your application, rather than terms from the underlying system. This may mean using terms that are associated with the tasks your application supports. For example, in medicine, the paper folder that contains patient information is called a “chart”. Hence, a medical application might refer to a patient record as a “chart” rather than as a “patient database record”.

Use the standard GNOME terms when referring to parts of the user interface, such as ‘pointer’ and ‘window’. You can find a full list of these in the GNOME Documentation Style Guide, Recommended Terminology.

Avoid repetition where possible.

# Capitalización

Two styles of capitalization are used in GNOME user interfaces: header capitalization and sentence capitalization.

## Header Capitalization

Header capitalization should be used for any headings, including header bar headings and page, tab and menu titles. It should also be used for short control labels that do not normally form proper sentences, such as button labels, switch labels and menu items.

Capitalize the first letter of:

Todas las palabras de cuatro o más letras.

Verbs of any length, such as “Be”, “Are”, “Is”, “See” and “Add”.

The first and last word.

Hyphenated words; for example: “Self-Test” or “Post-Install”.

Por ejemplo: «Crear un documento», «Buscar y reemplazar», «Documento no encontrado».

## Sentence Capitalization

Sentence capitalization should be used for labels that form sentences or that run on to other text, including labels for check boxes, radio buttons, sliders, text entry boxes, field labels and combobox labels. It should also be used for explanatory or body text, such as in dialogs or notifications.

Capitalize the first letter of:

La primera palabra.

Any words normally capitalized in sentences, such as proper nouns.

For example: “The document cannot be found in this location.” “Finding results for London.”

# Elipsis (…)

Use an ellipsis (…) at the end of a label if further input or confirmation is required from the user before the action can be carried out. For example, Save As…, Find… or Delete….

Do not add an ellipsis to labels such as Properties or Preferences. While these commands open windows that can incorporate further functionality, the label does not specify an action, and therefore does not need to communicate that further input or confirmation is required.