Typography refresh/es

Este documento describe una actualización hecha recientemente a la apariencia predeterminada del software MediaWiki y los proyectos de Wikimedia, «Vector», con respecto a la tipografía. (Nota: el cambio todavía no se ha realizado en el repositorio «core» de MediaWiki. Hasta el $date, lo mencionado en tiempo presente aún se encuentra en el futuro.)

Resumen de los cambios
We approached this update to Wikimedia's default typography with the following requirements in mind:

Legibilidad: Los tipos de letra deben ser legibles a cualquier tamaño. La tipografía como elemento debe ayudar a diferenciar claramente los elementos de interfaz del contenido del artículo. En ese contexto, cambiamos las siguentes cambios:
 * 1) Consistency: A consistent visual experience across desktop and mobile devices.
 * 2) Availability: All typefaces we use must be already usable (or made available) on all platforms where Wikimedia projects are present. Any selections must degrade gracefully across devices and platforms (Mac OS X, Windows, Linux, and mobile operating systems).
 * 3) Accessibility: Wikimedia content must be highly accessible to all, including those with impairments.


 * New font specifications: We have set the following font families: heading styles have been set to "Linux Libertine, Georgia, Times, serif". Body copy (the main text of pages) has been set to "Helvetica Neue, Helvetica, Arial, sans-serif".


 * Note that these lists do not mean you will receive all of these fonts. Rather, your browser and operating system will look for the first font in the list that you have installed, and will present that.


 * New spacing and sizing for headings, body copy, and leading: With the current text width, headings need to clearly stand out and the leading (whitespace between lines) needs to be sufficient to enable readability without creating eye fatigue. Headings will now be set to the following: H1 (page titles) will be 1.3/1.8em, H2 (main section headings) will be 1.3/1.4em. H3 will be 1.6/1.17em, H4 1.6/1em, H5 1.6/1em. The body copy has been increased to 0.875em (from 0.8em). Depending on your browser and operating system, this will translate to slightly different pixel values, but overall results in a slightly larger body font size. The superscript (sup) and subscript (sub) line-heights are now set to 1, to fix a long-standing problem with reference numbers affecting the leading.


 * New body font color: In hex triplets, the body copy color is now set to  on , from   on  . In less technical terms, this means the color has changed from pure black text on a pure white background, to very dark grey text on pure white background. (Colors for links, headings, and other elements have not changed.)

Preguntas frecuentes
Los siguentes párafos son respuestas a unas preguntas claves acerca de este cambio.

¿Quienes verán los cambios?
Todos los usarios de sitios de Wikipedia que usan el «skin>> estandár Vector, incluso los lectores y editores. Usarios que usan sus preferencias o otro metodo de usar un «skin» alternativo, como Monobook o Cologne Blue, no verán cambios.

Nota que los usarios que han customizados su CSS personal, o que usan un sitio en que los administradores locales han alterado el CSS del todo el sitio, pueden notar discrepencias con las nuevas opciones estandares. Por favor, ve este resumen y estas Preguntas Frecuentes para ver si se puede atribuir un elemento particular del diseño a este cambio.

Para empezar, ¿qué problemas existían con la tipografía previa?
El texto es nuestro elemento visual essensial de los proyectos de Wikimedia, aunque sea una encyclopedia (como Wikipedia) o un proyecto más pequeño como Wikisource y Wikibooks. Queremos que nuestros usarios sientan precisión, reliabilidad, y claridad en nuestro diseño, como el contenido que leen. Antes de esta actualización de la tipografía, tuvimos más que 20 tamaños de letra arbitrariamente decidios solamente en ordenadoras sobremesa, que aparecen inconsistentemente para nuestros usarios. El tamaño de letra fue demasiado pequeño para muchos lectores, y la altura de linea dificultó la lectura de contenido largo. Para títulos, deben actuar como puntos de entrada en páginas largas de texto y se estializan para ayudar la legibilidad. Buscamos lograr un balance mejor y cohesión para usarios que ojean la página o leen articulos largos.

Se abordó los problemas operativos de nuestros estilos vijeos por mejoras de nuestro tipografía móvil. Esto nos dio la oportunidad de probar un tamaño de letra más grande, de aumentar el primer renglón, y títulos de fuentes serif. Ahora, es el momento de abordar la legibilidad y la accesibilidad de todos idiomas/proyectos, y también de crear consistencia del lenguaje de diseño incluso en los sobremesas, moviles y apps.

¿Hay una fuente perfecta que caje todas nuestras necesidades de legibilidad de todas las escritura? ¿Pensamos que es este?
No, no hay una sola fuente perfecta que represente... Tenemos que tomar una decisión práctica a partir de lo que encaja bien con estes requisitos, dentro de nuestras limitaciones. Mil millones de usarios leen Wikipedia en aparatos diferentes cada día. Las selecciones correntes de fuentes mejorarán la legibilidad y consistancia entre platformas, aunque no sean perfectos.
 * 1) Ubiquidad: esto es availabilidad en todos sistemas operativos de sobremesas y móviles.
 * 2) Representación correcta de glifos y diacríticos: para cientos de escrituras no latinas, además para buen «kerning» de parejas de letras, para que usarios no tengan que bizquear para leer la letra.
 * 3) Tamaño-x respectable: para que el texto es legible a los tamaños pequeños para cosas como navigación de la izquierda, leyendas, terminos de servicio o información secundaria.
 * 4) «Hinting»: para evitar la letra borrosa en tamaños pequeños, particularmente en Windows.

¿Por qué se ha aumentado el tamaño del texto y del primer renglón?
Esto es un cambio pequeño y conservativo. El tamaño del texto previo era ilegible por muchos usarios. Encontramos por comentario de usarios que se usa «zooming» del texto extensivamente para mejorar la legibilidad aún para los que tienen problemas o discapacidades básicos de visión, puesto que eforzamos en hacer la información accesible a todos los usarios, este cambio nos parece un requisito basico para cualquier mejora. Junto con el tamaño de letra, se ha aumentado el primer renglón a 21px de primer renglón, según estandares tipográficos de primer renglón esto es 120% del tamaño de letra. Esto ayuda a los lectores que pasan la introducción y leen párafos largos.

El cuerpo del texto es el enfoque de las páginas en proyectos Wikimedia. Para la mayoría de proyectos de lenguaje el tamaño de letra es pequeño y denso con nuestro metodo corriente. La falta de lo amplio ayuda con la eficacia pero crea fatigo de los ojos con lectura extendida. Además, no se recomienda menos de 14px para escrituras no latinas. Palabras llevan superíndeces y glifos que se tende aplastar y no se puede descifrarlas sin bizquear.

¿Por qué se están utilizando tipos con remates (serif) en los encabezados?
Combining serif and sans-serif is not an unusual or original idea. We do so in this case to provide better contrast and distinction between body and headings. Headings act as entry points when users are scanning a page, looking for information. Both headings and images play an important role in breaking up the visual monotony of the page, which is of critical importance considering that much of Wikimedia content (content pages, discussion pages, help text, policies, etc.) are quite lengthy and have many sections.

Why did we specify Linux Libertine, Georgia, and Times as the serif fonts?
Section titles are entry points into the article. A serif font provides visual differentiation and character compared to the body copy, which helps a user scan the page. Serif are also well-known for conveying a traditional demeanor that is in keeping with our design goals.

Linux Libertine is not widely available, but is a well-designed and free/open serif font that is also used in the Wikipedia logo. This makes it a ubiquitous part of the Wikimedia design language, as well as being appropriate for use in headings. Georgia is a font optimized for browsers and screens. It is also widely available on our most popular platforms, including for users of Windows, Mac OSX, and iOS. Linux Libertine and Georgia act as good complementary fonts, and pair well with Helvetica and Arial. Times is set specifically to ensure that users on Linux systems have a good serif by default – Linux systems do not by default include Linux Libertine, nor Georgia. By setting Times, most Linux users will see Nimbus Roman No9 L.

