typography.xml 3.4 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
  4. <!ENTITY % general-entities SYSTEM "../general.ent">
  5. %general-entities;
  6. ]>
  7. <sect1 id="pre-typography">
  8. <?dbhtml filename="typography.html"?>
  9. <title>Typography</title>
  10. <para>To make things easier to follow, there are a few typographical
  11. conventions used throughout this book. This section contains some
  12. examples of the typographical format found throughout Linux From
  13. Scratch.</para>
  14. <screen role="nodump"><userinput>./configure --prefix=/usr</userinput></screen>
  15. <para>This form of text is designed to be typed exactly as seen unless
  16. otherwise noted in the surrounding text. It is also used in the explanation
  17. sections to identify which of the commands is being referenced.</para>
  18. <screen><computeroutput>install-info: unknown option '--dir-file=/mnt/lfs/usr/info/dir'</computeroutput></screen>
  19. <para>This form of text (fixed-width text) shows screen output, probably as
  20. the result of commands issued. This format is also used to show filenames,
  21. such as <filename>/etc/ld.so.conf</filename>.</para>
  22. <para><emphasis>Emphasis</emphasis></para>
  23. <para>This form of text is used for several purposes in the book. Its main
  24. purpose is to emphasize important points or items.</para>
  25. <para><ulink url="&lfs-root;"/></para>
  26. <para>This format is used for hyperlinks both within the LFS community and to
  27. external pages. It includes HOWTOs, download locations, and websites.</para>
  28. <screen role="nodump"><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF"
  29. <literal>root:x:0:
  30. bin:x:1:
  31. ......</literal>
  32. EOF</userinput></screen>
  33. <para>This format is used when creating configuration files. The first command
  34. tells the system to create the file <filename>$LFS/etc/group</filename> from
  35. whatever is typed on the following lines until the sequence end of file (EOF)
  36. is encountered. Therefore, this entire section is generally typed as
  37. seen.</para>
  38. <para><replaceable>[REPLACED TEXT]</replaceable></para>
  39. <para>This format is used to encapsulate text that is not to be typed
  40. as seen or copied-and-pasted.</para>
  41. <para><filename>passwd(5)</filename></para>
  42. <para>This format is used to refer to a specific manual page (hereinafter
  43. referred to simply as a <quote>man</quote> page). The number inside parentheses
  44. indicates a specific section inside of <command>man</command>. For example,
  45. <command>passwd</command> has two man pages. Per LFS installation instructions,
  46. those two man pages will be located at
  47. <filename>/usr/share/man/man1/passwd.1</filename> and
  48. <filename>/usr/share/man/man5/passwd.5</filename>. Both man pages have different
  49. information in them. When the book uses <filename>passwd(5)</filename> it is
  50. specifically referring to <filename>/usr/share/man/man5/passwd.5</filename>.
  51. <command>man passwd</command> will print the first man page it finds that
  52. matches <quote>passwd</quote>, which will be
  53. <filename>/usr/share/man/man1/passwd.1</filename>. For this example, you will
  54. need to run <command>man 5 passwd</command> in order to read the specific page
  55. being referred to. It should be noted that most man pages do not have duplicate
  56. page names in different sections. Therefore, <command>man <replaceable>[program
  57. name]</replaceable></command> is generally sufficient.</para>
  58. </sect1>