/usr/share/help/es/hig/compatibility.page is in gnome-devel-docs 3.14.1-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 | <?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" type="topic" id="compatibility" xml:lang="es">
<info>
<credit type="author">
<name>Allan Day</name>
<email>aday@gnome.org</email>
</credit>
<include xmlns="http://www.w3.org/2001/XInclude" href="legal.xml"/>
<desc>Using the HIG for cross-platform or GNOME 2 style applications.</desc>
<mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">
<mal:name>Daniel Mustieles</mal:name>
<mal:email>daniel.mustieles@gmail.com</mal:email>
<mal:years>2011 - 2014</mal:years>
</mal:credit>
<mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">
<mal:name>Nicolás Satragno</mal:name>
<mal:email>nsatragno@gnome.org</mal:email>
<mal:years>2013</mal:years>
</mal:credit>
<mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">
<mal:name>Benjamín Valero Espinosa</mal:name>
<mal:email>benjavalero@gmail.com</mal:email>
<mal:years>2011</mal:years>
</mal:credit>
<mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">
<mal:name>Jorge González</mal:name>
<mal:email>jorgegonz@svn.gnome.org</mal:email>
<mal:years>2009</mal:years>
</mal:credit>
</info>
<title>Compatibilidad</title>
<p>These Human Interface Guidelines are primarily targeted towards new GTK+ and GNOME applications, with an emphasis on GNOME 3 integration. However, they are also intended to be useful to cross-platform applications, as well as older applications, which may have been designed and implemented in accordance with the GNOME 2 HIG.</p>
<section id="cross-platform-compatibility">
<title>Compatibilidad con otras plataformas</title>
<p>Cross-platform guidance is provided for those design patterns and UI elements that require special treatment in cross-platform cases. Otherwise, all the design patterns provided in these guidelines can be used in a cross-platform manner.</p>
<p>Since some platforms provide system-level integration for <link xref="menu-bars">menu bars</link>, this pattern is of special relevance for cross-platform applications.</p>
</section>
<section id="gnome-2-compatibility">
<title>Compatibilidad con GNOME 2</title>
<p>These Human Interface Guidelines are an evolution of the GNOME 2 HIG. The design patterns provided improve upon the previous version of the HIG, and encourage more modern application design. Applications that follow this version of the HIG will use space more efficiently, provide a more focused user experience, and will use modern interpretations of key functionality, such as search, online integration, or notifications.</p>
<p>Much of the advice contained within this HIG can be incorporated into GNOME 2 style applications with minimal disruption, and will lead to an improved experience for users. This includes:</p>
<list>
<item><p>New user interface elements, such as popovers.</p></item>
<item><p>Improved GTK+ abilities, like animations.</p></item>
<item><p>Updated guidance on subjects such as visual layout, typography and icon usage.</p></item>
</list>
<p>Incorporating these elements of the guidelines can enhance your application without requiring a major redesign, and all GTK+ and GNOME applications can benefit from them.</p>
<p>At the same time, following some of the design patterns in these guidelines may imply larger-scale design changes for GNOME 2 style applications, particularly if those applications are complex. In particular, replacing window title bars and <link xref="menu-bars">menu bars</link> with a <link xref="header-bars">header bar</link> could be a big change for your application.</p>
<p>These Human Interface Guidelines have been designed to assist you in determining the best design for your application, rather than proposing a single template to be used in all applications. As such, while they recommend <link xref="header-bars">header bars</link> over <link xref="menu-bars">menu bars</link>, they provide guidance on both approaches.</p>
</section>
</page>
|