Languages and scripts for which problems have been reported with Georgia or Times include Russian/Cyrillic, Hebrew, Arab, Polish, Chinese, Japanese and Korean.

Why did we specify new sans-serif fonts?
The previous state of our body content is that only "sans-serif" was specified, leaving it up to the browser to use its default sans-serif. With the exception of Helvetica, Arial and Nimbus Sans L, the fonts that most browsers use in this condition do not account for proper rendering of glyphs, pairs, and diacritical marks at small sizes. There is no free/open font that addresses this need and is ubiquitously available (see table).

We specify Neue Helvetica for Mac users, as it is a slightly more developed version of Helvetica where punctuation has been improved, the x-height is slightly more consistent, and in some cases it has more rounded bowls and counters. Overall it is an optimization of Helvetica, though it may not be as ideal in all scripts.

We specify fonts both to achieve consistency across devices and platforms and to guarantee appropriate readability and rendering at small sizes for Latin and non-Latin scripts alike. With the specifications in place, users who are interested can download the free/open fonts that have been tested or report issues to us for the fallback cases, which will allow us to address issues in a more systematic manner.

In the past, we experimented with several alternative fonts that were freely-licensed, including: Arimo, Liberation Sans, and others. Ultimately these fonts are either not commonly installed by users (creating no effect) or they render poorly on older systems or those without font smoothing/hinting.

Why did we include non-free fonts in the font stack?
The stack specified a range of fonts from Helvetica Neue to Arial that are available across all major platforms. Even though Arial is widely used as a default, we need to specify it so that the CSS degradation is predictable. To ensure a reliable experience to users across platforms as best as we can, we decided to include non-free fonts in the stack since many operating systems (such as Windows, MacOS, and iOS) do not have any FOSS fonts installed by default. Meanwhile many operating systems will use a FOSS font (such as Nimbus Sans L) in place of "Helvetica".

It is particularly important to note that, because of the way CSS font-family settings work, specifying a particular font does not create a hard dependency on that font, nor does it cause the user to download that font. This means that fonts we specify only appear if the user has them already, and Wikimedia text will continue to appear regardless of whether you have a particular font or not.

¿No se podían emplear tipos de letra web (web fonts)?
Webfonts is a system to deliver a font to users who do not have it installed. This involves having a user's browser download a font we provide, which causes additional resources to load and would have a negative impact on site performance (i.e. how fast pages load). This is particularly true for older browsers. In the future we may explore using webfonts, but for now this update provides greater readability and consistency while not degrading page load times.

¿Por qué se ha modificado el color del cuerpo de texto?
The new values ( on  ) have a contrast ratio of 15.3:1, which is an AAA rating according to WCAG 2.0 1.4.6. Pure black for both body copy and captions is not recommended against white for several reasons. Dyslexic users are sensitive to the juxtaposition of pure black text on a pure white background due to its high contrast. This can cause the words to swirl or blur together. To avoid this, use a slightly off-white color for your background, like a light gray, or decrease the contrast between foreground (text) and background. For users without accessibility issues, the harsh contrast of pure black on pure white can increase eye strain as well.

¿Cómo es que todo esto ocurrió?
This typography update was first tested for four months, and then released on mobile web for all Wikimedia projects in October 2012. These included font stack declarations for serif headings and sans serif body copy, as well as increased type size and leading for body copy and captions.

These changes were later brought into desktop as a beta feature, starting in November 2013. This beta feature then went through three major iterations based on community feedback.

