Context Navigation

r5e18c49c	rc2ee009c
39	39	and abstraction, integrated windowing system with support for
40	40	translucent windows and multiple display layers on top of the Linux
41		framebuffer device.</para></sect3>
	41	frame buffer device.</para></sect3>
42	42
43	43	</sect2>

general/graphlib/directfb/directfb-intro.xml

r5e18c49c	rc2ee009c
2	2	<title>Introduction to <application>DirectFB</application></title>
3	3
4		<para><application>DirectFB</application> is a graphics library on top of the Linux framebuffer
	4	<para><application>DirectFB</application> is a graphics library on top of the Linux frame buffer
5	5	device. It offers maximum hardware accelerated performance at a
6	6	minimum of resource usage and overhead.</para>

-              r5e18c49c
+              rc2ee009c
 <sect3><title>icclink</title>
 <para><command>icclink</command> links two or more profiles into a
 single devicelink profile.</para></sect3>
+single device link profile.</para></sect3>
 <sect3><title>icctrans</title>
 <para><command>icctrans</command> is a ColorSpace conversion
+<para><command>icctrans</command> is a Color Space conversion
 calculator.</para></sect3>

-              r5e18c49c
+              rc2ee009c
 <para>The libungif package contains libraries for reading all
 <acronym>GIF</acronym>s and writing uncompressed ones as well as programs for
+<acronym>GIF</acronym>s and writing non-compressed ones as well as programs for
 converting and working with <acronym>GIF</acronym> files.  The libraries are
 useful for any graphics program wishing to deal with <acronym>GIF</acronym>
 …
 up images.</para>
 <para>The reason libungif only writes uncompressed <acronym>GIF</acronym>s
+<para>The reason libungif only writes non-compressed <acronym>GIF</acronym>s
 is due to a legal issue with <acronym>LZW</acronym> compression (which Unisys
 claims a patent on). Reading <acronym>GIF</acronym>s is not a problem as the
 uncompression routines do not seem to be limited in this way.  Note that this
+decompression routines do not seem to be limited in this way.  Note that this
 has in the past been disputed.  The best way to avoid this whole mess is to
 simply use libungif for looking at <acronym>GIF</acronym> images on the web,

r5e18c49c	rc2ee009c
19	19	<sect3><title>libvgagl library</title>
20	20	<para><filename class="libraryfile">libvgagl</filename> is a fast
21		frame~~buffer-~~level graphics library based on libvga.</para></sect3>
	21	frame buffer level graphics library based on libvga.</para></sect3>
22	22
23	23	<sect3><title>dumpreg</title>

r5e18c49c	rc2ee009c
13	13	The first test will be whether to install a boot script in the <filename
14	14	class="directory">/etc/rc.d/init.d</filename> directory with the
15		appropriate symbolic links in runlevels 2, 3, 4, and 5. The second is to
	15	appropriate symbolic links in run levels 2, 3, 4, and 5. The second is to
16	16	stop any current fcron processes and start a new one. Since this is
17	17	probably your first install and we want a boot script based upon the

-              r5e18c49c
+              rc2ee009c
 <para>Note that by default, <command>hdparm</command> is installed in
+<filename>/sbin</filename> as some systems may require it on bootup
+before <filename>/usr</filename> is mounted.  If you wish to install
+<command>hdparm</command> under the <filename>/usr</filename> hierarchy, then replace the
+above commands with the following:</para>
+<filename class="directory">/sbin</filename> as some systems may require it
+during the boot process before <filename class="directory">/usr</filename>
+is mounted.  If you wish to install <command>hdparm</command> under the
+<filename class="directory">/usr</filename> hierarchy, then replace the above
+commands with the following:</para>
 <screen><userinput><command>make &amp;&amp;

Note: See TracChangeset for help on using the changeset viewer.