Author: manuel
Date: 2005-05-22 04:28:05 -0600 (Sun, 22 May 2005)
New Revision: 4448
Modified:
trunk/BOOK/gnome/add/gtkhtml.xml
trunk/BOOK/postlfs/config/profile.xml
trunk/BOOK/xsoft/graphweb/dillo.xml
Log:
Removed remaining inline tags into titles.
Modified: trunk/BOOK/gnome/add/gtkhtml.xml
===================================================================
--- trunk/BOOK/gnome/add/gtkhtml.xml 2005-05-22 10:19:50 UTC (rev 4447)
+++ trunk/BOOK/gnome/add/gtkhtml.xml 2005-05-22 10:28:05 UTC (rev 4448)
@@ -27,7 +27,7 @@
</indexterm>
<sect2 role="package">
- <title>Introduction to <application>GtkHTML</application></title>
+ <title>Introduction to GtkHTML</title>
<para>The <application>GtkHTML</application> package contains a
lightweight HTML rendering/printing/editing engine. This is an
@@ -67,7 +67,7 @@
</sect2>
<sect2 role="installation">
- <title>Installation of <application>GtkHTML</application></title>
+ <title>Installation of GtkHTML</title>
<para>Install <application>GtkHTML</application> by running the following
commands:</para>
Modified: trunk/BOOK/postlfs/config/profile.xml
===================================================================
--- trunk/BOOK/postlfs/config/profile.xml 2005-05-22 10:19:50 UTC (rev
4447)
+++ trunk/BOOK/postlfs/config/profile.xml 2005-05-22 10:28:05 UTC (rev
4448)
@@ -19,14 +19,14 @@
referred to as just "the shell") uses a collection of startup files to
help create an environment. Each file has a specific use and
may affect login and interactive environments differently. The files in
- the <filename class="directory">/etc</filename> directory generally provide
+ the <filename class="directory">/etc</filename> directory generally provide
global settings. If an equivalent file exists in your home directory it may
override the global settings.</para>
<para>An interactive login shell is started after a successful login, using
- <filename>/bin/login</filename>, by reading the
<filename>/etc/passwd</filename>
- file. This shell invocation normally reads
<filename>/etc/profile</filename>
- and its private equivalent <filename>~/.bash_profile</filename> upon
+ <filename>/bin/login</filename>, by reading the
<filename>/etc/passwd</filename>
+ file. This shell invocation normally reads <filename>/etc/profile</filename>
+ and its private equivalent <filename>~/.bash_profile</filename> upon
startup.</para>
<para>An interactive non-login shell is normally started at the command-line
@@ -47,11 +47,11 @@
invocation of the shell. It is read and executed when a user exits from an
interactive login shell.</para>
- <para>To the standard files, <filename>/etc/bashrc</filename> is called from
- the user's <filename>~/.bashrc</filename> for system wide initialization of
+ <para>To the standard files, <filename>/etc/bashrc</filename> is called from
+ the user's <filename>~/.bashrc</filename> for system wide initialization of
non-login shells.</para>
- <para>For more information see <command>info bash</command> --
+ <para>For more information see <command>info bash</command> --
<emphasis role="strong">Nodes: Bash Startup Files and Interactive
Shells.</emphasis></para>
@@ -65,7 +65,7 @@
<para>Here is a base <filename>/etc/profile</filename>. This file starts by
setting up some helper functions and some basic parameters. It specifies
some
<filename>bash</filename> history parameters and, for security purposes,
- disables keeping a permanent history file for the <systemitem
+ disables keeping a permanent history file for the <systemitem
class="username">root</systemitem> user. It also sets a
default user prompt. It then calls small, single purpose scripts in the
<filename class='directory'>/etc/profile.d</filename> directory to provide
most
@@ -81,14 +81,14 @@
# Written for Beyond Linux From Scratch
# by James Robertson <[EMAIL PROTECTED]>
# modifications by Dagmar d'Surreal <[EMAIL PROTECTED]>
-
+
# System wide environment variables and startup programs.
-
+
# System wide aliases and functions should go in /etc/bashrc. Personal
# environment variables and startup programs should go into
# ~/.bash_profile. Personal aliases and functions should go into
# ~/.bashrc.
-
+
# Functions to help us manage paths. Second argument is the name of the
# path variable to be modified (default: PATH)
pathremove () {
@@ -103,20 +103,20 @@
done
export $PATHVARIABLE="$NEWPATH"
}
-
+
pathprepend () {
pathremove $1 $2
local PATHVARIABLE=${2:-PATH}
export $PATHVARIABLE="$1${!PATHVARIABLE:+:${!PATHVARIABLE}}"
}
-
+
pathappend () {
pathremove $1 $2
local PATHVARIABLE=${2:-PATH}
export $PATHVARIABLE="${!PATHVARIABLE:+${!PATHVARIABLE}:}$1"
}
-
+
# Set the initial path
export PATH=/bin:/usr/bin
@@ -124,21 +124,21 @@
pathappend /sbin:/usr/sbin
unset HISTFILE
fi
-
+
# Setup some environment variables.
export HISTSIZE=1000
export HISTIGNORE="&:[bf]g:exit"
#export PS1="[EMAIL PROTECTED] \w]\\$ "
export PS1='[EMAIL PROTECTED]:\w\$ '
-
+
for script in /etc/profile.d/*.sh ; do
if [ -r $script ] ; then
. $script
fi
done
-
+
# Now to clean up
-unset pathremove pathprepend pathappend
+unset pathremove pathprepend pathappend
# End /etc/profile</literal>
EOF</userinput></screen>
@@ -150,7 +150,7 @@
<primary sortas="e-etc-profile.d">/etc/profile.d</primary>
</indexterm>
- <para>Now create the <filename
class='directory'>/etc/profile.d</filename>
+ <para>Now create the <filename
class='directory'>/etc/profile.d</filename>
directory, where the individual initialization scripts are placed.</para>
<screen role="root"><userinput>install --directory --mode=0755 --owner=root
--group=root /etc/profile.d</userinput></screen>
@@ -174,7 +174,7 @@
<literal># Setup for /bin/ls to support color, the alias is in /etc/bashrc.
if [ -f "/etc/dircolors" ] ; then
eval $(dircolors -b /etc/dircolors)
-
+
if [ -f "$HOME/.dircolors" ] ; then
eval $(dircolors -b $HOME/.dircolors)
fi
@@ -192,12 +192,12 @@
</indexterm>
<para>This script adds several useful paths to the <envar>PATH</envar>
and
- <envar>PKG_CONFIG_PATH</envar> environment variables. If you want, you
- can uncomment the last section to put a dot at the end of your path.
This will
- allow executables in the current working directory to be executed
without
- specifiying a ./, however you are warned that this is generally
considered a
+ <envar>PKG_CONFIG_PATH</envar> environment variables. If you want, you
+ can uncomment the last section to put a dot at the end of your path.
This will
+ allow executables in the current working directory to be executed without
+ specifiying a ./, however you are warned that this is generally
considered a
security hazard.</para>
-
+
<screen role="root"><userinput>cat > /etc/profile.d/extrapaths.sh <<
"EOF"
<literal>if [ -d /usr/local/lib/pkgconfig ] ; then
pathappend /usr/local/lib/pkgconfig PKG_CONFIG_PATH
@@ -231,8 +231,8 @@
<primary
sortas="e-etc-profile.d-readline.sh">/etc/profile.d/readline.sh</primary>
</indexterm>
- <para>This script sets up the default <filename>inputrc</filename>
- configuration file. If the user does not have individual settings, it
uses the
+ <para>This script sets up the default <filename>inputrc</filename>
+ configuration file. If the user does not have individual settings, it
uses the
global file.</para>
<screen role="root"><userinput>cat > /etc/profile.d/readline.sh <<
"EOF"
@@ -252,17 +252,17 @@
<primary
sortas="e-etc-profile.d-tinker-term.sh">/etc/profile.d/tinker-term.sh</primary>
</indexterm>
- <para>Some applications need a specific <envar>TERM</envar> setting to
+ <para>Some applications need a specific <envar>TERM</envar> setting to
support color.</para>
<screen role="root"><userinput>cat > /etc/profile.d/tinker-term.sh <<
"EOF"
-<literal># This will tinker with the value of TERM in order to convince
certain
+<literal># This will tinker with the value of TERM in order to convince certain
# apps that we can, indeed, display color in their window.
-
+
if [ -n "$COLORTERM" ]; then
export TERM=xterm-color
fi
-
+
if [ "$TERM" = "xterm" ]; then
export TERM=xterm-color
fi</literal>
@@ -276,9 +276,9 @@
<indexterm zone="postlfs-config-profile umask.sh">
<primary
sortas="e-etc-profile.d-umask.sh">/etc/profile.d/umask.sh</primary>
</indexterm>
-
- <para>Setting the <command>umask</command> value is important for
security.
- Here the default group write permissions are turned off for system users
and when
+
+ <para>Setting the <command>umask</command> value is important for
security.
+ Here the default group write permissions are turned off for system users
and when
the user name and group name are not the same.</para>
<screen role="root"><userinput>cat > /etc/profile.d/umask.sh << "EOF"
@@ -299,7 +299,7 @@
<primary sortas="e-etc-profile.d-X.sh">/etc/profile.d/X.sh</primary>
</indexterm>
- <para>If <application>X</application> is installed, the
<envar>PATH</envar>
+ <para>If <application>X</application> is installed, the
<envar>PATH</envar>
and <envar>PKG_CONFIG_PATH</envar> variables are also updated.</para>
<screen role="root"><userinput>cat > /etc/profile.d/X.sh << "EOF"
@@ -320,12 +320,12 @@
<primary
sortas="e-etc-profile.d-titlebars.sh">/etc/profile.d/titlebars.sh</primary>
</indexterm>
- <para>This script shows an example of a different way of setting the
prompt.
- The normal variable, <envar>PS1</envar>, is supplemented by
- <envar>PROMPT_COMMAND</envar>. If set, the value of
- <envar>PROMPT_COMMAND</envar> is executed as a command prior to
+ <para>This script shows an example of a different way of setting the
prompt.
+ The normal variable, <envar>PS1</envar>, is supplemented by
+ <envar>PROMPT_COMMAND</envar>. If set, the value of
+ <envar>PROMPT_COMMAND</envar> is executed as a command prior to
issuing each primary prompt.</para>
-
+
<screen role="root"><userinput>cat > /etc/profile.d/xterm-titlebars.sh
<< "EOF"
<literal># The substring match ensures this works for "xterm" and
"xterm-xfree86".
if [ "${TERM:0:5}" = "xterm" ]; then
@@ -337,22 +337,22 @@
</sect3>
<sect3 id="i18n.sh">
- <title><filename>/etc/profile.d/i18n.sh</filename></title>
+ <title>'/etc/profile.d/i18n.sh'</title>
<indexterm zone="postlfs-config-profile i18n.sh">
<primary
sortas="e-etc-profile.d-i18n.sh">/etc/profile.d/i18n.sh</primary>
</indexterm>
- <para>This script shows how to set some environment variables necessary
for
- native language support. Setting these variables properly gives
you:</para>
+ <para>This script shows how to set some environment variables necessary
for
+ native language support. Setting these variables properly gives
you:</para>
<itemizedlist>
<listitem>
<para>the output of programs translated into your native
language</para>
</listitem>
<listitem>
- <para>correct classification of characters into letters, digits and
- other classes – this is necessary for
<application>Bash</application>
+ <para>correct classification of characters into letters, digits and
+ other classes – this is necessary for
<application>Bash</application>
to accept keystrokes properly in non-English locales</para>
</listitem>
<listitem>
@@ -366,24 +366,24 @@
</listitem>
</itemizedlist>
- <para>Replace <replaceable>[ll]</replaceable> with the two-letter code
for
- your language (e.g., <quote>en</quote>) and
- <replaceable>[CC]</replaceable> with the two-letter code for your
country
- (e.g., <quote>GB</quote>). Also you may need to specify (and this is
actually
- the preferred form) your character encoding (e.g.,
<quote>iso8859-1</quote>)
- after a dot (so that the result is <quote>en_GB.iso8859-1</quote>).
Issue the
+ <para>Replace <replaceable>[ll]</replaceable> with the two-letter code
for
+ your language (e.g., <quote>en</quote>) and
+ <replaceable>[CC]</replaceable> with the two-letter code for your country
+ (e.g., <quote>GB</quote>). Also you may need to specify (and this is
actually
+ the preferred form) your character encoding (e.g.,
<quote>iso8859-1</quote>)
+ after a dot (so that the result is <quote>en_GB.iso8859-1</quote>).
Issue the
following command for more information:</para>
<screen><userinput>man 3 setlocale</userinput></screen>
- <para>The list of all locales supported by
<application>Glibc</application>
+ <para>The list of all locales supported by
<application>Glibc</application>
can be obtained by running the following command:</para>
-<screen><userinput>locale -a</userinput></screen>
+<screen><userinput>locale -a</userinput></screen>
- <para>After you are sure about your locale settings, create the
- <filename>/etc/profile.d/i18n.sh</filename> file:</para>
-
+ <para>After you are sure about your locale settings, create the
+ <filename>/etc/profile.d/i18n.sh</filename> file:</para>
+
<screen role="root"><userinput>cat > /etc/profile.d/i18n.sh << "EOF"
<literal># Set up i18n variables
export LC_ALL=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>
@@ -391,13 +391,13 @@
export [EMAIL PROTECTED]</literal>
EOF</userinput></screen>
- <para>The <envar>LC_ALL</envar> variable sets the same value for all
locale
- categories. For better control, you may prefer to set values
individually for
- all categories listed in the output of the <command>locale</command>
+ <para>The <envar>LC_ALL</envar> variable sets the same value for all
locale
+ categories. For better control, you may prefer to set values
individually for
+ all categories listed in the output of the <command>locale</command>
command.</para>
<para>The <envar>G_FILENAME_ENCODING</envar> variable tells applications
- such as <application>Glib</application> and
<application>GTK+</application>
+ such as <application>Glib</application> and
<application>GTK+</application>
that filenames are in the default locale encoding and not in UTF-8 as
assumed by default.</para>
@@ -406,8 +406,8 @@
<sect3>
<title>Other Initialization Values</title>
- <para>Other initialization can easily be added to the
- <filename>profile</filename> by adding additional scripts to the
+ <para>Other initialization can easily be added to the
+ <filename>profile</filename> by adding additional scripts to the
<filename class='directory'>/etc/profile.d</filename> directory.</para>
</sect3>
@@ -425,8 +425,8 @@
file should explain everything you need.</para>
<screen role="root"><userinput>cat > /etc/bashrc << "EOF"
-<literal># Begin /etc/bashrc
-# Written for Beyond Linux From Scratch
+<literal># Begin /etc/bashrc
+# Written for Beyond Linux From Scratch
# by James Robertson <[EMAIL PROTECTED]>
# updated by Bruce Dubbs <[EMAIL PROTECTED]>
@@ -454,7 +454,7 @@
# Provides prompt for non-login shells, specifically shells started
# in the X environment. [Review the LFS archive thread titled
-# PS1 Environment Variable for a great case study behind this script
+# PS1 Environment Variable for a great case study behind this script
# addendum.]
#export PS1="[EMAIL PROTECTED] \w]\\$ "
@@ -477,7 +477,7 @@
the command to <filename>/etc/skel/.bash_profile</filename> and check the
permissions after the command is run. You can then copy
<filename>/etc/skel/.bash_profile</filename> to the home directories of
already
- existing users, including <systemitem class="username">root</systemitem>,
+ existing users, including <systemitem class="username">root</systemitem>,
and set the owner and group appropriately.</para>
<screen><userinput>cat > ~/.bash_profile << "EOF"
@@ -499,9 +499,9 @@
for DIR in $PATH; do
if [ "$DIR" != "$1" ]; then
NEWPATH=${NEWPATH:+$NEWPATH:}$DIR
- fi
+ fi
done
-
+
# Then append the directory
export PATH=$NEWPATH:$1
}
@@ -511,7 +511,7 @@
fi
if [ -d "$HOME/bin" ] ; then
- append $HOME/bin
+ append $HOME/bin
fi
unset append
@@ -520,7 +520,7 @@
EOF</userinput></screen>
</sect2>
-
+
<sect2 id="bashrc-profile">
<title>~/.bashrc</title>
@@ -543,7 +543,7 @@
# Personal environment variables and startup programs should go in
# ~/.bash_profile. System wide environment variables and startup
# programs are in /etc/profile. System wide aliases and functions are
-# in /etc/bashrc.
+# in /etc/bashrc.
if [ -f "/etc/bashrc" ] ; then
source /etc/bashrc
@@ -553,8 +553,8 @@
EOF</userinput></screen>
</sect2>
-
-
+
+
<sect2 id="bash_logout-profile">
<title>~/.bash_logout</title>
@@ -578,8 +578,8 @@
EOF</userinput></screen>
</sect2>
-
-
+
+
<sect2 id="etc-dircolors-profile">
<title>/etc/dircolors</title>
@@ -594,15 +594,15 @@
<para> If you want to use the <filename>dircolors</filename> capability,
then
run the following command. The <filename
class="directory">/etc/skel</filename>
setup steps seen above also can be used here to provide a
- <filename>~/.dircolors</filename> file when a new user is set up. As
before,
+ <filename>~/.dircolors</filename> file when a new user is set up. As
before,
just change the output file name on the following command and assure the
- permissions, owner, and group are correct on the files created and/or
+ permissions, owner, and group are correct on the files created and/or
copied.</para>
<screen role="root"><userinput>dircolors -p >
/etc/dircolors</userinput></screen>
<para>If you wish to customize the colors used for different file types,
you can
- edit the <filename>/etc/dircolors</filename> file. The instructions for
setting
+ edit the <filename>/etc/dircolors</filename> file. The instructions for
setting
the colors are embedded in the file.</para>
Modified: trunk/BOOK/xsoft/graphweb/dillo.xml
===================================================================
--- trunk/BOOK/xsoft/graphweb/dillo.xml 2005-05-22 10:19:50 UTC (rev 4447)
+++ trunk/BOOK/xsoft/graphweb/dillo.xml 2005-05-22 10:28:05 UTC (rev 4448)
@@ -20,7 +20,7 @@
<date>$Date$</date>
</sect1info>
- <title><application>Dillo</application>-&dillo-version;</title>
+ <title>Dillo-&dillo-version;</title>
<indexterm zone="dillo">
<primary sortas="a-Dillo">Dillo</primary>
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
