Add ability to generate ASCII documentation from the TeX files.

These changes add the ability to run 'make asterisk.txt' just like the existing
'make asterisk.pdf' commands to generate a text document from the TeX files we
have in the doc/tex/ directory. I've also updated a few of the .tex files because
they weren't properly escaping certain characters so they would show up as Unicode
characters (like [U+021C]). Made changes to the configure scripts so it would
detect the catdvi program which is required to convert the .dvi file generated
by latex.

I've also added a few lines to the build_tools/prep_tarball script so that the
text documentation gets generated and added to future tarballs of Asterisk
releases.

(closes issue #17220)
Reported by: lmadsen
Patches: 
      asterisk.txt.patch uploaded by lmadsen (license 10)
      asterisk.txt.patch-v4 uploaded by pabelanger (license 224)
Tested by: lmadsen, pabelanger

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@258351 65c4cc65-6c06-0410-ace0-fbb531ad65f3

1 files changed, 1 insertions, 1 deletions

diff --git a/doc/tex/security-events.tex b/doc/tex/security-events.tex
index d46b1505d..ecb59809e 100644
--- a/doc/tex/security-events.tex
+++ b/doc/tex/security-events.tex
@@ -147,7 +147,7 @@ logger levels within Asterisk.
     [Feb 11 07:57:03] SECURITY[23736] res_security_log.c: <...>
 \end{verbatim}
 
-    The part of the log entry identified by <...> is where the security event
+    The part of the log entry identified by $<$...$>$ is where the security event
 content resides.  The security event content is a comma separated list
 of key value pairs.  The key is the information element type, and the value is a
 quoted string that contains the associated meta data for that information