source: prologue/typography.xml@ 7187e06

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 7187e06 was 7187e06, checked in by Bruce Dubbs <bdubbs@…>, 16 years ago

Typo

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@8580 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 4.0 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="pre-typography">
9 <?dbhtml filename="typography.html"?>
10
11 <title>Typography</title>
12
13 <para>To make things easier to follow, there are a few typographical
14 conventions used throughout this book. This section contains some
15 examples of the typographical format found throughout Linux From
16 Scratch.</para>
17
18<screen role="nodump"><userinput>./configure --prefix=/usr</userinput></screen>
19
20 <para>This form of text is designed to be typed exactly as seen unless
21 otherwise noted in the surrounding text. It is also used in the explanation
22 sections to identify which of the commands is being referenced.</para>
23
24 <para>In some cases, a logical line is extended to two or more physical lines
25 with a backslash at the end of the line.</para>
26
27<screen role="nodump"><userinput>CC="gcc -B/usr/bin/" ../binutils-2.18/configure \
28 --prefix=/tools --disable-nls --disable-werror</userinput></screen>
29
30 <para>Note that the backslash must be followed by an immediate return. Other
31 whitespace characters like spaces or tab characters will create incorrect
32 results.</para>
33
34<screen><computeroutput>install-info: unknown option '--dir-file=/mnt/lfs/usr/info/dir'</computeroutput></screen>
35
36 <para>This form of text (fixed-width text) shows screen output, probably as
37 the result of commands issued. This format is also used to show filenames,
38 such as <filename>/etc/ld.so.conf</filename>.</para>
39
40 <para><emphasis>Emphasis</emphasis></para>
41
42 <para>This form of text is used for several purposes in the book. Its main
43 purpose is to emphasize important points or items.</para>
44
45 <para><ulink url="&lfs-root;"/></para>
46
47 <para>This format is used for hyperlinks both within the LFS community and to
48 external pages. It includes HOWTOs, download locations, and websites.</para>
49
50<screen role="nodump"><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF"
51<literal>root:x:0:
52bin:x:1:
53......</literal>
54EOF</userinput></screen>
55
56 <para>This format is used when creating configuration files. The first command
57 tells the system to create the file <filename>$LFS/etc/group</filename> from
58 whatever is typed on the following lines until the sequence end of file (EOF)
59 is encountered. Therefore, this entire section is generally typed as
60 seen.</para>
61
62 <para><replaceable>&lt;REPLACED TEXT&gt;</replaceable></para>
63
64 <para>This format is used to encapsulate text that is not to be typed
65 as seen or for copy-and-paste operations.</para>
66
67 <para><replaceable>[OPTIONAL TEXT]</replaceable></para>
68
69 <para>This format is used to encapsulate text that is optional.</para>
70
71 <para><filename>passwd(5)</filename></para>
72
73 <para>This format is used to refer to a specific manual page (hereinafter
74 referred to simply as a <quote>man</quote> page). The number inside parentheses
75 indicates a specific section inside of <command>man</command>. For example,
76 <command>passwd</command> has two man pages. Per LFS installation instructions,
77 those two man pages will be located at
78 <filename>/usr/share/man/man1/passwd.1</filename> and
79 <filename>/usr/share/man/man5/passwd.5</filename>. Both man pages have different
80 information in them. When the book uses <filename>passwd(5)</filename> it is
81 specifically referring to <filename>/usr/share/man/man5/passwd.5</filename>.
82 <command>man passwd</command> will print the first man page it finds that
83 matches <quote>passwd</quote>, which will be
84 <filename>/usr/share/man/man1/passwd.1</filename>. For this example, you will
85 need to run <command>man 5 passwd</command> in order to read the specific page
86 being referred to. It should be noted that most man pages do not have duplicate
87 page names in different sections. Therefore, <command>man <replaceable>&lt;program
88 name&gt;</replaceable></command> is generally sufficient.</para>
89
90</sect1>
91
Note: See TracBrowser for help on using the repository browser.