How did we get feedback?
Many of the typography changes were first tested on mobile in October 2012, much of the learning was integrated into the typography beta feature for desktop which was launched October 2013 and went through three major releases. During that time the beta feature was used by over 14,000 users across the top 10 Wikipedias, and more than 100 discussion threads were created on the feature's Talk page.

Can I opt out of changes to the default fonts?
Yes. It is possible for logged-in users of Wikimedia sites to customize their personal CSS (i.e. Special:MyPage/vector.css on each wiki) to override some or all of the changes. You can copy User:Cathfolant/typographyrefreshoverride.css into your personal CSS if you don't want to learn CSS in order to opt out of the changes. You may also of course choose to switch to another skin entirely, in your Preferences under the Appearance tab. Last but not least, you can define the default font your browser uses to display “serif” and “sans-serif” fonts, if your system does not have any of these specified fonts this browser preference will be used instead.

¿Lo probamos en una variedad de navegadores y sistemas operativos?
Yes. The new font stack was tested on the following operating systems: Windows XP, Windows 7, Windows 8, Ubuntu Linux, Mac OS X 10.8-9, iOS 6 and 7, Android, and Chrome OS. Size, leading, glyphs, hinting and font renders were tested on Windows, Ubuntu Linux, Mac OS X 10.8, Android, and Chrome OS.

¿Cómo se adaptarán los proyectos en otras lenguas a estos cambios?
Por defecto, la actualización de la tipografía pondrá en accion a todos proyectos (como parte del «skin» Vector). Puede ser idiomas que necesiten omitir algunos de estos estilos para acomodar escrituras particulares. Por ejemplo, algunas escrituras necesitan una altura más alta o un tamaño de fuente más grande. Cada wiki pueden omitir estes estilos particulares por editar su página MediaWiki:Vector.css. Animamos los otros proyectos a auditar los cambios introducidos por la actualización, y a omitir el CSS solamente donde está necesario a partir de sus escrituras.

También, vea los problemas de que ya nos hemos dado cuenta sobre nuestros otros proyectos de lenguaje.

¿Y las escrituras no latinas?
The old type size in non-Latin scripts was 0.8em (12.8px). This squashes glyphs and superscripts significantly along with the type being too small to read. Scripts examined were Urdu, Marathi, Bahasa Melayu, Chinese, Korean, Navajo. The body copy type size increase will improve readability for most scripts. Specifically for Navajo, an override will be provided because character pairs render strangely in Helvetica.

Inline CSS guidance can be provided to ensure that languages make overrides on a case-by-case basis as needed. Please comment on the Talk page if you primarily use a non-Latin script and encounter significant problems.

Did you run any controlled experiments e.g. A/B or split tests to measure impact of the new typography?
No.

We often first launch new features in controlled experiments, to objectively measure their performance and test hypotheses about positive impact they might have. In the most common version (an A/B or split test) we randomly select a sample of readers or editors, give half the new version, and give half no new experience. In this case, Foundation research scientists advised against running any A/B tests or other controlled experiments. It is unlikely that minor typography changes alone would make a large impact on reading-related metrics like time on site, number of page views per visitor etc., which could be measured with confidence.

Related goals, like enhanced trust in Wikimedia sites or comprehension in reading, are not the kind of data we can best learn about on a quantitative basis, or which are also largely impacted by unrelated factors like the page content and subject, what type of page is being read (Talk versus articles, for example), and more.

Can using these new fonts cause Wikipedia to be slower for me?
No. We typically measure the site performance impact of a new feature, meaning whether it makes pages take longer to load. In this case, we are not adding to the list of resources that a user must download to view a page, so any change in performance will be negligible.

Enlaces al código

 * Vector style variables in LESS:
 * Plus local wiki files such as en:MediaWiki:Vector.css and en:MediaWiki:Common.css
 * Plus local wiki files such as en:MediaWiki:Vector.css and en:MediaWiki:Common.css
 * Plus local wiki files such as en:MediaWiki:Vector.css and en:MediaWiki:Common.css