typography.xml 3.3 KB

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