mirrors/wayland
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland.git synced 2026-04-02 07:15:53 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: consistently indent the xml files by 2 spaces

Browse source 
2 spaces is enough for xml, otherwise we end up with too little room for the
actual text.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
Peter Hutterer 2012-03-29 10:50:13 +10:00 • committed by Kristian Høgsberg
parent 966e8ec9c0
commit f68e156b8f
5 changed files with 383 additions and 383 deletions
Download patch file Download diff file Expand all files Collapse all files

66
doc/Wayland/en_US/Overview.xml
View file

@ -23,23 +23,23 @@
<section id="sect-Wayland-Overview-Replacing-X11"> <section id="sect-Wayland-Overview-Replacing-X11">
<title>Replacing X11</title> <title>Replacing X11</title>
<para> <para>
In Linux and other Unix-like systems, the X stack has grown to In Linux and other Unix-like systems, the X stack has grown to
encompass functionality arguably belonging in client libraries, encompass functionality arguably belonging in client libraries,
helper libraries, or the host operating system kernel. Support for helper libraries, or the host operating system kernel. Support for
things like PCI resource management, display configuration management, things like PCI resource management, display configuration management,
direct rendering, and memory management has been integrated into the X direct rendering, and memory management has been integrated into the X
stack, imposing limitations like limited support for standalone stack, imposing limitations like limited support for standalone
applications, duplication in other projects (e.g. the Linux fb layer applications, duplication in other projects (e.g. the Linux fb layer
or the DirectFB project), and high levels of complexity for systems or the DirectFB project), and high levels of complexity for systems
combining multiple elements (for example radeon memory map handling combining multiple elements (for example radeon memory map handling
between the fb driver and X driver, or VT switching). between the fb driver and X driver, or VT switching).
</para> </para>
<para> <para>
Moreover, X has grown to incorporate modern features like offscreen Moreover, X has grown to incorporate modern features like offscreen
rendering and scene composition, but subject to the limitations of the rendering and scene composition, but subject to the limitations of the
X architecture. For example, the X implementation of composition adds X architecture. For example, the X implementation of composition adds
additional context switches and makes things like input redirection additional context switches and makes things like input redirection
difficult. difficult.
</para> </para>
<mediaobject> <mediaobject>
<imageobject> <imageobject>
@ -52,22 +52,22 @@ difficult.
the screen. the screen.
</para> </para>
<para> <para>
Over time, X developers came to understand the shortcomings of this Over time, X developers came to understand the shortcomings of this
approach and worked to split things up. Over the past several years, approach and worked to split things up. Over the past several years,
a lot of functionality has moved out of the X server and into a lot of functionality has moved out of the X server and into
client-side libraries or kernel drivers. One of the first components client-side libraries or kernel drivers. One of the first components
to move out was font rendering, with freetype and fontconfig providing to move out was font rendering, with freetype and fontconfig providing
an alternative to the core X fonts. Direct rendering OpenGL as a an alternative to the core X fonts. Direct rendering OpenGL as a
graphics driver in a client side library went through some iterations, graphics driver in a client side library went through some iterations,
ending up as DRI2, which abstracted most of the direct rendering ending up as DRI2, which abstracted most of the direct rendering
buffer management from client code. Then cairo came along and provided buffer management from client code. Then cairo came along and provided
a modern 2D rendering library independent of X, and compositing a modern 2D rendering library independent of X, and compositing
managers took over control of the rendering of the desktop as toolkits managers took over control of the rendering of the desktop as toolkits
like GTK+ and Qt moved away from using X APIs for rendering. Recently, like GTK+ and Qt moved away from using X APIs for rendering. Recently,
memory and display management have moved to the Linux kernel, further memory and display management have moved to the Linux kernel, further
reducing the scope of X and its driver stack. The end result is a reducing the scope of X and its driver stack. The end result is a
highly modular graphics stack. highly modular graphics stack.
</para> </para>
</section> </section>