docs/124137: [patch] Fix Dashes in FAQ

[Gabor PALI]

>Number:         124137
>Category:       docs
>Synopsis:       [patch] Fix Dashes in FAQ
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 30 16:20:04 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gabor PALI
>Release:        FreeBSD 6.3-STABLE i386
>Organization:
>Environment:
System: FreeBSD disznohal 6.3-STABLE FreeBSD 6.3-STABLE #4: Fri Apr 4 23:29:43 CEST 2008 dezzy at disznohal:/usr/obj/usr/src/sys/GENERIC_ i386

>Description:
	I found a lot of dashes without a correct markup in the FreeBSD FAQ.
	It would be the best to use the — entity for rendering dashes.
	I created a patch to correct this.

>How-To-Repeat:

>Fix:

--- books.faq.patch.20.diff begins here ---
Index: book.sgml
===================================================================
RCS file: /doc/en_US.ISO8859-1/books/faq/book.sgml,v
retrieving revision 1.827
diff -u -r1.827 book.sgml
--- book.sgml	27 May 2008 23:51:07 -0000	1.827
+++ book.sgml	29 May 2008 03:17:09 -0000
@@ -3034,7 +3034,7 @@
             compile <filename>ls.c</filename> into
             <filename>ls.o</filename>. If you then run <quote>make
             buildworld</quote> again, and the compile fails in the same
-            place then this is a broken build -- try updating your sources
+            place then this is a broken build — try updating your sources
             and try again. If the compile fails elsewhere then this is
             almost certainly hardware.</para>
 
@@ -3713,7 +3713,7 @@
             the &man.hosts.5; and &man.named.8; manual pages for more
             information.  If this is on the global Internet, the problem
             may be that your server's resolver is not functioning
-            correctly.  To check, try to look up another host--say,
+            correctly.  To check, try to look up another host — say,
             <hostid>www.yahoo.com</hostid>.  If it does not work, that is
             your problem.</para>
 
@@ -9748,7 +9748,7 @@
             using port address <literal>0x3f8</literal>, and has a
             16550A-type UART chip.  The second uses the same kind of chip
             but is on irq 3 and is at port address <literal>0x2f8</literal>.
-            Internal modem cards are treated just like serial ports---except
+            Internal modem cards are treated just like serial ports — except
             that they always have a modem <quote>attached</quote> to the
             port.</para>
 
@@ -9956,7 +9956,7 @@
             The terminal type for this port is
             <literal>dialup</literal>.  The port is
             <literal>on</literal> and is
-            <literal>insecure</literal>---meaning
+            <literal>insecure</literal> — meaning
             <username>root</username> logins on the port are not
             allowed. For dialin ports like this one, use the
             <devicename>ttyd<replaceable>X</replaceable></devicename>
@@ -10049,7 +10049,7 @@
 
       <qandaentry>
         <question id="hayes-unsupported">
-          <para>My stock Hayes modem is not supported---what
+          <para>My stock Hayes modem is not supported — what
             can I do?</para>
         </question>
 
@@ -10061,7 +10061,7 @@
             file.</para>
 
           <para>The Hayes driver is not smart enough to recognize some of
-            the advanced features of newer modems---messages like
+            the advanced features of newer modems — messages like
             <literal>BUSY</literal>, <literal>NO DIALTONE</literal>, or
             <literal>CONNECT 115200</literal> will just confuse it. You
             should turn those messages off when you use &man.tip.1;
--- books.faq.patch.20.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted: