diff --git a/flarq_doxygen/distclean.sh b/flarq_doxygen/distclean.sh
new file mode 100755
index 00000000..710f4243
--- /dev/null
+++ b/flarq_doxygen/distclean.sh
@@ -0,0 +1,8 @@
+#!/bin/bash
+
+# Distribution clean of documents
+
+rm -rf pdf/
+rm -rf compressed_html/
+rm -rf user_docs/
+
diff --git a/flarq_doxygen/images/ARQout.png b/flarq_doxygen/images/ARQout.png
new file mode 100644
index 00000000..a4e7f986
Binary files /dev/null and b/flarq_doxygen/images/ARQout.png differ
diff --git a/flarq_doxygen/images/OLxpress.png b/flarq_doxygen/images/OLxpress.png
new file mode 100644
index 00000000..e6171f85
Binary files /dev/null and b/flarq_doxygen/images/OLxpress.png differ
diff --git a/flarq_doxygen/images/SelectFromARQout.png b/flarq_doxygen/images/SelectFromARQout.png
new file mode 100644
index 00000000..0566bce7
Binary files /dev/null and b/flarq_doxygen/images/SelectFromARQout.png differ
diff --git a/flarq_doxygen/images/SendMenu.png b/flarq_doxygen/images/SendMenu.png
new file mode 100644
index 00000000..dace2671
Binary files /dev/null and b/flarq_doxygen/images/SendMenu.png differ
diff --git a/flarq_doxygen/images/beacon.png b/flarq_doxygen/images/beacon.png
new file mode 100644
index 00000000..09e3b79d
Binary files /dev/null and b/flarq_doxygen/images/beacon.png differ
diff --git a/flarq_doxygen/images/composer.png b/flarq_doxygen/images/composer.png
new file mode 100644
index 00000000..0273b595
Binary files /dev/null and b/flarq_doxygen/images/composer.png differ
diff --git a/flarq_doxygen/images/configdialog.png b/flarq_doxygen/images/configdialog.png
new file mode 100644
index 00000000..c88ba58e
Binary files /dev/null and b/flarq_doxygen/images/configdialog.png differ
diff --git a/flarq_doxygen/images/flarqlogo.png b/flarq_doxygen/images/flarqlogo.png
new file mode 100644
index 00000000..479f103c
Binary files /dev/null and b/flarq_doxygen/images/flarqlogo.png differ
diff --git a/flarq_doxygen/images/maindialog.png b/flarq_doxygen/images/maindialog.png
new file mode 100644
index 00000000..b82940f0
Binary files /dev/null and b/flarq_doxygen/images/maindialog.png differ
diff --git a/flarq_doxygen/images/sylpheed-arqout.png b/flarq_doxygen/images/sylpheed-arqout.png
new file mode 100644
index 00000000..3a4f0606
Binary files /dev/null and b/flarq_doxygen/images/sylpheed-arqout.png differ
diff --git a/flarq_doxygen/images/wxstatus_tpl.png b/flarq_doxygen/images/wxstatus_tpl.png
new file mode 100644
index 00000000..1505a063
Binary files /dev/null and b/flarq_doxygen/images/wxstatus_tpl.png differ
diff --git a/flarq_doxygen/make_docs.sh b/flarq_doxygen/make_docs.sh
new file mode 100755
index 00000000..a43389dc
--- /dev/null
+++ b/flarq_doxygen/make_docs.sh
@@ -0,0 +1,276 @@
+#!/bin/bash
+#
+# A simple script for creating/archiving doxygen documentation for FLArq
+
+PRG_NAME="FLArq"
+
+LATEX="0"
+DOXY="0"
+BUILD_PROG_DOCS="0"
+
+if [ -z $1 ]; then
+	BUILD_USER_DOCS="1"
+else
+	BUILD_USER_DOCS="0"
+fi
+
+macintosh_file_clean()
+{
+	BASE_PATH=$1
+	if [ -z $BASE_PATH ]; then
+		BASE_PATH="${PWD}"
+	fi
+
+	find $BASE_PATH -name ".DS_Store" -exec rm -rf {} \;
+}
+
+doc_version()
+{
+	if [ ! -f $1 ]; then
+		echo "Doxyfile not found ($1)"
+		echo "PWD=$PWD"
+		VER_NUM="UNKNOWN_VERSION"
+		return
+	fi
+
+	VER_STR=`grep -e "PROJECT_NUMBER*=*" $1`
+
+	if [ -z $VER_STR ]; then
+		VER_NUM="UNKNOWN_VERSION"
+		return
+	fi
+
+	VER_NUM="${VER_STR#*=}"
+	VER_NUM="${VER_NUM#"${VER_NUM%%[![:space:]]*}"}"
+	VER_NUM="${VER_NUM%"${VER_NUM##*[![:space:]]}"}"
+}
+
+help()
+{
+	echo ""
+	echo "Use:"
+	echo "   make_docs.sh <user or help>"
+	echo ""
+	echo "default: user"
+	echo "user: Generate user documentation"
+	echo "help: This message"
+	echo ""
+}
+
+macintosh_file_clean()
+{
+	BASE_PATH=$1
+	if [ -z $BASE_PATH ]; then
+		BASE_PATH="${PWD}"
+	fi
+
+	find $BASE_PATH -name .DS_Store -exec rm -rf {} \;
+}
+
+rename_file()
+{
+	if [ -f "$1" ]; then
+		mv "$1" "$2"
+	fi
+}
+
+make_dir()
+{
+	echo "Make Dir: $1"
+
+	if [ -d "$1" ]; then
+		return
+	fi
+
+	mkdir "$1"
+}
+
+function check_dir()
+{
+	if [ -d "$1" ]; then
+		echo "1"
+		return
+	fi
+
+	echo "0"
+}
+
+function check_file()
+{
+	if [ -f "$1" ]; then
+		echo "1"
+		return
+	fi
+
+	echo "0"
+}
+
+check_doxy()
+{
+	RESULTS=$(check_file "$PWD/Doxyfile")
+
+	if [ "$RESULTS" = "1" ]; then
+		doxygen
+	else
+		echo "Doxyfile not found in directory $PWD"
+	fi
+}
+
+check_doxy_exec()
+{
+	PROG_NAME=`which doxygen`
+	EXEC_FILE=`basename $PROG_NAME`
+
+	if [ "$EXEC_FILE" != "doxygen" ]; then
+		echo "Install doxygen to build documentation"
+		DOXY="0"
+	else
+		echo "Found $PROG_NAME"
+		DOXY="1"
+	fi
+}
+
+check_latex_exec()
+{
+	PROG_NAME=`which latex`
+	EXEC_FILE=`basename $PROG_NAME`
+
+	if [ "$EXEC_FILE" != "latex" ]; then
+		echo "Install TeX/LaTeX to build pdf documentation"
+		LATEX="0"
+	else
+		echo "Found $PROG_NAME"
+		LATEX="1"
+	fi
+}
+
+pdf_docs()
+{
+	if [ "$LATEX" = "1" ]; then
+
+		OP_DIR="$1"
+
+		RESULTS=$(check_dir "$OP_DIR")
+
+		if [ "$RESULTS" = "1" ]; then
+			cd $OP_DIR
+			make
+			rename_file "refman.pdf" "$2"
+		fi
+	fi
+}
+
+compress_html()
+{
+	if [ -z $1 ]; then
+		return
+	fi
+
+	if [ -z $2 ]; then
+		return
+	fi
+
+	TAR=`which tar`
+	if [ -z $TAR ]; then
+	    echo "***************************************"
+		echo "* Compression program 'tar' not found *"
+	    echo "***************************************"
+		return
+	fi
+
+	SAVE_NAME="compressed_html/$1_html.tar.bz2"
+
+	cd ".."
+    echo "CWD=${PWD}"
+	COMP_DIR="$2/html/"
+
+	RESULTS=$(check_dir "$COMP_DIR")
+
+	if [ "$RESULTS" = "1" ]; then
+		$TAR -cvjf "$SAVE_NAME" "$COMP_DIR"
+	fi
+}
+
+for var in "$@"
+do
+	case "$var" in
+		prog)
+			BUILD_PROG_DOCS="1"
+			;;
+		PROG)
+			BUILD_PROG_DOCS="1"
+			;;
+		USER)
+			BUILD_USER_DOCS="1"
+			;;
+		user)
+			BUILD_USER_DOCS="1"
+			;;
+		*)
+			help
+			exit
+			;;
+	esac
+done
+
+check_doxy_exec
+
+if [ "$DOXY" != "1" ]; then
+	echo "**************************************"
+	echo "* Install Doxygen to build documents *"
+	echo "**************************************"
+	exit
+fi
+
+check_latex_exec
+
+if [ "$LATEX" != "1" ]; then
+	echo "********************************************"
+	echo "* Install TeX/LaTeX to build PDF documents *"
+	echo "********************************************"
+fi
+
+
+SCRIPT_PATH="$PWD/make_docs.sh"
+
+echo "Looking for Script: $SCRIPT_PATH"
+
+if [ -f "$SCRIPT_PATH" ]; then
+	make_dir "pdf"
+	make_dir "compressed_html"
+	make_dir "programmer_docs"
+	make_dir "user_docs"
+
+#   Additional files for html link references
+	make_dir "user_docs/html"
+	make_dir "user_docs/html/aux"
+	cp ./user_src_doc/aux/*.* ./user_docs/html/aux
+
+else
+	echo "***********************************************************************"
+	echo "* Change Directory to the ./make_doc.sh location then execute script. *"
+	echo "***********************************************************************"
+	exit
+fi
+
+# User Manual
+if [ $BUILD_USER_DOCS -eq "1" ]; then
+(
+	cd user_src_doc
+	doc_version "${PWD}/Doxyfile"
+	check_doxy
+	( compress_html "${PRG_NAME}_${VER_NUM}_Users_Manual" "user_docs")
+	pdf_docs "../user_docs/latex" "../../pdf/${PRG_NAME}_${VER_NUM}_Users_Manual.pdf"
+)
+fi
+
+# Programmers Code Reference built from FLDIGI make_docs.sh script
+#if [ $BUILD_PROG_DOCS -eq "1" ]; then
+#(
+#	cd prog_src_doc
+#	doc_version "${PWD}/Doxyfile"
+#	check_doxy
+#	( compress_html "${PRG_NAME}_${VER_NUM}_Code_Reference" "programmer_docs" )
+#	pdf_docs "../../doc/programmer_docs/latex" "../../pdf/${PRG_NAME}_${VER_NUM}_Code_Reference.pdf"
+#)
+#fi
diff --git a/flarq_doxygen/user_src_doc/Doxyfile b/flarq_doxygen/user_src_doc/Doxyfile
new file mode 100644
index 00000000..0ed47121
--- /dev/null
+++ b/flarq_doxygen/user_src_doc/Doxyfile
@@ -0,0 +1,51 @@
+#
+#
+#
+# Copyright (C) 2014 Robert Stiles, KK5VD.
+#
+# Permission to use, copy, modify, and distribute this software and its
+# documentation under the terms of the GNU General Public License is hereby
+# granted. No representations are made about the suitability of this software
+# for any purpose. It is provided "as is" without express or implied warranty.
+# See the GNU General Public License for more details.
+#
+# Documents produced by Doxygen are derivative works derived from the
+# input used in their production; they are not affected by this license.
+
+PROJECT_NAME         = "FLARQ Users Manual"
+PROJECT_NUMBER       = 4.3
+PROJECT_BRIEF        =
+ALLEXTERNALS         = NO
+CASE_SENSE_NAMES     = NO
+DISABLE_INDEX        = NO
+DOXYFILE_ENCODING    = UTF-8
+ENABLE_PREPROCESSING = NO
+ENABLED_SECTIONS     = logo_on
+EXTRACT_ALL          = NO
+EXTRA_PACKAGES       = graphicx caption subcaption float
+EXTRACT_PRIVATE      = NO
+FILE_PATTERNS        = *.cpp *.h *.doc *.txt
+GENERATE_HTML        = YES
+GENERATE_HTMLHELP    = NO
+GENERATE_LATEX       = YES
+GENERATE_MAN         = NO
+GENERATE_RTF         = NO
+GENERATE_TREEVIEW    = NO
+GENERATE_XML         = NO
+HTML_COLORSTYLE_SAT  = 0
+HTML_FOOTER          =
+HTML_HEADER          =
+IMAGE_PATH           = ../images
+INPUT                = index.txt
+OUTPUT_DIRECTORY     = ../user_docs
+OUTPUT_LANGUAGE      = English
+PDF_HYPERLINKS       = YES
+PERL_PATH            = /usr/bin/perl
+PROJECT_LOGO         = ../images/flarqlogo.png
+QUIET                = NO
+RECURSIVE            = NO
+SEARCHENGINE         = NO
+STRIP_CODE_COMMENTS  = NO
+TAGFILES             =
+USE_PDFLATEX         = YES
+WARNINGS             = YES
diff --git a/flarq_doxygen/user_src_doc/aux/ARQ2.pdf b/flarq_doxygen/user_src_doc/aux/ARQ2.pdf
new file mode 100644
index 00000000..5267f7a7
Binary files /dev/null and b/flarq_doxygen/user_src_doc/aux/ARQ2.pdf differ
diff --git a/flarq_doxygen/user_src_doc/index.txt b/flarq_doxygen/user_src_doc/index.txt
new file mode 100644
index 00000000..699dee1e
--- /dev/null
+++ b/flarq_doxygen/user_src_doc/index.txt
@@ -0,0 +1,445 @@
+/******************************************************************************
+ * Copyright (C) 2014 Robert Stiles, KK5VD.
+ *
+ * Permission to use, copy, modify, and distribute this software and its
+ * documentation under the terms of the GNU General Public License is hereby
+ * granted. No representations are made about the suitability of this software
+ * for any purpose. It is provided "as is" without express or implied warranty.
+ * See the GNU General Public License for more details.
+ *
+ * Documents produced by Doxygen are derivative works derived from the
+ * input used in their production; they are not affected by this license.
+ *
+ * Requires Doxygen for HTML output
+ * plus LiveTeX (LaTeX) for PDF output
+ *
+ */
+
+
+/*!
+
+\mainpage FLARQ Users Manual - Version 4.3
+
+\tableofcontents
+
+<center>
+\image latex flarqlogo.png "" width=0.5in
+\image html flarqlogo.png ""
+</center>
+
+<!--FLARQ User Manual-->
+\section sFlarqDesc Transceiver Control
+
+
+<b>F</b>ast <b>L</b>ight <b>A</b>utomatic <b>R</b>epeat re<b>Q</b>uest is a
+file transfer application that is based on the
+<a href="aux/ARQ2.pdf">ARQ specification</a> developed by Paul Schmidt,
+K9PS.  It is capable of transmitting and receiving frames of ARQ data
+via either FLDIGI or MultiPsk on Windows, or FLDIGI on Linux/Macintosh OSX.
+The interaction between FLARQ and FLDIGI requires no operator intervention.
+Program data exchange between FLARQ and FLDIGI is accomplished using a
+localhost socket interface.  The socket interface requires that one program
+act as the server and the other the client.  FLARQ is a client program and
+FLDIGI is a server program.
+
+FLARQ will not execute unless either FLDIGI (preferred) or MultiPsk is
+already running on the host computer.  If MultiPsk is used it must be set
+to the "socket" mode before executing FLARQ.  If you attempt to run FLARQ
+without FLDIGI already running you will view an information window asking
+you to first start FLDIGI.
+
+The ARQ transfer must take place between two systems both of which are
+running the FLARQ / FLDIGI.  The ARQ specification and the source code
+for FLARQ are GPL licensed.  Other developers wishing to duplicate or
+expand upon the FLARQ ARQ implementation may freely do so.
+
+FLARQ can be used with the following digital modem as the transport layer:
+
+BPSK all baud rates<br>
+QPSK all baud rates<br>
+MFSK all baud rates<br>
+DOMINOEX 11 or faster (do not use FEC)<br>
+THOR all baud rates, 11 or faster recommended<br>
+MT63 - all baud rates, FLARQ timing should be increased to accommodate mt63
+latency<br>
+
+Please note that Olivia IS NOT compatible with FLARQ transmissions.  Olivia
+does not allow the transmission of the control codes required for FLARQ.
+
+The main screen dialog for FLARQ is:
+
+<center>
+\image latex maindialog.png "Main Dialog" width=5.5in
+\image html maindialog.png "Main Dialog"
+</center>
+<br>
+
+ARQ data is sent in data frames which clearly delineate from whom the data
+is being sent, it's purpose or type, the actual data, and a checksum value.
+The "Beacon" button will cause the transmission of the ARQ equivalent of a
+"CQ" frame which can be easily recognized by a receiving station. Upon
+receipt of the beacon frame a monitoring FLARQ will automatically insert
+the sending stations callsign into the edit box to the right of the
+"Connect" button.  The receiving station can then press the "Connect"
+button and the connect process begins.
+
+<center>
+
+|Diamond Color | Indicator                |
+|:------------:|:-------------------------|
+| WHITE        | Not Connected            |
+| YELLOW	   | Connecting               |
+| GREEN	       | Connected - Receiving    |
+| RED	       | Connected - Transmitting |
+| BLACK	       | Timed Out                |
+
+</center>
+
+The state of the connection also appears in plain text to the right of the
+diamond indicator.
+
+Pressing the "Beacon" button sends both the text and T/R commands to the
+modem program.  The beacon will repeat with a wait time between transmissions
+set by the Beacon interval in seconds on the Configure dialog.  During the
+silent period between beacon transmissions the Beacon button will show the
+count down timer.  You can stop the beacon at any time it is in the count
+down mode by simply pressing that button or by pressing the Abort button.
+The default beacon interval is 60 seconds.  The minimum is 15 seconds and
+the maximum 300 seconds.  If you find that stations are  having difficulty
+connecting to your beacon call then you probably need to increase the time
+between beacons to avoid ARQ collisions similar to doubling on voice.  When
+FLARQ is in the Beacon mode the words BEACON ON, and the green light on the
+Beacon button will be lit.
+
+The status bar at the bottom of the main dialog contains a status text
+message area to the left and a progress bar to the right.  During a file
+transfer you will be notified of actions and also see the transfer percent
+completion in the progress bar.
+
+\section sConfigure Configuring FLARQ
+
+
+Before using FLARQ (and upon its initial execution) you will have to enter
+some configuration parameters:
+
+<center>
+\image latex configdialog.png "Configure Dialog" width=5.5in
+\image html configdialog.png "Configure Dialog"
+</center>
+<br>
+
+The highlighted field, "My Call" is the only one that you must fill in to
+start using the application.  The folder locations for Text/Binary Files
+and also for the Mail Client files should all be OK as preconfigured for
+the operating system in use.
+
+Read through the ARQ specification for additional detail.  The Exponent is
+a 2^N factor which delineates the size of the text data block that is
+transmitted in a data frame.  2^5 is 32 and should be satisfactory for
+most s/n conditions.  If you are experiencing many repeats you can lower
+the Exponent value.  If the path between rx and tx stations is very good
+you could increase its value.  FLARQ allows the following range of values:
+
+<center>
+
+|Exponent | Block size |
+|:-------:|:----------:|
+| 4       | 16         |
+| 5	      | 32         |
+| 6	      | 64         |
+| 7	      | 128        |
+| 8	      | 256        |
+
+</center>
+
+Retries specifies how many times a repeat request should be made before
+the link is declared DOWN.
+
+Wait time is the time between retries.
+
+Timeout is the time period during which NO RECEPTION of frames has occured
+before the link is declared DOWN.
+
+The Tx delay is the time between the end of the Rx and the beginning of the
+Tx cycle for an ARQ exchange.  One-half second should be more than
+sufficient for most transceivers.  You might be able to lower the value
+for your rig.  Older rigs may need the value increased.
+
+Beacon text - will be transmitted with each beacon transmission.
+
+Sylpheed Mail Client - Sylpheed stores the message files using numeric file
+names without extension.  Check this box to insure that FLARQ stores the
+files in sequential numeric order without creating duplicates.  This is
+primarily for Linux users.  Windows users should leave this box unchecked
+unless they are using the Sylpheed Mail Client.
+
+\section sConnecting Connecting
+
+The normal connection process is that the station with traffic will request
+the connecting station to send a beacon. This tests the ability of the
+connecting station to forward. The station with traffic will then be the
+one to press the Connect button.  The receiving station will see the
+beacon message displayed in the FLARQ text area and also see the beacon
+stations callsign appear in the callsign box.  The connecting station
+presses the connect button and after a few automatic exchanges the diamond
+indicator to the right of the callsign turns green indicating that they
+are successfully connected.  A connect may take a few retries if the
+transmission path s/n is marginal.  During the connect process the diamond
+indicator will be yellow.
+
+After the two stations are CONNECTED either operator may effect a file
+transfer.  Who goes first may be negotiated using FLDIGI in a plain text
+mode or using the FLARQ "Plain Talk" facility, once connected.  The FLDIGI
+T/R functions can be used in parallel with any ARQ transmissions.  It might
+be best to conclude those negotiations before establishing the ARQ
+connection.
+
+Either station may initiate a DISCONNECT process.
+
+This is what the outgoing beacon will look like on FLDIGI:
+
+
+<center>
+\image latex beacon.png "Beacon Message" width=2.7in
+\image html beacon.png "Beacon Message"
+</center>
+<br>
+
+The \<soh\> and \<eot\> are control codes that surround every ARQ frame.
+FLDIGI recognizes that it is connected to FLARQ and shows the control codes as
+ASCII named equivalents since they are not normally printable.
+
+The text will appear very similar on the receiving end of the exchange.
+
+\section sTransfering Transferring files
+
+You may transfer several different file types:
+
+<center>
+\image latex SendMenu.png "Send - File Transfer" width=2.7in
+\image html SendMenu.png "Send - File Transfer"
+</center>
+<br>
+
+<ul>
+  <li>Email - created using FLARQ's composer, Outlook Express,
+      Outlook, Thunderbird, Sylpheed or any other email client,
+      or received via the internet and handled by the email client.</li>
+  <li>Text - any ASCII file which does not contain non-printable text</li>
+  <li>Image - any image file, jpeg, png, bmp, etc.</li>
+  <li>Binary - any file containing arbtrary data where each byte is
+      anything from 00 hex to FF hex.</li>
+</ul>
+
+
+\subsection ssTransferingTIB Transfering Text, Images or Binary Files
+
+If you select Text, Image or Binary file for transfer a regular file picker
+dialog is opened.  You can navigate anywhere in the file system to pick a
+file.  The default location for the files are unique in Windows and
+Linux/MacOSX. In Linux the default location is in $HOME/ARQsend and in
+Windows it is c:\\NBEMS\\ARQsend.   Move files to that location to make
+finding the target file easy.  Use the file manager or move the file using
+command line processing in a terminal window.  Image and binary files will be
+converted into ASCII text files using base64 conversion.  This basically is
+the same type of conversion that an email client would perform on an image or
+binary attachment.  The file is encoded using base64 coding at the sending
+end and then decoded back to its original form at the receiving end.
+At the conclusion of a satisfactory ARQ transfer the two files will be
+identical, including name and size.  The target directory for received
+files is $HOME/ARQrcvd in Linux, and c:\\NBEMS\\ARQrcvd in Windows.  The
+receiving station opens the c:\\NBEMS\\Mail\\ARQin folder and drags the
+incoming message placed there by FLARQ over to the Outlook Express email
+client, or just double-clicks on the .eml message to open it in the default
+email client.  It is the reciprocal process from that which the sending
+station uses.
+
+During the transfer the sending station transmits blocks of data.  Each
+block has a header, data, checksum and trailing component.  The receiving
+station acknowledges which blocks have been correctly received and which
+need retransmission.  Missing blocks sometimes occur in the middle of the
+set of acknowledged blocks.  The text in the FLARQ text window will only
+update as contiguous blocks are available.  So you might see the update
+occur in what appears to be random intervals.  As the sending and receiving
+stations go from receive-to-transmit-to-receive the diamond indicator will
+toggle from green to red and back to green.
+
+
+\subsection ssComposingEmail Composing Email
+
+FLARQ has a built-in email composer that creates files with a minimum of
+email overhead.  It is a text only composer with no attachment or other
+niceties associated with a normal email client.  It does produce very
+small email files which is a benefit when transmitting files over slower
+modem baud rates.  Click on the "Compose" menu item.  That will open the
+following dialog:
+
+<center>
+\image latex composer.png "Composer" width=5.25in
+\image html composer.png "Composer"
+</center>
+<br>
+
+Enter the email address of the destination addressee, the subject and the
+email body text.  Then press "Save" to save the file for later transmission.
+
+You can create a template for later use and then save the template by
+pressing SHIFT while clicking on the Save button.   Here is an example of a
+template in preparation:
+
+<center>
+\image latex wxstatus_tpl.png "Composer WX Template" width=5.25in
+\image html wxstatus_tpl.png "Composer WX Template"
+</center>
+<br>
+
+This file will be saved as "wxstatus.tpl".  FLARQ recognizes the tpl
+extension as the template file.  When you later click the Template button
+the new "wxstatus.tpl" template will be available to load and use in
+creating the wx status report.   After opening a template you can either
+modify it and save as a new or overwrite the existing template, or you
+can save the filled-in template as a regular file for subsequent
+transmission.
+
+\subsection ssUsingEmailClient Using Email client - Outlook Express
+
+You can use Outlook Express for the email client to create outgoing ARQ
+traffic.  Just remember that you should create all email traffic as ASCII
+text and not HTML text to reduce the size of the message body.  You are
+going to send this via an RF link and not over the internet with a high
+speed connection.
+
+Create your email just as you would for transfer over the internet and
+then save it in the Drafts folder.  In Outlook Express, click Create
+Email and use the format, name\@phonenumber, such as information
+\@8005551212, for the address if it is to be delivered by phone, and is
+not an email.  Save each message in the Drafts folder by clicking File,
+and then Save.  Exit the composition window.  Open the ARQout folder
+(located at c:\\NBEMS\\Mail\\ARQout) on the desktop along with Outlook
+Express as shown below.  Then drag the message from the "To ... Subject"
+area of Outlook Express and drop it on the ARQout folder. This places
+them in a folder that FLARQ can locate.
+
+<center>
+\image latex OLxpress.png "Outlook Express" width=5.5in
+\image html OLxpress.png "Outlook Express"
+\image latex ARQout.png "Outlook Express EMail Files" width=4.7in
+\image html ARQout.png "Outlook Express EMail Files"
+</center>
+<br>
+
+When you select the FLARQ menu item "Send / Email" a dialog will open
+that shows the contents of the messages that are in the ARQout folder:
+
+
+<center>
+\image latex SelectFromARQout.png "Select Message" width=5.25in
+\image html SelectFromARQout.png "Select Message"
+</center>
+<br>
+
+
+Multiple email entries would appear on separate lines with scroll bars as
+appropriate.  You highlight the desired file and then press "Send" or the
+Enter key to commence the file transfer.  The email may contain attachments
+(which may be images) or be just plain text.  Remember that this is a
+fairly slow transfer process so small is beautiful.  If the email has
+images then it will be in html and base-64 format.  That adds a lot of
+overhead to the email.  "Cancel" aborts the email transfer process.  After
+a successful transfer from sending to receiving station the email is
+automatically moved from the ARQout to the ARQsent folder.  If you are
+using Outlook Express you can open the c:\\NBEMS\\Mail\\ARQsent folder the
+same way that the ARQout folder can be opened.  At the receiving end the
+email will be placed in the Sylpheed ARQin folder.  Sylpheed does not
+need to be executing for this to occur at either end.
+
+\subsection ssUsingEmailClientSylpheed Using Email client - Sylpheed
+
+FLARQ has been optimally designed to interoperate with Sylpheed as its
+email client for emergency communications of email traffic.  When you
+install Sylpheed you will be asked to choose a default directory for the
+mail store.  On Linux/MacOSX this should be the default $HOME/Mail.  On Windows
+you should choose c:\\NBEMS\\Mail.  Three additional folders are used for
+transferring files between the FLARQ application and Sylpheed.
+These are:
+
+<ul>
+  <li>ARQin</li>
+  <li>ARQout, and</li>
+  <li>ARQsent</li>
+</ul>
+
+You can create these folders from within the Sylpheed application.
+
+<center>
+\image latex sylpheed-arqout.png "Sylpheed EMail Client" width=3.09in
+\image html sylpheed-arqout.png "Sylpheed EMail Client"
+</center>
+<br>
+
+The above image shows the folders already in place.  If they were not
+present they could be created by right clicking on the "Mailbox (MH)"
+icon and selecting "Create new folder".  Name each new folder as
+specified above and shown in the image.  These folders are required
+for FLARQ to be able to work with the Sylpheed email messages.  Each
+message in Sylpheed is a separate file.  These are usually numbered
+sequentially in each of the Sylpheed folders.  FLARQ manages the correct
+sequential naming of files as they are transferred in, out and moved
+between these three folders.  If you run the FLARQ application before
+Sylpheed then the c:\\NBEMS\\Mail and the c:\\NBEMS\\Mail\\ARQin, ARQout, and
+ARQsent folders will be created by that application and will appear in the
+Sylpheed folder system.
+
+To create a new email traffic you press the "Compose" button.  Fill out the
+email as usual and then press the "Draft" button from within the composer.
+The new message for transfer via FLARQ is now in the Drafts folder shown
+above.  Open that folder by clicking on it.  Select the desired draft
+message and drag and drop in onto the ARQout folder icon.  That's it!
+The message is now ready for FLARQ to perform the ARQ transfer.
+
+Upon completion of the transfer FLARQ will move the message to the ARQsent
+folder.  Sylpheed will not immediately recognize that the change has
+occured.  That is easily accomplished by either changing to another folder
+and then back again or by right clicking on the ARQout (or ARQin, or
+ARQsent) folder icon and selecting "Update summary".  Sylpheed will re-read
+the folder contents and adjust it's views accordingly.
+
+Incoming traffic will be placed in the ARQin folder.  You may have to refresh
+the folder as described above.
+
+FLARQ can find and parse the newly created email document that has been moved
+or copied to the ARQout folder.  If you select to send email a picker dialog
+will appear that lists all of the out going email traffic that is contained
+in the Sylpheed ARQout folder.
+
+\subsection ssOtherClients Other Email clients
+
+If you use an email client other than Sylpheed or Outlook Express you can
+transfer emails as above.  Just be sure that the emails have file names
+with the extension "eml" as in "mytest_message.eml".
+
+
+\subsection ssAbortingTX Aborting a transmission
+
+The transmission may be aborted by either the sending or the receiving
+station at any time during the file transfer.  When Connected  and
+transferring a file, the Connect button is re-labeled <b>Abort</b>.  Since
+data is sent in multiple blocks the actual abort will take place at
+the conclusion of the current group transmission.  Abort will cause
+the transfer to be interrupted.  The connection will be maintained
+and a new transfer can be initiated if required.
+
+\section sPlainTalk Plain Talk
+
+After a connection is established the two stations can exchange text using
+the "Plain Talk" entry control at the bottom of the main dialog.  Enter up
+to 80 characters and then press the Enter key to transmit the text.  This
+text is sent UNPROTO, which means that NO repeat request will be made.  The
+block is sent without any acknowledgement from the receiving station.  This
+is not an ACK/NACK system, but meant only as a way of allowing quick
+operator to operator exchanges without having to disconnect and use the
+digital modem program keyboard entry.  "Plain Talk"can be interspersed
+with normal ARQ file transfer blocks.
+
+\ref sFlarqDesc "Top of Page"
+*/
diff --git a/fldigi_doxygen/distclean.sh b/fldigi_doxygen/distclean.sh
new file mode 100755
index 00000000..af335ba6
--- /dev/null
+++ b/fldigi_doxygen/distclean.sh
@@ -0,0 +1,9 @@
+#!/bin/bash
+
+# Distribution clean of documents
+
+rm -rf pdf/
+rm -rf compressed_html/
+rm -rf user_docs/
+rm -rf prog_docs/
+
diff --git a/fldigi_doxygen/images/CWkeyingCircuit.png b/fldigi_doxygen/images/CWkeyingCircuit.png
new file mode 100644
index 00000000..f82e7389
Binary files /dev/null and b/fldigi_doxygen/images/CWkeyingCircuit.png differ
diff --git a/fldigi_doxygen/images/CabrilloSetup.png b/fldigi_doxygen/images/CabrilloSetup.png
new file mode 100644
index 00000000..db229b28
Binary files /dev/null and b/fldigi_doxygen/images/CabrilloSetup.png differ
diff --git a/fldigi_doxygen/images/ColorsFonts-buttons.png b/fldigi_doxygen/images/ColorsFonts-buttons.png
new file mode 100644
index 00000000..73086d96
Binary files /dev/null and b/fldigi_doxygen/images/ColorsFonts-buttons.png differ
diff --git a/fldigi_doxygen/images/ColorsFonts-dsp.png b/fldigi_doxygen/images/ColorsFonts-dsp.png
new file mode 100644
index 00000000..f9c1d11c
Binary files /dev/null and b/fldigi_doxygen/images/ColorsFonts-dsp.png differ
diff --git a/fldigi_doxygen/images/ColorsFonts-fkeys.png b/fldigi_doxygen/images/ColorsFonts-fkeys.png
new file mode 100644
index 00000000..b00d2c98
Binary files /dev/null and b/fldigi_doxygen/images/ColorsFonts-fkeys.png differ
diff --git a/fldigi_doxygen/images/ColorsFonts-log.png b/fldigi_doxygen/images/ColorsFonts-log.png
new file mode 100644
index 00000000..bf902098
Binary files /dev/null and b/fldigi_doxygen/images/ColorsFonts-log.png differ
diff --git a/fldigi_doxygen/images/ColorsFonts-rxtx.png b/fldigi_doxygen/images/ColorsFonts-rxtx.png
new file mode 100644
index 00000000..2956bb87
Binary files /dev/null and b/fldigi_doxygen/images/ColorsFonts-rxtx.png differ
diff --git a/fldigi_doxygen/images/ColorsFonts-siglvl.png b/fldigi_doxygen/images/ColorsFonts-siglvl.png
new file mode 100644
index 00000000..2df19421
Binary files /dev/null and b/fldigi_doxygen/images/ColorsFonts-siglvl.png differ
diff --git a/fldigi_doxygen/images/ColorsFonts-tabs.png b/fldigi_doxygen/images/ColorsFonts-tabs.png
new file mode 100644
index 00000000..41d0ecc9
Binary files /dev/null and b/fldigi_doxygen/images/ColorsFonts-tabs.png differ
diff --git a/fldigi_doxygen/images/DXCC_list.png b/fldigi_doxygen/images/DXCC_list.png
new file mode 100644
index 00000000..7685874c
Binary files /dev/null and b/fldigi_doxygen/images/DXCC_list.png differ
diff --git a/fldigi_doxygen/images/DataFilesSources.png b/fldigi_doxygen/images/DataFilesSources.png
new file mode 100644
index 00000000..bef1ef54
Binary files /dev/null and b/fldigi_doxygen/images/DataFilesSources.png differ
diff --git a/fldigi_doxygen/images/Dual-fldigi.png b/fldigi_doxygen/images/Dual-fldigi.png
new file mode 100644
index 00000000..155cb290
Binary files /dev/null and b/fldigi_doxygen/images/Dual-fldigi.png differ
diff --git a/fldigi_doxygen/images/ExportSetup.png b/fldigi_doxygen/images/ExportSetup.png
new file mode 100644
index 00000000..ce0d1353
Binary files /dev/null and b/fldigi_doxygen/images/ExportSetup.png differ
diff --git a/fldigi_doxygen/images/FLDigiWindow.png b/fldigi_doxygen/images/FLDigiWindow.png
new file mode 100644
index 00000000..5056592d
Binary files /dev/null and b/fldigi_doxygen/images/FLDigiWindow.png differ
diff --git a/fldigi_doxygen/images/FLDigiWindowHtml.png b/fldigi_doxygen/images/FLDigiWindowHtml.png
new file mode 100644
index 00000000..b9b9ebde
Binary files /dev/null and b/fldigi_doxygen/images/FLDigiWindowHtml.png differ
diff --git a/fldigi_doxygen/images/FindReception.png b/fldigi_doxygen/images/FindReception.png
new file mode 100644
index 00000000..0cde41d0
Binary files /dev/null and b/fldigi_doxygen/images/FindReception.png differ
diff --git a/fldigi_doxygen/images/FindTransmit.png b/fldigi_doxygen/images/FindTransmit.png
new file mode 100644
index 00000000..baaaa33f
Binary files /dev/null and b/fldigi_doxygen/images/FindTransmit.png differ
diff --git a/fldigi_doxygen/images/Fl_Native_File_Chooser.png b/fldigi_doxygen/images/Fl_Native_File_Chooser.png
new file mode 100644
index 00000000..1f1e6686
Binary files /dev/null and b/fldigi_doxygen/images/Fl_Native_File_Chooser.png differ
diff --git a/fldigi_doxygen/images/FreqAnal.png b/fldigi_doxygen/images/FreqAnal.png
new file mode 100644
index 00000000..799cb11f
Binary files /dev/null and b/fldigi_doxygen/images/FreqAnal.png differ
diff --git a/fldigi_doxygen/images/Google-Maps-Kml.png b/fldigi_doxygen/images/Google-Maps-Kml.png
new file mode 100644
index 00000000..91fb96f5
Binary files /dev/null and b/fldigi_doxygen/images/Google-Maps-Kml.png differ
diff --git a/fldigi_doxygen/images/GoogleEarth.png b/fldigi_doxygen/images/GoogleEarth.png
new file mode 100644
index 00000000..a4c7cecb
Binary files /dev/null and b/fldigi_doxygen/images/GoogleEarth.png differ
diff --git a/fldigi_doxygen/images/Icom_FSK.png b/fldigi_doxygen/images/Icom_FSK.png
new file mode 100644
index 00000000..f7652a0c
Binary files /dev/null and b/fldigi_doxygen/images/Icom_FSK.png differ
diff --git a/fldigi_doxygen/images/KML-Config.png b/fldigi_doxygen/images/KML-Config.png
new file mode 100644
index 00000000..1c4cc474
Binary files /dev/null and b/fldigi_doxygen/images/KML-Config.png differ
diff --git a/fldigi_doxygen/images/KML-Directory.png b/fldigi_doxygen/images/KML-Directory.png
new file mode 100644
index 00000000..fa0ef4f6
Binary files /dev/null and b/fldigi_doxygen/images/KML-Directory.png differ
diff --git a/fldigi_doxygen/images/KML-Logo.png b/fldigi_doxygen/images/KML-Logo.png
new file mode 100644
index 00000000..c3c5bf44
Binary files /dev/null and b/fldigi_doxygen/images/KML-Logo.png differ
diff --git a/fldigi_doxygen/images/Level-Indicator.png b/fldigi_doxygen/images/Level-Indicator.png
new file mode 100644
index 00000000..ec6d73d3
Binary files /dev/null and b/fldigi_doxygen/images/Level-Indicator.png differ
diff --git a/fldigi_doxygen/images/MultiChannelBPSKWaterfall.png b/fldigi_doxygen/images/MultiChannelBPSKWaterfall.png
new file mode 100644
index 00000000..c383f564
Binary files /dev/null and b/fldigi_doxygen/images/MultiChannelBPSKWaterfall.png differ
diff --git a/fldigi_doxygen/images/MultiChannelBPSKWaterfall80pct.png b/fldigi_doxygen/images/MultiChannelBPSKWaterfall80pct.png
new file mode 100644
index 00000000..ab0a298f
Binary files /dev/null and b/fldigi_doxygen/images/MultiChannelBPSKWaterfall80pct.png differ
diff --git a/fldigi_doxygen/images/Navtex-Choosing-Stations-File.png b/fldigi_doxygen/images/Navtex-Choosing-Stations-File.png
new file mode 100644
index 00000000..bf77ea57
Binary files /dev/null and b/fldigi_doxygen/images/Navtex-Choosing-Stations-File.png differ
diff --git a/fldigi_doxygen/images/Navtex-Choosing.png b/fldigi_doxygen/images/Navtex-Choosing.png
new file mode 100644
index 00000000..761b8c37
Binary files /dev/null and b/fldigi_doxygen/images/Navtex-Choosing.png differ
diff --git a/fldigi_doxygen/images/Navtex-Config-Tab-With-Kml.png b/fldigi_doxygen/images/Navtex-Config-Tab-With-Kml.png
new file mode 100644
index 00000000..bbb90fd4
Binary files /dev/null and b/fldigi_doxygen/images/Navtex-Config-Tab-With-Kml.png differ
diff --git a/fldigi_doxygen/images/Navtex-Configuration.png b/fldigi_doxygen/images/Navtex-Configuration.png
new file mode 100644
index 00000000..d471a3f6
Binary files /dev/null and b/fldigi_doxygen/images/Navtex-Configuration.png differ
diff --git a/fldigi_doxygen/images/Navtex-Logged-Contacts.png b/fldigi_doxygen/images/Navtex-Logged-Contacts.png
new file mode 100644
index 00000000..682264b6
Binary files /dev/null and b/fldigi_doxygen/images/Navtex-Logged-Contacts.png differ
diff --git a/fldigi_doxygen/images/Navtex-Reception.png b/fldigi_doxygen/images/Navtex-Reception.png
new file mode 100644
index 00000000..ec03de66
Binary files /dev/null and b/fldigi_doxygen/images/Navtex-Reception.png differ
diff --git a/fldigi_doxygen/images/Notifications.png b/fldigi_doxygen/images/Notifications.png
new file mode 100644
index 00000000..58b063f2
Binary files /dev/null and b/fldigi_doxygen/images/Notifications.png differ
diff --git a/fldigi_doxygen/images/Notifier-popup.png b/fldigi_doxygen/images/Notifier-popup.png
new file mode 100644
index 00000000..da979312
Binary files /dev/null and b/fldigi_doxygen/images/Notifier-popup.png differ
diff --git a/fldigi_doxygen/images/Notifier-rxtext.png b/fldigi_doxygen/images/Notifier-rxtext.png
new file mode 100644
index 00000000..1844d94b
Binary files /dev/null and b/fldigi_doxygen/images/Notifier-rxtext.png differ
diff --git a/fldigi_doxygen/images/Olivia32-1000.png b/fldigi_doxygen/images/Olivia32-1000.png
new file mode 100644
index 00000000..5b2454b3
Binary files /dev/null and b/fldigi_doxygen/images/Olivia32-1000.png differ
diff --git a/fldigi_doxygen/images/Opening-DataFiles-Menu.png b/fldigi_doxygen/images/Opening-DataFiles-Menu.png
new file mode 100644
index 00000000..8cf6bf6d
Binary files /dev/null and b/fldigi_doxygen/images/Opening-DataFiles-Menu.png differ
diff --git a/fldigi_doxygen/images/RS-id.png b/fldigi_doxygen/images/RS-id.png
new file mode 100644
index 00000000..b74ac2e1
Binary files /dev/null and b/fldigi_doxygen/images/RS-id.png differ
diff --git a/fldigi_doxygen/images/RSID.png b/fldigi_doxygen/images/RSID.png
new file mode 100644
index 00000000..c5d71f24
Binary files /dev/null and b/fldigi_doxygen/images/RSID.png differ
diff --git a/fldigi_doxygen/images/RTTY-Config-Tab-With-Synop.png b/fldigi_doxygen/images/RTTY-Config-Tab-With-Synop.png
new file mode 100644
index 00000000..a08cabbf
Binary files /dev/null and b/fldigi_doxygen/images/RTTY-Config-Tab-With-Synop.png differ
diff --git a/fldigi_doxygen/images/RTTY-demodulator.png b/fldigi_doxygen/images/RTTY-demodulator.png
new file mode 100644
index 00000000..61337c8d
Binary files /dev/null and b/fldigi_doxygen/images/RTTY-demodulator.png differ
diff --git a/fldigi_doxygen/images/RTTY.-overdriven.png b/fldigi_doxygen/images/RTTY.-overdriven.png
new file mode 100644
index 00000000..712d5c4a
Binary files /dev/null and b/fldigi_doxygen/images/RTTY.-overdriven.png differ
diff --git a/fldigi_doxygen/images/RWM+25361ppm.png b/fldigi_doxygen/images/RWM+25361ppm.png
new file mode 100644
index 00000000..4c5551bb
Binary files /dev/null and b/fldigi_doxygen/images/RWM+25361ppm.png differ
diff --git a/fldigi_doxygen/images/RWMpost-cal-x5.png b/fldigi_doxygen/images/RWMpost-cal-x5.png
new file mode 100644
index 00000000..630d1a22
Binary files /dev/null and b/fldigi_doxygen/images/RWMpost-cal-x5.png differ
diff --git a/fldigi_doxygen/images/RWMpre-cal.png b/fldigi_doxygen/images/RWMpre-cal.png
new file mode 100644
index 00000000..7339dc1b
Binary files /dev/null and b/fldigi_doxygen/images/RWMpre-cal.png differ
diff --git a/fldigi_doxygen/images/Reception.png b/fldigi_doxygen/images/Reception.png
new file mode 100644
index 00000000..df4eec4e
Binary files /dev/null and b/fldigi_doxygen/images/Reception.png differ
diff --git a/fldigi_doxygen/images/Reception_Empty.png b/fldigi_doxygen/images/Reception_Empty.png
new file mode 100644
index 00000000..c5efed56
Binary files /dev/null and b/fldigi_doxygen/images/Reception_Empty.png differ
diff --git a/fldigi_doxygen/images/SavedWAVFileSampleRate.png b/fldigi_doxygen/images/SavedWAVFileSampleRate.png
new file mode 100644
index 00000000..5b7413cc
Binary files /dev/null and b/fldigi_doxygen/images/SavedWAVFileSampleRate.png differ
diff --git a/fldigi_doxygen/images/Screenshot.png b/fldigi_doxygen/images/Screenshot.png
new file mode 100644
index 00000000..8eb1fa36
Binary files /dev/null and b/fldigi_doxygen/images/Screenshot.png differ
diff --git a/fldigi_doxygen/images/TR-controls.png b/fldigi_doxygen/images/TR-controls.png
new file mode 100644
index 00000000..5b6989c5
Binary files /dev/null and b/fldigi_doxygen/images/TR-controls.png differ
diff --git a/fldigi_doxygen/images/TX-level.png b/fldigi_doxygen/images/TX-level.png
new file mode 100644
index 00000000..c8f1fc3c
Binary files /dev/null and b/fldigi_doxygen/images/TX-level.png differ
diff --git a/fldigi_doxygen/images/Thor-1.png b/fldigi_doxygen/images/Thor-1.png
new file mode 100644
index 00000000..5bf4bd72
Binary files /dev/null and b/fldigi_doxygen/images/Thor-1.png differ
diff --git a/fldigi_doxygen/images/Transmit_A.png b/fldigi_doxygen/images/Transmit_A.png
new file mode 100644
index 00000000..346fe474
Binary files /dev/null and b/fldigi_doxygen/images/Transmit_A.png differ
diff --git a/fldigi_doxygen/images/Transmit_B.png b/fldigi_doxygen/images/Transmit_B.png
new file mode 100644
index 00000000..91ff0202
Binary files /dev/null and b/fldigi_doxygen/images/Transmit_B.png differ
diff --git a/fldigi_doxygen/images/TxMenu.png b/fldigi_doxygen/images/TxMenu.png
new file mode 100644
index 00000000..070708bd
Binary files /dev/null and b/fldigi_doxygen/images/TxMenu.png differ
diff --git a/fldigi_doxygen/images/UI-minimized.png b/fldigi_doxygen/images/UI-minimized.png
new file mode 100644
index 00000000..b9552f53
Binary files /dev/null and b/fldigi_doxygen/images/UI-minimized.png differ
diff --git a/fldigi_doxygen/images/UTF8-Example.png b/fldigi_doxygen/images/UTF8-Example.png
new file mode 100644
index 00000000..2fada5d6
Binary files /dev/null and b/fldigi_doxygen/images/UTF8-Example.png differ
diff --git a/fldigi_doxygen/images/W5ZIT-interface.png b/fldigi_doxygen/images/W5ZIT-interface.png
new file mode 100644
index 00000000..682007b3
Binary files /dev/null and b/fldigi_doxygen/images/W5ZIT-interface.png differ
diff --git a/fldigi_doxygen/images/Wefax-Configuration.png b/fldigi_doxygen/images/Wefax-Configuration.png
new file mode 100644
index 00000000..97047234
Binary files /dev/null and b/fldigi_doxygen/images/Wefax-Configuration.png differ
diff --git a/fldigi_doxygen/images/Wefax-Detached-Windows.png b/fldigi_doxygen/images/Wefax-Detached-Windows.png
new file mode 100644
index 00000000..f51c606d
Binary files /dev/null and b/fldigi_doxygen/images/Wefax-Detached-Windows.png differ
diff --git a/fldigi_doxygen/images/Wefax-Display-And-Receive.png b/fldigi_doxygen/images/Wefax-Display-And-Receive.png
new file mode 100644
index 00000000..081c341a
Binary files /dev/null and b/fldigi_doxygen/images/Wefax-Display-And-Receive.png differ
diff --git a/fldigi_doxygen/images/Wefax-File-Received.png b/fldigi_doxygen/images/Wefax-File-Received.png
new file mode 100644
index 00000000..d4a8b5ce
Binary files /dev/null and b/fldigi_doxygen/images/Wefax-File-Received.png differ
diff --git a/fldigi_doxygen/images/Wefax-Sending.png b/fldigi_doxygen/images/Wefax-Sending.png
new file mode 100644
index 00000000..b2165502
Binary files /dev/null and b/fldigi_doxygen/images/Wefax-Sending.png differ
diff --git a/fldigi_doxygen/images/Wefax-Tab.png b/fldigi_doxygen/images/Wefax-Tab.png
new file mode 100644
index 00000000..54195e6b
Binary files /dev/null and b/fldigi_doxygen/images/Wefax-Tab.png differ
diff --git a/fldigi_doxygen/images/Xmt-Pix.png b/fldigi_doxygen/images/Xmt-Pix.png
new file mode 100644
index 00000000..0bcfc7c1
Binary files /dev/null and b/fldigi_doxygen/images/Xmt-Pix.png differ
diff --git a/fldigi_doxygen/images/Xmt-Pix1.png b/fldigi_doxygen/images/Xmt-Pix1.png
new file mode 100644
index 00000000..ff8c6e50
Binary files /dev/null and b/fldigi_doxygen/images/Xmt-Pix1.png differ
diff --git a/fldigi_doxygen/images/Xmt-Pix3.png b/fldigi_doxygen/images/Xmt-Pix3.png
new file mode 100644
index 00000000..78aa0323
Binary files /dev/null and b/fldigi_doxygen/images/Xmt-Pix3.png differ
diff --git a/fldigi_doxygen/images/Xmt-Pix4.png b/fldigi_doxygen/images/Xmt-Pix4.png
new file mode 100644
index 00000000..dfd14d03
Binary files /dev/null and b/fldigi_doxygen/images/Xmt-Pix4.png differ
diff --git a/fldigi_doxygen/images/activity-reports.png b/fldigi_doxygen/images/activity-reports.png
new file mode 100644
index 00000000..ba422533
Binary files /dev/null and b/fldigi_doxygen/images/activity-reports.png differ
diff --git a/fldigi_doxygen/images/autostart_programs.png b/fldigi_doxygen/images/autostart_programs.png
new file mode 100644
index 00000000..6ba38e4d
Binary files /dev/null and b/fldigi_doxygen/images/autostart_programs.png differ
diff --git a/fldigi_doxygen/images/blue_line_text.png b/fldigi_doxygen/images/blue_line_text.png
new file mode 100644
index 00000000..138f3d8a
Binary files /dev/null and b/fldigi_doxygen/images/blue_line_text.png differ
diff --git a/fldigi_doxygen/images/browser-panel.png b/fldigi_doxygen/images/browser-panel.png
new file mode 100644
index 00000000..756f8b5b
Binary files /dev/null and b/fldigi_doxygen/images/browser-panel.png differ
diff --git a/fldigi_doxygen/images/callsign_capture.png b/fldigi_doxygen/images/callsign_capture.png
new file mode 100644
index 00000000..70864ca3
Binary files /dev/null and b/fldigi_doxygen/images/callsign_capture.png differ
diff --git a/fldigi_doxygen/images/config-WX.png b/fldigi_doxygen/images/config-WX.png
new file mode 100644
index 00000000..13567e2d
Binary files /dev/null and b/fldigi_doxygen/images/config-WX.png differ
diff --git a/fldigi_doxygen/images/config-audio-devices.png b/fldigi_doxygen/images/config-audio-devices.png
new file mode 100644
index 00000000..1153b22b
Binary files /dev/null and b/fldigi_doxygen/images/config-audio-devices.png differ
diff --git a/fldigi_doxygen/images/config-audio-mixer.png b/fldigi_doxygen/images/config-audio-mixer.png
new file mode 100644
index 00000000..e9120862
Binary files /dev/null and b/fldigi_doxygen/images/config-audio-mixer.png differ
diff --git a/fldigi_doxygen/images/config-audio-right.png b/fldigi_doxygen/images/config-audio-right.png
new file mode 100644
index 00000000..8e831e8c
Binary files /dev/null and b/fldigi_doxygen/images/config-audio-right.png differ
diff --git a/fldigi_doxygen/images/config-audio-settings.png b/fldigi_doxygen/images/config-audio-settings.png
new file mode 100644
index 00000000..bb503194
Binary files /dev/null and b/fldigi_doxygen/images/config-audio-settings.png differ
diff --git a/fldigi_doxygen/images/config-audio-wav.png b/fldigi_doxygen/images/config-audio-wav.png
new file mode 100644
index 00000000..c7717f64
Binary files /dev/null and b/fldigi_doxygen/images/config-audio-wav.png differ
diff --git a/fldigi_doxygen/images/config-callsign-db.png b/fldigi_doxygen/images/config-callsign-db.png
new file mode 100644
index 00000000..6d4594ad
Binary files /dev/null and b/fldigi_doxygen/images/config-callsign-db.png differ
diff --git a/fldigi_doxygen/images/config-contest.png b/fldigi_doxygen/images/config-contest.png
new file mode 100644
index 00000000..e8354dda
Binary files /dev/null and b/fldigi_doxygen/images/config-contest.png differ
diff --git a/fldigi_doxygen/images/config-contestia.png b/fldigi_doxygen/images/config-contestia.png
new file mode 100644
index 00000000..0646cbad
Binary files /dev/null and b/fldigi_doxygen/images/config-contestia.png differ
diff --git a/fldigi_doxygen/images/config-cw-general.png b/fldigi_doxygen/images/config-cw-general.png
new file mode 100644
index 00000000..54971ec4
Binary files /dev/null and b/fldigi_doxygen/images/config-cw-general.png differ
diff --git a/fldigi_doxygen/images/config-cw-prosign-popup.png b/fldigi_doxygen/images/config-cw-prosign-popup.png
new file mode 100644
index 00000000..152cb721
Binary files /dev/null and b/fldigi_doxygen/images/config-cw-prosign-popup.png differ
diff --git a/fldigi_doxygen/images/config-cw-prosigns.png b/fldigi_doxygen/images/config-cw-prosigns.png
new file mode 100644
index 00000000..b76f52c3
Binary files /dev/null and b/fldigi_doxygen/images/config-cw-prosigns.png differ
diff --git a/fldigi_doxygen/images/config-cw-qsk.png b/fldigi_doxygen/images/config-cw-qsk.png
new file mode 100644
index 00000000..6e30c803
Binary files /dev/null and b/fldigi_doxygen/images/config-cw-qsk.png differ
diff --git a/fldigi_doxygen/images/config-domino.png b/fldigi_doxygen/images/config-domino.png
new file mode 100644
index 00000000..e71f1b08
Binary files /dev/null and b/fldigi_doxygen/images/config-domino.png differ
diff --git a/fldigi_doxygen/images/config-eqsl.png b/fldigi_doxygen/images/config-eqsl.png
new file mode 100644
index 00000000..898e9ab1
Binary files /dev/null and b/fldigi_doxygen/images/config-eqsl.png differ
diff --git a/fldigi_doxygen/images/config-feldhell.png b/fldigi_doxygen/images/config-feldhell.png
new file mode 100644
index 00000000..8d0aed5c
Binary files /dev/null and b/fldigi_doxygen/images/config-feldhell.png differ
diff --git a/fldigi_doxygen/images/config-id-cw-modes.png b/fldigi_doxygen/images/config-id-cw-modes.png
new file mode 100644
index 00000000..604c1368
Binary files /dev/null and b/fldigi_doxygen/images/config-id-cw-modes.png differ
diff --git a/fldigi_doxygen/images/config-id-cw.png b/fldigi_doxygen/images/config-id-cw.png
new file mode 100644
index 00000000..52433660
Binary files /dev/null and b/fldigi_doxygen/images/config-id-cw.png differ
diff --git a/fldigi_doxygen/images/config-id-rsid.png b/fldigi_doxygen/images/config-id-rsid.png
new file mode 100644
index 00000000..d8e23296
Binary files /dev/null and b/fldigi_doxygen/images/config-id-rsid.png differ
diff --git a/fldigi_doxygen/images/config-id-rx-modes.png b/fldigi_doxygen/images/config-id-rx-modes.png
new file mode 100644
index 00000000..6b6b9779
Binary files /dev/null and b/fldigi_doxygen/images/config-id-rx-modes.png differ
diff --git a/fldigi_doxygen/images/config-id-video-modes.png b/fldigi_doxygen/images/config-id-video-modes.png
new file mode 100644
index 00000000..06c785c9
Binary files /dev/null and b/fldigi_doxygen/images/config-id-video-modes.png differ
diff --git a/fldigi_doxygen/images/config-id-video.png b/fldigi_doxygen/images/config-id-video.png
new file mode 100644
index 00000000..449cc485
Binary files /dev/null and b/fldigi_doxygen/images/config-id-video.png differ
diff --git a/fldigi_doxygen/images/config-id-xmt-modes.png b/fldigi_doxygen/images/config-id-xmt-modes.png
new file mode 100644
index 00000000..181e1a9e
Binary files /dev/null and b/fldigi_doxygen/images/config-id-xmt-modes.png differ
diff --git a/fldigi_doxygen/images/config-id.png b/fldigi_doxygen/images/config-id.png
new file mode 100644
index 00000000..a5ce780f
Binary files /dev/null and b/fldigi_doxygen/images/config-id.png differ
diff --git a/fldigi_doxygen/images/config-macrobars.png b/fldigi_doxygen/images/config-macrobars.png
new file mode 100644
index 00000000..9329a691
Binary files /dev/null and b/fldigi_doxygen/images/config-macrobars.png differ
diff --git a/fldigi_doxygen/images/config-misc-cpu.png b/fldigi_doxygen/images/config-misc-cpu.png
new file mode 100644
index 00000000..db8ad307
Binary files /dev/null and b/fldigi_doxygen/images/config-misc-cpu.png differ
diff --git a/fldigi_doxygen/images/config-misc-dtmf.png b/fldigi_doxygen/images/config-misc-dtmf.png
new file mode 100644
index 00000000..c5ea9fcd
Binary files /dev/null and b/fldigi_doxygen/images/config-misc-dtmf.png differ
diff --git a/fldigi_doxygen/images/config-misc-kml.png b/fldigi_doxygen/images/config-misc-kml.png
new file mode 100644
index 00000000..729782aa
Binary files /dev/null and b/fldigi_doxygen/images/config-misc-kml.png differ
diff --git a/fldigi_doxygen/images/config-misc-nbems.png b/fldigi_doxygen/images/config-misc-nbems.png
new file mode 100644
index 00000000..eed318ff
Binary files /dev/null and b/fldigi_doxygen/images/config-misc-nbems.png differ
diff --git a/fldigi_doxygen/images/config-misc-spotting.png b/fldigi_doxygen/images/config-misc-spotting.png
new file mode 100644
index 00000000..3371c578
Binary files /dev/null and b/fldigi_doxygen/images/config-misc-spotting.png differ
diff --git a/fldigi_doxygen/images/config-misc-sweet.png b/fldigi_doxygen/images/config-misc-sweet.png
new file mode 100644
index 00000000..8802d39a
Binary files /dev/null and b/fldigi_doxygen/images/config-misc-sweet.png differ
diff --git a/fldigi_doxygen/images/config-misc-textio.png b/fldigi_doxygen/images/config-misc-textio.png
new file mode 100644
index 00000000..b6a2dcb3
Binary files /dev/null and b/fldigi_doxygen/images/config-misc-textio.png differ
diff --git a/fldigi_doxygen/images/config-misc-wx.png b/fldigi_doxygen/images/config-misc-wx.png
new file mode 100644
index 00000000..f50790d4
Binary files /dev/null and b/fldigi_doxygen/images/config-misc-wx.png differ
diff --git a/fldigi_doxygen/images/config-mt63.png b/fldigi_doxygen/images/config-mt63.png
new file mode 100644
index 00000000..99e96f6f
Binary files /dev/null and b/fldigi_doxygen/images/config-mt63.png differ
diff --git a/fldigi_doxygen/images/config-olivia.png b/fldigi_doxygen/images/config-olivia.png
new file mode 100644
index 00000000..25c95e3e
Binary files /dev/null and b/fldigi_doxygen/images/config-olivia.png differ
diff --git a/fldigi_doxygen/images/config-operator.png b/fldigi_doxygen/images/config-operator.png
new file mode 100644
index 00000000..9f1af4df
Binary files /dev/null and b/fldigi_doxygen/images/config-operator.png differ
diff --git a/fldigi_doxygen/images/config-psk-general.png b/fldigi_doxygen/images/config-psk-general.png
new file mode 100644
index 00000000..5841a67f
Binary files /dev/null and b/fldigi_doxygen/images/config-psk-general.png differ
diff --git a/fldigi_doxygen/images/config-psk-mail.png b/fldigi_doxygen/images/config-psk-mail.png
new file mode 100644
index 00000000..3112d052
Binary files /dev/null and b/fldigi_doxygen/images/config-psk-mail.png differ
diff --git a/fldigi_doxygen/images/config-qrz.png b/fldigi_doxygen/images/config-qrz.png
new file mode 100644
index 00000000..e7e05d86
Binary files /dev/null and b/fldigi_doxygen/images/config-qrz.png differ
diff --git a/fldigi_doxygen/images/config-rig-hamlib.png b/fldigi_doxygen/images/config-rig-hamlib.png
new file mode 100644
index 00000000..f2499964
Binary files /dev/null and b/fldigi_doxygen/images/config-rig-hamlib.png differ
diff --git a/fldigi_doxygen/images/config-rig-hardware.png b/fldigi_doxygen/images/config-rig-hardware.png
new file mode 100644
index 00000000..ff0209c4
Binary files /dev/null and b/fldigi_doxygen/images/config-rig-hardware.png differ
diff --git a/fldigi_doxygen/images/config-rig-rigcat.png b/fldigi_doxygen/images/config-rig-rigcat.png
new file mode 100644
index 00000000..900660a3
Binary files /dev/null and b/fldigi_doxygen/images/config-rig-rigcat.png differ
diff --git a/fldigi_doxygen/images/config-rig-xmlrpc.png b/fldigi_doxygen/images/config-rig-xmlrpc.png
new file mode 100644
index 00000000..ca0ff9f7
Binary files /dev/null and b/fldigi_doxygen/images/config-rig-xmlrpc.png differ
diff --git a/fldigi_doxygen/images/config-rtty-classic-scope.png b/fldigi_doxygen/images/config-rtty-classic-scope.png
new file mode 100644
index 00000000..d8dff7b5
Binary files /dev/null and b/fldigi_doxygen/images/config-rtty-classic-scope.png differ
diff --git a/fldigi_doxygen/images/config-rtty-pseudo-scope.png b/fldigi_doxygen/images/config-rtty-pseudo-scope.png
new file mode 100644
index 00000000..d67c740e
Binary files /dev/null and b/fldigi_doxygen/images/config-rtty-pseudo-scope.png differ
diff --git a/fldigi_doxygen/images/config-rtty-rx.png b/fldigi_doxygen/images/config-rtty-rx.png
new file mode 100644
index 00000000..a63cbb82
Binary files /dev/null and b/fldigi_doxygen/images/config-rtty-rx.png differ
diff --git a/fldigi_doxygen/images/config-rtty-synop.png b/fldigi_doxygen/images/config-rtty-synop.png
new file mode 100644
index 00000000..05974bac
Binary files /dev/null and b/fldigi_doxygen/images/config-rtty-synop.png differ
diff --git a/fldigi_doxygen/images/config-rtty-tx.png b/fldigi_doxygen/images/config-rtty-tx.png
new file mode 100644
index 00000000..7dd09543
Binary files /dev/null and b/fldigi_doxygen/images/config-rtty-tx.png differ
diff --git a/fldigi_doxygen/images/config-rtty.png b/fldigi_doxygen/images/config-rtty.png
new file mode 100644
index 00000000..4b2b9078
Binary files /dev/null and b/fldigi_doxygen/images/config-rtty.png differ
diff --git a/fldigi_doxygen/images/config-thor.png b/fldigi_doxygen/images/config-thor.png
new file mode 100644
index 00000000..976bc21f
Binary files /dev/null and b/fldigi_doxygen/images/config-thor.png differ
diff --git a/fldigi_doxygen/images/config-thor.png.png b/fldigi_doxygen/images/config-thor.png.png
new file mode 100644
index 00000000..3b9202ac
Binary files /dev/null and b/fldigi_doxygen/images/config-thor.png.png differ
diff --git a/fldigi_doxygen/images/config-ui-bro-wser.png b/fldigi_doxygen/images/config-ui-bro-wser.png
new file mode 100644
index 00000000..583583c9
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-bro-wser.png differ
diff --git a/fldigi_doxygen/images/config-ui-browser.png b/fldigi_doxygen/images/config-ui-browser.png
new file mode 100644
index 00000000..164fabc4
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-browser.png differ
diff --git a/fldigi_doxygen/images/config-ui-colors-fonts.png b/fldigi_doxygen/images/config-ui-colors-fonts.png
new file mode 100644
index 00000000..2956bb87
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-colors-fonts.png differ
diff --git a/fldigi_doxygen/images/config-ui-contest.png b/fldigi_doxygen/images/config-ui-contest.png
new file mode 100644
index 00000000..f7f15e55
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-contest.png differ
diff --git a/fldigi_doxygen/images/config-ui-general.png b/fldigi_doxygen/images/config-ui-general.png
new file mode 100644
index 00000000..dbe98dc0
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-general.png differ
diff --git a/fldigi_doxygen/images/config-ui-lan.png b/fldigi_doxygen/images/config-ui-lan.png
new file mode 100644
index 00000000..40a68645
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-lan.png differ
diff --git a/fldigi_doxygen/images/config-ui-logserver.png b/fldigi_doxygen/images/config-ui-logserver.png
new file mode 100644
index 00000000..39c2e935
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-logserver.png differ
diff --git a/fldigi_doxygen/images/config-ui-macros.png b/fldigi_doxygen/images/config-ui-macros.png
new file mode 100644
index 00000000..2fa7988d
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-macros.png differ
diff --git a/fldigi_doxygen/images/config-ui-oper-controls.png b/fldigi_doxygen/images/config-ui-oper-controls.png
new file mode 100644
index 00000000..6e5d83b8
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-oper-controls.png differ
diff --git a/fldigi_doxygen/images/config-ui-qso-logging.png b/fldigi_doxygen/images/config-ui-qso-logging.png
new file mode 100644
index 00000000..60be3a20
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-qso-logging.png differ
diff --git a/fldigi_doxygen/images/config-ui-restart.png b/fldigi_doxygen/images/config-ui-restart.png
new file mode 100644
index 00000000..31562372
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-restart.png differ
diff --git a/fldigi_doxygen/images/config-ui-rxtext-2.png b/fldigi_doxygen/images/config-ui-rxtext-2.png
new file mode 100644
index 00000000..54b24773
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-rxtext-2.png differ
diff --git a/fldigi_doxygen/images/config-ui-rxtext.png b/fldigi_doxygen/images/config-ui-rxtext.png
new file mode 100644
index 00000000..09741a12
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-rxtext.png differ
diff --git a/fldigi_doxygen/images/config-ui-tabs.png b/fldigi_doxygen/images/config-ui-tabs.png
new file mode 100644
index 00000000..1b69a95b
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-tabs.png differ
diff --git a/fldigi_doxygen/images/config-ui-wf-controls-2.png b/fldigi_doxygen/images/config-ui-wf-controls-2.png
new file mode 100644
index 00000000..defdfb29
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-wf-controls-2.png differ
diff --git a/fldigi_doxygen/images/config-ui-wf-controls.png b/fldigi_doxygen/images/config-ui-wf-controls.png
new file mode 100644
index 00000000..5677a690
Binary files /dev/null and b/fldigi_doxygen/images/config-ui-wf-controls.png differ
diff --git a/fldigi_doxygen/images/config-wf-display.png b/fldigi_doxygen/images/config-wf-display.png
new file mode 100644
index 00000000..44b9e94e
Binary files /dev/null and b/fldigi_doxygen/images/config-wf-display.png differ
diff --git a/fldigi_doxygen/images/config-wf-fft.png b/fldigi_doxygen/images/config-wf-fft.png
new file mode 100644
index 00000000..b10451c8
Binary files /dev/null and b/fldigi_doxygen/images/config-wf-fft.png differ
diff --git a/fldigi_doxygen/images/config-wf-mouse.png b/fldigi_doxygen/images/config-wf-mouse.png
new file mode 100644
index 00000000..36d1f508
Binary files /dev/null and b/fldigi_doxygen/images/config-wf-mouse.png differ
diff --git a/fldigi_doxygen/images/connect-to-logserver.png b/fldigi_doxygen/images/connect-to-logserver.png
new file mode 100644
index 00000000..180bb3c1
Binary files /dev/null and b/fldigi_doxygen/images/connect-to-logserver.png differ
diff --git a/fldigi_doxygen/images/contest-fields.png b/fldigi_doxygen/images/contest-fields.png
new file mode 100644
index 00000000..e2a959a1
Binary files /dev/null and b/fldigi_doxygen/images/contest-fields.png differ
diff --git a/fldigi_doxygen/images/counter.png b/fldigi_doxygen/images/counter.png
new file mode 100644
index 00000000..3c51f621
Binary files /dev/null and b/fldigi_doxygen/images/counter.png differ
diff --git a/fldigi_doxygen/images/cq-1.png b/fldigi_doxygen/images/cq-1.png
new file mode 100644
index 00000000..566065a1
Binary files /dev/null and b/fldigi_doxygen/images/cq-1.png differ
diff --git a/fldigi_doxygen/images/cq-2.png b/fldigi_doxygen/images/cq-2.png
new file mode 100644
index 00000000..54847486
Binary files /dev/null and b/fldigi_doxygen/images/cq-2.png differ
diff --git a/fldigi_doxygen/images/cq_digipan.png b/fldigi_doxygen/images/cq_digipan.png
new file mode 100644
index 00000000..b3161d63
Binary files /dev/null and b/fldigi_doxygen/images/cq_digipan.png differ
diff --git a/fldigi_doxygen/images/cq_multipsk.png b/fldigi_doxygen/images/cq_multipsk.png
new file mode 100644
index 00000000..e15e4b2e
Binary files /dev/null and b/fldigi_doxygen/images/cq_multipsk.png differ
diff --git a/fldigi_doxygen/images/cw-00-30.png b/fldigi_doxygen/images/cw-00-30.png
new file mode 100644
index 00000000..2156c169
Binary files /dev/null and b/fldigi_doxygen/images/cw-00-30.png differ
diff --git a/fldigi_doxygen/images/cw-00-40.png b/fldigi_doxygen/images/cw-00-40.png
new file mode 100644
index 00000000..bc98a4a7
Binary files /dev/null and b/fldigi_doxygen/images/cw-00-40.png differ
diff --git a/fldigi_doxygen/images/cw-120-30.png b/fldigi_doxygen/images/cw-120-30.png
new file mode 100644
index 00000000..51213dc5
Binary files /dev/null and b/fldigi_doxygen/images/cw-120-30.png differ
diff --git a/fldigi_doxygen/images/cw-30-30.png b/fldigi_doxygen/images/cw-30-30.png
new file mode 100644
index 00000000..5931b998
Binary files /dev/null and b/fldigi_doxygen/images/cw-30-30.png differ
diff --git a/fldigi_doxygen/images/cw-60-30.png b/fldigi_doxygen/images/cw-60-30.png
new file mode 100644
index 00000000..13bc8a2c
Binary files /dev/null and b/fldigi_doxygen/images/cw-60-30.png differ
diff --git a/fldigi_doxygen/images/cw_status_1.png b/fldigi_doxygen/images/cw_status_1.png
new file mode 100644
index 00000000..f3b8be20
Binary files /dev/null and b/fldigi_doxygen/images/cw_status_1.png differ
diff --git a/fldigi_doxygen/images/cw_status_2.png b/fldigi_doxygen/images/cw_status_2.png
new file mode 100644
index 00000000..57fa0974
Binary files /dev/null and b/fldigi_doxygen/images/cw_status_2.png differ
diff --git a/fldigi_doxygen/images/dcf77-0.png b/fldigi_doxygen/images/dcf77-0.png
new file mode 100644
index 00000000..8e3ebcfe
Binary files /dev/null and b/fldigi_doxygen/images/dcf77-0.png differ
diff --git a/fldigi_doxygen/images/dcf77-0zoom.png b/fldigi_doxygen/images/dcf77-0zoom.png
new file mode 100644
index 00000000..7ce576b6
Binary files /dev/null and b/fldigi_doxygen/images/dcf77-0zoom.png differ
diff --git a/fldigi_doxygen/images/dcf77-1000.png b/fldigi_doxygen/images/dcf77-1000.png
new file mode 100644
index 00000000..ae8a0795
Binary files /dev/null and b/fldigi_doxygen/images/dcf77-1000.png differ
diff --git a/fldigi_doxygen/images/dcf77-65zoom.png b/fldigi_doxygen/images/dcf77-65zoom.png
new file mode 100644
index 00000000..b7cda458
Binary files /dev/null and b/fldigi_doxygen/images/dcf77-65zoom.png differ
diff --git a/fldigi_doxygen/images/dcf77.png b/fldigi_doxygen/images/dcf77.png
new file mode 100644
index 00000000..6b40a50a
Binary files /dev/null and b/fldigi_doxygen/images/dcf77.png differ
diff --git a/fldigi_doxygen/images/dialog-rig-control.png b/fldigi_doxygen/images/dialog-rig-control.png
new file mode 100644
index 00000000..f36ff8e3
Binary files /dev/null and b/fldigi_doxygen/images/dialog-rig-control.png differ
diff --git a/fldigi_doxygen/images/digiscope-cw.png b/fldigi_doxygen/images/digiscope-cw.png
new file mode 100644
index 00000000..a5b8a753
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-cw.png differ
diff --git a/fldigi_doxygen/images/digiscope-domexA.png b/fldigi_doxygen/images/digiscope-domexA.png
new file mode 100644
index 00000000..24aca254
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-domexA.png differ
diff --git a/fldigi_doxygen/images/digiscope-domexB.png b/fldigi_doxygen/images/digiscope-domexB.png
new file mode 100644
index 00000000..0f93221b
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-domexB.png differ
diff --git a/fldigi_doxygen/images/digiscope-mfsk.png b/fldigi_doxygen/images/digiscope-mfsk.png
new file mode 100644
index 00000000..fada00d3
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-mfsk.png differ
diff --git a/fldigi_doxygen/images/digiscope-psk-high.png b/fldigi_doxygen/images/digiscope-psk-high.png
new file mode 100644
index 00000000..001f14f0
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-psk-high.png differ
diff --git a/fldigi_doxygen/images/digiscope-psk-history-amplitude.png b/fldigi_doxygen/images/digiscope-psk-history-amplitude.png
new file mode 100644
index 00000000..2ef61c34
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-psk-history-amplitude.png differ
diff --git a/fldigi_doxygen/images/digiscope-psk-history.png b/fldigi_doxygen/images/digiscope-psk-history.png
new file mode 100644
index 00000000..1ec83c0a
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-psk-history.png differ
diff --git a/fldigi_doxygen/images/digiscope-psk-low.png b/fldigi_doxygen/images/digiscope-psk-low.png
new file mode 100644
index 00000000..53d4954d
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-psk-low.png differ
diff --git a/fldigi_doxygen/images/digiscope-psk-nosig.png b/fldigi_doxygen/images/digiscope-psk-nosig.png
new file mode 100644
index 00000000..fd87dbbd
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-psk-nosig.png differ
diff --git a/fldigi_doxygen/images/digiscope-psk.png b/fldigi_doxygen/images/digiscope-psk.png
new file mode 100644
index 00000000..4bda6715
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-psk.png differ
diff --git a/fldigi_doxygen/images/digiscope-rtty-2.png b/fldigi_doxygen/images/digiscope-rtty-2.png
new file mode 100644
index 00000000..f165e7bb
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-rtty-2.png differ
diff --git a/fldigi_doxygen/images/digiscope-rtty.png b/fldigi_doxygen/images/digiscope-rtty.png
new file mode 100644
index 00000000..495ff717
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-rtty.png differ
diff --git a/fldigi_doxygen/images/digiscope-xhair-rtty.png b/fldigi_doxygen/images/digiscope-xhair-rtty.png
new file mode 100644
index 00000000..5f17c05b
Binary files /dev/null and b/fldigi_doxygen/images/digiscope-xhair-rtty.png differ
diff --git a/fldigi_doxygen/images/docked-rig-control.png b/fldigi_doxygen/images/docked-rig-control.png
new file mode 100644
index 00000000..80b29a55
Binary files /dev/null and b/fldigi_doxygen/images/docked-rig-control.png differ
diff --git a/fldigi_doxygen/images/dominoex-1.png b/fldigi_doxygen/images/dominoex-1.png
new file mode 100644
index 00000000..864dfaf5
Binary files /dev/null and b/fldigi_doxygen/images/dominoex-1.png differ
diff --git a/fldigi_doxygen/images/dominoex-1a.png b/fldigi_doxygen/images/dominoex-1a.png
new file mode 100644
index 00000000..a86da3aa
Binary files /dev/null and b/fldigi_doxygen/images/dominoex-1a.png differ
diff --git a/fldigi_doxygen/images/dominoex-2.png b/fldigi_doxygen/images/dominoex-2.png
new file mode 100644
index 00000000..17da4752
Binary files /dev/null and b/fldigi_doxygen/images/dominoex-2.png differ
diff --git a/fldigi_doxygen/images/dominoex-3.png b/fldigi_doxygen/images/dominoex-3.png
new file mode 100644
index 00000000..034472b7
Binary files /dev/null and b/fldigi_doxygen/images/dominoex-3.png differ
diff --git a/fldigi_doxygen/images/event-log-debug.png b/fldigi_doxygen/images/event-log-debug.png
new file mode 100644
index 00000000..91d94ee3
Binary files /dev/null and b/fldigi_doxygen/images/event-log-debug.png differ
diff --git a/fldigi_doxygen/images/event-log-error.png b/fldigi_doxygen/images/event-log-error.png
new file mode 100644
index 00000000..4027be3e
Binary files /dev/null and b/fldigi_doxygen/images/event-log-error.png differ
diff --git a/fldigi_doxygen/images/event-log-info.png b/fldigi_doxygen/images/event-log-info.png
new file mode 100644
index 00000000..b2019d64
Binary files /dev/null and b/fldigi_doxygen/images/event-log-info.png differ
diff --git a/fldigi_doxygen/images/event-log-menu.png b/fldigi_doxygen/images/event-log-menu.png
new file mode 100644
index 00000000..03b89800
Binary files /dev/null and b/fldigi_doxygen/images/event-log-menu.png differ
diff --git a/fldigi_doxygen/images/event-log-quiet.png b/fldigi_doxygen/images/event-log-quiet.png
new file mode 100644
index 00000000..21bc48d3
Binary files /dev/null and b/fldigi_doxygen/images/event-log-quiet.png differ
diff --git a/fldigi_doxygen/images/event-log-verbose.png b/fldigi_doxygen/images/event-log-verbose.png
new file mode 100644
index 00000000..6e586184
Binary files /dev/null and b/fldigi_doxygen/images/event-log-verbose.png differ
diff --git a/fldigi_doxygen/images/event-log-warning.png b/fldigi_doxygen/images/event-log-warning.png
new file mode 100644
index 00000000..a1fa5502
Binary files /dev/null and b/fldigi_doxygen/images/event-log-warning.png differ
diff --git a/fldigi_doxygen/images/event-log.png b/fldigi_doxygen/images/event-log.png
new file mode 100644
index 00000000..afdfbbf1
Binary files /dev/null and b/fldigi_doxygen/images/event-log.png differ
diff --git a/fldigi_doxygen/images/export-setup.png b/fldigi_doxygen/images/export-setup.png
new file mode 100644
index 00000000..b5509544
Binary files /dev/null and b/fldigi_doxygen/images/export-setup.png differ
diff --git a/fldigi_doxygen/images/farnsworth.png b/fldigi_doxygen/images/farnsworth.png
new file mode 100644
index 00000000..1cb8de6c
Binary files /dev/null and b/fldigi_doxygen/images/farnsworth.png differ
diff --git a/fldigi_doxygen/images/feld-hell.png b/fldigi_doxygen/images/feld-hell.png
new file mode 100644
index 00000000..6dc036c4
Binary files /dev/null and b/fldigi_doxygen/images/feld-hell.png differ
diff --git a/fldigi_doxygen/images/fldigi-320-OSXb.png b/fldigi_doxygen/images/fldigi-320-OSXb.png
new file mode 100644
index 00000000..04c24f3c
Binary files /dev/null and b/fldigi_doxygen/images/fldigi-320-OSXb.png differ
diff --git a/fldigi_doxygen/images/fldigi-controls.png b/fldigi_doxygen/images/fldigi-controls.png
new file mode 100644
index 00000000..1d08b687
Binary files /dev/null and b/fldigi_doxygen/images/fldigi-controls.png differ
diff --git a/fldigi_doxygen/images/fldigi-macrobuttons.png b/fldigi_doxygen/images/fldigi-macrobuttons.png
new file mode 100644
index 00000000..f6a554b7
Binary files /dev/null and b/fldigi_doxygen/images/fldigi-macrobuttons.png differ
diff --git a/fldigi_doxygen/images/fldigi-on-Ubuntu.png b/fldigi_doxygen/images/fldigi-on-Ubuntu.png
new file mode 100644
index 00000000..4696e785
Binary files /dev/null and b/fldigi_doxygen/images/fldigi-on-Ubuntu.png differ
diff --git a/fldigi_doxygen/images/fldigi-on-XP.PNG b/fldigi_doxygen/images/fldigi-on-XP.PNG
new file mode 100644
index 00000000..98752d57
Binary files /dev/null and b/fldigi_doxygen/images/fldigi-on-XP.PNG differ
diff --git a/fldigi_doxygen/images/fldigi-on-vista.png b/fldigi_doxygen/images/fldigi-on-vista.png
new file mode 100644
index 00000000..d80e0f53
Binary files /dev/null and b/fldigi_doxygen/images/fldigi-on-vista.png differ
diff --git a/fldigi_doxygen/images/fldigi-psk.png b/fldigi_doxygen/images/fldigi-psk.png
new file mode 100644
index 00000000..d9192645
Binary files /dev/null and b/fldigi_doxygen/images/fldigi-psk.png differ
diff --git a/fldigi_doxygen/images/fldigi-qsodata.png b/fldigi_doxygen/images/fldigi-qsodata.png
new file mode 100644
index 00000000..4494a5c1
Binary files /dev/null and b/fldigi_doxygen/images/fldigi-qsodata.png differ
diff --git a/fldigi_doxygen/images/fldigi-rcvdivider.png b/fldigi_doxygen/images/fldigi-rcvdivider.png
new file mode 100644
index 00000000..0783c94e
Binary files /dev/null and b/fldigi_doxygen/images/fldigi-rcvdivider.png differ
diff --git a/fldigi_doxygen/images/fldigi_Icom_AFSK-1dB.png b/fldigi_doxygen/images/fldigi_Icom_AFSK-1dB.png
new file mode 100644
index 00000000..475d8371
Binary files /dev/null and b/fldigi_doxygen/images/fldigi_Icom_AFSK-1dB.png differ
diff --git a/fldigi_doxygen/images/fldigi_Icom_AFSK-1r5dB.png b/fldigi_doxygen/images/fldigi_Icom_AFSK-1r5dB.png
new file mode 100644
index 00000000..6c306714
Binary files /dev/null and b/fldigi_doxygen/images/fldigi_Icom_AFSK-1r5dB.png differ
diff --git a/fldigi_doxygen/images/fldigi_Icom_AFSK.png b/fldigi_doxygen/images/fldigi_Icom_AFSK.png
new file mode 100644
index 00000000..aa429594
Binary files /dev/null and b/fldigi_doxygen/images/fldigi_Icom_AFSK.png differ
diff --git a/fldigi_doxygen/images/flush_spectrum.png b/fldigi_doxygen/images/flush_spectrum.png
new file mode 100644
index 00000000..d721bf19
Binary files /dev/null and b/fldigi_doxygen/images/flush_spectrum.png differ
diff --git a/fldigi_doxygen/images/folder-palettes.png b/fldigi_doxygen/images/folder-palettes.png
new file mode 100644
index 00000000..a15c7814
Binary files /dev/null and b/fldigi_doxygen/images/folder-palettes.png differ
diff --git a/fldigi_doxygen/images/folder-working.png b/fldigi_doxygen/images/folder-working.png
new file mode 100644
index 00000000..8e6a5c20
Binary files /dev/null and b/fldigi_doxygen/images/folder-working.png differ
diff --git a/fldigi_doxygen/images/freqlist.clearmenu.png b/fldigi_doxygen/images/freqlist.clearmenu.png
new file mode 100644
index 00000000..24c4bd98
Binary files /dev/null and b/fldigi_doxygen/images/freqlist.clearmenu.png differ
diff --git a/fldigi_doxygen/images/init-rig-setup.png b/fldigi_doxygen/images/init-rig-setup.png
new file mode 100644
index 00000000..4bfbcc61
Binary files /dev/null and b/fldigi_doxygen/images/init-rig-setup.png differ
diff --git a/fldigi_doxygen/images/k0og.png b/fldigi_doxygen/images/k0og.png
new file mode 100644
index 00000000..a326cb25
Binary files /dev/null and b/fldigi_doxygen/images/k0og.png differ
diff --git a/fldigi_doxygen/images/limited_modes.png b/fldigi_doxygen/images/limited_modes.png
new file mode 100644
index 00000000..7406f79d
Binary files /dev/null and b/fldigi_doxygen/images/limited_modes.png differ
diff --git a/fldigi_doxygen/images/log-buttons.png b/fldigi_doxygen/images/log-buttons.png
new file mode 100644
index 00000000..3a54034d
Binary files /dev/null and b/fldigi_doxygen/images/log-buttons.png differ
diff --git a/fldigi_doxygen/images/log-contest-min.png b/fldigi_doxygen/images/log-contest-min.png
new file mode 100644
index 00000000..411e0b2b
Binary files /dev/null and b/fldigi_doxygen/images/log-contest-min.png differ
diff --git a/fldigi_doxygen/images/log-contest.png b/fldigi_doxygen/images/log-contest.png
new file mode 100644
index 00000000..9fa0df7f
Binary files /dev/null and b/fldigi_doxygen/images/log-contest.png differ
diff --git a/fldigi_doxygen/images/log-it.png b/fldigi_doxygen/images/log-it.png
new file mode 100644
index 00000000..f746b4d7
Binary files /dev/null and b/fldigi_doxygen/images/log-it.png differ
diff --git a/fldigi_doxygen/images/log-qso-min.png b/fldigi_doxygen/images/log-qso-min.png
new file mode 100644
index 00000000..877789e2
Binary files /dev/null and b/fldigi_doxygen/images/log-qso-min.png differ
diff --git a/fldigi_doxygen/images/log-qso.png b/fldigi_doxygen/images/log-qso.png
new file mode 100644
index 00000000..162bf769
Binary files /dev/null and b/fldigi_doxygen/images/log-qso.png differ
diff --git a/fldigi_doxygen/images/logbook.png b/fldigi_doxygen/images/logbook.png
new file mode 100644
index 00000000..834f4540
Binary files /dev/null and b/fldigi_doxygen/images/logbook.png differ
diff --git a/fldigi_doxygen/images/macro-editor.png b/fldigi_doxygen/images/macro-editor.png
new file mode 100644
index 00000000..71525379
Binary files /dev/null and b/fldigi_doxygen/images/macro-editor.png differ
diff --git a/fldigi_doxygen/images/macrobuttons.png b/fldigi_doxygen/images/macrobuttons.png
new file mode 100644
index 00000000..4d86e4fa
Binary files /dev/null and b/fldigi_doxygen/images/macrobuttons.png differ
diff --git a/fldigi_doxygen/images/main-dialog-browser.png b/fldigi_doxygen/images/main-dialog-browser.png
new file mode 100644
index 00000000..0fa1f816
Binary files /dev/null and b/fldigi_doxygen/images/main-dialog-browser.png differ
diff --git a/fldigi_doxygen/images/main-dialog-newinstall.png b/fldigi_doxygen/images/main-dialog-newinstall.png
new file mode 100644
index 00000000..2e742098
Binary files /dev/null and b/fldigi_doxygen/images/main-dialog-newinstall.png differ
diff --git a/fldigi_doxygen/images/main-dialog.png b/fldigi_doxygen/images/main-dialog.png
new file mode 100644
index 00000000..52f99379
Binary files /dev/null and b/fldigi_doxygen/images/main-dialog.png differ
diff --git a/fldigi_doxygen/images/menu-configure.png b/fldigi_doxygen/images/menu-configure.png
new file mode 100644
index 00000000..aee825e7
Binary files /dev/null and b/fldigi_doxygen/images/menu-configure.png differ
diff --git a/fldigi_doxygen/images/menu-contest.png b/fldigi_doxygen/images/menu-contest.png
new file mode 100644
index 00000000..995e28db
Binary files /dev/null and b/fldigi_doxygen/images/menu-contest.png differ
diff --git a/fldigi_doxygen/images/menu-contestia.png b/fldigi_doxygen/images/menu-contestia.png
new file mode 100644
index 00000000..fd7d7807
Binary files /dev/null and b/fldigi_doxygen/images/menu-contestia.png differ
diff --git a/fldigi_doxygen/images/menu-dominoex.png b/fldigi_doxygen/images/menu-dominoex.png
new file mode 100644
index 00000000..7dc2b670
Binary files /dev/null and b/fldigi_doxygen/images/menu-dominoex.png differ
diff --git a/fldigi_doxygen/images/menu-editfield-popup.png b/fldigi_doxygen/images/menu-editfield-popup.png
new file mode 100644
index 00000000..ffe42309
Binary files /dev/null and b/fldigi_doxygen/images/menu-editfield-popup.png differ
diff --git a/fldigi_doxygen/images/menu-files-audio.png b/fldigi_doxygen/images/menu-files-audio.png
new file mode 100644
index 00000000..6692ae06
Binary files /dev/null and b/fldigi_doxygen/images/menu-files-audio.png differ
diff --git a/fldigi_doxygen/images/menu-files-folders.png b/fldigi_doxygen/images/menu-files-folders.png
new file mode 100644
index 00000000..77ae6173
Binary files /dev/null and b/fldigi_doxygen/images/menu-files-folders.png differ
diff --git a/fldigi_doxygen/images/menu-files-macros.png b/fldigi_doxygen/images/menu-files-macros.png
new file mode 100644
index 00000000..5235bf81
Binary files /dev/null and b/fldigi_doxygen/images/menu-files-macros.png differ
diff --git a/fldigi_doxygen/images/menu-files-text.png b/fldigi_doxygen/images/menu-files-text.png
new file mode 100644
index 00000000..4465b399
Binary files /dev/null and b/fldigi_doxygen/images/menu-files-text.png differ
diff --git a/fldigi_doxygen/images/menu-hell.png b/fldigi_doxygen/images/menu-hell.png
new file mode 100644
index 00000000..828571fd
Binary files /dev/null and b/fldigi_doxygen/images/menu-hell.png differ
diff --git a/fldigi_doxygen/images/menu-help.png b/fldigi_doxygen/images/menu-help.png
new file mode 100644
index 00000000..78fcca58
Binary files /dev/null and b/fldigi_doxygen/images/menu-help.png differ
diff --git a/fldigi_doxygen/images/menu-linux.png b/fldigi_doxygen/images/menu-linux.png
new file mode 100644
index 00000000..90ed6b13
Binary files /dev/null and b/fldigi_doxygen/images/menu-linux.png differ
diff --git a/fldigi_doxygen/images/menu-logbook-adif.png b/fldigi_doxygen/images/menu-logbook-adif.png
new file mode 100644
index 00000000..6c1c7615
Binary files /dev/null and b/fldigi_doxygen/images/menu-logbook-adif.png differ
diff --git a/fldigi_doxygen/images/menu-logbook-reports.png b/fldigi_doxygen/images/menu-logbook-reports.png
new file mode 100644
index 00000000..8ebc3dbc
Binary files /dev/null and b/fldigi_doxygen/images/menu-logbook-reports.png differ
diff --git a/fldigi_doxygen/images/menu-logbook.png b/fldigi_doxygen/images/menu-logbook.png
new file mode 100644
index 00000000..65a7595b
Binary files /dev/null and b/fldigi_doxygen/images/menu-logbook.png differ
diff --git a/fldigi_doxygen/images/menu-mfsk.png b/fldigi_doxygen/images/menu-mfsk.png
new file mode 100644
index 00000000..f5cffe90
Binary files /dev/null and b/fldigi_doxygen/images/menu-mfsk.png differ
diff --git a/fldigi_doxygen/images/menu-mt63.png b/fldigi_doxygen/images/menu-mt63.png
new file mode 100644
index 00000000..18c127ec
Binary files /dev/null and b/fldigi_doxygen/images/menu-mt63.png differ
diff --git a/fldigi_doxygen/images/menu-navtex.png b/fldigi_doxygen/images/menu-navtex.png
new file mode 100644
index 00000000..6b24fd58
Binary files /dev/null and b/fldigi_doxygen/images/menu-navtex.png differ
diff --git a/fldigi_doxygen/images/menu-nbems.png b/fldigi_doxygen/images/menu-nbems.png
new file mode 100644
index 00000000..6e571c7a
Binary files /dev/null and b/fldigi_doxygen/images/menu-nbems.png differ
diff --git a/fldigi_doxygen/images/menu-olivia.png b/fldigi_doxygen/images/menu-olivia.png
new file mode 100644
index 00000000..0947de2d
Binary files /dev/null and b/fldigi_doxygen/images/menu-olivia.png differ
diff --git a/fldigi_doxygen/images/menu-opmode.png b/fldigi_doxygen/images/menu-opmode.png
new file mode 100644
index 00000000..fc68d34d
Binary files /dev/null and b/fldigi_doxygen/images/menu-opmode.png differ
diff --git a/fldigi_doxygen/images/menu-popup-edit-field.png b/fldigi_doxygen/images/menu-popup-edit-field.png
new file mode 100644
index 00000000..2ec4a687
Binary files /dev/null and b/fldigi_doxygen/images/menu-popup-edit-field.png differ
diff --git a/fldigi_doxygen/images/menu-psk-multi-carrier.png b/fldigi_doxygen/images/menu-psk-multi-carrier.png
new file mode 100644
index 00000000..3b50f6b7
Binary files /dev/null and b/fldigi_doxygen/images/menu-psk-multi-carrier.png differ
diff --git a/fldigi_doxygen/images/menu-psk.png b/fldigi_doxygen/images/menu-psk.png
new file mode 100644
index 00000000..19cc30d5
Binary files /dev/null and b/fldigi_doxygen/images/menu-psk.png differ
diff --git a/fldigi_doxygen/images/menu-pskr.png b/fldigi_doxygen/images/menu-pskr.png
new file mode 100644
index 00000000..b165736a
Binary files /dev/null and b/fldigi_doxygen/images/menu-pskr.png differ
diff --git a/fldigi_doxygen/images/menu-qpsk.png b/fldigi_doxygen/images/menu-qpsk.png
new file mode 100644
index 00000000..70cd47f7
Binary files /dev/null and b/fldigi_doxygen/images/menu-qpsk.png differ
diff --git a/fldigi_doxygen/images/menu-rtty.png b/fldigi_doxygen/images/menu-rtty.png
new file mode 100644
index 00000000..2fdee298
Binary files /dev/null and b/fldigi_doxygen/images/menu-rtty.png differ
diff --git a/fldigi_doxygen/images/menu-rx-popup-contest-long.png b/fldigi_doxygen/images/menu-rx-popup-contest-long.png
new file mode 100644
index 00000000..fce3cff2
Binary files /dev/null and b/fldigi_doxygen/images/menu-rx-popup-contest-long.png differ
diff --git a/fldigi_doxygen/images/menu-rx-popup-contest-short.png b/fldigi_doxygen/images/menu-rx-popup-contest-short.png
new file mode 100644
index 00000000..581c1217
Binary files /dev/null and b/fldigi_doxygen/images/menu-rx-popup-contest-short.png differ
diff --git a/fldigi_doxygen/images/menu-rx-popup-long.png b/fldigi_doxygen/images/menu-rx-popup-long.png
new file mode 100644
index 00000000..e72f2bc6
Binary files /dev/null and b/fldigi_doxygen/images/menu-rx-popup-long.png differ
diff --git a/fldigi_doxygen/images/menu-rx-popup-short.png b/fldigi_doxygen/images/menu-rx-popup-short.png
new file mode 100644
index 00000000..c60551d3
Binary files /dev/null and b/fldigi_doxygen/images/menu-rx-popup-short.png differ
diff --git a/fldigi_doxygen/images/menu-rx-popup.png b/fldigi_doxygen/images/menu-rx-popup.png
new file mode 100644
index 00000000..6de748f9
Binary files /dev/null and b/fldigi_doxygen/images/menu-rx-popup.png differ
diff --git a/fldigi_doxygen/images/menu-thor.png b/fldigi_doxygen/images/menu-thor.png
new file mode 100644
index 00000000..ca71e3da
Binary files /dev/null and b/fldigi_doxygen/images/menu-thor.png differ
diff --git a/fldigi_doxygen/images/menu-throb.png b/fldigi_doxygen/images/menu-throb.png
new file mode 100644
index 00000000..3406def5
Binary files /dev/null and b/fldigi_doxygen/images/menu-throb.png differ
diff --git a/fldigi_doxygen/images/menu-tx-popup.png b/fldigi_doxygen/images/menu-tx-popup.png
new file mode 100644
index 00000000..f91bd3f9
Binary files /dev/null and b/fldigi_doxygen/images/menu-tx-popup.png differ
diff --git a/fldigi_doxygen/images/menu-tx-popup2.png b/fldigi_doxygen/images/menu-tx-popup2.png
new file mode 100644
index 00000000..57439027
Binary files /dev/null and b/fldigi_doxygen/images/menu-tx-popup2.png differ
diff --git a/fldigi_doxygen/images/menu-view-controls.png b/fldigi_doxygen/images/menu-view-controls.png
new file mode 100644
index 00000000..2fff2045
Binary files /dev/null and b/fldigi_doxygen/images/menu-view-controls.png differ
diff --git a/fldigi_doxygen/images/menu-view-waterfall.png b/fldigi_doxygen/images/menu-view-waterfall.png
new file mode 100644
index 00000000..1575f206
Binary files /dev/null and b/fldigi_doxygen/images/menu-view-waterfall.png differ
diff --git a/fldigi_doxygen/images/menu-view.png b/fldigi_doxygen/images/menu-view.png
new file mode 100644
index 00000000..a8600e55
Binary files /dev/null and b/fldigi_doxygen/images/menu-view.png differ
diff --git a/fldigi_doxygen/images/menu-wefax.png b/fldigi_doxygen/images/menu-wefax.png
new file mode 100644
index 00000000..c1a8fb6e
Binary files /dev/null and b/fldigi_doxygen/images/menu-wefax.png differ
diff --git a/fldigi_doxygen/images/mfsk-9db-x2.png b/fldigi_doxygen/images/mfsk-9db-x2.png
new file mode 100644
index 00000000..fd0c0e55
Binary files /dev/null and b/fldigi_doxygen/images/mfsk-9db-x2.png differ
diff --git a/fldigi_doxygen/images/mfsk-9db.png b/fldigi_doxygen/images/mfsk-9db.png
new file mode 100644
index 00000000..e77172d3
Binary files /dev/null and b/fldigi_doxygen/images/mfsk-9db.png differ
diff --git a/fldigi_doxygen/images/mfskpix-bee.png b/fldigi_doxygen/images/mfskpix-bee.png
new file mode 100644
index 00000000..985d8bfb
Binary files /dev/null and b/fldigi_doxygen/images/mfskpix-bee.png differ
diff --git a/fldigi_doxygen/images/middle.png b/fldigi_doxygen/images/middle.png
new file mode 100644
index 00000000..91d7a76e
Binary files /dev/null and b/fldigi_doxygen/images/middle.png differ
diff --git a/fldigi_doxygen/images/mt63-1000.png b/fldigi_doxygen/images/mt63-1000.png
new file mode 100644
index 00000000..d1cad586
Binary files /dev/null and b/fldigi_doxygen/images/mt63-1000.png differ
diff --git a/fldigi_doxygen/images/mt63-500.png b/fldigi_doxygen/images/mt63-500.png
new file mode 100644
index 00000000..1fabe3cf
Binary files /dev/null and b/fldigi_doxygen/images/mt63-500.png differ
diff --git a/fldigi_doxygen/images/narrow.png b/fldigi_doxygen/images/narrow.png
new file mode 100644
index 00000000..401c919a
Binary files /dev/null and b/fldigi_doxygen/images/narrow.png differ
diff --git a/fldigi_doxygen/images/osx-command.png b/fldigi_doxygen/images/osx-command.png
new file mode 100644
index 00000000..7791c40e
Binary files /dev/null and b/fldigi_doxygen/images/osx-command.png differ
diff --git a/fldigi_doxygen/images/psk-signal-oscope.png b/fldigi_doxygen/images/psk-signal-oscope.png
new file mode 100644
index 00000000..76331fda
Binary files /dev/null and b/fldigi_doxygen/images/psk-signal-oscope.png differ
diff --git a/fldigi_doxygen/images/psk-signal-waterfall.png b/fldigi_doxygen/images/psk-signal-waterfall.png
new file mode 100644
index 00000000..0d932c65
Binary files /dev/null and b/fldigi_doxygen/images/psk-signal-waterfall.png differ
diff --git a/fldigi_doxygen/images/psk-waterfall.png b/fldigi_doxygen/images/psk-waterfall.png
new file mode 100644
index 00000000..ad8648ec
Binary files /dev/null and b/fldigi_doxygen/images/psk-waterfall.png differ
diff --git a/fldigi_doxygen/images/psk-waterfallx1.png b/fldigi_doxygen/images/psk-waterfallx1.png
new file mode 100644
index 00000000..0e0747a7
Binary files /dev/null and b/fldigi_doxygen/images/psk-waterfallx1.png differ
diff --git a/fldigi_doxygen/images/psk-waterfallx2.png b/fldigi_doxygen/images/psk-waterfallx2.png
new file mode 100644
index 00000000..f8663307
Binary files /dev/null and b/fldigi_doxygen/images/psk-waterfallx2.png differ
diff --git a/fldigi_doxygen/images/psk-waterfallx4.png b/fldigi_doxygen/images/psk-waterfallx4.png
new file mode 100644
index 00000000..3fab2d17
Binary files /dev/null and b/fldigi_doxygen/images/psk-waterfallx4.png differ
diff --git a/fldigi_doxygen/images/qpsk-signal-oscope.png b/fldigi_doxygen/images/qpsk-signal-oscope.png
new file mode 100644
index 00000000..8e684b30
Binary files /dev/null and b/fldigi_doxygen/images/qpsk-signal-oscope.png differ
diff --git a/fldigi_doxygen/images/qpsk-signal-waterfall.png b/fldigi_doxygen/images/qpsk-signal-waterfall.png
new file mode 100644
index 00000000..b92a8ab3
Binary files /dev/null and b/fldigi_doxygen/images/qpsk-signal-waterfall.png differ
diff --git a/fldigi_doxygen/images/red_line_text.png b/fldigi_doxygen/images/red_line_text.png
new file mode 100644
index 00000000..b4d226df
Binary files /dev/null and b/fldigi_doxygen/images/red_line_text.png differ
diff --git a/fldigi_doxygen/images/rig-control.png b/fldigi_doxygen/images/rig-control.png
new file mode 100644
index 00000000..c0e9d069
Binary files /dev/null and b/fldigi_doxygen/images/rig-control.png differ
diff --git a/fldigi_doxygen/images/rtty-mouse-wheel.png b/fldigi_doxygen/images/rtty-mouse-wheel.png
new file mode 100644
index 00000000..10fb6017
Binary files /dev/null and b/fldigi_doxygen/images/rtty-mouse-wheel.png differ
diff --git a/fldigi_doxygen/images/rtty-spectrum.png b/fldigi_doxygen/images/rtty-spectrum.png
new file mode 100644
index 00000000..e25bad11
Binary files /dev/null and b/fldigi_doxygen/images/rtty-spectrum.png differ
diff --git a/fldigi_doxygen/images/rtty-transmit.png b/fldigi_doxygen/images/rtty-transmit.png
new file mode 100644
index 00000000..28fefca0
Binary files /dev/null and b/fldigi_doxygen/images/rtty-transmit.png differ
diff --git a/fldigi_doxygen/images/rtty_overdrive.png b/fldigi_doxygen/images/rtty_overdrive.png
new file mode 100644
index 00000000..10a1af38
Binary files /dev/null and b/fldigi_doxygen/images/rtty_overdrive.png differ
diff --git a/fldigi_doxygen/images/show-popup.png b/fldigi_doxygen/images/show-popup.png
new file mode 100644
index 00000000..c44894fb
Binary files /dev/null and b/fldigi_doxygen/images/show-popup.png differ
diff --git a/fldigi_doxygen/images/show-popup2.png b/fldigi_doxygen/images/show-popup2.png
new file mode 100644
index 00000000..4692a67c
Binary files /dev/null and b/fldigi_doxygen/images/show-popup2.png differ
diff --git a/fldigi_doxygen/images/signal-viewer.png b/fldigi_doxygen/images/signal-viewer.png
new file mode 100644
index 00000000..72973d62
Binary files /dev/null and b/fldigi_doxygen/images/signal-viewer.png differ
diff --git a/fldigi_doxygen/images/status-mode-popup.png b/fldigi_doxygen/images/status-mode-popup.png
new file mode 100644
index 00000000..95f47d84
Binary files /dev/null and b/fldigi_doxygen/images/status-mode-popup.png differ
diff --git a/fldigi_doxygen/images/stereo-plug.png b/fldigi_doxygen/images/stereo-plug.png
new file mode 100644
index 00000000..23312468
Binary files /dev/null and b/fldigi_doxygen/images/stereo-plug.png differ
diff --git a/fldigi_doxygen/images/support_data_dialog.png b/fldigi_doxygen/images/support_data_dialog.png
new file mode 100644
index 00000000..34fa5b05
Binary files /dev/null and b/fldigi_doxygen/images/support_data_dialog.png differ
diff --git a/fldigi_doxygen/images/support_data_menu_item.png b/fldigi_doxygen/images/support_data_menu_item.png
new file mode 100644
index 00000000..0559d91f
Binary files /dev/null and b/fldigi_doxygen/images/support_data_menu_item.png differ
diff --git a/fldigi_doxygen/images/symbols.png b/fldigi_doxygen/images/symbols.png
new file mode 100644
index 00000000..bf2d3f56
Binary files /dev/null and b/fldigi_doxygen/images/symbols.png differ
diff --git a/fldigi_doxygen/images/tty-split-ops.png b/fldigi_doxygen/images/tty-split-ops.png
new file mode 100644
index 00000000..6bf03ad6
Binary files /dev/null and b/fldigi_doxygen/images/tty-split-ops.png differ
diff --git a/fldigi_doxygen/images/under_construction.gif b/fldigi_doxygen/images/under_construction.gif
new file mode 100644
index 00000000..45e2ad34
Binary files /dev/null and b/fldigi_doxygen/images/under_construction.gif differ
diff --git a/fldigi_doxygen/images/vid-large.png b/fldigi_doxygen/images/vid-large.png
new file mode 100644
index 00000000..97f201e6
Binary files /dev/null and b/fldigi_doxygen/images/vid-large.png differ
diff --git a/fldigi_doxygen/images/vid-small.png b/fldigi_doxygen/images/vid-small.png
new file mode 100644
index 00000000..dc96af52
Binary files /dev/null and b/fldigi_doxygen/images/vid-small.png differ
diff --git a/fldigi_doxygen/images/video-preamble.png b/fldigi_doxygen/images/video-preamble.png
new file mode 100644
index 00000000..29d62d4f
Binary files /dev/null and b/fldigi_doxygen/images/video-preamble.png differ
diff --git a/fldigi_doxygen/images/view-menu.png b/fldigi_doxygen/images/view-menu.png
new file mode 100644
index 00000000..a720f188
Binary files /dev/null and b/fldigi_doxygen/images/view-menu.png differ
diff --git a/fldigi_doxygen/images/visible_modes.png b/fldigi_doxygen/images/visible_modes.png
new file mode 100644
index 00000000..fd391b28
Binary files /dev/null and b/fldigi_doxygen/images/visible_modes.png differ
diff --git a/fldigi_doxygen/images/w1aw-rtty-80.png b/fldigi_doxygen/images/w1aw-rtty-80.png
new file mode 100644
index 00000000..1012f1a7
Binary files /dev/null and b/fldigi_doxygen/images/w1aw-rtty-80.png differ
diff --git a/fldigi_doxygen/images/w1aw_rtty.png b/fldigi_doxygen/images/w1aw_rtty.png
new file mode 100644
index 00000000..10a1af38
Binary files /dev/null and b/fldigi_doxygen/images/w1aw_rtty.png differ
diff --git a/fldigi_doxygen/images/w4tv/Icom_FSK.png b/fldigi_doxygen/images/w4tv/Icom_FSK.png
new file mode 100644
index 00000000..a29e6e01
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/Icom_FSK.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_70W_1000Hz.png b/fldigi_doxygen/images/w4tv/fldigi_70W_1000Hz.png
new file mode 100644
index 00000000..8ac9b5d0
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_70W_1000Hz.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_70W_1000Hz_2K.png b/fldigi_doxygen/images/w4tv/fldigi_70W_1000Hz_2K.png
new file mode 100644
index 00000000..3d2ed99a
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_70W_1000Hz_2K.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_70W_1000Hz_5K.png b/fldigi_doxygen/images/w4tv/fldigi_70W_1000Hz_5K.png
new file mode 100644
index 00000000..1647f295
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_70W_1000Hz_5K.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_70W_2stop.png b/fldigi_doxygen/images/w4tv/fldigi_70W_2stop.png
new file mode 100644
index 00000000..cb2d0aa4
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_70W_2stop.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_70W_2stop_wide.png b/fldigi_doxygen/images/w4tv/fldigi_70W_2stop_wide.png
new file mode 100644
index 00000000..b393e878
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_70W_2stop_wide.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_Icom_AFSK-1dB.png b/fldigi_doxygen/images/w4tv/fldigi_Icom_AFSK-1dB.png
new file mode 100644
index 00000000..86d176d9
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_Icom_AFSK-1dB.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_Icom_AFSK-1r5dB.png b/fldigi_doxygen/images/w4tv/fldigi_Icom_AFSK-1r5dB.png
new file mode 100644
index 00000000..75eccd39
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_Icom_AFSK-1r5dB.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_Icom_AFSK.png b/fldigi_doxygen/images/w4tv/fldigi_Icom_AFSK.png
new file mode 100644
index 00000000..0adb3514
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_Icom_AFSK.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_saturated_input_1000Hz.png b/fldigi_doxygen/images/w4tv/fldigi_saturated_input_1000Hz.png
new file mode 100644
index 00000000..ef444366
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_saturated_input_1000Hz.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_saturated_input_1000Hz_2K.png b/fldigi_doxygen/images/w4tv/fldigi_saturated_input_1000Hz_2K.png
new file mode 100644
index 00000000..2c7638be
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_saturated_input_1000Hz_2K.png differ
diff --git a/fldigi_doxygen/images/w4tv/fldigi_saturated_input_1000Hz_5K.png b/fldigi_doxygen/images/w4tv/fldigi_saturated_input_1000Hz_5K.png
new file mode 100644
index 00000000..469932d6
Binary files /dev/null and b/fldigi_doxygen/images/w4tv/fldigi_saturated_input_1000Hz_5K.png differ
diff --git a/fldigi_doxygen/images/w5zit-ts2000-interface.png b/fldigi_doxygen/images/w5zit-ts2000-interface.png
new file mode 100644
index 00000000..2c725e3f
Binary files /dev/null and b/fldigi_doxygen/images/w5zit-ts2000-interface.png differ
diff --git a/fldigi_doxygen/images/wide.png b/fldigi_doxygen/images/wide.png
new file mode 100644
index 00000000..d41e5b33
Binary files /dev/null and b/fldigi_doxygen/images/wide.png differ
diff --git a/fldigi_doxygen/images/wizard-page_1.png b/fldigi_doxygen/images/wizard-page_1.png
new file mode 100644
index 00000000..017f203c
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_1.png differ
diff --git a/fldigi_doxygen/images/wizard-page_2-Operator-Information.png b/fldigi_doxygen/images/wizard-page_2-Operator-Information.png
new file mode 100644
index 00000000..0874aa82
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_2-Operator-Information.png differ
diff --git a/fldigi_doxygen/images/wizard-page_3-AudioDevices-Device.png b/fldigi_doxygen/images/wizard-page_3-AudioDevices-Device.png
new file mode 100644
index 00000000..a3b0cc2b
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_3-AudioDevices-Device.png differ
diff --git a/fldigi_doxygen/images/wizard-page_3-AudioDevices-Right-Channel.png b/fldigi_doxygen/images/wizard-page_3-AudioDevices-Right-Channel.png
new file mode 100644
index 00000000..63292440
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_3-AudioDevices-Right-Channel.png differ
diff --git a/fldigi_doxygen/images/wizard-page_3-AudioDevices-Settings.png b/fldigi_doxygen/images/wizard-page_3-AudioDevices-Settings.png
new file mode 100644
index 00000000..3afea306
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_3-AudioDevices-Settings.png differ
diff --git a/fldigi_doxygen/images/wizard-page_4-txControl-Hamlib.png b/fldigi_doxygen/images/wizard-page_4-txControl-Hamlib.png
new file mode 100644
index 00000000..d03ac8c3
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_4-txControl-Hamlib.png differ
diff --git a/fldigi_doxygen/images/wizard-page_4-txControl-RigCat.png b/fldigi_doxygen/images/wizard-page_4-txControl-RigCat.png
new file mode 100644
index 00000000..1fd51cf6
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_4-txControl-RigCat.png differ
diff --git a/fldigi_doxygen/images/wizard-page_4-txControl-hwd-ptt.png b/fldigi_doxygen/images/wizard-page_4-txControl-hwd-ptt.png
new file mode 100644
index 00000000..3269ec63
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_4-txControl-hwd-ptt.png differ
diff --git a/fldigi_doxygen/images/wizard-page_4-txControl-xmlprc.png b/fldigi_doxygen/images/wizard-page_4-txControl-xmlprc.png
new file mode 100644
index 00000000..716ef04a
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_4-txControl-xmlprc.png differ
diff --git a/fldigi_doxygen/images/wizard-page_5-Tabular-Data.png b/fldigi_doxygen/images/wizard-page_5-Tabular-Data.png
new file mode 100644
index 00000000..c7ecb707
Binary files /dev/null and b/fldigi_doxygen/images/wizard-page_5-Tabular-Data.png differ
diff --git a/fldigi_doxygen/images/wwv.png b/fldigi_doxygen/images/wwv.png
new file mode 100644
index 00000000..6086dc35
Binary files /dev/null and b/fldigi_doxygen/images/wwv.png differ
diff --git a/fldigi_doxygen/images/wwv1-lgneg.png b/fldigi_doxygen/images/wwv1-lgneg.png
new file mode 100644
index 00000000..2fcf4add
Binary files /dev/null and b/fldigi_doxygen/images/wwv1-lgneg.png differ
diff --git a/fldigi_doxygen/images/wwv2-000ppm.png b/fldigi_doxygen/images/wwv2-000ppm.png
new file mode 100644
index 00000000..f7c96cb9
Binary files /dev/null and b/fldigi_doxygen/images/wwv2-000ppm.png differ
diff --git a/fldigi_doxygen/images/wwv2-125ppm.png b/fldigi_doxygen/images/wwv2-125ppm.png
new file mode 100644
index 00000000..d53b5939
Binary files /dev/null and b/fldigi_doxygen/images/wwv2-125ppm.png differ
diff --git a/fldigi_doxygen/images/wwv2-lgpos.png b/fldigi_doxygen/images/wwv2-lgpos.png
new file mode 100644
index 00000000..4829d0f7
Binary files /dev/null and b/fldigi_doxygen/images/wwv2-lgpos.png differ
diff --git a/fldigi_doxygen/images/wwv3.png b/fldigi_doxygen/images/wwv3.png
new file mode 100644
index 00000000..f8eeed43
Binary files /dev/null and b/fldigi_doxygen/images/wwv3.png differ
diff --git a/fldigi_doxygen/images/xbeg-xend.png b/fldigi_doxygen/images/xbeg-xend.png
new file mode 100644
index 00000000..c8ea4aa8
Binary files /dev/null and b/fldigi_doxygen/images/xbeg-xend.png differ
diff --git a/fldigi_doxygen/make_docs.sh b/fldigi_doxygen/make_docs.sh
new file mode 100755
index 00000000..14199ef1
--- /dev/null
+++ b/fldigi_doxygen/make_docs.sh
@@ -0,0 +1,353 @@
+#!/bin/bash
+#
+# A simple script for creating/archiving doxygen documentation for FLDigi
+
+PRG_NAME="FLDigi"
+
+LATEX="0"
+DOXY="0"
+BUILD_PROG_DOCS="0"
+BUILD_USER_DOCS="0"
+
+if [ -z $1 ]; then
+	BUILD_USER_DOCS="1"
+else
+	BUILD_USER_DOCS="0"
+fi
+
+macintosh_file_clean()
+{
+	BASE_PATH=$1
+	if [ -z $BASE_PATH ]; then
+		BASE_PATH="${PWD}"
+	fi
+
+	find $BASE_PATH -name ".DS_Store" -exec rm -rf {} \;
+}
+
+doc_version()
+{
+	if [ ! -f $1 ]; then
+		echo "Doxyfile not found ($1)"
+		echo "PWD=$PWD"
+		VER_NUM="UNKNOWN_VERSION"
+		return
+	fi
+
+	VER_STR=`grep -e "PROJECT_NUMBER*=*" $1`
+
+	if [ -z $VER_STR ]; then
+		VER_NUM="UNKNOWN_VERSION"
+		return
+	fi
+
+	VER_NUM="${VER_STR#*=}"
+	VER_NUM="${VER_NUM#"${VER_NUM%%[![:space:]]*}"}"
+	VER_NUM="${VER_NUM%"${VER_NUM##*[![:space:]]}"}"
+}
+
+help()
+{
+	echo ""
+	echo "Use:"
+	echo "   make_docs.sh <user or help>"
+	echo ""
+	echo "default: user"
+	echo "user: Generate user documentation"
+	echo "help: This message"
+	echo ""
+}
+
+rename_file()
+{
+	if [ -f "$1" ]; then
+		mv "$1" "$2"
+	fi
+}
+
+make_dir()
+{
+	echo "Make Dir: $1"
+
+	if [ -d "$1" ]; then
+		return
+	fi
+
+	mkdir "$1"
+}
+
+function check_dir()
+{
+	if [ -d "$1" ]; then
+		echo "1"
+		return
+	fi
+
+	echo "0"
+}
+
+function check_file()
+{
+	if [ -f "$1" ]; then
+		echo "1"
+		return
+	fi
+
+	echo "0"
+}
+
+check_doxy()
+{
+	RESULTS=$(check_file "$PWD/Doxyfile")
+
+	if [ "$RESULTS" = "1" ]; then
+		doxygen
+	else
+		echo "Doxyfile not found in directory $PWD"
+	fi
+}
+
+check_doxy_exec()
+{
+	PROG_NAME=`which doxygen`
+	EXEC_FILE=`basename $PROG_NAME`
+
+	if [ "$EXEC_FILE" != "doxygen" ]; then
+		echo "Install doxygen to build documentation"
+		DOXY="0"
+	else
+		echo "Found $PROG_NAME"
+		DOXY="1"
+	fi
+}
+
+check_latex_exec()
+{
+	PROG_NAME=`which latex`
+	EXEC_FILE=`basename $PROG_NAME`
+
+	if [ "$EXEC_FILE" != "latex" ]; then
+		echo "Install TeX/LaTeX to build pdf documentation"
+		LATEX="0"
+	else
+		echo "Found $PROG_NAME"
+		LATEX="1"
+	fi
+}
+
+pdf_docs()
+{
+	if [ "$LATEX" = "1" ]; then
+
+		OP_DIR="$1"
+
+		RESULTS=$(check_dir "$OP_DIR")
+
+		if [ "$RESULTS" = "1" ]; then
+			cd $OP_DIR
+			make
+			rename_file "refman.pdf" "$2"
+			TAR=`which tar`
+			if [ -z $TAR ]; then
+	    		echo "***************************************"
+				echo "* Compression program 'tar' not found *"
+	    		echo "***************************************"
+				return
+			fi
+			DIR=`dirname "$2"`
+			FILE=`basename "$2" .pdf`
+			( cd $DIR
+              $TAR -cvzf "${FILE}_pdf.tgz" "${FILE}.pdf" )
+		fi
+	fi
+}
+
+compress_html()
+{
+	if [ -z $1 ]; then
+		return
+	fi
+
+	if [ -z $2 ]; then
+		return
+	fi
+
+	TAR=`which tar`
+	if [ -z $TAR ]; then
+	    echo "***************************************"
+		echo "* Compression program 'tar' not found *"
+	    echo "***************************************"
+		return
+	fi
+
+	echo "PWD=$PWD"
+	cd "../$2"
+
+	RESULTS=$(check_dir "$COMP_DIR")
+
+	SAVE_NAME="../compressed_html/$1_html.tgz"
+
+	if [ "$RESULTS" = "1" ]; then
+		$TAR -cvzf "$SAVE_NAME" "html/"
+	fi
+}
+
+copy_files()
+{
+	SRC="images"
+	DST="user_docs/latex"
+
+	echo "********************************************************"
+	echo "* Copying required images to LaTeX folder"
+	echo "* Source $PWD/$SRC"
+	echo "* Destination $PWD/$DST"
+	echo "********************************************************"
+
+	cp $SRC/event-log-debug.png $DST/event-log-debug.png
+	cp $SRC/event-log-error.png $DST/event-log-error.png
+	cp $SRC/event-log-info.png $DST/event-log-info.png
+	cp $SRC/event-log-quiet.png $DST/event-log-quiet.png
+	cp $SRC/event-log-verbose.png $DST/event-log-verbose.png
+	cp $SRC/event-log-warning.png $DST/event-log-warning.png
+	cp $SRC/digiscope-psk-nosig.png $DST/digiscope-psk-nosig.png
+	cp $SRC/digiscope-psk.png $DST/digiscope-psk.png
+	cp $SRC/digiscope-psk-low.png $DST/digiscope-psk-low.png
+	cp $SRC/digiscope-psk-high.png $DST/digiscope-psk-high.png
+	cp $SRC/digiscope-psk-history.png $DST/digiscope-psk-history.png
+	cp $SRC/digiscope-psk-history-amplitude.png $DST/digiscope-psk-history-amplitude.png
+	cp $SRC/wwv3.png $DST/wwv3.png
+	cp $SRC/wwv1-lgneg.png $DST/wwv1-lgneg.png
+	cp $SRC/wwv2-000ppm.png $DST/wwv2-000ppm.png
+	cp $SRC/wwv2-lgpos.png $DST/wwv2-lgpos.png
+	cp $SRC/wwv2-125ppm.png $DST/wwv2-125ppm.png
+	cp $SRC/dcf77-0.png $DST/dcf77-0.png
+	cp $SRC/dcf77-0zoom.png $DST/dcf77-0zoom.png
+	cp $SRC/dcf77-1000.png $DST/dcf77-1000.png
+	cp $SRC/dcf77-65zoom.png $DST/dcf77-65zoom.png
+	cp $SRC/RWMpre-cal.png $DST/RWMpre-cal.png
+	cp $SRC/RWM+25361ppm.png $DST/RWM+25361ppm.png
+	cp $SRC/RWMpost-cal-x5.png $DST/RWMpost-cal-x5.png
+
+
+	DST="user_docs/html"
+
+	echo "********************************************************"
+	echo "* Copying required images to HTML folder"
+	echo "* Source $PWD/$SRC"
+	echo "* Destination $PWD/$DST"
+	echo "********************************************************"
+
+	cp $SRC/event-log-debug.png $DST/event-log-debug.png
+	cp $SRC/event-log-error.png $DST/event-log-error.png
+	cp $SRC/event-log-info.png $DST/event-log-info.png
+	cp $SRC/event-log-quiet.png $DST/event-log-quiet.png
+	cp $SRC/event-log-verbose.png $DST/event-log-verbose.png
+	cp $SRC/event-log-warning.png $DST/event-log-warning.png
+	cp $SRC/digiscope-psk-nosig.png $DST/digiscope-psk-nosig.png
+	cp $SRC/digiscope-psk.png $DST/digiscope-psk.png
+	cp $SRC/digiscope-psk-low.png $DST/digiscope-psk-low.png
+	cp $SRC/digiscope-psk-high.png $DST/digiscope-psk-high.png
+	cp $SRC/digiscope-psk-history.png $DST/digiscope-psk-history.png
+	cp $SRC/digiscope-psk-history-amplitude.png $DST/digiscope-psk-history-amplitude.png
+	cp $SRC/wwv3.png $DST/wwv3.png
+	cp $SRC/wwv1-lgneg.png $DST/wwv1-lgneg.png
+	cp $SRC/wwv2-000ppm.png $DST/wwv2-000ppm.png
+	cp $SRC/wwv2-lgpos.png $DST/wwv2-lgpos.png
+	cp $SRC/wwv2-125ppm.png $DST/wwv2-125ppm.png
+	cp $SRC/dcf77-0.png $DST/dcf77-0.png
+	cp $SRC/dcf77-0zoom.png $DST/dcf77-0zoom.png
+	cp $SRC/dcf77-1000.png $DST/dcf77-1000.png
+	cp $SRC/dcf77-65zoom.png $DST/dcf77-65zoom.png
+	cp $SRC/RWMpre-cal.png $DST/RWMpre-cal.png
+	cp $SRC/RWM+25361ppm.png $DST/RWM+25361ppm.png
+	cp $SRC/RWMpost-cal-x5.png $DST/RWMpost-cal-x5.png
+
+}
+
+for var in "$@"
+do
+	case "$var" in
+		prog)
+			BUILD_PROG_DOCS="1"
+			;;
+		PROG)
+			BUILD_PROG_DOCS="1"
+			;;
+		USER)
+			BUILD_USER_DOCS="1"
+			;;
+		user)
+			BUILD_USER_DOCS="1"
+			;;
+		*)
+			help
+			exit
+			;;
+	esac
+done
+
+check_doxy_exec
+
+if [ "$DOXY" != "1" ]; then
+	echo "**************************************"
+	echo "* Install Doxygen to build documents *"
+	echo "**************************************"
+	exit
+fi
+
+check_latex_exec
+
+if [ "$LATEX" != "1" ]; then
+	echo "********************************************"
+	echo "* Install TeX/LaTeX to build PDF documents *"
+	echo "********************************************"
+fi
+
+
+SCRIPT_PATH="$PWD/make_docs.sh"
+
+echo "Looking for Script: $SCRIPT_PATH"
+
+if [ -f "$SCRIPT_PATH" ]; then
+
+	HTML="fldigi_${VER_NUM}_user_manual_html"
+
+	make_dir "pdf"
+	make_dir "compressed_html"
+	make_dir "user_docs"
+	make_dir "user_docs/latex"
+	make_dir "user_docs/html"
+	make_dir "prog_docs"
+	make_dir "prog_docs/latex"
+	make_dir "prog_docs/html"
+
+	( cd doxygen; copy_files )
+
+else
+	echo "***********************************************************************"
+	echo "* Change Directory to the ./make_doc.sh location then execute script. *"
+	echo "***********************************************************************"
+	exit
+fi
+
+# User Manual
+if [ $BUILD_USER_DOCS -eq "1" ]; then
+(
+	cd user_src_docs
+	doc_version "${PWD}/Doxyfile"
+	check_doxy
+	( compress_html "${PRG_NAME}_${VER_NUM}_Users_Manual" "user_docs")
+	pdf_docs "../user_docs/latex" "../../pdf/${PRG_NAME}_${VER_NUM}_Users_Manual.pdf"
+)
+fi
+
+# Programmers Code Reference
+if [ $BUILD_PROG_DOCS -eq "1" ]; then
+(
+	cd prog_src_doc
+	doc_version "${PWD}/Doxyfile"
+	check_doxy
+	( compress_html "${PRG_NAME}_${VER_NUM}_Code_Reference" "prog_docs" )
+	pdf_docs "../prog_docs/latex" "../../pdf/${PRG_NAME}_${VER_NUM}_Code_Reference.pdf"
+)
+fi
diff --git a/fldigi_doxygen/prog_src_doc/Doxyfile b/fldigi_doxygen/prog_src_doc/Doxyfile
new file mode 100644
index 00000000..9322c802
--- /dev/null
+++ b/fldigi_doxygen/prog_src_doc/Doxyfile
@@ -0,0 +1,54 @@
+#
+#
+#
+# Copyright (C) 2013 Robert Stiles, KK5VD.
+#
+# Permission to use, copy, modify, and distribute this software and its
+# documentation under the terms of the GNU General Public License is hereby
+# granted. No representations are made about the suitability of this software
+# for any purpose. It is provided "as is" without express or implied warranty.
+# See the GNU General Public License for more details.
+#
+# Documents produced by Doxygen are derivative works derived from the
+# input used in their production; they are not affected by this license.
+
+PROJECT_NAME         = "FLDIGI Programmers Manual"
+PROJECT_NUMBER       = 3.21
+PROJECT_BRIEF        =
+ALLEXTERNALS         = NO
+CASE_SENSE_NAMES     = NO
+DISABLE_INDEX        = NO
+DOXYFILE_ENCODING    = UTF-8
+INPUT_ENCODING       = UTF-8
+ENABLE_PREPROCESSING = NO
+ENABLED_SECTIONS     = logo_on
+EXTRACT_ALL          = NO
+EXTRACT_PRIVATE      = NO
+EXTRA_PACKAGES       = graphicx caption subcaption float
+FILE_PATTERNS        = *.c *.cc *.cxx *.cpp *.c++ *.h *.hh *.hxx *.hpp *.txt
+GENERATE_HTML        = YES
+GENERATE_HTMLHELP    = NO
+GENERATE_LATEX       = YES
+GENERATE_MAN         = NO
+GENERATE_RTF         = NO
+GENERATE_TREEVIEW    = NO
+GENERATE_XML         = NO
+HTML_COLORSTYLE_SAT  = 0
+HTML_FOOTER          =
+HTML_HEADER          =
+IMAGE_PATH           = ../images
+INPUT                = index.txt ../../src
+INCLUDE_PATH         = .
+EXAMPLE_PATH         = .
+OUTPUT_DIRECTORY     = ../prog_docs
+OUTPUT_LANGUAGE      = English
+PDF_HYPERLINKS       = YES
+PERL_PATH            = /usr/bin/perl
+QUIET                = NO
+RECURSIVE            = YES
+SEARCHENGINE         = NO
+STRIP_CODE_COMMENTS  = NO
+TAGFILES             =
+USE_PDFLATEX         = YES
+WARNINGS             = YES
+
diff --git a/fldigi_doxygen/prog_src_doc/index.txt b/fldigi_doxygen/prog_src_doc/index.txt
new file mode 100644
index 00000000..a9bce422
--- /dev/null
+++ b/fldigi_doxygen/prog_src_doc/index.txt
@@ -0,0 +1,87 @@
+// =====================================================================
+//  FLDIGI - Programmers Code Reference Doxygen Main Page Documentation
+//
+//  index.txt
+//
+//  Author(s):
+//		Robert Stiles, KK5VD, Copyright (C) 2013
+//
+// This is free software; you can redistribute it and/or modify
+// it under the terms of the GNU General Public License as published by
+// the Free Software Foundation; either version 3 of the License, or
+// (at your option) any later version.
+//
+// This software is distributed in the hope that it will be useful,
+// but WITHOUT ANY WARRANTY; without even the implied warranty of
+// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+// GNU General Public License for more details.
+//
+// You should have received a copy of the GNU General Public License
+// along with the program; if not, write to the Free Software
+// Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+// =====================================================================
+
+/*!
+
+\mainpage FLDIGI - Programmers Code Reference
+
+\section depLibs Dependency Libraries
+Fast Light Tool Kit Version 1.3.x:
+	http://fltk.org
+
+Libsndfile:
+	http://www.mega-nerd.com/libsndfile/
+
+Libsamplerate:
+	http://www.mega-nerd.com/SRC/
+
+Audio input/output:
+	portaudio: (Mac OSX, and ???)
+		http://www.portaudio.com
+
+	or (depends on OS type/version)
+
+	pulseaudio: (???)
+		http://www.freedesktop.org/wiki/Software/PulseAudio
+
+xmlrpc-c:
+	http://xmlrpc-c.sourceforge.net
+
+Hamlib: (optional)
+	version 1.2.12S: (needed for static linking of driver modules)
+
+	version 1.2.15.3 (latest): (does not support static linking of driver modules)
+		http://sourceforge.net/apps/mediawiki/hamlib/index.php?title=Main_Page
+
+png:
+	http://www.libpng.org
+
+pkg-config:
+	http://www.freedesktop.org/wiki/Software/pkg-config
+
+
+Possible other required libs/tools, depends on your OS vendor and development tools.
+
+libtool:
+	http://www.gnu.org/software/libtool/
+
+jpeg:
+	http://www.ijg.org
+
+zlib;
+	http://www.zlib.net
+
+gettext:
+	http://www.gnu.org/software/gettext/
+
+automake:
+	http://www.gnu.org/software/automake/
+
+autoconf:
+	http://www.gnu.org/software/autoconf/
+
+m4:
+	http://www.gnu.org/software/m4/
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/CW.txt b/fldigi_doxygen/user_src_docs/CW.txt
new file mode 100644
index 00000000..c244819b
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/CW.txt
@@ -0,0 +1,129 @@
+/**
+\page cw_page CW
+
+\tableofcontents
+
+\section cw_freq Carrier Frequency
+
+Fldigi generates CW by inserting a keyed tone at the current
+waterfall audio frequency.  The CW carrier frequency is the USB
+carrier + the audio frequency, or the LSB carrier -
+the audio frequency.  If fldigi is tracking and receiving a CW
+signal on the waterfall your transmitted signal will be exactly on the
+frequency of the other operator.  You probably cannot use your
+transceivers CW filter unless that filter can be used with the SSB mode.<br>
+<br>
+
+\section qsk_tab_key QSK and the TAB KEY
+
+If you are operating QSK with a separate transmitter / receiver you can
+very quickly stop your transmit signal with the TAB key.  In
+the CW mode only the TAB key causes the program to skip over the remaining
+text in the transmit text buffer.  The text that is skipped will
+be color coded blue.  The program remains in the transmit mode
+(PTT enabled), but since the buffer is now empty no A2 CW signal is
+generated.  Code transmission will then restart with the very
+next keyboard closure of a valid CW character.
+<br>
+
+\section pause_transmit Pausing transmit
+
+The Pause/Break momentarily key stops sending text.  Pressing it again
+resumes transmission.
+<br>
+
+\section abort_transmit Aborting transmit
+
+The Escape key is used to immediately stop text transmission.  The Tx buffer
+is cleared.
+<br>
+
+\section wpm_adjustements WPM adjustment
+
+In CW mode the status bar is changed to include a transmit WPM adjuster.  Use
+the arrow buttons or the mouse. Mouse wheel up/down changes transmit WPM
+by +/- 1.  Hold the shift and mouse mouse wheel changes transmit WPM
+by +/- 10.  The "*" button immediately to the right of the WPM adjuster is
+used to toggle between the current and the default transmit WPM.
+<br>
+
+The transmit WPM can also be adjusted with three hot keys:
+<br>
+
+<ul>
+<li>Numeric keypad "+" increases the transmit WPM by 1</li>
+<li>Numeric keypad "-" decreases the transmit WPM by 1</li>
+<li>Numeric keypad "*" toggles between the selected transmit WPM and the
+default transmit WPM</li>
+</ul>
+
+The "Default" control on the CW tab sets that default value.  If during a
+QSO you needed to slow down to give the other op a better chance to
+copy what you are sending, just hit the "*" on the numeric keypad and
+the CW code will immediately switch to sending CW at the set default
+value (18 wpm in this example).  Press the "*" again to return to
+back to the CW speed that you were previously using.
+<br>
+
+Each time the transmit WPM is changed the receive decoder WPM tracking
+is reset to the new transmit WPM.  This allows you to quickly
+force the decoder to a new WPM range.
+<br>
+
+\image html cw_status_1.png "The Rx and Tx WPM are shown in the status bar."
+\image latex cw_status_1.png "The Rx and Tx WPM are shown in the status bar." width=2.2in
+
+<br>
+
+\image html cw_status_2.png "* indicates that default WPM is selected"
+\image latex cw_status_2.png "* indicates that default WPM is selected" width=3.0in
+
+\section sec_farnsworth Farnsworth keying
+
+You might want to use farnsworth keying to provide a character rate that is
+faster than the word per minute rate.<br>
+
+\image html farnsworth.png "Farnworth Timing"
+\image latex farnsworth.png "Farnworth Timing" width=5.0in
+<br>
+
+Set the F-WPM slider to tthe character rate and enable the Use
+Farnsworth timing check box.  When the TX WPM is set to a speed
+below the Farnsworth value then the character rate will be at the
+Farnsworth setting and the word rate will be at the TX WPM rate.
+You can also set the TX WPM and F-WPM from within a \ref macro_page.
+<br>
+
+\section cw_config CW configuration
+
+The \ref cw_configuration_page is easily reached from the Config menu or
+by right clicking on  the left  most entry in the status bar (CW).
+<br>
+
+\section sub_prosigns Prosigns
+
+The prosigns are configurable \(see \ref cw_configuration_page \).  The
+defaults are:
+<br>
+
+PROSIGN  | KEYBOARD  | DISPLAYED AS
+:------: | :-------: | :--------:
+BT       | =         | \<BT\>
+AA	     | ~         | \<AA\>
+AR       | >         | \<AR\>
+AS       | <         | \<AS\>
+HM       | {         | \<HM\>
+INT      | &         | \<INT\>
+SK       | %         | \<SK\>
+KN       | +         | \<KN\>
+VE       | }         | \<VE\>
+
+
+
+<br>
+\ref cw_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/CWkeying.txt b/fldigi_doxygen/user_src_docs/CWkeying.txt
new file mode 100644
index 00000000..f7afdc5c
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/CWkeying.txt
@@ -0,0 +1,70 @@
+/**
+\page cw_keying_page CW Keying
+
+\tableofcontents
+
+\image html config-cw-qsk.png "Timing and QSK"
+\image latex config-cw-qsk.png "Timing and QSK" width=5.0in
+<br>
+
+Click on the Configure menu item to open the <i>fldigi</i> configuration
+dialog.  Click on the Modems tab and then on the  QSK tab.
+
+<ol>
+ <li>Set the Pre Timing and Post Timing to zero.</li>
+ <li>Activate the QSK feature by clicking "QSK on right channel".</li>
+</ol>
+
+Click the CW tab and adjust the CW settings to your preference.  Use the Test
+char and the Send continuous controls to ease the adjustment process.
+<br>
+
+FLdigi is now ready to generate a 1600 hertz CW tone on the right channel of
+the stereo audio out of your sound card.
+<br>
+
+The left channel will be the normal raised cosine shaped CW wave form
+that you may use for your side tone.
+<br>
+
+The following circuit may be used to take the FLdigi QSK OUT signal from the
+right channel of your SOUND CARD  to key  your transmitter or a QSK circuit.
+<br>
+
+\image html CWkeyingCircuit.png "CW Keying Circuit"
+\image latex CWkeyingCircuit.png "CW Keying Circuit" width=6.5in
+<br>
+
+
+<b>NOTE:</b>
+L1 - Radio Shack has two items that may be used for this isolation transformer.
+<br>
+
+<ul>
+  <li> Catalog # 270-054</li>
+  <li> Catalog # 273-1374</li>
+</ul>
+
+Attach an audio cable from the Rt. Channel out of the your computer's
+SOUND CARD to the input of this QSK INTERFACE CIRCUIT (input of L1).
+
+Attach another cable from the output of this circuit to your Rig's Keying
+Jack.mall>
+
+Every CW tone that is generated by FLdigi is rectified by this
+FULL WAVE VOLTAGE DOUBLER circuit.  The resultant voltage turns the Q1
+transistor on and "grounds" the collector,  which takes the RIG'S CW
+KEYING JACK to ground and "keys" the transmitter.
+
+You can adjust the start and stop timing of the QSK circuit relative to the
+CW waveform with the "pre" and "post" settings.
+
+
+<br>
+\ref cw_keying_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/ConfigID.txt b/fldigi_doxygen/user_src_docs/ConfigID.txt
new file mode 100644
index 00000000..a97d1f48
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigID.txt
@@ -0,0 +1,126 @@
+/**
+\page id_configuration_page  ID Configuration
+
+\tableofcontents
+
+\image html config-id-rsid.png "RSID Config Panel"
+\image latex config-id-rsid.png "RSID Config Panel" width=5.0in
+
+Fldigi offers several ways to identify the operator or mode that is being
+used. This is particularly useful when using a hard to recognize
+mode such as \ref thor_page "Thor", \ref olivia_page "Olivia"
+or \ref mt63_page "MT63".
+<br>
+
+\section subsec_reed_solomon_id Reed Solomon Identifier
+
+<b>RSID</b>, <b>R</b>eed <b>S</b>olomon <b>ID</b>entifier
+is a special transmission designed by Patrick Lindecker, F6CTE, for the
+modem program MultiPsk. It has been adapted to other modem
+programs. Fldigi's implementation is compatible with the MultiPsk
+RSID, but provides a slight variation. You can transmit RSID at
+both the beginning and end of a transmission. The detection of
+RSID normally only occurs in the near vicinity of the current waterfall
+tracking point. This cuts down on extraneous RSID detections when the
+band is crowded and several RSID signals might be present. If you want
+fldigi to search the entire waterfall for RSID signals you can do so by
+enabling the "Detector searches entire passband". You start the
+search for a signal based on RSID by using the main panel switch.
+The RSID detector is a separate decoder that operates in parallel with all
+other modem decoders. If you select the "Mark previous frequency and
+mode" a restore link will be inserted into the RX text upon detecting
+an RSID signal. Clicking on this link restores the previous
+frequency and mode of operation. You elect to disable the RSID
+upon first detection. You also have the option of just receiving
+notification when an RSID signal is detected. The notification
+occurs with a pop-up message box.
+<br>
+
+You can select which modes will include the transmitted RS identifier,
+and which modes will react to a received and decoded RS identifier.
+<br>
+
+The mode to identifier relationships are selected by pressing the associated
+"modes" button.
+
+\image html config-id-rx-modes.png "Receive Modes"
+\image latex config-id-rx-modes.png "Receive Modes" width=2.5in
+<br>
+
+\image html config-id-xmt-modes.png "Transmit Modes"
+\image latex config-id-xmt-modes.png "Transmit Modes" width=2.5in
+
+\section subsec_video_text Video Text
+<br>
+
+Transmitted video text will appear as a sequence of characters on the
+waterfall.The text can be a brief mode identifier or some user specified
+text. You can use a small font that always appears as a 2
+character wide sequence or a larger font that can be 1 to 4 characters
+wide. You should be aware that the video signal is a constant
+energy signal and the content will be spread across multiple
+characters. The highest s/n at the receiving end will be for 1
+character wide video. Small font at 2 character width is next in
+s/n performance followed by 2 character large font etc. You can
+select which modes will include the video text preamble. You can
+limit the horizontal (frequency width) of the video signal in one of
+several inclusive ways.
+<br>
+
+<ul>
+<li>Number of characters per row of text</li>
+<li>Constrain to be less than or equal to 500 Hz</li>
+<li>Constrain to be within the bandwidth limits of the mode in use</li>
+</ul>
+
+Fldigi uses abbreviated acronyms for the mode and it's characteristics
+when you are transmitting the mode ID using a video text. Here
+are two examples, one in small and the other in large font.<br>
+
+\image html vid-small.png "Small Font"
+\image latex vid-small.png "Small Font" width=2.5in
+<br>
+
+\image html vid-large.png "Large Font"
+\image latex vid-large.png "Large Font" width=2.0in
+<br>
+
+Notice that Olivia 16-500 is abbreviated to OL-16/500 and that the
+number of characters is limited to 8 per row. You might want to
+use the large characters by default if you routinely have QSO's with
+operators using older digital mode programs or one whose waterfall
+visual is not on a par with fldigi's.
+<br>
+
+\image html config-id-video.png "Video ID Config Panel"
+\image latex config-id-video.png "Video ID Config Panel" width=5.0in
+<br>
+
+\image html config-id-video-modes.png "Video ID Modes"
+\image latex config-id-video-modes.png "Video ID Modes" width=1.8in
+
+\section subsec_cw_postamble CW Postamble
+<br>
+
+You can transmit your callsign in CW as a postamble to all modes except of
+CW (a bit redundant to do that). You can select which modes will
+include the CW postamble.
+<br>
+
+<center>
+\image html config-id-cw.png "CW Postamble ID Config Panel"
+\image latex config-id-cw.png "CW Postamble ID Config Panel" width=5.0in
+<br>
+
+\image html config-id-cw-modes.png "CW ID Modes"
+\image latex config-id-cw-modes.png "CW ID Modes" width=2.4in
+</center>
+
+<br>
+
+\ref id_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/ConfigMisc.txt b/fldigi_doxygen/user_src_docs/ConfigMisc.txt
new file mode 100644
index 00000000..a45c3409
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigMisc.txt
@@ -0,0 +1,202 @@
+/**
+\page miscellaneous_configuration_page  Miscellaneous Configuration
+\tableofcontents
+<br>
+
+\section subsec_sweet_spot Sweet spot
+<br>
+
+\image html config-misc-sweet.png "Misc Sweet Spot Config"
+\image latex config-misc-sweet.png "Misc Sweet Spot Config" width=5.0in
+<br>
+
+The sweet spot is the audio frequency at which your transceiver
+provides the best filtering for a particular signal type. You can
+specify the value of the sweet spot for CW, RTTY and all others.
+You can also elect to have the audio cursor placed at the sweet
+spot when changing modes. The sweet spot is used for the
+\ref operating_controls_page "QSY function".
+
+The K3 A1A lower sideband can be selected for any transceiver that only
+provides LSB in the CW mode.
+<br>
+
+\section subsec_callsig_spotting Callsign spotting
+<br>
+\image html config-misc-spotting.png "Callsign spotting"
+\image latex config-misc-spotting.png "Callsign spotting" width=5.0in
+<br>
+
+Fldigi allows you to automatically participate in a spotting network
+maintained by Philip Gladstone. You can see what the web based reporter
+looks like by visiting this web site: http://pskreporter.info/pskmap?W1HKJ
+or by simply selecting the menu item "Help / Reception reports...".
+<br>
+
+Fldigi will continuously scan for spotted callsigns in the decoded text and
+send reports in the background if you check the "Automat..." option.
+<br>
+
+Reports will also (or only) be sent when you log the QSO into the logbook.
+<br>
+
+If you have rig control enabled the reported rig frequency will also be
+sent to the spotting network. Do not change the Host and Port
+numbers unless these are changed by Philip.
+<br>
+
+You need to press the Initialize to begin reporting spot information.
+You will receive a warning message if you did not enter your antenna
+information on the Operator tab.
+<br>
+
+If your CPU performance is marginal you can disable spotting when no
+signal browser is visible.
+<br>
+
+\section subsec_cpu_performance CPU performance
+<br>
+
+\image html config-misc-cpu.png "Misc CPU"
+\image latex config-misc-cpu.png "Misc CPU" width=5.0in
+<br>
+
+When fldigi is executed for the first time it does some tests to determine
+the performance factor for your central processor unit. If it
+determines that the cpu is below a critical speed it tries to
+compensate by modifying some of its timing and algorithms. If you
+are using a "slow" cpu the "Slow cpu" check box will be enabled.
+You can also manually check this box if you find that fldigi is
+not performing well on some of the more esoteric modes such as PSK250,
+MFSK32, etc.
+<br>
+
+
+\section subsec_text_io Text i/o
+<br>
+
+\image html config-misc-textio.png "Misc Text I/O"
+\image latex config-misc-textio.png "Misc Text I/O" width=5.0in
+<br>
+
+Fldigi can perform automatic capture of the Rx text stream. The simplest
+is to simply capture all incoming text to a file. Select this
+from the lower of the two frames. The Rx file is named
+"textout.txt" and is written to the directory as shown above. The
+file can be used to review an execution session, or it can be accessed
+by an external program. For example it could be parsed to provide
+a text to speech conversion.
+<br>
+
+\section subsec_nbems_flxxx_interface NBEMS (flmsg / flwrap) interface
+<br>
+
+\image html config-misc-nbems.png "Config Misc NBEMS"
+\image latex config-misc-nbems.png "Config Misc NBEMS" width=5.0in
+<br>
+
+The NBEMS suite of programs, fldigi, flarq, flwrap and flmsg provide the
+emergency operator with a set of tools to assist in the transfer of data files
+over HF and VHF radio.Additional information on flarq is available here:
+<br>
+
+<ul>
+  <li><a href="http://www.w1hkj.com/FlarqHelpFiles/flarq.html">flarq help system</a>.</li>
+  <li><a href="http://www.w1hkj.com/Flwrap/index.html">wrap help system</a>.</li>
+  <li><a href="http://www.w1hkj.com/flmsg-help/index.html">flmsg help system</a></li>
+</ul>
+
+The reception of a flwrap and flmsg files can be automated by selecting
+the "Enable detection &amp; extraction" option. The wrap program
+can then be used to test for validity and data extraction at some later
+time. fldigi can recognize flmsg data files and automatically
+open the flmsg program with the newly received data stream. It
+can also transfer the data stream to flmsg and instruct flmsg to save
+the data file, unwrap and decode it, display the data in a fully
+formatted html page and then exit. Pressing "Locate flmsg"
+performs differently on the different OS that are supported.
+<br>
+
+<ul>
+<li>Linux - a file finder is opened to the /usr/local/bin/
+folder. Select the flmsg executable and the entry box is
+correctly populated</li>
+
+<li>Windows - a file finder is opened to the "C:\Program Files\"
+folder. Drill down to the most current flmsg folder and then
+select the flmsg.exe file. The entry box will be correctly
+populated.</li>
+
+<li>OS X - a file browser is opened to the "Applications"
+folder. Locate the flmsg icon, and right click on it.
+Select "Show Package Contents". Double click "Contents".
+Double click on "MacOS". You will be viewing an icon labeled
+"flmsg". Drag and drop the icon on to the "flmsg:" entry box and
+the the value will be correctly entered.</li>
+</ul>
+
+\section subsec_dtmf_decoding DTMF decoding
+<br>
+
+\image html config-misc-dtmf.png "Misc DTMF Decoding"
+\image latex config-misc-dtmf.png "Misc DTMF Decoding" width=5.0in
+<br>
+
+Fldigi can encode and decode DTMF tone sequences. Enable this check box
+to display the decoded tone sequence in the Rx panel. DTMF encoding is
+accomplished by a \ref macros_sub_page "MACRO" tag.<br>
+<br>
+
+\section subsec_wx_rss_xml WX rss-xml queries
+<br>
+
+\image html config-WX.png "Misc WX"
+\image latex config-WX.png "Misc WX" width=5.0in
+<br>
+
+Fldigi provides an automated query of a specified RSS-XML feed to obtain and
+format weather data. The report is added to the transmit text stream
+using the appropriate \ref macros_sub_page "MACRO" tag. The report
+for the above configuration is:
+<br>
+
+\verbatim
+Huntsville, Madison County Executive Airport, AL, United States (KMDQ) 34-51-41N 086-33-26W
+Cond: overcast
+Wind: 210 at 12 mph 19 kph
+Temp: 62 F 17 C
+Baro: 30.04 in Hg 1017 mbar
+\endverbatim
+
+The full report option creates this report:
+
+\verbatim
+Huntsville, Madison County Executive Airport, AL, United States (KMDQ) 34-51-41N 086-33-26W
+Feb 29, 2012 - 07:15 AM EST / 2012.02.29 1215 UTC
+Wind: from the SSW (210 degrees) at 12 MPH (10 KT) gusting to 17 MPH (15 KT):0
+Visibility: 10 mile(s):0
+Sky conditions: overcast
+Temperature: 62 F (17 C)
+Dew Point: 60 F (16 C)
+Relative Humidity: 93%
+Pressure (altimeter): 30.04 in. Hg (1017 hPa)
+\endverbatim
+<br>
+
+The "Search on web" button will open your browser toGreg Thompson's
+<a href="http://weather.rap.ucar.edu/surface/stations.txt">global listing</a>
+of METAR station.
+<br>
+
+RSS feeds for world wide airports can be searched here
+<a href="http://www.airrouting.com/content/AirportLocatorForm.aspx">
+http://www.airrouting.com/content/AirportLocatorForm.aspx</a>.
+<br>
+
+\ref miscellaneous_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
+
diff --git a/fldigi_doxygen/user_src_docs/ConfigOperator.txt b/fldigi_doxygen/user_src_docs/ConfigOperator.txt
new file mode 100644
index 00000000..b1dd16f2
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigOperator.txt
@@ -0,0 +1,29 @@
+/**
+\page operator_configuration_page  Configure Operator
+\tableofcontents
+<br>
+
+\image html config-operator.png "Operator"
+\image latex config-operator.png "Operator" width=5.0in
+
+Enter your personal information on the <b>Operator</b> tab of the
+configuration dialog. This information is used by some of
+the macro expanders.
+<br>
+
+The antenna information is required if you elect to report to the spotting web
+site, <a href="http://pskreporter.info">PSK reporter</a>.
+<br>
+
+Your locator data is also used for automatically computing Azimuth to a
+remote locator when that is available from an on-line database Call query.
+<br>
+
+<br>
+\ref operator_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/ConfigUI-WF-controls.txt b/fldigi_doxygen/user_src_docs/ConfigUI-WF-controls.txt
new file mode 100644
index 00000000..22a8e254
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigUI-WF-controls.txt
@@ -0,0 +1,32 @@
+/**
+\page  ui_configuration_waterfall_controls_page User Interface Configuration - WF Controls
+
+\tableofcontents
+
+\image html config-ui-tabs.png "UI Tabs"
+\image latex config-ui-tabs.png "UI Tabs" width=5.0in
+<br>
+
+\image html config-ui-wf-controls.png "UI Configure - WF Controls"
+\image latex config-ui-wf-controls.png "UI Configure - WF Controls" width=5.0in
+<br>
+
+You can configure the appearance of fldigi in a variety of ways,
+including the suppression of unused waterfall controls.
+<br>
+
+\image html config-ui-wf-controls-2.png "UI Configure - WF Controls 2"
+\image latex config-ui-wf-controls-2.png "UI Configure - WF Controls 2" width=3.0in
+<br>
+
+Before adjusting these settings it is recommended that you enable this
+menu item. You can then see the effect of enabling and disabling the
+various selection boxes.
+
+<br>
+\ref ui_configuration_waterfall_controls_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/ConfigUI-browser.txt b/fldigi_doxygen/user_src_docs/ConfigUI-browser.txt
new file mode 100644
index 00000000..2126ca91
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigUI-browser.txt
@@ -0,0 +1,86 @@
+/**
+\page ui_configuration_broswer_page  User Interface Configuration - Browser
+
+\tableofcontents
+
+\image html config-ui-browser.png "UI Browser Configuration"
+\image latex config-ui-browser.png "UI Browser Configuration" width=5.0in
+<br>
+
+\image html browser-panel.png "Browser Panel"
+\image latex browser-panel.png "Browser Panel" width=5.0in
+<br>
+
+Fldigi can display multiple decoded signals in both PSK and RTTY modes.
+The multi-channel display is either a separate dialog or an embedded resizable
+panel.
+
+1) select the number of 100 Hz channels you want visible<br>
+2) select the start frequency for the browser (your transceiver may
+not rx signals below this value)<br>
+3) select the inactivity timeout for the browser. After this
+number of seconds the channel will be cleared and prepared for the next
+detection cycle.<br>
+4) select what kind of label annotation you want on each line<br>
+5) select the font and font size to be used in the browser<br>
+6) You can enter any text you want to search for in the
+<i>Seek Regular Expression</i> widget. This text can be a simple text
+snippet such as "CQ" or any regular expression. When the regex is
+satisfied in a channel the text color for that channel is changed to
+red. With a regex you can specify a more generic pattern, which means
+that you can match more things and your search is somewhat noise tolerant.
+Here is an example for a CQ from a US station (should match most
+callsigns):
+<br>
+
+\verbatim
+>cq.+[aknw][a-z]?[0-9][a-pr-z][a-z]{1,2}
+\endverbatim
+<br>
+
+This says "cq followed by at least one character, followed by one A,
+K, N, or W, followed by an optional letter, followed by a digit,
+followed by a letter that is not q, followed by one or two letters".
+The search is case-insensitive.
+<br>
+
+All plain text is a valid regular expression, unless you really had
+been looking for these metacharacters:
+<br>
+
+\verbatim
+>.[{()\*+?|^$</span></big><br>
+\endverbatim
+<br>
+
+These will have to be escaped with a backslash.<br>
+
+7) select whether you want a marquee type of continuous scrolling, or simply
+ clear the line when it is filled.<br>
+8) select whether you want the lowest frequency at the bottom (checked) or
+ the top of browser panel<br>
+9) select whether you want the audio stream history buffer to be played back
+ when you select an active channel. The first-in first-out audio
+ history represents the previous 2 minutes of received audio.<br>
+10) Both the background and slider highlight colors can be selected for the
+signal browser detection level control. The default colors are shown
+in these images.<br>
+11) You can set the 2 levels of text hi-lighting that is used in the browser
+lines<br>
+
+<ul>
+<li>HiLite 1 - Text color when the regular expression evaluator finds the
+target text</li>
+<li>HiLite 2 - Text color when your call sign appears in that receive
+channel</li>
+</ul>
+12) You can set the background colors for the odd/even lines and the line selection color<br>
+
+<br>
+\ref ui_configuration_broswer_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/ConfigUI-contest.txt b/fldigi_doxygen/user_src_docs/ConfigUI-contest.txt
new file mode 100644
index 00000000..28bc3e76
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigUI-contest.txt
@@ -0,0 +1,44 @@
+/**
+\page  ui_configuration_contest_page  User Interface Configuration - Contest
+
+\tableofcontents
+
+
+
+\image html config-ui-tabs.png "UI Tabs"
+\image latex config-ui-tabs.png "UI Tabs" width=4.0in
+<br>
+
+
+Fldigi supports a generic but robust set of contest functions. In
+addition to serial-in and serial-out you can capture and transmit three
+exchange sequences unique to a specific contest. Enter the
+exchange you want to send for each of the three. You can force
+the RST in/out to always be 599. That seems to be a norm for many
+contests. When operating in a CW contest you can have fldigi send
+cut numbers, T for 0, N for nine.
+<br>
+
+\image html config-ui-contest.png "UI Contest"
+\image latex config-ui-contest.png "UI Contest" width=5.0in
+<br>
+
+The serial number can be set to use leading zeros.  You can specify the
+starting number for the sequence and how many digits are sent, ie:
+0024. Pressing Reset will set the starting number to the QSO logging
+serial out field. See \ref contest_how_to_page "Contest How To" for more
+info.
+<br>
+
+You can check for duplicates by any combination of the specified named
+fields. You can also specify that the duplicate had to occur with a
+given time interval. Some VHF contests allow a duplicate CALL after
+a given time interval.
+<br>
+
+\ref ui_configuration_contest_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/ConfigUI-general.txt b/fldigi_doxygen/user_src_docs/ConfigUI-general.txt
new file mode 100644
index 00000000..0846dd18
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigUI-general.txt
@@ -0,0 +1,93 @@
+/**
+\page  ui_configuration_general_page  User Interface Configuration - General
+
+\tableofcontents
+
+\image html config-ui-tabs.png "UI Tabs"
+\image latex config-ui-tabs.png "UI Tabs" width=5.0in
+<br>
+
+\image html config-ui-general.png "General UI Config Panel"
+\image latex config-ui-general.png "General UI Config Panel" width=5.0in
+<br>
+
+Fldigi offers tips on the use of nearly every aspect of its operation.
+These are particularly useful when you first use the program, but
+after you are familiar with it's operation they tend to get in the way.
+You can turn them off by de-selecting "Show tooltips"
+<br>
+
+Some users prefer to not have icons on the menu system. You can turn
+them off also.
+<br>
+
+Fldigi offers three different look and feel based on the parent Fast Light
+Toolkit graphics interface; "base", "gtk+" and "plastic". These
+can be combined with command line specifiers for the default background
+and foreground colors to create a user unique look to fldigi. You
+will probably discover that the default colors and the gtk+ UI scheme
+are to be preferred.
+<br>
+
+Fldigi has internationalization files for French, Italian and
+Spanish. These control the contents of various menu items and
+labels. Linux users should build and install fldigi from source
+to gain access to these. Windows users should select the language
+of choice from the list, press the "Save" button and then close and
+restart fldigi. The "UI language" selector is only present on the
+Windows version of fldigi. The percentage indicates the
+completeness of the translation.
+<br>
+
+CW, RTTY (baudot), THROB,
+and CONTESTIA are modes that only transmit in upper case
+characters. They also have a very limited set of non-alpha
+characters. A screen full of UPPERCASE characters can be
+stressful. Select this option to print all of this text in lower
+case
+<br>
+
+Select the configuration items to allow prompting when exiting the
+program. Note that the prompts are only active if the menu item
+File/Exit is used.
+<br>
+
+You can elect to have the program check for updates every time it is
+started. You can also manually check for updates from the "Help /
+Check for updates" menu item.
+<br>
+
+\section visible_modes Visible Modes
+
+\image html visible_modes.png "Visible Modes"
+\image latex visible_modes.png "Visible Modes" width=2.0in
+<br>
+
+You may not want to use all possible modes when operating fldigi.
+Press the "Visible modes" button and open the mode selector dialog.
+<br>
+
+The use of this dialog should be obvious after a few clicks here and there.
+<br>
+
+\section limit_modes Limit Modes
+
+\image html limited_modes.png "Limit Modes"
+\image latex limited_modes.png "Limit Modes" width=1.5in
+<br>
+
+By deselecting all but CW, PSK31, PSK63 and RTTY
+the Op_Mode menu is uncluttered of all the other modes. The WWV
+and Freq Analysis modes are always visible. When a subset of the
+entire mode bank is selected a new menu item is added to the Op_Mode
+menu, "Show all modes". This is a toggle to restore all modes to
+the menu. The inverse toggle is "Show fewer modes."
+<br>
+
+<br>
+\ref ui_configuration_general_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/ConfigUI-logserver.txt b/fldigi_doxygen/user_src_docs/ConfigUI-logserver.txt
new file mode 100644
index 00000000..dfe22d12
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigUI-logserver.txt
@@ -0,0 +1,134 @@
+/**
+\page  ui_configuration_log_server_page User Interface Configuration - Log server
+
+\tableofcontents
+
+\image html config-ui-tabs.png "UI Tabs"
+\image latex config-ui-tabs.png "UI Tabs" width=5.0in
+<br>
+
+
+\image html config-ui-qso-logging.png "QSO Logging"
+\image latex config-ui-qso-logging.png "QSO Logging" width=5.0in
+<br>
+
+\section captureing_log_data Capturing Log data
+
+Fldigi has a built in logbook. You can request to be prompted whenever
+there is an unsaved entry in the qso log area. You can also elect to
+whether to clear all of the qso fields when the log is saved or to leave them
+intact.
+Auto-fill Country and Azimuth uses the data found in the file
+"cty.dat" that you should download and place in the fldigi default
+folder. You can force the callsign field to be upper case
+independent of capture or keyboard entry. You enter your default
+Transmit Power which is used for the logbook record.
+<br>
+
+Fldigi has various ways to transfer data in the Rx panel to the qso logging
+fields. The default is to use a Shift-Left-Click paradigm.
+You can also use a double click method if you prefer. The
+Shift-Left-Click will still function. Each data item is
+considered to be a single word normally delimited by the space, tab or
+end-of-line character. You can add word delimiter characters in
+the designated text box. The default is to add *-,.; to the
+normal delimiters. This is a useful tool for extracting contest
+exchange data. The exchange might be RST, STATE and NAME.
+The station being worked might send this as 599-NJ-Bozo. Double
+clicking on the 599 NJ and Bozo would treat each as a separate word.
+<br>
+
+You can elect to have the RST in/out preset to 599 after you clear the QSO
+entry fields.
+<br>
+
+If you check the "callsign tooltips in received text" then the Rx
+text area will popup an information box whenever the mouse is held over
+a callsign for more than 2 seconds. The popup will look like one
+of the following:
+<br>
+
+\section pop_ups Pop ups
+
+\image html show-popup.png "Pop ups"
+\image latex show-popup.png "Pop ups" width=2.75in
+<br>
+
+\image html show-popup2.png "Pop ups 2"
+\image latex show-popup2.png "Pop ups 2" width=2.75in
+<br>
+
+\section country_files Country Files
+
+The data is derived by parsing the callsign and referral to both the
+logbook and the "cty.dat" file. If the station was previously
+worked the operator's name and azimuth/distance will be computed from
+the logbook gridsquare entry (Loc). Otherwise the
+azimuth/distance is computed from the data in the cty.dat file.
+<br>
+
+This file is maintained by, and can be downloaded from the following web site:
+<br>
+
+<a href="http://www.country-files.com/">http://www.country-files.com/</a><br>
+
+The default location for this file is in the fldigi default files
+folder. You have the option of changing that file location by
+either entering the new folder pathname in the edit control, or by
+using the "Browse" or "Default" button. If you change the
+contents of cty.dat while fldigi is running you should force fldigi to
+reload the data from the file. This data is normally only read
+when the program starts.
+<br>
+
+\section internal_logbook Internal Logbook
+
+Fldigi has an internal logbook. That log should be used for single
+operator operations. There may be times that you need to share a
+log, either between programs on a single computer, or with other
+operators running fldigi on other computers on a LAN (or even WAN).
+<br>
+
+In lieu of the internal logbook you can elect to use a common logbook
+server. This logbook is maintained by a separate logbook program,
+<a href="http://www.w1hkj.com/fllog-help/index.html">fllog</a>. fllog
+provides access to read, query and update records via an xmlrpc socket
+interface. fllog provides the server function and connecting applications
+are clients.
+<br>
+
+You need to specify both the socket address and socket port. The
+defaults are as shown and are for the instance when both fllog and
+fldigi are on a single computer. Unless configured otherwise,
+fllog will always use the port address 8421.
+<br>
+
+\section logbook_network_address  Logbook Network Address
+<br>
+
+\image html config-ui-lan.png "Network Address"
+\image latex config-ui-lan.png "Network Address" width=2.25in
+<br>
+
+My home network has IP address assignments as shown. If fllog were
+running on the mini-mac (fl-mac) and fldigi running on the linux-dev
+machine. I would enter the server address 192.168.1.94 into the fldigi
+configuration for the Client/Server Logbook.
+<br>
+
+\image html connect-to-logserver.png "Connect to Server"
+\image latex connect-to-logserver.png "Connect to Server" width=2.25in
+<br>
+
+The "Logbook/Connect to server" menu item allows you to connect to the
+remote logbook. If successful then the toggle remains checked and
+the menu items for accessing the internal logbook are disabled.
+<br>
+
+<br>
+\ref ui_configuration_log_server_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/ConfigUI-macros.txt b/fldigi_doxygen/user_src_docs/ConfigUI-macros.txt
new file mode 100644
index 00000000..44fb270c
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigUI-macros.txt
@@ -0,0 +1,62 @@
+/**
+\page  ui_configuration_macros_page User Interface Configuration - Macros
+
+\tableofcontents
+
+\image html config-ui-tabs.png "UI Tabs"
+\image latex config-ui-tabs.png "UI Tabs" width=5.0in
+<br>
+
+\image html config-ui-macros.png "UI Configure - Macros"
+\image latex config-ui-macros.png "UI Configure - Macros" width=5.0in
+<br>
+
+Access to a macro is gained by pressing the associated function
+key. There are actually 48 separate macros that can be
+created. With the default configuration you rotate between the
+sub-sets of 12 using the numbered button to the right of the macro bar,
+or by selecting a set with the Alt-1, Alt-2, Alt-3 or Alt-4 key
+combination. (on OS X use the Option-1 etc.)
+<br>
+
+The default user interface is a single macro bar of 12 buttons located just
+above the waterfall panel. There are times when you need ready access
+to more than 12 macro functions. When a 2 row configuration is
+selected the original row is forced to the Alt-1, or first sub-set of
+macros, and it's numeric rotate button is disabled. The second or
+SHIFTED macro button row can be rotate through Alt-2 ... Alt-4 using
+either it's numeric button or the Alt-\#key combination. The
+fldigi macro bar positions will change immediately so you can see the
+selection.
+<br>
+
+With 2 rows shown you obtain access to the primary set with normal
+Function key press. The secondary set is accessed by a
+SHIFT-Function-key press.
+<br>
+
+You edit any macro definition by using a mouse right-click on it's button.
+<br>
+
+You can also select to use the mouse wheel to rotate through the macro
+sub-sets. When checked you simply hover the mouse over the macro
+bar and roll the mouse wheel.
+<br>
+
+Fldigi manages multiple files that contain macro definitions. You may
+want to have the last used macro file be the one available the next time you
+start fldigi. If so, simply enable the "load last used Macro file on
+startup" check box. You can also choose to display which macro file was
+loaded at startup or when a new macro file is loaded. A brief message
+indicating which file was loaded will be written to the Rx text area if
+this option is selected.
+<br>
+
+
+<br>
+\ref ui_configuration_macros_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/ConfigWaterfall.txt b/fldigi_doxygen/user_src_docs/ConfigWaterfall.txt
new file mode 100644
index 00000000..c87f5dd2
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ConfigWaterfall.txt
@@ -0,0 +1,130 @@
+/**
+\page  ui_configuration_waterfall_page Waterfall Configuration
+
+\tableofcontents
+
+\image html config-ui-tabs.png "UI Tabs"
+\image latex config-ui-tabs.png "UI Tabs" width=5.0in
+<br>
+
+\image html config-wf-display.png "UI Waterfall Display"
+\image latex config-wf-display.png "UI Waterfall Display" width=5.0in
+<br>
+
+The waterfall palette or color scheme can be altered to suit your
+personal tastes and visual needs. When fldigi is first started it
+creates a wide range of pre-built palettes in the $HOME/.fldigi folder.
+The "Load" button gives you access to those palettes. You
+may change any palette by clicking on the various color buttons beneath
+the palette sample. A color picker opens for you to select the
+color by various means including specifying the RGB values. If
+you create a palette that suits you better than any of the prebuilt
+ones you can "Save" the palette.
+<br>
+
+The waterfall cursor is a set of markers on the frequency scale
+that are spaced a signal bandwidth apart. You canadd a pair
+of lines that drop down from those two markers for the full
+height of the waterfall by selecting Cursor BW. You can add a
+center line cursor to this pair of BW line by selecting Cursor Center line.
+You can also add a set of BW lines that straddle the received
+signal tracking point by selecting Bandwidth tracks. All three of these
+options are color selectable. Click on the colored button below the
+check box and a color selection dialog will open.
+<br>
+
+The frequency scale defaults to RF frequency. You can select to show
+audio frequencies.
+<br>
+
+You can monitor the transmitted audio waveform and also set the level of
+the monitored signal. This IS NOT your final transmitted signal!
+<br>
+
+Fldigi can set a notch from the waterfall when used with flrig and a
+transceiver that supports CAT control of a manual notch filter.
+When the notch is engaged a dotted vertical line is placed on the
+waterfall at the notch location. You can configure the color of
+the dotted notch indicator.
+<br>
+
+\section configure_fft_waterfall FFT Waterfall
+
+\image html config-wf-fft.png "UI Waterfall Display"
+\image latex config-wf-fft.png "UI Waterfall Display" width=5.0in
+<br>
+
+You can extinguish the display of received signals below a particular audio
+frequency.
+<br>
+
+Fldigi's waterfall FFT has a bin size of 1 Hz. With an FFT
+of 8192 and a sampling rate of 8000 it takes almost a second to
+accumulate enough data to perform the full FFT. A waterfall that
+dropped at one scan line per second would be hard on the viewer, so
+fldigi uses a first-in-first-out (FIFO) 8192 byte buffer for the FFT data.
+512 byte audio blocks move through the buffer with each successive
+read of the sound card. The full buffer of 8192 samples is used to
+compute the FFT. That means that data in the FFT can have a
+latency of 8 scans. This provides excellent frequency resolution but
+poor time resolution (the vertical waterfall appearance).
+The latency control allows you to select the number of 512 byte blocks that
+are used for the FFT. The default latency is set to 4. You should be able to
+achieve a reasonable compromise between the time and frequency
+domain resolutions.
+<br>
+
+FFT averaging can be used to smooth the waterfall display in the frequency
+domain.
+<br>
+
+The FFT Prefilter or window function is used to reduce aliasing in the
+FFT computation.
+<br>
+
+The default prefilter for the Fast Fourier Transform associated with the
+waterfall is <i>Blackman</i>. You can try the other windowing filter.
+Under some conditions you might prefer one of those. The Blackman window has
+proven best for my setup.
+<br>
+
+\section waterfall_mouse_behavior Waterfall Mouse Behavior
+
+\image html config-wf-mouse.png "UI Waterfall Mouse Behavior"
+\image latex config-wf-mouse.png "UI Waterfall Mouse Behavior" width=5.0in
+<br>
+
+The mouse behavior in the waterfall panel can be controlled to suit your
+particular operating style. You might want to replay the saved
+audio history every time you either left click to select or right click
+to preview a particular signal. You can move the transceiver
+frequency in increments of 100 Hz by dragging the waterfall scale.
+You can also choose to insert a line of text into the Rx panel
+each time you left click a waterfall signal. The text can include
+expandable macro tags.
+<br>
+
+\subsection waterfall_mouse_behavior_tailoring Waterfall Mouse Behavior Tailoring
+
+The mouse wheel behavior can also be tailored to your liking:
+<br>
+
+<ul>
+<li>None - no mouse wheel activity in waterfall panel</li>
+<li>AFC range or BW - adjust the AFC range/BW up/down</li>
+<li>Squelch level - adjust the squelch level up/down</li>
+<li>Signal search - search up / down for next signal in current mode</li>
+<li>Modem carrier - adjust the audio tracking point +/- Hz increments</li>
+<li>Modem - select modem type from a full rotary of available modems</li>
+<li>Scroll - move the waterfall left/right in 100 Hz increments (for 2x, 4x expanded waterfall view)</li>
+</ul>
+
+
+<br>
+\ref ui_configuration_waterfall_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/Contest-How-To.txt b/fldigi_doxygen/user_src_docs/Contest-How-To.txt
new file mode 100644
index 00000000..b492c835
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Contest-How-To.txt
@@ -0,0 +1,481 @@
+/**
+\page  contest_how_to_page Contest - How To
+
+\tableofcontents
+
+
+Fldigi supports a basic contesting format.   Select the menu item
+View/Contest fields to see how the QSO entry entry fields change for
+contest data.  You will see that fldigi has fields to support
+received and sent contest numbers as well as generic contest exchange
+information.
+<br>
+
+\section contest_fields Contest Fields
+\image html contest-fields.png "Contest Fields"
+\image latex contest-fields.png "Contest Fields" width=4.5in
+<br>
+
+The serial number out (\#Out) is automatically initialized and updated by
+the built-in serial number generator.   You can enter the
+appropriate exchange information via the keyboard or mouse.  Text
+in the Rx pane can be selected by the usual left-click-swipe of
+highlighting.  Then right click anywhere after highlighting the
+desired text and a popup menu will appear allowing you to select the
+destination QSO field.  Make your selection and the info is placed
+in the correct text box.  Note that the popup menu changes with
+the QSO logging view and also with a change in "Quick entry".  A
+full description is found in the description of operating the
+ \ref qso_log_book_page "Logbook".  The important thing to note for contest
+operation is that the Call and Serial \# are single word captures.  The Xchg
+capture can be either single word or multiple word (mark / right click).  If
+the Xchg field has text contents then the new capture is appended to
+end of the current text in that field.  That means you can point
+to the word representing the field, right click and select from the menu.
+You do not need to highlight the text for the word capture.  You can very
+rapidly fill in the serial number and the exchange data (even if multi value)
+by simply pointing and right clicking on the desired word.
+<br>
+
+\image html config-ui-contest.png "UI Contest"
+\image latex config-ui-contest.png "UI Contest" width=4.5in
+<br>
+
+To set up fldigi for contesting you will need to open configure contest.
+the 1st row contains what info you want sent with the appropriate macro
+tag. ie...if the contest requires RST and name you would fill in the
+Exchange Out box with your name.  The contents of this field are accessed from
+a macro with the \<XOUT\> tag. You will also need to check the RST
+always 599 box as this is the de-facto signal report in contests.
+<br>
+
+If you are participating in a CW contest you may want to select the "Send CW cut
+numbers", cut numbers is the norm for a CW contest.  The cut
+numbers will send N for 9 and T for zero.
+<br>
+
+The next box contains the needed requirements to use serial numbers for
+a contest. You will always want to use leading zeros, start with 1 and use 3
+digits.  Press reset to initialize the \#Out QSO field to the Start number.
+<br>
+
+Check the appropriate fields for determining if this is a duplicate call. If
+a duplicate is detected the Call entry will be highlighted as shown in
+the "Dup Color" button.  Pressing this button opens a color selector so
+you may customize the color.  There are many choices to alert you to a
+duplicate contact.  The duplicate is based on the logical AND of all of the
+fields to be checked.  The DUPE is cleared when you press the
+clear QSO log button (the brush icon).
+<br>
+
+After you have filled in all the required information, make sure you save and
+close.
+<br>
+
+Remember YOU MUST click the Reset button in the Serial number panel for the
+serial number counter to be initialized.  You should also press
+the QSO clear button (broom) in the QSO entry widget for the other
+changes to take effect.
+<br>
+
+It would be best to create a new log for each contest.  You create a new
+log by selecting the menu item File/Logs/New logbook.  The default new log
+name will be newlog.adif on Linux and newlog.adi on Windows.   You can rename
+the new log file now or later by using the system file manager or when you
+save the log.  The import/export feature of fldigi will allow you to export
+the log into your everyday logging software or the built-in fldigi logbook.
+<br>
+
+\section restarting_contest_session Restarting a contest session
+
+You might have closed down fldigi in the middle of a contest, everyone
+needs a break now and then.  You then start fldigi and want to
+continue the contest.  Here are the steps to insure that you
+continue operations with no glitches.
+<br>
+
+<ul>
+<li>Load your macro file that contains your contest macros (more on that below)</li>
+<li>Select the menu item View/Contest fields</li>
+<li>Select the menu item View/Logbook</li>
+<li>Make sure you have the contest logbook open ... if not then this is the
+time to open that logbook database.  <br>Select the menu item "File/Logs/Open
+logbook..." and find your log data file.</li>
+<li>Look at the last record and check the serial number sent.  Enter that
+number plus one in the Start entry on the config contest tab (see above).</li>
+<li>Press the Reset button in that panel.</li>
+</ul>
+
+You are ready to keep on contesting
+<br>
+
+\section remembering_a_contact Remembering a contact
+
+If you are copying a potential contact but you are not being heard you can
+save fldigi's modem state using one of two methods
+<br>
+
+<ol>
+<li>double click the signal on the waterfall</li>
+<li>right click on the Rx panel and select "Insert marker"</li>
+</ol>
+
+A line of text will be inserted at the end of the Rx text buffer.  It will
+appear similar to this:
+<br>
+
+\<\<2008-12-30T10:06Z BPSK-31 @ 3580000+0781\>\>
+<br>
+
+The date-time, the mode, the transceiver operating frequency and the audio
+offset will be recorded.  The text line is in blue and behaves in
+a way that you might expect a url reference to behave in a web browser
+window.  Work a few more contacts (even on a different band or
+frequency) and then scroll the Rx pane to that special divider.
+ Left click on the line of text and fldigi will restore the
+transceiver to its frequency, change the mode to the saved mode and put
+the waterfall cursor at the audio offset frequency.  Changing the
+transceiver frequency will only work if you are using CAT control of
+your transceiver.  If you are not using CAT control the mode and
+waterfall cursor will still be restored.
+<br>
+
+There is no limit to the number of divider lines that can be inserted into
+the Rx pane.  They will all be removed when the Rx pane is cleared.
+<br>
+
+\section saving_session Saving the entire session
+
+Select the menu item "File/Logs/Log all RX/TX text".  If this toggle menu
+is checked your entire session of received and sent text will be saved
+to a file in the fldigi default files folder.  It will be given a
+name synonymous with the date and time is is started, ie:
+fldigi20081230.log.  You can review this log by selecting the menu
+item "File/Show config" which will open your OS default file explorer
+to the fldigi files folder.  The file is an ASCII text file.
+<br>
+
+The format of the daily log is shown in Working Logs.
+<br>
+
+\section contesting_macro_tips Contesting Macro Tips
+<br>
+
+OK, now we have fldigi setup for basic contesting, lets move on to some
+ideas on macros to use.  I tend to make generic one size
+fits all macros.  I recommend that you make a new macro file, mine is
+named contest.mdf, this will give you 48 macros to use based on the
+type of contest you are entering.  Take a good look at the examples I
+have listed, you will notice there are no commas, hyphens or other
+extraneous items.  I have seen just about every example of a poorly
+thought out macro there is or has ever been dreamed up. Classic
+examples are:
+<br>
+
+<ul>
+<li>w3nr you are 599 in Alabama your serial number is 001-001-001 how copy ??</li>
+<li>hello ed thanks for the call you are 599-599-001-001-001 QTH Alabama back
+to you</li>
+</ul>
+
+The list goes on and on. Just think, you have to try and capture the
+exchange, try it and you will see what I mean.
+<br>
+
+When you enter a contest you have to decide whether you are going to sit on
+one frequency and call CQ (Run) or are you going to tune the band
+looking for stations to work (S&amp;P).  So lets set up some macros that
+should cover both cases.
+<br>
+
+Several new macro tags have been created to facilitate contesting, these
+include the following tags.
+<br>
+
+<table>
+<tr>
+<td>\<LOG\></td>
+<td>add QSO data to the logbook &amp;
+clear the QSO data fields</td>
+</tr>
+<tr>
+<td>\<CNTR\></td>
+<td>insert current contest serial number into the text stream</td>
+</tr>
+<tr>
+<td>\<INCR\></td>
+<td>increment contest serial number</td>
+</tr>
+<tr>
+<td>\<DECR\></td>
+<td>decrement contest serial number</td>
+</tr>
+<tr>
+<td>\<XOUT\></td>
+<td>contest exchange</td>
+</tr>
+<tr>
+<td>\<QSOTIME\></td>
+<td>current log time in Zulu HHMM format</td>
+</tr>
+<tr>
+<td>\<LDT\></td>
+<td>local date time</td>
+</tr>
+<tr>
+<td>\<ILDT\></td>
+<td>LDT in iso-8601 format</td>
+</tr>
+<tr>
+<td>\<ZDT\></td>
+<td>Zulu date time</td>
+</tr>
+<tr>
+<td>\<IZDT\></td>
+<td>ZDT in iso-8601 format</td>
+</tr>
+<tr>
+      <td>\<QSOTIME\><br>
+      </td>
+      <td>actual time of execution of the macro ... useful where exact times are used to match contest log submissions<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<SAVEXCHG\><br>
+      </td>
+      <td>save entire contents of the expanded macro text to the "Exchange Out" field in the logbook<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<XBEG\><br>
+      </td>
+      <td>mark the beginning of a text string that is to be saved to the "Exchange Out" field in the logbook<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<XEND\><br>
+      </td>
+      <td>mark the end of the text string that
+      is to be saved to the "Exchange Out" field in the logbook
+      <br>
+note:  \<SAVEXCHG\> and the \<XBEG\>...\<XEND\> macro tags are
+mutually exclusive
+<br>
+\<XBEG\>...\<XEND\> is given priority if both all three are specified
+in a single macro
+<br>
+      </td>
+    </tr>
+</table>
+<br>
+
+See \ref macros_sub_page "Macros" for additional information on editing
+and using the fldigi macro system.
+<br>
+
+\section run_macros RUN Macros
+
+We need just a few, starting with a CQ macro - Put this in the F1 key definition
+<br>
+
+\verbatim
+<TX>
+cq test de <MYCALL> <MYCALL> cq k
+<RX>
+\endverbatim
+<br>
+
+Notice that I left 2 spaces between my call and 3 spaces at the end before the
+k. This will make it easier for a station to grab my call and the k on
+the end eliminates garbage characters before my macro finishes. The
+tx/rx are on separate lines as I want to be sure my macro is on a line
+by itself and not mixed in with screen garbage.
+<br>
+
+Now the exchange macro - Put this in the F2 key definition<br>
+<br>
+
+\verbatim
+<TX>
+<CALL> 599  <CNTR> <CNTR>  <X1>  <X1> <CALL>  k
+<RX>
+\endverbatim
+
+Why do I have his call at the beginning as well as the end, to make sure I
+have copied his call correctly. You will also see that I have not as
+yet logged the contact,why, well are you sure he does not need to
+correct his call or ask for a repeat.
+<br>
+
+You are asked to repeat the exchange, you can just re-send the exchange macro,
+this verifies all of the information. Now he sends you his info and if you have
+copied it correctly you need a TU macro. - Put this in the F3 key definition.
+<br>
+
+\verbatim
+<TX>
+qsl tu qrz test  <MYCALL>  k
+<RX><LOG><INCR>
+\endverbatim
+
+Here we have done all the necessary items to complete the exchange. Notice
+that I did not log the contact until after everything was correct. I
+have fldigi set to clear on save, so when the \<LOG\> part of the
+macro executes the QSO area is cleared.
+<br>
+
+Thats the end of my RUN macro setup, told you it was rather simplistic and
+generic.
+<br>
+
+\section s_p_macros S \& P Macros
+
+I rarely if ever use S&amp;P, but there are times I
+need to, especially if my QSO rate drops while running.  Again the macros are
+very generic with only the needed info.  If band conditions warrant you may
+want to send your call 3 times.  Put this in the F5 key definition
+<br>
+
+\verbatim
+<TX>
+<MYCALL>  <MYCALL>  k
+<RX>
+\endverbatim
+
+Why just my call ?? Well I assume the other guy already knows his call !
+<br>
+
+The exchange macro is basically the same as the RUN macro.  Put this one in the F6 key definition<br>
+<br>
+
+\verbatim
+<TX>
+599  <CNTR>  <CNTR>  <X1>  <X1>    k
+<RX>
+\endverbatim
+
+
+As you see I have not as yet logged the QSO or incremented the serial
+number.  This is the final S&amp;P macro.  Put this one in the F7 key
+definition.
+<br>
+
+\verbatim
+<LOG><INCR>
+\endverbatim
+
+Now this is the most important macro you will ever need......trust me. Put it
+where you won't fail to find it.  How about F9 ?
+<br>
+
+\verbatim
+<TX>
+agn  agn  k
+<RX>
+\endverbatim
+
+
+You will see that it is used many times during a contest, especially with
+weak stations and heavy QRN/QRM.
+<br>
+
+\<QSOTIME\>
+
+<ul>
+<li>
+time sent in Tx stream</li>
+<li>
+repeat execution of \<QSOTIME\> before a \<LOG\> macro or a save to
+log button press will resend the original time</li>
+<li>
+\<LOG\> macro or a save-to-log button press appends the QSOTIME to
+the STX_STRING field in the adif log record and clears the QSOTIME.
+<br>
+</li>
+</ul>
+\<XBEG\>
+<ul>
+<li>
+use at end of a contest exchange to save the entire exchange string in STX_STRING</li>
+<li>
+usurps QSOTIME if both are contained in same macro text, ie:
+"\<RST\> \<CNTR\> \<QSOTIME\>\<SAVEXCHG\>" will send an
+exchange as  599 024 1125 if RST = 599, Counter = 024 and time of
+execution is 1125</li>
+<li>
+repeats the same as \<QSOTIME \></li>
+<li>
+\<LOG\> macro or a a save-to-log button press saves the associated
+macro text (after expansion).  QSOTIME and the saved exchange text
+are cleared after the save occurs.</li>
+</ul>
+
+
+An example of the SAVEXCHG macro tag<br>
+
+\verbatim
+<RST> <CNTR> <XOUT> <QSOTIME><SAVEXCHG>
+\endverbatim
+
+
+Where RST = 599, CNTR = 0125, XOUT = AL, QSOTIME = 1433<br>
+<br>
+
+Will save this string to the <i>Exchange Out</i> field in the
+logbook: "599 0125 AL 1433"
+<br>
+
+Please note that you should not include any text or macro tags that are
+not to be a part of <i>Exchange Out</i>.  If your macro had this:
+<br>
+
+\verbatim
+<TX><CALL> UR <RST> <CNTR> <XOUT> <QSOTIME> de <MYCALL> k<RX><SAVEXCHG>
+\endverbatim
+
+
+Where CALL = W3NR, MYCALL = W1HKJ<br>
+<br>
+
+the saved <i>Exchange Out</i> field would contain: "W3NR UR 599 0125 AL 1433 de W1HKJ k"
+<br>
+
+Probably not what you want.  Use separate function keys for the
+"\<TX\>CALL ..." and the "de \<MYCALL\> k\<RX\>" or use the next
+set of macro tags
+<br>
+
+\verbatim
+<XBEG>...<XEND>
+\endverbatim
+
+
+These two macro tags are delimiters for capturing the transmitted exchange
+data, for example:
+<br>
+
+\verbatim
+<TX><CALL> de <MYCALL> QSL <XBEG><RST> <CNTR> <QSOTIME><XEND> K<RX>
+\endverbatim
+
+
+Will place the expanded \<RST\> \<CNTR\> \<QSOTIME\> into the
+<i>Exchange Out</i> field of the logbook when the contact is saved.  This is
+much better illustrated with a screen shot.  This one shows the macro
+editor contents, the logbook entry in <i>Exchange Out</i>, and the transmit
+text buffer.
+<br>
+<br>
+
+\image html xbeg-xend.png "Exchange Begin-End"
+\image latex xbeg-xend.png "Exchange Begin-End" width=6.0in
+<br>
+
+<br>
+\ref contest_how_to_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/Contestia.txt b/fldigi_doxygen/user_src_docs/Contestia.txt
new file mode 100644
index 00000000..99000f4e
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Contestia.txt
@@ -0,0 +1,68 @@
+/**
+\page contestia_page Contestia
+
+\tableofcontents
+
+Fldigi can operate on the following Contestia modes without special setup
+by the operator:
+<br>
+
+Mode  | Symbole Rate \(Baud\) | Typing speed \(WPM\) | Bandwidth \(Hz\)
+:---------------: | :-----------: | :-----------: | :---------:
+Contestia 4-250   | 62.5          | ~ 40          | 250
+Contestia 8-250   | 31.25         | ~ 30          | 250
+Contestia 4-500   | 125           | ~ 78          | 500
+Contestia 8-500   | 62.5          | ~ 60          | 500
+Contestia 16-500  | 31.25         | ~ 30          | 500
+Contestia 8-1000  | 125           | ~ 117         | 1000
+Contestia 16-1000 | 62.5          | ~ 78          | 1000
+Contestia 32-1000 | 31.25         | ~ 48          | 1000
+
+Unusual combinations of symbol rate and bandwidth can be selected
+using the \ref contestia_configuration_page tab.
+<br>
+
+Contestia is a digital mode directly derived from Olivia that is not
+quite as robust - but more of a compromise between speed and
+performance. It was developed by Nick Fedoseev, UT2UZ, in 2005. It
+sounds almost identical to Olivia, can be configured in as many ways,
+but has essentially twice the speed.
+
+Contestia has 40 formats just like Olivia - some of which are
+considered standard and they all have different characteristics. The
+formats vary in bandwidth (125,250,500,1000, and 2000hz) and number of
+tones used (2,4,8,16,32,64,128, or 256). The standard Contestia formats
+(bandwidth/tones) are 125/4, 250/8, 500/16, 1000/32, and 2000/64.
+The most commonly used formats right now seem to be 250/8, 500/16, and
+1000/32.
+<br>
+
+Contestia performs very well under weak signal conditions. It handles
+QRM, QRN, and QSB very well also. It decodes below the noise level but
+Olivia still outperforms it in this area by about 1.5 - 3db depending
+on configuration.
+
+It is twice as fast as Olivia per configuration. It is an excellent
+weak signal, ragchew, QRP, and DX digital mode. When ragchewing under
+fair or better conditions it can be more preferable to many hams than
+Olivia because of the faster speed. For contests it might also be a
+good mode IF the even faster configurations such as 1000/8 or 500/4 are
+used.
+
+Contestia get it's increased speed by using a smaller symbol block size
+(32) than Olivia (64) and by a using 6bit decimal character set rather
+than 7bit ASCII set that Olivia does. Therefore, it has a reduced
+character set and does not print out in both upper and lower case (like
+RTTY). Some traffic nets might not want to use this mode because it
+does not support upper and lower case characters and extended
+characters found in many documents and messages. For normal digital
+chats and ham communications that does not pose any problem.
+
+
+<br>
+\ref contestia_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/DXCC_list.txt b/fldigi_doxygen/user_src_docs/DXCC_list.txt
new file mode 100644
index 00000000..fc26c7d0
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/DXCC_list.txt
@@ -0,0 +1,77 @@
+/**
+\page  dxcc_list_page DXCC List etal
+
+\tableofcontents
+
+Fldigi uses several data files that are not included with the
+distribution.  These must be downloaded from the list maintenance
+web sites for the most current data.  These lists include:
+<br>
+
+<table>
+	<tr>
+	<td>List Data<br>
+	</td>
+	<td>List Name<br>
+	</td>
+	<td>Web source<br>
+	</td>
+	</tr>
+	<tr>
+	<td>DXCC<br>
+	</td>
+	<td>cty.dat<br>
+	</td>
+	<td>
+	<a href="http://www.country-files.com/cty/">http://www.country-files.com/cty/</a>
+	<br>
+	</td>
+	</tr>
+	<tr>
+	<td>LOTW<br>
+	</td>
+	<td>lotw1.txt<br>
+	</td>
+	<td>
+	<a href="http://www.hb9bza.net/lotw/lotw1.txt">http://www.hb9bza.net/lotw/lotw1.txt</a>
+	<br>
+	</td>
+	</tr>
+	<tr>
+	<td>EQSL<br>
+	</td>
+	<td>AGMemberList.txt<br>
+	</td>
+	<td>
+	<a href="http://www.eqsl.cc/QSLcard/DownloadedFiles/AGMemberList.txt">http://www.eqsl.cc/QSLcard/DownloadedFiles/AGMemberList.txt</a>
+	<br>
+	</td>
+	</tr>
+	</table>
+<br>
+
+These files should be downloaded and placed in the fldigi files
+directory.  The most convenient way to open the fldigi files
+directory is via the menu item "File / Show config".
+<br>
+
+The DXCC list browser is shown by selecting the menu item
+"View / Countries".
+<br>
+
+\image html DXCC_list.png "DXCC List"
+\image latex DXCC_list.png "DXCC List" width=4.0in
+<br>
+
+
+You can sort the list by Country, Continent, ITU or CQ zone by clicking on
+the various column headers.
+<br>
+
+<br>
+\ref dxcc_list_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/DigiWWV.txt b/fldigi_doxygen/user_src_docs/DigiWWV.txt
new file mode 100644
index 00000000..4562f8ca
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/DigiWWV.txt
@@ -0,0 +1,332 @@
+/**
+\page  digiscope_display_wwv_mode Digiscope Display - WWV mode
+
+\tableofcontents
+
+The WWV mode is used to measure the offset of the sound card oscillator.
+It does this by comparing the timing loop for the sound card measurements
+against the clock tick signal that is transmitted by WWV and WWVH.  The
+sampling rate for the sound card should be set to "native".  The sound card
+samples the signal and returns the values in 512 blocks.  This block
+sampling is what sets the basic timing mechanism for the thread that
+reads the sound card, sends data to the waterfall, and sends data to
+the modem signal processing functions.  A process of filtering is
+used that simultaneously reduces the sampling rate.  Most modern
+soundcards will use 44100 or 48000 as the native smampling rate.
+That sample rate in down converted to 1000 using a decimation in time
+type FIR.  The resulting signal is then power detected and
+further filtered with a filter called a moving average filter. The moving
+average is very good at detecting the edge of a pulse such as the 1 second
+tick transmitted by WWV.  This output is then displayed in a manner very
+similar to a FAX signal.  Each scan line represents the received signal
+over a 1 second interval.  The bright white line is the time tick.  You can
+see a very slight slope from left to right as the signal goes from top to
+bottom of the display.
+<br>
+
+Open the configure dialog box to the "SndCrd" tab.  You are going
+to be adjusting the "Rx corr Rate" while you observe the effect of this
+control on the slope of the time tick line.
+<br>
+
+Tune in WWV or WWVH on 2.5, 5.0, 10.0 or 15.0 MHz in the AM mode. This
+seems to give the best signal view.  Select the WWV modem and allow the data
+to begin to accumulate in the digiscope display.  When you can clearly see
+the bright tick line, move the cursor to the bottom of the line and left
+click at that position.  That will resync the digiscope display and put the
+ensuing tick marks at the center line red graticule.
+<br>
+
+Then right click anywhere in the digiscope display.  That changes
+the zoom level to show more detail regarding the slope of the time tick
+line.  The zoom level increases by a factor of 5.  Right
+clicking again restores the original zoom level.  I recommend
+making the adjustments to the Rx corr Rate control in the x5 zoom level.
+<br>
+
+If the slope of the time tick line is positive you will need to apply a
+negative value to the Rx corr Rate.  If it is negative then a
+positive correction is needed.
+<br>
+
+Start with a correction of 0 ppm and observe the slope.  Try a
+value of 1000 ppm and observe the slope.  Again, try a -1000 ppm
+correction and observe the slope.  The following are some observations
+made on 10 MHz WWV, DCF-77 and RWM under less than ideal conditions.
+<br>
+
+\image html wwv3.png "WWV corrected 20 minute trace 5x scale"
+\image latex wwv3.png "WWV corrected 20 minute trace 5x scale" width=1.25in
+
+
+\htmlonly
+
+<table style="text-align: left; width: 100px;" border="0" cellpadding="2" cellspacing="2">
+
+<tr>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 117px; height: 115px;" alt="" src="wwv1-lgneg.png">
+<br>
+
+-1000 ppm WWV<br>
+
+5x scale</td>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 116px; height: 116px;" alt="" src="wwv2-000ppm.png">
+<br>
+
+0 ppm WWV<br>
+
+5x scale</td>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 117px; height: 118px;" alt="" src="wwv2-lgpos.png">
+<br>
+
++1000 ppm WWV<br>
+
+5x scale</td>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 117px; height: 116px;" alt="" src="wwv2-125ppm.png">
+
++120 ppm WWV<br>
+
+5x scale</td>
+</tr>
+<tr>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 114px; height: 115px;" alt="" src="dcf77-0.png">
+<br>
+
+0 ppm DCF-77 <br>
+
+1x scale</td>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 114px; height: 114px;" alt="" src="dcf77-0zoom.png">
+<br>
+
+0 ppm DCF-77<br>
+
+5x scale</td>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 115px; height: 115px;" alt="" src="dcf77-1000.png">
+<br>
+
++1000 ppm DCF-77<br>
+
+1x scale</td>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 114px; height: 114px;" alt="" src="dcf77-65zoom.png">
+<br>
+
++65 ppm DCF-77<br>
+
+5x scale</td>
+</tr>
+<tr>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 121px; height: 121px;" alt="" src="RWMpre-cal.png">
+<br>
+
+RWM uncorrected<br>
+
+1x scale</td>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 119px; height: 121px;" alt="" src="RWM+25361ppm.png">
+<br>
+
+RWM <br>+25361 ppm<br>
+
+1x scale</td>
+<td style="vertical-align: top; text-align: center;">
+<img style="width: 119px; height: 119px;" alt="" src="RWMpost-cal-x5.png">
+<br>
+
+RWM <br>+25361 ppm<br>
+
+5x scale</td>
+<td style="vertical-align: top;">
+<br>
+</td>
+</tr>
+</table>
+
+\endhtmlonly
+
+\latexonly
+
+\begin{figure}[H]
+
+    \centering
+
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{wwv1-lgneg.png}
+        \caption{0 ppm WWV 5x scale}
+        \label{fig:wwv1_lgneg}
+    \end{subfigure} ~
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{wwv2-000ppm.png}
+        \caption{+1000 ppm WWV 5x scale}
+        \label{fig:wwv2_000ppm}
+    \end{subfigure} ~
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{wwv2-lgpos.png}
+        \caption{-1000 ppm WWV 5x scale}
+        \label{fig:wwv2_lgpos}
+    \end{subfigure} ~
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{wwv2-125ppm.png}
+        \caption{+120 ppm WWV 5x scale}
+        \label{fig:wwv2_125ppm}
+    \end{subfigure}
+
+     \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{dcf77-0.png}
+        \caption{0 ppm DCF-77 1x scale}
+        \label{fig:dcf77_0}
+    \end{subfigure} ~
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{dcf77-0zoom.png}
+        \caption{0 ppm DCF-77 5x scale}
+        \label{fig:dcf77_0zoom}
+    \end{subfigure} ~
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{dcf77-1000.png}
+        \caption{+1000 ppm DCF-77 1x scale}
+        \label{fig:dcf77_1000}
+    \end{subfigure} ~
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{dcf77-65zoom.png}
+        \caption{+65 ppm DCF-77 5x scale}
+        \label{fig:dcf77_65zoom}
+    \end{subfigure}
+
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{RWMpre-cal.png}
+        \caption{RWM uncorrected 1x scale}
+        \label{fig:RWMpre_cal}
+    \end{subfigure} ~
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{RWM+25361ppm.png}
+        \caption{RWM +25361 ppm 1x scale}
+        \label{fig:RWM_25361ppm}
+    \end{subfigure} ~
+    \begin{subfigure}[t]{0.25\textwidth}
+        \centering
+        \includegraphics[width=0.75in]{RWMpost-cal-x5.png}
+        \caption{RWM +25361 ppm 5x scale}
+        \label{fig:RWMpost_cal_x5}
+    \end{subfigure}
+
+    \caption{PSK Digiscopes}
+    \label{fig:psk_digiscopes}
+\end{figure}
+
+\endlatexonly
+<br>
+
+You can see that my sound card requires a positive correction since the
+slope is negative with a 0 ppm entry.  The required correction of
++120 ppm was determined by guessing the needed correction to be close
+to 1/10 of the -1000 ppm slope and then adjusting for a steady track
+along the red graticule.  The DCF-77 images were provided by
+Walter, DL8FCL.  The RWM images were provided by Andy G3TDJ.
+<br>
+
+You can left click on the tick line anytime you want to recenter the
+signal.  That will aid in making your visual observation.
+<br>
+
+When you are finished, the Rx corr Rate entry is the correct one for
+your sound card.  Save the configuration for future fldigi use.
+<br>
+
+Andy also provided information on the RWM transmissions:
+<br>
+
+
+RWM details extracted from <a class="moz-txt-link-freetext" href="http://www.irkutsk.com/radio/tis.htm">http://www.irkutsk.com/radio/tis.htm</a>
+<br>
+
+Station RWM - Main characteristics
+<br>
+
+Location: Russia, Moscow
+<br>
+
+55 degr. 44' North , 38 degr. 12' East
+<br>
+
+Standard frequencies : 4996, 9996 and 14996 kHz
+<br>
+
+Radiated power: 5kW on 4996 and 9996 kHz; 8kW on 14996 kHz
+<br>
+
+Period of operation: 24 hours per day,  except 08.00-16.00 msk for maintenance as below:
+<br>
+
+on 4996  kHz : 1st wednesday of the 1st month of quater;
+<br>
+
+on 9996  kHz : 2nd wednesday of the 1st month of the quater;
+<br>
+
+on 14996 kHz : 3rd wednesday of each odd month;
+<br>
+
+Coverage: 20 degr. - 120 degr. East
+<br>
+
+35 degr. - 75 degr. North
+<br>
+
+Time signals A1X are given every second of 100 ms duration with a frequency
+of 1 Hz. Minute pip is extended to 500 ms.
+<br>
+
+Hourly transmission schedule
+<br>
+
+ m:s  -  m:s
+
+00:00 - 07:55   --  MON signals (no modulation)
+<br>
+08:00 - 09:00   --  transmitter is signed off
+<br>
+09:00 - 10:00   --  station's identification is sent by Morse Code
+<br>
+10:00 - 19:55   --  A1X signals and identification of DUT1+dUT1
+<br>
+20:00 - 29:55   --  DXXXW signals
+<br>
+30:00 - 37:55   --  N0N signals (no modulation)
+<br>
+38:00 - 39:00   --  transmitter is signed off
+<br>
+39:00 - 40:00   --  station's identification is sent by Morse Code
+<br>
+40:00 - 49:55   --  A1X signals and identification of DUT1+dUT1
+<br>
+50:00 - 59:55   --  DXXXW signals
+
+<br>
+See \ref wwv_tx_mode "Transmitting Simulated WWV Timing Tone"
+
+<br>
+
+\ref digiscope_display_wwv_mode "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/DigiscopeDisplay.txt b/fldigi_doxygen/user_src_docs/DigiscopeDisplay.txt
new file mode 100644
index 00000000..9dcea595
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/DigiscopeDisplay.txt
@@ -0,0 +1,252 @@
+/**
+\page  digiscope_display_page Digiscope Display
+
+\tableofcontents
+
+Fldigi provides several different views
+of the decoded signal with its waterfall, text and a scope displays. The
+scope display is either a separate moveable, resizable dialog that is opened
+from the "View/Digiscope" menu item or a docked scope.
+<br>
+
+\section cw_scope CW
+<br>
+
+
+
+\image html digiscope-cw.png "Digiscope CW"
+\image latex digiscope-cw.png "Digiscope CW" width=1.0in
+<br>
+
+The CW signal will consist of the time domain amplitude detected signal. The
+horizontal timing is dependent on CW speed, so that the display will appear
+similar independent of CW speed.
+<br>
+
+\image html digiscope-cw.png "Digiscope CW"
+\image latex digiscope-cw.png "Digiscope CW" width=1.0in
+<br>
+
+\section domino_ex_scope DominoEX / Thor
+
+\image html digiscope-domexA.png "Digiscope DominoEX \& Thor"
+\image latex digiscope-domexA.png "Digiscope DominoEX \& Thor" width=1.0in
+<br>
+
+DominoEX and Thor have two alternate views available on the digiscope
+display.  You can toggle between the views by left clicking on the
+digiscope display area.  The triangular view shows data propogation
+through the interleave filter.  As signal s/n degrades this display
+will become more wavy.
+<br>
+
+\image html digiscope-domexB.png "Digiscope DominoEX \& Thor"
+\image latex digiscope-domexB.png "Digiscope DominoEX \& Thor" width=1.0in
+<br>
+
+The second view is the decoded data stream viewed in the frequency
+domain.  The dots will be very distinct when the signal is fully
+acquired and decoding properly.  It will be fuzzy when the decoder is
+not locked or there is interference present.
+<br>
+
+\section mfsk_scope MFSK
+
+\image html digiscope-mfsk.png "Digiscope MSFK"
+\image latex digiscope-mfsk.png "Digiscope MSFK" width=1.0in
+<br>
+
+This is what you expect to see for all of the MFSK type modes.  The
+number of steps in the slant lines will change with the various modes,
+but they will all have the same general appearance.  If the signal
+is mistuned the sloped lines will become bowed and distorted.
+<br>
+
+\section psk_scope PSK
+
+The digiscope display just to the right of the waterfall displays
+signal quality in various formats.  The display for PSK modes is
+the vector scope:
+<br>
+
+<center>
+\htmlonly
+<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
+<tr>
+<td style="width: 5%;">
+<br>
+</td>
+<td style="text-align: center;">
+<div style="text-align: center;">
+<img style="width: 102px; height: 100px;" alt="" src="digiscope-psk-nosig.png" hspace="5">
+<br>
+</div>
+<br>
+<div style="text-align: left;">The
+display with no signal or below squelch level.  If the SQL is off
+this display will be random vectors driven by noise.</div>
+</td>
+<td style="text-align: center; vertical-align: top;">
+<img style="width: 103px; height: 99px;" alt="" src="digiscope-psk.png" hspace="5">
+<br>
+<br>
+<div style="text-align: left;">The display with a normal psk31 signal.  The vector flips between 0 and 6 o'clock</div>
+</td>
+<td style="text-align: center; vertical-align: top;">
+<img style="width: 101px; height: 96px;" alt="" src="digiscope-psk-low.png" hspace="5">
+<br>
+<br>
+<div style="text-align: left;">AFC off and receive carrier set below the center of the received signal</div>
+</td>
+<td style="width: 5%;">
+<br>
+</td>
+</tr>
+<tr>
+<td>
+<br>
+</td>
+<td style="text-align: center; vertical-align: top;">
+<img style="width: 98px; height: 99px;" alt="" src="digiscope-psk-high.png" hspace="5">
+<br>
+<br>
+<div style="text-align: left;">
+AFC off and receive carrier set above the center of the received signal.</div>
+</td>
+<td style="text-align: center; vertical-align: top;">
+<img style="width: 99px; height: 102px;" alt="" src="digiscope-psk-history.png">
+<br>
+<br>
+<div style="text-align: left;">AFC enabled, Fading History Display Mode Selected (left click on scope)</div>
+</td>
+<td style="text-align: center; vertical-align: top;">
+<img style="width: 101px; height: 99px;" alt="" src="digiscope-psk-history-amplitude.png">
+<br>
+<br>
+<div style="text-align: left;">AFC enabled, Fading History / Amplitude Display Mode Selected (2nd left click on scope)</div>
+</td>
+<td>
+<br>
+</td>
+</tr>
+</table>
+\endhtmlonly
+</center>
+
+\latexonly
+
+\begin{figure}[H]
+
+	\centering
+
+	\begin{subfigure}[t]{0.3\textwidth}
+		\centering
+		\includegraphics[width=1.0in]{digiscope-psk-nosig.png}
+		\caption{The display with no signal or below squelch level.  If the
+		SQL is off this display will be random vectors driven by noise. }
+		\label{fig:digiscope_psk_nosig}
+	\end{subfigure} ~
+    \begin{subfigure}[t]{0.3\textwidth}
+		\centering
+    	\includegraphics[width=1.0in]{digiscope-psk.png}
+        \caption{The display with a normal psk31 signal.  The vector flips between 0 and 6 o'clock}
+        \label{fig:digiscope_psk}
+	\end{subfigure} ~
+    \begin{subfigure}[t]{0.3\textwidth}
+		\centering
+    	\includegraphics[width=1.0in]{digiscope-psk-low.png}
+        \caption{AFC off and receive carrier set below the center of the received signal}
+        \label{fig:digiscope_psk_low}
+    \end{subfigure}
+
+	\begin{subfigure}[t]{0.3\textwidth}
+		\centering
+		\includegraphics[width=1.0in]{digiscope-psk-high.png}
+		\caption{AFC off and receive carrier set above the center of the received signal.}
+		\label{fig:digiscope_psk_high}
+	\end{subfigure} ~
+    \begin{subfigure}[t]{0.3\textwidth}
+		\centering
+    	\includegraphics[width=1.0in]{digiscope-psk-history.png}
+        \caption{AFC enabled, Fading History Display Mode Selected (left click on scope)}
+        \label{fig:digiscope_psk_history}
+	\end{subfigure} ~
+    \begin{subfigure}[t]{0.3\textwidth}
+		\centering
+    	\includegraphics[width=1.0in]{digiscope-psk-history-amplitude.png}
+        \caption{AFC enabled, Fading History / Amplitude Display Mode Selected (2nd left click on scope)}
+        \label{fig:digiscope_psk_history_amp}
+    \end{subfigure}
+
+    \caption{PSK Digiscopes}
+	\label{fig:psk_digiscopes}
+
+\end{figure}
+
+\endlatexonly
+
+<br>
+
+You can see the effect of mistuning by slewing the carrier carrier
+control moving from low to high over the signal .  You must do
+this with AFC off.  Engage the AFC and the vectors will
+immediately snap to vertical positions.
+<br>
+
+You can alter the appearance of the phase vectors by left clicking on
+the digiscope display.  One click will give you a history of phase
+vectors that fade with time.  A second click will give you a
+history of phase vectors that both fade with time and are amplitude
+significant.  The third click returns you to the original phase
+vector display.
+<br>
+
+The effect is the same with QPSK signals except you will see 4 vectors that
+are 90 degrees from each other.
+<br>
+
+\section sec_rtty RTTY
+<br>
+
+
+\image html digiscope-rtty.png "Digiscope RTTY"
+\image latex digiscope-rtty.png "Digiscope RTTY" width=1.0in
+<br>
+
+The signal can be viewed in two different ways on the digiscope.  This
+is the time domain representation of the detected FSK signal.  The
+two yellow lines represent the MARK and SPACE frequencies.  This
+display is for Baudot, 45.45 baud, 182 Hz shift.  If the
+transmitting station were transmitting at 200 Hz shift the signal
+extremes would lie above and below the yellow lines.  Try tuning
+across the RTTY signal with the AFC disabled.  You will see the
+signal move above and below the yellow lines as you tune.  Then
+enable the AFC and the signal should rapidly move into the center
+region of the display.  This signal was about 3 - 6 dB above the
+noise floor.  It looked marginal on the waterfall but still gave
+good copy.
+
+\image html digiscope-rtty-2.png "Digiscope RTTY"
+\image latex digiscope-rtty-2.png "Digiscope RTTY" width=1.0in
+<br>
+
+This is the other digiscope display for RTTY.  You obtain this view by
+left clicking anywhere in the digiscope display window.  You can
+toggle back and forth between these views.  The MARK / SPACE
+frequencies are represented by the quadrature ellipses.  When the
+RTTY signal is properly tuned in the lines will be in quadrature and
+aligned as shown.  Tune across the RTTY signal and the MARK/SPACE
+lines will rotate around the center.  If the sending station is
+using a shift that is smaller than you have the decoder setting then
+the two lines will close toward the NW/SE quadrants.  If the
+sending station is using a shift that is greater than the decoder
+setting then the two lines will close toward the NE/SW quadrants.
+
+
+<br>
+\ref digiscope_display_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/DominoEX.txt b/fldigi_doxygen/user_src_docs/DominoEX.txt
new file mode 100644
index 00000000..156a729c
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/DominoEX.txt
@@ -0,0 +1,67 @@
+/**
+\page  domino_ex_page DominoEX
+
+\tableofcontents
+
+The modem code for dominoEX uses a wide band multiple frequency
+detector that can lock on and detect the incoming signal even when
+badly mistuned.  Frequency domain oversampling is used to allow
+proper tone detection without the need for AFC.  The AFC control does
+not alter the decoder in any way.
+<br>
+
+
+The waterfall and digiscope will appear as:
+<br>
+
+\image html dominoex-1.png "DominoEX"
+\image latex dominoex-1.png "DominoEX" width=6.5in
+<br>
+
+The text displayed in the status area is
+the secondary text being sent by the transmitting station.  When
+the keyboard buffer is empty the dominoEX modem transmits text from the
+secondary text buffer.  Your secondary text buffer can be edited
+on the DominoEX configuration tab.
+<br>
+
+The digiscope display represents the tone pairs moving through the tone
+filters. You can also use an alternate digiscope display (left click on
+the digiscope display area).
+<br>
+
+\image html dominoex-1a.png "DominoEX"
+\image latex dominoex-1a.png "DominoEX" width=1.0in
+<br>
+
+In this display mode the red line represents the center of the multiple
+tone bins that are in the detector.  The dots will be blurry if the AFC is
+not locked on and become very distinct when AFC lock has been achieved.  The
+tone dots will move from bottom to top (opposite the direction of the
+waterfall).
+<br>
+
+This is the same signal mistuned:<br>
+<br>
+
+\image html dominoex-1a.png "DominoEX Mistuned"
+\image latex dominoex-1a.png "DominoEX Mistuned" width=1.0in
+<br>
+
+and with the signal badly mistuned:
+<br>
+
+\image html dominoex-3.png "DominoEX Mistuned"
+\image latex dominoex-3.png "DominoEX Mistuned" width=6.0in
+<br>
+
+See \ref domino_ex_configuration_page "DominoEX Configuration".
+<br>
+
+<br>
+\ref domino_ex_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Doxyfile b/fldigi_doxygen/user_src_docs/Doxyfile
new file mode 100644
index 00000000..671468b0
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Doxyfile
@@ -0,0 +1,79 @@
+#
+#
+#
+# Copyright (C) 2013 Robert Stiles, KK5VD.
+#
+# Permission to use, copy, modify, and distribute this software and its
+# documentation under the terms of the GNU General Public License is hereby
+# granted. No representations are made about the suitability of this software
+# for any purpose. It is provided "as is" without express or implied warranty.
+# See the GNU General Public License for more details.
+#
+# Documents produced by Doxygen are derivative works derived from the
+# input used in their production; they are not affected by this license.
+
+PROJECT_NAME         = "FLDIGI Users Manual"
+PROJECT_NUMBER       = 3.21
+PROJECT_BRIEF        =
+ALLEXTERNALS         = NO
+CASE_SENSE_NAMES     = NO
+DISABLE_INDEX        = NO
+DOXYFILE_ENCODING    = UTF-8
+INPUT_ENCODING       = UTF-8
+ENABLE_PREPROCESSING = NO
+ENABLED_SECTIONS     = logo_on
+EXTRACT_ALL          = NO
+EXTRACT_PRIVATE      = NO
+EXTRA_PACKAGES       = graphicx caption subcaption float
+FILE_PATTERNS        = *.cpp *.h *.txt
+GENERATE_HTML        = YES
+GENERATE_HTMLHELP    = NO
+GENERATE_LATEX       = YES
+GENERATE_MAN         = NO
+GENERATE_RTF         = NO
+GENERATE_TREEVIEW    = NO
+GENERATE_XML         = NO
+HTML_COLORSTYLE_SAT  = 0
+HTML_FOOTER          =
+HTML_HEADER          =
+IMAGE_PATH           = ../images ../images/w4tv
+INPUT                = index.txt \
+	fldigi_configuration.txt fldigi_logging.txt \
+	fldigi_macros.txt fldigi_modems.txt fldigi_operating.txt \
+	fldigi-static.txt fldigi_developer.txt \
+	New-Install.txt colorsandfonts.txt \
+	configcallsigndb.txt configContestia.txt configCW.txt \
+	configDomEX.txt configFH.txt ConfigID.txt ConfigMisc.txt \
+	configMT63.txt configOlivia.txt ConfigOperator.txt configPSK.txt \
+	configRTTY.txt configThor.txt ConfigUI-browser.txt \
+	ConfigUI-contest.txt ConfigUI-general.txt ConfigUI-logserver.txt \
+	ConfigUI-macros.txt ConfigUI-WF-controls.txt ConfigWaterfall.txt \
+	SoundCardSetup.txt Contest-How-To.txt cabrilloreporter.txt \
+	Logbook.txt LogExports.txt working_logs.txt Macros.txt \
+	InlineMacroTags.txt advanced_qsy.txt execmacro.txt CW.txt \
+	DominoEX.txt hell.txt Contestia.txt MFSK.txt MT63.txt \
+	Navtex.txt psk.txt Olivia.txt RTTYFSK.txt Thor.txt \
+	throb.txt tune.txt WEFAX.txt WWV-xmt.txt FrequencyAnalysis.txt \
+	DigiscopeDisplay.txt DigiWWV.txt MousingKeyboardShortcuts.txt \
+	Multiples.txt Notifier.txt OperatingControls.txt RST-RSQ.txt \
+	Spotter.txt Synop.txt TransceiverControl.txt UTF8.txt \
+	pskmail_config.txt PskViewer.txt DXCC_list.txt \
+	KeyboardAndKeys.txt KML.txt support_data.txt Installing.txt WindowsOS.txt \
+	Wizard.txt Menus.txt ModeTable.txt CWkeying.txt  \
+	PseudoFSK.txt w5zit-interface.txt rigxml.txt commandline.txt \
+	buildinfo.txt xmlrpc-control.txt parseUALR.txt ualr-telnet.txt \
+	map.txt License.txt Recognitions.txt
+INCLUDE_PATH         = .
+EXAMPLE_PATH         = .
+OUTPUT_DIRECTORY     = ../user_docs
+OUTPUT_LANGUAGE      = English
+PDF_HYPERLINKS       = YES
+PERL_PATH            = /usr/bin/perl
+QUIET                = NO
+RECURSIVE            = NO
+SEARCHENGINE         = NO
+STRIP_CODE_COMMENTS  = NO
+TAGFILES             =
+USE_PDFLATEX         = YES
+WARNINGS             = YES
+
diff --git a/fldigi_doxygen/user_src_docs/FrequencyAnalysis.txt b/fldigi_doxygen/user_src_docs/FrequencyAnalysis.txt
new file mode 100644
index 00000000..116eaa88
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/FrequencyAnalysis.txt
@@ -0,0 +1,54 @@
+/**
+\page  frequency_analyzer_page Frequency Analyzer
+
+\tableofcontents
+<br>
+<br>
+
+Fldigi can be used to accurately measure the frequency of a remote signal
+that is transmitting a steady carrier.
+<br>
+
+\image html FreqAnal.png "Frequency Analyzer"
+\image latex FreqAnal.png "Frequency Analyzer" width=6.5in
+<br>
+
+I have set the sound card up using the WWV modem and have it adjusted
+for the proper PPM offset on receive.  I followed the frequency calibration
+procedure that ICOM recommends for the IC-746PRO, adjusting WWV at
+10 MHz for a zero beat.
+<br>
+
+Then fldigi was used in the "Freq Analysis" mode to track the WWV carrier
+at 10 MHz.  In this mode the decoder is merely a very narrow band
+AFC tracking filter.  The filter bandwidth is set to 2 Hz and the
+tracking time constants to about 5 seconds.  Future releases will
+probably make both of these user adjustable.  When the signal is
+being tracked the digiscope (right hand display) will be a horizontal
+line.  If the signal is very noisy and tracking difficult the
+digiscope will jump and become wavy.  You can see from the above
+image that I am tracking about 0.22 Hz high on WWV.  I have
+repeated this measurement at various times during the day and on
+various days with nearly the same result.  So I am comfortable
+with knowing that my local oscillator is just a little low (that is why
+the Frequency reads high).
+<br>
+
+ARRL frequently announces a frequency measurement test (FMT) which takes
+place on 160, 80 and 40 meters.  This is a chance to test your
+skills in frequency measurement.  You should be able to make a
+submission to the FMT using this technique.  Make corrections to the FMT
+transmission based upon your WWV measurement.  You may have to adjust
+for other local oscillator effects as well.  If you have some good
+ways to measure and correct for these I would be glad to share them
+with the other fldigi users.
+<br>
+
+<br>
+\ref frequency_analyzer_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/InlineMacroTags.txt b/fldigi_doxygen/user_src_docs/InlineMacroTags.txt
new file mode 100644
index 00000000..15afb41b
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/InlineMacroTags.txt
@@ -0,0 +1,198 @@
+/**
+\page  inline_macro_page Inline Macros
+
+\tableofcontents
+
+
+The following macro tags will be parsed and acted upon then they occur
+during the transmission of the macro.
+<br>
+
+ Tag                       | Description
+:------------------------: | :-----------------
+\<!WPM:NN\>                | CW words per minute
+\<!POST:+/-nn.n\>	       | CW post delay
+\<!PRE:nn.n\>	           | CW pre delay
+\<RISE:nn.n\>\<RISE:nn.n\> | CW rise/decay time
+\<!MODEM: ,...\>           | Change to specified modem with parameters
+\<!GOHOME\>	               | Move audio carrier to mode sweet spot frequency
+\<!GOFREQ:NNNN\>	       | Move audio carrier to specific audio frequency
+\<!QSY:FFF.F[:NNNN]\>      | Move to specific RF and Audio frequency
+\<!IDLE:NN.nn\>	        | Transmit idle signal for specified number of seconds
+\<!WAIT:NN\>	           | Wait (no audio) for specified number of seconds
+\<!WPM:ww[:ff]\>	       | CW - ww = WPM, optional ff = Farnsworth wpm
+
+<br>
+
+Note that each of these tags is identical to their immediate mode
+counterparts.  The exception is the addition of the exclamation
+mark following the leading '\<'.  The use of these tags is best
+explained by example.
+<br>
+
+
+\section cw_code_practice CW Code Practice Transmission
+
+\verbatim
+<MODEM:CW><TX>
+<!GOFREQ:600><!WPM:10:15>
+NOW IS THE TIME - now 180 wpm
+<!IDLE:2><!RISE:1.0><!PRE:0.4><!POST:+0.2><!WPM:180>
+FOR ALL GOOD MEN TO COME TO THE AID of their country.
+now 30 wpm<!IDLE:2>
+<!WPM:30>de <MYCALL> k
+<RX>
+\endverbatim
+<br>
+
+<ul>
+  <li>Modem type is changed to CW before start of transmission (\<MODEM:CW\>)
+  does not have the addition of the ! symbol</li>
+  <li>Audio carrier is changed to 600 Hertz</li>
+  <li>Transmit WPM set to 30 words per minute, followed by text</li>
+  <li>Transmit is silent for 2 seconds</li>
+  <li>Rise time, pre and post delays are adjusted and the WPM changed to 180
+  words per minute</li>
+  <li>Text is sent at 180 WPM</li>
+  <li>WPM changed to 30 words per minute, followed by identification string
+  and signoff</li>
+  <li>Return to receive</li>
+</ul>
+
+This is a more complex macro that might be used for a code practice
+transmission such as the W1AW broadcast on 3580 KHz.<br>
+<br>
+
+\verbatim
+<MODEM:NULL>
+<!QSY:3579.200:800>
+<TX>
+<!MODEM:CW>
+<!WPM:5:15><!IDLE:2><FILE:/home/dave/fldigi.ft950/scripts/practice-5wpm.txt>
+<!WPM:10:15><!IDLE:5><FILE:/home/dave/fldigi.ft950/scripts/practice-10wpm.txt>
+<!WPM:15:15><!IDLE:5><FILE:/home/dave/fldigi.ft950/scripts/practice-15wpm.txt>
+<!WPM:18><!IDLE:10><FILE:/home/dave/fldigi.ft950/scripts/bulletin.txt>
+<!IDLE:5>end of broadcast de <MYCALL> k
+<RX>
+\endverbatim
+<br>
+
+\section qsy_test QSY:ffff.f:aaaa test
+
+\verbatim
+<MODEM:NULL><TX>
+<!QSY:3583.0:1750>
+<!MODEM:RTTY:170:45.45:5>
+RYRYRYRYRYRY de <MYCALL> k
+<RX>
+\endverbatim
+<br>
+
+<ul>
+	<li>Change modem type to NULL to suppress sending any signal when
+transmit enabled.  This is necessary to allow the transmit data
+stream to be processed.</li>
+	<li>Send frequency change command to transceiver, new frequency is 3583.0
+  		kHz.  Set audio frequency to 1750 Hz</li>
+	<li>Change modem to RTTY, 170 Hz shift, 45.45 Baud, 5 Bit code (standard
+	Baudot)</li>
+	<li>Send RY... text</li>
+	<li>Return to receive</li>
+</ul>
+
+\section advanced_qsy Advanced QSY operations
+
+Several QSY frequencies or ranges of frequencies provided by one increment,
+can be proposed, in which case the first frequency after the current
+frequency is chosen.
+
+\ref advanced_qsy_page
+<br>
+
+\section arrl_style_broadcast ARRL style broadcast in multiple modes
+
+\verbatim
+<MODEM:NULL>
+<!QSY:3594:915>
+<!MODEM:RTTY:170:45.45:5><!IDLE:2>
+<FILE:/home/dave/arrl_test/bulletin.txt>
+<!MODEM:NULL><!GOFREQ:1000><!IDLE:5><!MODEM:BPSK31><!IDLE:2>
+<FILE:/home/dave/arrl_test/bulletin.txt>
+<TX><RX>
+\endverbatim
+<br>
+
+<ul>
+  <li>Change modem type to NULL to suppress transmission and start the Tx
+  data stream processor</li>
+  <li>Send frequency change command to transceiver, new frequency is
+3594 kHz, audio frequency 915 Hz. Note that this puts the MARK tone at
+1000 Hz.</li>
+  <li>Change modem to RTTY 170 Hz shift, 45.45 baud (default is 5 bits).
+  Idle for 2 seconds.</li>
+  <li>Send the file contents of specified file</li>
+  <li>Change to NULL modem.  Turns off the RTTY diddle ... audio stream is
+  silent.</li>
+  <li>Change audio frequency to 1000 Hz.  Idle for 5 seconds (complete
+  silence of transmit)</li>
+  <li>Change modem type to BPSK-31.  Send BPSK idle for 2 seconds</li>
+  <li>Send the file contents of specified file</li>
+  <li>Return to receive (note that the \<TX\> can appear anywhere
+is the macro definition as it is executed when the macro text is
+parsed).  \<RX\> is always moved to the end of the Tx
+buffer.  It could also have appeared anywhere in the macro string.</li>
+</ul>
+
+\section appearance_tx_buffer Appearance of tx buffer
+
+\verbatim
+^!
+^!^!
+QST de W1HKJ
+Test bulletin for 9/7/2011
+QST de W1HKJ SK
+
+^!^!^!^!^!
+QST de W1HKJ
+Test bulletin for 9/7/2011
+QST de W1HKJ SK
+
+^r
+\endverbatim
+<br>
+
+This is the contents of the ARRL broadcast macro text at the time the
+macro button is pressed.  Each of the \<!... macro tags has been
+specified by the string "^!" which the Tx processor interprets as the
+command to process the top most tag in the first-in, first-out sequence
+of tags.  As each "^!" is executed the referenced tag is printed
+to the Rx buffer using color coded text.<br>
+<br>
+
+\verbatim
+<!QSY:3594:915>
+<!MODEM:RTTY:170:45.45:5>
+<!IDLE:2>
+
+QST DE W1HKJ
+TEST BULLETIN FOR 9/7/2011
+QST DE W1HKJ SK
+
+<!MODEM:NULL>
+<!GOFREQ:1000>
+<!IDLE:5>
+<!MODEM:BPSK31>
+<!IDLE:2>
+
+QST de W1HKJ
+Test bulletin for 9/7/2011
+QST de W1HKJ SK
+\endverbatim
+
+<br>
+\ref inline_macro_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Installing.txt b/fldigi_doxygen/user_src_docs/Installing.txt
new file mode 100755
index 00000000..e9dad569
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Installing.txt
@@ -0,0 +1,30 @@
+/**
+\page  install_from_source_page Installing from Source
+
+\tableofcontents
+
+The developers recommend that you build either fldigi from source or install
+from the repository associated with your distribution.  The repository may
+not be immediately available for the most current version number.  In that
+case you can try installing the binary distribution.  Keep in mind that the
+version numbers of the dependent shared libraries must match those on the
+machine used to create the binary.
+
+The source code for fldigi is very large and has a number of dependencies
+that must be satisfied before a successful compile.  If you are not familiar
+with compiling and linking source code you should probably practice on a
+simpler package before treading these waters. Please refer to the following
+web site for information on building for
+Linux, Windows and OS X.
+<br>
+
+<a href="https://fedorahosted.org/fldigi/wiki/Documentation/HOWTO#Buildingfromsource">Fldigi WIKI - build instructions</a>
+<br>
+
+<br>
+\ref install_from_source_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/KML.txt b/fldigi_doxygen/user_src_docs/KML.txt
new file mode 100644
index 00000000..3e6febad
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/KML.txt
@@ -0,0 +1,444 @@
+/**
+\page  kml_page KML
+
+\tableofcontents
+
+\image html KML-Logo.png "KML Logo"
+\image latex KML-Logo.png "KML Logo" width=1.0in
+<br>
+
+Section data_source Data sources
+<br>
+
+<a href="http://en.wikipedia.org/wiki/Keyhole_Markup_Language">Keyhole
+Markup Language</a>
+
+(KML) is an XML file format for geographic visualization in
+two-dimensional maps such as Google Maps and three-dimensional earth
+browsers such as Google Earth
+or <a href="http://en.wikipedia.org/wiki/Marble_%28software%29">Marble</a>.
+<br>
+
+Fldigi can generate data with geographical locations, which can be used to
+generate KML data. This list might expand in the future
+
+<ul>
+	<li>The emitting station of a
+	<a href="http://en.wikipedia.org/wiki/Navtex">Navtex</a> message.</li>
+	<li>The origin of a <a href="http://en.wikipedia.org/wiki/SYNOP">SYNOP</a>
+	weather report.</li>
+	<li>The Maidenhead locator of the user, as entered in fldigi user's
+	profile.</li>
+</ul>
+<br>
+
+\section kml_generation_navtex KML generation from Navtex messages
+
+\image html Navtex-Config-Tab-With-Kml.png "Navtex configuration tab with KML option"
+\image latex Navtex-Config-Tab-With-Kml.png "Navtex configuration tab with KML option" width=5.0in
+<br>
+
+Each Navtex message comes with the code of the sending station, also
+called <i>origin</i>.
+
+These messages are displayed, in KML files, at the coordinates of the
+sender. That is: KML placemarks are created or updated with these
+coordinates. Fldigi parses the Navtex reports, uses the station identifier
+to make a lookup in the Navtex stations file which contains geographical
+coordinates. These coordinates are used to create KML placemarks.
+<br>
+
+More explanation about how station coordinates are used, are given at
+the \ref navtex_and_sitorb_page "Navtex page".
+<br>
+
+Navtex messages are quite often sent with embedded coordinates of the event
+they describe (Ship wreck, oil exploration etc...). For example:
+\"<code>LIGHT BUOY MARKING DANGEROUS WRECK 58-01.2 NORTH 005-27.1 WEST</code>\"
+or \"<code>THREE MEN OVERBOARD IN PSN 39-07,7N 026-39,2E</code>\" . A
+future version will parse the content of the message, extracting raw
+coordinates, and will display a graphic entity at the location of the
+described event.
+<br>
+
+\section kml_generation_synop KML generation from SYNOP reports
+
+<a href="Synop.html">SYNOP</a> is a code used for reporting weather
+information and as such, is used to broadcast meteorological data by
+radio. One of the most important emitter is
+<a href="http://www.dwd.de/bvbw/generator/DWDWWW/Content/Schifffahrt/Sendeplan/Schedule__rtty__01,templateId%3Draw,property%3DpublicationFile.pdf/Schedule_rtty_01.pdf">Deutsche Wetterdienst which transmits them in RTTY</a>,
+and fldigi is able to decode them and generate KML placemarks at the
+location of the weather information.
+<br>
+
+
+\section kml_file_structure KML files structure
+<br>
+
+<b>The KML data are made of different files</b>
+
+<center>
+<table>
+<tr>
+<td> <b><i><code>fldigi.kml</code></i></b></td>
+<td>Entry point. Only this one has to be loaded. It never
+changes.</td>
+</tr>
+<tr>
+<td><b><i><code>styles.kml</code></i></b></td>
+<td>KML style sheet. Freely changeable by the user, for
+example to customize the icons.</td>
+</tr>
+<tr>
+<td><b><i><code>User.kml</code></i></b></td>
+<td>Location of the user based on
+his/her <a href="http://fr.wikipedia.org/wiki/Maidenhead_Locator_System">Maidenhead
+locator</a>.</td>
+</tr>
+<tr>
+<td><b><i><code>Synop.kml</code></i></b></td>
+<td>Synop weather reports displayed at the location of the
+WMO station, or ship, or buoy.</td>
+</tr>
+<tr>
+<td><b><i><code>Navtex.kml</code></i></b></td>
+<td>Navtex reports, displayed at the place of the emitting
+station. A future version will plot the position of the coordinates
+indicated in the Navtex messages themselves.</td>
+</tr>
+</table>
+</center>
+
+<br>
+\section extended_data Extended data
+
+When creating a new placemark, written in of the KML data files
+(<code>Synop.kml</code>, <code>Navtex.kml</code> etc... ) data are sent to
+the KML module in the form of key-value pairs and are written into two forms:
+<br>
+
+<ul>
+	<li>HTML content, in the <code>\<description\></code> tag,
+	surrounded by <code>CDATA</code> directives. The HTML format is chosen
+	exclusively for display purpose and might change at any new version.</li>
+	<li>Regular <code>\<ExtendedData\></code> XML tags: These data
+	are internally used by Fldigi to reload the previous session. The
+	format is stable and can be used by external applications. All useful
+	data are saved.</li>
+</ul>
+
+
+\section paramaters Parameters
+
+\image html KML-Config.png "KML configuration tab"
+\image latex KML-Config.png "KML configuration tab" width=5.0in
+<br>
+
+Fldigi maintains in a internal container, a set of placemarks which are data
+associated to geographical coordinates, an unique name, a set of
+key-value pairs and a timestamp. At regular intervals, a thread is
+woken up to save these geographical data to a KML file, in a
+specific directory. At this moment, a process can be started, running
+an external command. Depending on the type of data, a given
+file name will be used.
+<br>
+
+All KML files are accessible from an unique KML
+filename. Placemarks are identified  with an unique name, for
+example a vessel name, or their WMO identifier. Placemark with a moving
+position such as ships, can have their path visualized because they
+still cen be identified in two different reports. These reports can be
+kept as separate, or they can be merged into a single placemark: This
+depends on the distance between two placemarks with the same name,
+compared to the merging distance parameter.
+<br>
+
+Data can be kept for a given retention time,
+after which delay they are purged. At startup, former KML data can be
+reloaded, or cleaned up. Data as key-value pairs associated to a given
+placemarks can be displayed several ways.
+<br>
+
+All these parameters are controlled by the KML configuration tab.
+<br>
+
+
+\section destination_directory Destination directory
+
+\image html KML-Directory.png "Directory of generated KML files"
+\image latex KML-Directory.png "Directory of generated KML files" width=4.0in
+<br>
+
+The default destination directory where KML files are saved is a
+subdirectory called /kml in the fldigi users directory. For example on
+Linux: <code>$HOME/.fldigi/kml/</code> and
+<code>\<defaultpath\>/fldigi.files/kml</code> on Windows&trade;. This
+destination can be freely changed.
+<br>
+
+The file <code>fldigi.css</code> is created at installation, and is not changed
+later. Therefore it is possible to customize it by adding specific
+icons.
+<br>
+
+The file <code>fldigi.kml</code> is created by fldigi when it is not there,
+or when the refresh interval is changed.
+<br>
+
+If this destination directory is accessible from the internet, then it can
+be published to Google Maps.<br>
+
+<b>Note:</b>
+
+Files updates are atomic. This means that a file is not accessible by a
+reader until it is completely written and closed. This is achieved by
+writing into temporary files, which are atomically renamed (POSIX
+function <code>rename()</code> ) at the end of operation.
+<br>
+<br>
+
+Therefore, the KML destination directory can safely be accessed by one
+writer and multiple readers. Several sessions of fldigi might also updates
+different KML files, as long as the main <code>fldigi.kml</code> file is
+not changed.
+
+\section kml_root_file KML root file
+
+This is the default name of the entry file of the generated KML document,
+which by default is fldigi.kml. If it does not exist, it is generated with
+the list of possible source of KML data (Synop,
+Navtex etc...). If <a href="http://www.google.com/earth/index.html">Google
+Earth</a>  or <a href="http://marble.kde.org/">Marble</a>
+are installed on your machine, then they are associated to the file
+extension .kml and you just need to click on fldigi.kml to visualize
+it. It is automatically refreshed when fldigi adds new Synop weather
+reports or Navtex messages to it.
+<br>
+
+
+\section kml_refresh_interval KML refresh interval
+
+This delay, in seconds, is used at two places:
+<br>
+
+<ul>
+	<li>This is the frequency at
+	which new KML files are created, if new data is available</li>
+	<li>This is the refresh interval specified in the KML file with
+	tag \<refreshInterval\>.</li>
+	</ul>
+<br>
+
+This should not be too small, especially if the data files are big, otherwise
+fldigi will spend most of its time refreshing KML data, and accordingly
+Google Earth or Marble, reloading them.
+
+\section clean_up_on_startup Cleanup on startup
+
+By default, at startup, fldigi reloads the existing KML files, extracting
+the key-value pairs contained in the "ExtendedData" tags. However, it
+is possible to force fldigi to restart from scratch.
+<br>
+
+
+\section merge_distance Merging distance
+
+Different reports with the same placemark name can be merged into a
+single report if their distance is below a given threshold which is the
+merging distance. Otherwise, separate placemarks are created and joined
+by a red line, visible in the KML document.
+<br>
+
+\section kml_ballon_display_type KML balloon display type
+
+Reports are inserted in the KML document one after the other. These
+description data are visible as <i>KML balloons</i>, or when getting
+placemark properties. If they have the same name and are within the merging
+distance, they will form a single placemark. The descriptions of each
+report will be displayed and merged by three possible ways.
+<br>
+
+\subsection plain_text Plain text
+
+Description are inserted without any HTML formatting. Only special HTML
+entities such as ampersands are reformatted. This is especially useful
+if the KML document is later converted to GPX, because many GPS devices
+are not able to display HTML data.
+<br>
+
+\subsection html_tables HTML tables
+
+Each description of placemark is transformed into a HTML table labelled
+with the time stamp of the insertion. Here is an example of two Navtex
+messages from the same station at different times:
+<br>
+
+<table>
+<tr><td>2013-02-14 23:18</td></tr>
+<tr><td>Callsign</td><td>OST</td></tr>
+<tr><td>Country</td><td>Belgium</td></tr>
+<tr><td>Locator</td><td>JO11JE</td></tr>
+<tr><td>Message number</td><td>35</td></tr>
+<tr><td>Frequency</td><td>0</td></tr>
+<tr><td>Mode</td><td>TOR</td></tr>
+<tr><td>Message</td><td>191533 UTC NOV ;<br>
+WZ 1196<br>
+SELF CANCELING. CANCEL WZ 1192 (GA92) (MA33).<br>
+WALKER LIGHTBUOY NORMAL CONDITIONS RESTORED."</td></tr>
+<tr><td>2013-02-14 23:13</td></tr>
+<tr><td>Callsign</td><td>OST</td></tr>
+<tr><td>Country</td><td>Belgium</td></tr>
+<tr><td>Locator</td><td>JO11JE</td></tr>
+<tr><td>Message number</td><td>35</td></tr>
+<tr><td>Frequency</td><td>0</td></tr>
+<tr><td>Mode</td><td>TOR</td></tr>
+<tr><td>Message</td><td>... etc ...</td></tr>
+</table>
+<br>
+
+\subsection distance_html_matrix Distinct HTML matrix
+
+For the same KML placemark, the key will typically the same for all
+reports. More, some data are numeric. This is therefore convenient to
+group them in matrices:
+<br>
+
+Here is an example for SYNOP weather data, made of three reports:<br>
+<br>
+
+<table><tr><td><br></td><td>2012-12-16 00:00</td><td>2012-12-17 06:00</td><td>2012-12-18 00:00</td></tr>
+<tr><td>Dewpoint temperature</td><td><br></td><td>Undefined</td><td>Undefined</td></tr>
+<tr><td>Figure</td><td><br></td><td>11</td><td><br></td></tr>
+<tr><td>Humidity</td><td>Unspecified</td><td><br></td><td><br></td></tr>
+<tr><td>Precipitations</td><td><br></td><td>Omitted, no observation</td><td>Omitted, no observation</td></tr>
+<tr><td>Pressure change</td><td>Not specified</td><td>Not specified</td><td>Not specified</td></tr>
+<tr><td>Sea level pressure</td><td>994 hPa</td><td>1000 hPa</td><td>1013 hPa</td></tr>
+<tr><td>Ship average speed</td><td>0 knots</td><td>0 knots</td><td><br></td></tr>
+<tr><td>Ship direction</td><td>Calm</td><td>Calm</td><td><br></td></tr>
+<tr><td>Station type</td><td><br></td><td>Automated station. No observation (No 7WW)</td>
+<td>Automated station. No observation (No 7WW)</td></tr>
+<tr><td>Temperature</td><td>9.5 deg C</td><td>9.3 deg C</td><td>10.3 deg C</td></tr>
+<tr><td>Value</td><td><br></td><td>37</td><td><br></td></tr>
+<tr><td>Visibility</td><td><br></td><td>4 km</td><td>4 km</td></tr>
+<tr><td>Wave height</td><td>3.6 meters</td><td>4.7 meters</td><td><br></td></tr>
+<tr><td>Waves height</td><td>3.5 meters</td><td>4.5 meters</td><td><br></td></tr>
+<tr><td>Waves period</td><td>8 seconds</td><td>8 seconds</td><td><br></td></tr>
+<tr><td>Wind direction</td><td><br></td><td>265 degrees</td><td>275 degrees</td></tr>
+<tr><td>Wind speed</td><td><br></td><td>33 knots (Estimated)</td><td>15 knots (Estimated)</td></tr>
+</table>
+<br>
+
+
+\section data_retention_time Data Retention Time
+
+Data may be automatically purged based on their time-stamp and a maximum
+retention time in hours. If the retention time is zero, then data are kept
+for ever.
+<br>
+
+
+\section command_run_kml Command run on KML creation
+
+This command is executed at regular times, by default 180 seconds, and
+only if new data was written to any KML files. The first time this
+command is run, its process id is stored. Next time this command must
+be run, we check if this process is still running. If yes, no new
+process is created.
+
+<p>
+The intention is to handle the same way, programs
+which should always be running, for example KML visualizers, and on the
+other hand, one-shot scripts or converters. Typical situations are:
+</p>
+
+<ul>
+	<li>Starting a program such
+	as <a href="http://www.google.com/earth/index.html">Google
+	Earth</a>  or <a href="http://marble.kde.org/">Marble</a>, only once per
+	session.</li>
+	<li>They will be automatically restarted if they crash, because
+	their <a href="http://en.wikipedia.org/wiki/Process_identifier">process identifier</a>
+	is not present anymore.</li>
+	<li>Run as needed conversion programs such as GpsBabel, to
+	another format (<a href="http://en.wikipedia.org/wiki/GPS_eXchange_Format">GPX</a>). Or a <a href="http://en.wikipedia.org/wiki/FTP">FTP</a> transfer to a remote platform, for
+	inclusion of KML files in Google Maps.</li>
+	<li>Accordingly, do not restart this conversion process as long
+	it is not finished (FTP transfers might take long)</li>
+</ul>
+
+
+
+\subsection example_of_commands Example of commands
+
+\subsubsection ftp_transfer FTP Transfer
+
+A new transfer - and
+a new process - must be initiated at each KML file save. A script is
+created for this purpose, and the command can be:
+<br>
+
+<code>
+fldigi/scripts/ftp_kml_files.sh ftpperso.free.fr MyFtpUserName
+MyPassword kml</code>
+<br>
+
+\image html Google-Maps-Kml.png "KML files displayed in Google Maps"
+\image latex Google-Maps-Kml.png "KML files displayed in Google Maps" width=6.0in
+<br>
+
+
+An obvious use is to save these file to a remote machine where they
+can be accessed with a public URL. This URL can then be given as CGI
+parameter to <a href="http://maps.google.com/">Google Maps</a>
+which will display the placemarks on a map. There
+are <a href="https://developers.google.com/kml/documentation/mapsSupport">limitations</a>
+on the maximum size of KML files which have to be smaller than 10 megabytes.
+<br>
+
+Note that KML files are for the moment not compressed into KMZ files.
+<br>
+
+An FTP copy is not necessary if the destination directory for KML files
+storage is public (That is, accessible from the Internet).
+
+\subsubsection launch_google_earth Launch google-earth
+
+The program will only be launched once, because its process id is still
+present. The command can be:
+<br>
+
+<code>googleearth $HOME/.fldigi/kml/fldigi.kml</code>
+<br>
+
+It is possible to change the icons by customizing the file
+<code>styles.kml</code>.
+<br>
+
+\image html GoogleEarth.png "Google Earth"
+\image latex GoogleEarth.png "Google Earth" width=6.0in
+<br>
+
+
+\subsubsection gps_babel_conversion GPS Babel conversion
+
+The command <a href="http://www.gpsbabel.org/">GpsBabel</a>,
+for example, will selectively convert the KML file of Synop
+reports. It is generally advised to generate plain text description
+tags in the KML files, because GPS devices might not be able to
+correctly display HTML data. The command can be:
+<br>
+
+<code>gpsbabel -i kml -f $HOME/.fldigi/kml/Synop.kml -o gpx -F out.gpx</code>
+<br>
+
+The generated files can for example be fed
+into <a href="http://www.xastir.org">Xastir</a>.
+<br>
+
+<br>
+\ref kml_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/KeyboardAndKeys.txt b/fldigi_doxygen/user_src_docs/KeyboardAndKeys.txt
new file mode 100644
index 00000000..f3fab511
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/KeyboardAndKeys.txt
@@ -0,0 +1,113 @@
+/**
+\page keyboard_operation_page  Keyboard Operation
+
+\tableofcontents
+
+The transmit buffer for fldigi is type ahead which means that you
+can be typing text while the program is sending an earlier part of your
+transmitted message.
+
+Newly entered text appears in black and text which has been transmitted
+is changed to red.  You can backspace into the red area. When you do and
+the modem in use supports the BS character it will be sent to the receiving
+station.  If you monitor PSK and MFSK signals you will often find operators
+backspacing over previously sent text.  It's probably just as easy to just
+send XXX and retype that part of the message, but we have gotten used to
+word processors, email, etc. that allow us to send perfect (right) text, so
+we expect our digital modems to do the same.  Let's see, what was that
+prosign often used in CW for oooops.
+<br>
+
+All of the alpha numeric keys perform as you would expect, entering
+text into the transmit buffer.  There is one very important
+exception:
+<br>
+
+The caret "^" symbol.  This is used in the macro expansion routine
+and also used by the transmit buffer evaluator.  A ^r puts fldigi into
+receive mode.  So you can enter the ^r (caret followed by the r) at the end
+of your transmit buffer and when the sent character cursor (red chars) gets to
+that point the program will clear the text and return to the receive
+mode.
+<br>
+
+You can load the transmit buffer with any ASCII Text file of your
+choice.  Merely right click in the buffer window and select from
+the pop-up menu.  You can also short cut to the ^r from
+this popup.
+<br>
+
+Many ops (including me) do not like to be tied to a mouse.  The
+fldigi text widget supports some short cuts to make your life easier:
+<br>
+
+<ul>
+    <li>Pause/Break - a transmit / receive - pause button. </li>
+    <ul>
+        <li>if you are in the receive mode and press the Pause/Break key the
+        program will switch to the transmit mode.  It will begin transmitting
+        characters at the next point in the transmit buffer following the red
+        (previously sent text).  If the buffer only contains unsent text,
+        then it will begin at the first character in the buffer.  If the
+        buffer is empty, the program will switch to transmit mode and
+        depending on the mode of operation will send idle characters or
+        nothing at all until characters are entered into the buffer.</li>
+
+       <li>if you are in the transmit mode and press the Pause/Break key
+       the program will switch to the receive mode.  There may be a slight
+       delay for some modes like MFSK, PSK and others that require you to
+       send a postamble at the end of a transmission.  The transmit text
+       buffer stays intact, ready for the Pause/Break key to return you to
+       the transmit mode.</li>
+
+       <li>Think of the Pause/Break key as a software break-in capability.</li>
+  </ul>
+
+  <li>Esc - </li>
+  <ul>
+      <li>Abort transmission. - immediately returns the program to receive,
+      sending the required postamble for those modes requiring it. The
+      transmit buffer is cleared of all text.</li>
+
+      <li>Triple press on Esc - terminates the current transmission without
+      sending a postamble - The PANIC button.</li>
+  </ul>
+
+  <li>Ctrl-R will append the ^r (return to receive) at the end of the
+  current text buffer.</li>
+
+  <li>Ctrl-T will start transmitting if there is text in the transmit
+  text window.</li>
+
+  <li>Alt/Meta-R will perform the same function as the Pause/Break key</li>
+
+  <li>Tab moves the cursor to the end of the transmitted text (which
+  also pauses tx). A tab press at that position moves the cursor to the
+  character following the last one transmitted. CW operation is slightly
+  different, see the help for \ref cw_page .</li>
+
+  <li>Ctrl + three digits will insert the ASCII character designated by
+  that entry.</li>
+
+</ul>
+
+\section function_keys Function Keys
+
+Keys F1 through F12 are used to invoke the macro F1 - F12.  You
+can also just click on the macro key button associated with that
+function key.  There are 4 sets of 12 macros. If you press the numbered
+button on the macro button bar the next set of macros are referenced by
+the F1 - F12.   A right click on the numbered button provides a reverse
+rotation through the 4 sets of macro keys.  The respective macro set can be
+made available by pressing the Alt-1, Alt-2, Alt-3 or Alt-4 key
+combination.  Note that this is not Alt-F1 etc.
+<br>
+
+
+<br>
+\ref keyboard_operation_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/License.txt b/fldigi_doxygen/user_src_docs/License.txt
new file mode 100644
index 00000000..2fa36be1
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/License.txt
@@ -0,0 +1,47 @@
+/**
+\page license_page License(s)
+
+\tableofcontents
+
+<br>
+\section source_code_copyright Copyright
+
+Copyright &copy;
+<br>
+
+<ul>
+  <li>2006 through 2013 Dave Freese, W1HKJ</li>
+  <li>2007, 2008, 2009 Stelios Bounanos, M0GLD</li>
+  <li>2007, 2008, 2009 Leigh Klotz Jr., WA5ZNU</li>
+  <li>2007, 2008, 2009 Joe Veldhuis, N8FQ</li>
+  <li>2008, 2009 Stephane Fillod, F8CFE</li>
+  <li>2009 John Douyere, VK2ETA</li>
+  <li>2013 Remi Chateauneu, F4ECW</li>
+  <li>2013 Robert Stiles, KK5VD</li>
+</ul>
+
+This application and all supporting documentation is free software;
+you can redistribute it and/or modify it under the terms of the GNU
+Library General Public License as published by the Free Software
+Foundation; either version 2 of the License, or (at your option) any
+later version.
+<br>
+
+This program is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+Library General Public License for more details.
+<br>
+
+You should have received a copy of the GNU Library General Public
+License along with the source code for fldigi; if not, write to the Free Software
+Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+<br>
+
+<br>
+\ref license_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/LogExports.txt b/fldigi_doxygen/user_src_docs/LogExports.txt
new file mode 100644
index 00000000..8dc7b568
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/LogExports.txt
@@ -0,0 +1,58 @@
+/**
+\page  exporting_logbook_data Exporting Logbook Data
+
+\tableofcontents
+
+
+Fldigi provides automatic export of log records as they are recorded.  On
+Linux the data is forwarded to Xlog compatible programs using the SysV
+message queue system.  On Windows the records are exported via a temporary
+file structure and are accepted by Logger32.
+<br>
+
+The user may also export all or selected records consisting of all or
+selected fields.  Access to this export function of available from the
+menu "File/Log/Export ADIF", "File/Log/Export Text",
+and "File/Log/Export CSV".
+<br>
+
+\section export_adif Export ADIF
+
+Selecting the Export ADIF menu item opens the following dialog:<br>
+<br>
+
+\image html ExportSetup.png "Export Setup"
+\image latex ExportSetup.png "Export Setup" width=6.5in
+<br>
+
+If you want to export every record press the "Check All" in the left
+panel.  You can also select and deselect individual records. Choose which
+fields you want to export with the right panel controls.  Press the OK
+button to continue or Cancel to abort the operation.  A file chooser dialog
+will open which allows you to specify the name and location of the exported
+file.  Use the extension ".adi" on Windows and ".adif" on the other OS's.
+<br>
+
+\section export_text_csv Export Text / CSV
+
+The same Export Setup dialog is used for Text and CSV exports.
+<br>
+
+<br>The Text export produces a simple space delimited file with columns set
+at locations dictated by the field size for each field that is exported. It
+is suitable for use with a word processing program or for printing a hardcopy
+of your activities.
+<br>
+
+The CSV is a "Character Separated Value" file with the TAB character used
+as the field separator.  This type of file can be imported into nearly all
+spreadsheet programs such as Gnumeric, Open Office or MS Excel.
+<br>
+
+<br>
+\ref exporting_logbook_data "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Logbook.txt b/fldigi_doxygen/user_src_docs/Logbook.txt
new file mode 100644
index 00000000..3ed3b8b5
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Logbook.txt
@@ -0,0 +1,255 @@
+/**
+\page  qso_log_book_page QSO Logbook
+
+\tableofcontents
+
+
+Fldigi maintains a large set of QSO logbook fields that will probably be
+sufficient for casual operating, contesting and some certificate logging.  All
+of the fields that are captured in the logbook are maintained in an ADIF
+database that can be read by any logbook program that can read the ADIF text
+format.
+<br>
+
+\section list_of_log_fields List of Log Fields
+
+The complete set of logbook fields are:
+<br>
+
+ADIF FIELD |   | USE
+:--------- |:-:| :----------------------------------------------
+BAND       |   | QSO band (computed from frequency)
+CALL       | * | contacted stations call sign
+COMMENT    | * | comment field for QSO
+COUNTRY    | * | contacted stations DXCC entity name
+CQZ        |   | CQ zone
+DXCC       |   | contacted stations DXCC country code
+FREQ       | * | QSO frequency in MHz
+GRIDSQUARE | * | contacted stations Maidenhead Grid Square (Loc)
+IOTA       |   | Islands On The Air
+IOTA       |   | Islands-On-The-Air designator
+ITUZ       |   | ITU zone
+MODE       |   | QSO mode
+MYXCHG     |   | sent contest exchange
+NAME       | * | contacted operators name
+QSLRDATE   |   | QSL received date
+QSLSDATE   |   | QSL sent date
+QSO_DATE   | * | QSO data at start of contact
+QTH        | * | contacted stations city
+RST_RCVD   | * | received signal report
+RST_SENT   | * | sent signal report
+SRX        | * | QSO received serial number
+STATE      | * | contacted stations state
+STX        | * | QSO transmitted serial number
+TIME_OFF   | * | end time of QSO in HHMM format
+TIME_ON    | * | start time of QSO in HHMM format
+TX_PWR     | * | power transmitted by this station
+VE_PROV    | * | 2 letter abbreviation for Canadian Province
+XCHG1      | * | received contest exchange
+<br>
+
+\* - These fields are either captured on the main dialog, computed from
+internal values, or determined by configuration.
+<br>
+
+The data in the fldigi logbook can be exported to external text files;
+ADIF, text, and CSV (comma separated value).   The ADIF can be
+read by any ADIF compatible logbook program.  The text output is
+suitable for use in a wordprocessor and for printing.  The CSV can
+be read into many spreadsheet programs such as Excel, Open Office or
+Gnumeric.
+<br>
+
+\section digital_mode_signal_reports Digital Modes Signal Reports
+
+Fldigi does not enforce any rules on signal reporting.  It could very
+well do so for many of the modes in which signal quality is inherently
+measured as a part of the decoder.  Learning how to evaluate a
+signal, to properly report it, and then help in correcting deficiencies
+should be the goal of every amateur operator.  Please read further
+on using both \ref rst_rsq_page "RST and RSQ signal reports".
+<br>
+
+\section capturing_qso_data Capturing QSO Data
+
+Fldigi supports two QSO capture panels.  The first for casual QSO logging
+<br>
+
+\image html log-qso.png "QSO capture panel"
+\image latex log-qso.png "QSO capture panel" width=6.5in
+<br>
+
+and the second for contest fields
+<br>
+
+\image html log-contest.png "Contest capture panel"
+\image latex log-contest.png "Contest capture panel" width=6.5in
+<br>
+
+You might prefer a more minimal view of the logging fields.  You can select
+to completely suppress the log panel or to use a single line view as in
+either of these two:
+<br>
+
+\image html log-qso-min.png "Minimal QSO Capture Panel"
+\image latex log-qso-min.png "Minimal QSO Capture Panel" width=6.5in
+<br>
+
+\image html log-contest-min.png "Minimal Contest Capture Panel"
+\image latex log-contest-min.png "Minimal Contest Capture Panel" width=6.5in
+<br>
+
+These are selectable from the View menu:
+<br>
+
+\image html menu-view.png "View menu"
+\image latex menu-view.png "View menu" width=1.5in
+<br>
+
+These three buttons are associated with logbook entries.
+<br>
+
+<ul>
+	<li> The globe button provides access
+	to \ref callsign_db_configuration_page "QRZ queries" </li>
+	<li>The brush button clears all of the logging entries </li>
+	<li>The save-into button saves the current logging entries into the
+	logbook</li>
+</ul>
+<br>
+
+\image html log-buttons.png "Log Buttons"
+\image latex log-buttons.png "Log Butons" width=0.5in
+<br>
+
+The frequency, Off (time off), and \#Out are filled by the program. All
+the others can be populated by manual keyboard entry or by
+selection from the Rx panel.  The time off, Off, is continuously
+update with the current GMT.  The time on, On, will be filled in
+when the Call is updated, but can be modified later by the operator.
+<br>
+
+A right click on the Rx panel brings up a context sensitive menu that will
+reflect which of the two QSO capture views you have open.
+<br>
+
+\image html menu-rx-popup-short.png "Normal: Short Menu"
+\image latex menu-rx-popup-short.png "Normal: Short Menu" width=1.0in
+<br>
+
+\image html menu-rx-popup-long.png "Normal: Long Menu"
+\image latex menu-rx-popup-long.png "Normal: Long Menu" width=1.0in
+<br>
+
+\image html menu-rx-popup-contest-short.png "Contest: Short Menu"
+\image latex menu-rx-popup-contest-short.png "Contest: Short Menu" width=1.0in
+<br>
+
+\image html menu-rx-popup-contest-long.png "Contest: Long Menu"
+\image latex menu-rx-popup-contest-long.png "Contest: Long Menu" width=1.0in
+<br>
+
+\image html menu-view.png "Contest: Long Menu"
+\image latex menu-view.png "Contest: Long Menu" width=1.0in
+<br>
+
+If you highlight text in the Rx pane then the menu selection will operate
+on that text.  If you simply point to a word of text and right
+click then the menu selection will operate on the single word.
+<br>
+
+Certain fields may also be populated with automatic parsing, Call, Name, QTH
+and Loc.   You point to the Rx pane word and then either
+double-left-click or hold a shift key down and left click.  The
+program will attempt to parse the word as a regular expression to
+populate the Call, Name, QTH, and Loc fields in that order.  It
+may place some non standard calls into the Loc field if they qualify as
+a proper Maidenhead Grid Square, such as MM55CQ.  That may be a
+special event station, but it also looks like a grid square locator
+value.  You need to decide when that occurs and use the pop up
+menu for those special cases.  The first non-Call non-Loc word
+will fill the Name field and subsequent qualify words will go into the
+QTH field.
+<br>
+
+A highlighted section of text, can always be copied
+to the clipboard for subsequent pasting elsewhere.  The Copy menu
+item will be active when text in the Rx pane has been highlighted. That
+text can also be saved to a file.  Use the
+"Save <span style="text-decoration: underline;">a</span>s..."
+menu item for that purpose.  All data fields in fldigi share a
+common set of keyboard shortcuts.  Linux users will recognize
+these as familiar Emacs shortcuts.  There is also a small popup
+menu that can be opened for each field by right clicking the contents with
+the mouse:
+<br>
+
+\image html menu-popup-edit-field.png "Menu Popup Edit Field"
+\image latex menu-popup-edit-field.png "Menu Popup Edit Field" width=1.6in
+<br>
+
+Highlighted text will be overwritten when a paste is selected.  Otherwise the
+clipboard will be pasted at the current cursor position.
+<br>
+
+You can query on-line and local CD based data base systems for data
+regarding a Call.  Set up your query using
+the \ref callsign_db_configuration_page "Callsign DB configuration tab".
+You make the query by either clicking on the globe button, or
+selecing "Look up call" from the menu.  The latter will also move
+the call to the Call field and make the query.
+<br>
+
+If you have previously worked a station the logbook will be searched for the
+most recent qso and fill the Name, Qth and other fields from the logbook. If
+the logbook dialog is open that last QSO will be selected for viewing in the
+logbook.
+<br>
+
+You open the logbook by selecting from the Logbook menu; Logbook/View.  The
+logbook title bar will show you which logbook you currently have open.
+Fldigi can maintain an unlimited (except for disk space) number of logbooks.
+<br>
+
+\image html logbook.png "Log Book"
+\image latex logbook.png "Log Book" width=6.0in
+<br>
+
+<br>
+You can resize the dialog to suit your screen size and operating needs.
+Fldigi will remember the placement and size for subsequent use.
+<br>
+
+You can create new entries, update existing entries, and delete entries
+using this dialog.  You can also search for an entry by callsign.  The browser
+can be sorted by Date, Callsign, Frequency or Mode.  The sort can
+be forward or backward with the most recent being the default selected
+entry after each sort.  You execute the sort by clicking on the
+column button at the top of the column to be sorted.  Each click
+causes the sort to reverse.  I like to view my log with the most
+recent at the top.  You might want to view it with the most recent on the
+bottom.
+<br>
+
+There are no frills such as keeping track of DXCC
+worked, fancy printouts etc.  Fldigi's logbook is primarily a
+capture function.  You can export your data for use with an
+external database or for uploading to LOTW or eQSL.  Data from
+those sources can also be used for importing into the logbook.
+<br>
+
+Exporting logbook data: \ref exporting_logbook_data "Log Exports".
+<br>
+
+Cabrillo reporting: \ref cabrillo_report_page "Contest Reports".
+<br>
+
+
+<br>
+\ref qso_log_book_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
+
diff --git a/fldigi_doxygen/user_src_docs/MFSK.txt b/fldigi_doxygen/user_src_docs/MFSK.txt
new file mode 100644
index 00000000..de0f5a28
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/MFSK.txt
@@ -0,0 +1,216 @@
+/**
+\page  mfsk_page MFSK
+
+\tableofcontents
+
+MFSK16 and MFSK8 are multi-frequency shift keyed (MFSK) modes with low symbol
+rate. A single carrier of constant amplitude is stepped (between 16 or 32 tone
+frequencies respectively) in a constant phase manner.  As a result, no
+unwanted sidebands are generated, and no special amplifier linearity
+requirements are necessary.  The tones selected are set by the
+transmitted (4 or 5 bit) bit pattern and a gray-code table.
+
+The mode has full-time Forward Error Correction, so it is very robust. Tuning
+must be very accurate, and the software will not tolerate differences between
+transmit and receive frequency.  The mode was designed for long path HF DX,
+and due to its great sensitivity is one of the best for long distance QSOs
+and skeds.  MFSK8 has improved sensitivity, but is very difficult to tune,
+and suffers more from Doppler. It is useful as the band fades out.
+<br>
+
+MFSK-32 and MFSK-64 are high baud rate and wide bandwidth modes designed for
+use on VHF and UHF.  These are very useful for send large documents or files
+when some transmission errors are can be tolerated.
+<br>
+
+This is an example of properly tuned MFSK16 signal with a s/n of
+approximately 9 dB.
+<br>
+
+
+\image html mfsk-9db.png " MFSK16 signal"
+\image latex mfsk-9db.png " MFSK16 signal" width=6.0in
+<br>
+
+The same signal viewed with the waterfall expanded to the x2 factor.<br>
+
+\image html mfsk-9db-x2.png " MFSK16 signal"
+\image latex mfsk-9db-x2.png " MFSK16 signal" width=1.5in
+<br>
+
+
+\section mfsk_picture_mode MFSK Picture Mode
+
+Fldigi can send and receive images using all MFSK baud rates. When operating
+with other modem programs you should limit sending pictures to the MFSK-16
+baud rate.  The program can send and receive MFSK images in both black and
+white and in 24 bit color.  The transmission mode for MFSKpic is similar
+to FAX.
+<br>
+
+Reception of an MFSKpic transmission is fully automatic.  The
+MFSKpic transmission has a preamble sent which will be visible on the
+text screen.  The preamble reads as "Pic:WWWxHHH;" or "Pic:WWWxHHHC;" for b/w
+or color respectively.  The WWW and HHH are numbers specifying the width and
+height of the picture in pixels.
+<br>
+
+The successful reception of a MFSKpic is highly dependent on s/n
+conditions.  The data is transmitted as an FM modulated signal and
+is subject to burst and phase noise on the transmission path.  It
+can provide excellent photo transmission on a really good path.
+<br>
+
+\image html mfskpix-bee.png "Received MFSK Image"
+\image latex mfskpix-bee.png "Received MFSK Image" width=2.0in
+<br>
+
+This is an example of a photo received on a bench test.  The received
+image is an exact replica of the transmitted image.  The color depth is
+a full 24 bits.
+<br>
+
+Images should be carefully selected for size before beginning a
+transmission.  To calculate the transmit time for an image use the
+following formula:
+<br>
+
+Time(sec) = W * H / 1000 for black and white
+<br>
+
+Time(sec) = W * H * 3 / 1000 for color
+<br>
+
+Where the W and H are the dimensions of the photo in pixels.  A
+200 x 200 image will take 120 seconds to transmit in color and 40
+seconds to transmit in b/w.  The symbol rate for this mode is 1000
+data bytes per second.  The color image consists of 3 bytes; red,
+blue and green for each pixel.
+<br>
+
+\image html k0og.png "Picture received from K0OG"
+\image latex k0og.png "Picture received from K0OG" width=2.0in
+
+This is an example of a picture received live on 80 meters (thanks K0OG)
+<br>
+
+Received images are saved in the default folder $HOME/.fldigi/images
+(Linux) or \<defaultpath\>/fldigi.files/images (Windows).
+<br>
+
+\section tx_image Transmitting an Image
+
+
+\image html Xmt-Pix.png "Xmit Picture Dialog box"
+\image latex Xmt-Pix.png "Xmit Picture Dialog box" width=3.0in
+<br>
+
+You can only transmit an image while in the MFSK-16 mode.  The
+image can be prepared for transmission while in the receive mode. Right click
+in the transmit text box and select "Send Image" from the popup menu. This
+will open up the transmit image dialog which will be blank to start.
+<br>
+
+Press the "Load" button and a file selection dialog will allow you to
+select a suitable image for transmit.  The file selection dialog
+also has a preview capability so you will see what the image looks like.
+<br>
+
+You may also open a window manager file browser and drag and drop an image
+to the center part of the <b><i>Send image</i></b> dialog.
+<br>
+
+The "X1" button is a three-way toggle that allows you to transmit an image
+file in
+<br>
+X1 - normal and compatible with other modem programs
+<br>
+X2 - double speed, and<br>X4 - quadruple speed.  X2 and X4 are fldigi
+specific image modes.
+<br>
+
+\image html Xmt-Pix1.png "Xmit Picture Dialog Box with Image"
+\image latex Xmt-Pix1.png "Xmit Picture Dialog Box with Image" width=3.0in
+<br>
+
+The Send image dialog after the image was drag and dropped onto the
+dialog.
+<br>
+
+The properties box said this image was 120 x 119 24 bit
+color.  So it should take 42.8 seconds to transmit in full color.  You can
+send a color or a b/w image in either color mode or b/w mode.  If you
+transmit a color image in b/w the program will convert the image before
+transmitting.  If you transmit a b/w image as full color you are in effect
+transmitting redundant information, but it can be done.  I selected
+the "XmtClr" button for a trial run.  Pressing either the "XmtClr"
+or "XmtGry" will put the program and the transceiver into the transmit
+mode if it was in the receive mode. The image is cleared and then repainted
+as the transmission proceeds.  You see the same image progression that
+the receiving station should see.  The main display also displays the \%
+completion on the status bar.  Hold the mouse over either the
+XmtClr or the XmtGry button and the tooltip will tell you the transmit
+time for this image.
+<br>
+
+You may abort the transmission at any time by pressing the "Abort Xmt"
+button.  That will return you to the text mode for MFSK.  You
+will then have to toggle the T/R button if you want to return to
+receive.
+<br>
+
+\image html Xmt-Pix3.png "Received MFSK Image"
+\image latex Xmt-Pix3.png "Received MFSK Image" width=1.5in
+<br>
+
+The receiving program decodes the "Pic:110x119C;" as a color picture
+110 wide by 119 high.  Here is shown being received on a computer
+running Vista Home Premium.
+<br>
+
+
+\image html Xmt-Pix4.png "Waterfall of a MFSK Image"
+\image latex Xmt-Pix4.png "Waterfall of a MFSK Image" width=3.5in
+
+This is what the waterfall will look like during the reception of an
+MFSK-16 image.
+<br>
+
+The actual spectrum signature will vary with the image bytes being
+transmitted.  The waterfall scale is in the x4 mode and the above
+photo was being transmitted in 24 bit color for this screenshot. The
+waterfall clearly shows that the image transmission is within the bandwidth
+occupied by MFSK-16.
+<br>
+
+\section picture_slant Picture with a slant
+
+If either the send, receive or both ends of the transmission are using an
+uncalibrated sound card whose sampling rate is not an exact multiple of
+8000 Hz the resulting picture at the receive end will appear slanted.  The
+degree of slant is directly related to the accumulation of the frequency
+error at both ends of the transfer.  Stations wishing to send and receive
+MFSK pic's should calibrate their sound card.
+The \ref digiscope_display_wwv_mode "WWV calibration mode" is used to
+measure and set the parts per million (ppm) correction factor for the
+sound card.
+<br>
+
+Your sound system may be fully corrected, but the sending station may have
+an uncorrected sound card.  You can usually correct for small
+errors in the following way.  After the full picture is received
+move the mouse to bottom left or right corner of the slanted images
+(the corner that clearly visible).  Then left click on that
+corner.  The program will correct for the slant.  The
+correction will not be perfect but it may help to make the image more
+viewable.
+<br>
+
+
+<br>
+\ref mfsk_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/MT63.txt b/fldigi_doxygen/user_src_docs/MT63.txt
new file mode 100755
index 00000000..75a15b66
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/MT63.txt
@@ -0,0 +1,142 @@
+/**
+\page  mt63_page MT63
+
+\tableofcontents
+
+MT63 is an Orthogonal Frequency Division Multiplexed mode consisting of 64
+parallel carriers each carrying part of the transmitted signal.
+ The tones are differential BPSK modulated.  MT63 employs a
+unique highly redundant Forward Error Correction system which
+contributes to it robustness in the face of interference and facing.
+ The tones have synchronous symbols, and are raised cosine
+moduled.  This mode requires a very linear transmitter. Over-driving leads to
+excessive bandwidth and poorer reception.
+<br>
+
+The mode is very tolerant of tuning and fldigi will handle as much as 100
+Hz of mistuning.  This is very important since MT63 is often used
+in very low Signal to Noise ratios.  There are three standard modes:
+<br>
+
+<center>
+
+Mode      | Symbol Rate | Typing Speed       | Bandwidth
+:--------:|:-----------:|:------------------:|:---------:
+MT63-500  | 5.0 baud    | 5.0 cps (50 wpm)   | 500 Hz
+MT63-1000 | 10.0 baud   | 10.0 cps (100 wpm) | 1000 Hz
+MT63-2000 | 20 baud     | 20.0 cps (200 wpm) | 2000 Hz
+
+</center>
+<br>
+
+In addition there are two interleaver options (short and long) which can
+be set on the \ref mt63_configuration_page "MT63 configuration tab".  The
+default calling mode is MT63-1000.  If the short interleaver is used then
+one can expect some compromise in robustness.  The long interleaver results
+in somewhat excessive latency (delay between overs) for keyboard
+chatting.  MT63-1000 with the long interleaver has a latency of 12.8 seconds.
+<br>
+
+You can change from receive to transmit immediately upon seeing the other
+stations signal disappear from the waterfall.  You do not need to
+wait until the receive text completes.  Any remaining data in the
+interleaver will be flushed and the associated receive text printed
+quickly to the Rx pane.  Tx will commence right after the buffer
+is flushed.
+<br>
+
+MT63 may be operated in the default fixed audio frequency mode.  In this
+mode you are not allowed to randomly place of the signal on the waterfall.
+Your transmit signal, and also the received signal should be centered at
+750 Hz for MT63-500, 1000 Hz for MT63-1000, and 1500 Hz for MT63-2000.  If
+you click on the waterfall to move the tracking point it will be restored
+to the required position.
+
+The default mode, MT63-1000, looks like this on fldigi's waterfall.
+
+\image html mt63-1000.png "MT63-1000"
+\image latex mt63-1000.png "MT63-1000" width=1.75in
+<br>
+
+You can also elect to operate the MT63 modem in a "manual tune" mode
+(\ref mt63_configuration_page "MT63 configuration tab").
+The manual tune allows you to place both the Rx and the Tx signal to be
+anywhere within the confines of your SSB bandwidth.  This screen
+shot shows this capability:
+<br>
+
+\image html mt63-500.png "MT63-500 with QRM"
+\image latex mt63-500.png "MT63-500 with QRM" width=6.0in
+<br>
+
+This view also demonstrates how immune MT63 is to interference.
+The multiple PSK31 signals that appear on top of the MT63 signal did
+not degrade the decoder.  MT63 is usually used above 14073 MHz to avoid the
+possibility of this type of mode conflict.<br>
+
+<h4>Edited excerpts from Pawel Jalocha's official mt63 code release</h4>
+
+The MT63 modem is intended for amateur radio as a conversation (RTTY
+like) mode where one station transmits and one or more other stations
+can listen. In short, the modem transmits 64 tones in its baudrate specific
+bandwidth.  The differential bipolar phase modulation is used to encode 10
+bits of information per second on each tone. The user data in the form of
+7-bit ASCII characters is encoded as a set of 64-point Walsh functions. The
+bits are interleaved over 32 symbols (3.2 seconds) to provide resistance
+against both pulse and frequency selective noise or fading. The character
+rate equals to the symbols rate thus the modem can transmit 10 7-bit
+characters per second.
+<br>
+
+This modem can as well run in two other modes obtained by simple time
+scaling, the possible modes are summarized here:
+<br>
+
+<center>
+
+Bandwidth | Symbol Rate | Character Rate | Interleave / Char.
+:--------:|:-----------:|:--------------:|:------------------:
+500 Hz    | 5 baud      | 5 char / sec   | 6.4 or 12.8 sec
+1000 Hz   | 10 baud     | 10 char / sec  | 3.2 or 6.4 sec
+2000 Hz   | 20 baud     | 20 char / sec  | 1.6 or 3.2 sec
+
+</center>
+<br>
+
+For each mode the interleave factor can be doubled thus each character
+becomes spread over twice as long period of time.
+<br>
+
+The MT63 modem is made for single side band operation. The audio
+generated by the modem (sound card output) is applied to the SSB
+modulator. On the receiver side, the output of the SSB demodulator is
+put into the sound card input. The envelope of the MT63 signal is not
+constant as in other multi-tone systems - it is rather
+noise-like.  One must be careful not to overdrive the transmitter.
+<br>
+
+The receiver of the MT63 is self-tuning and self-synchronizing thus the
+radio operator is only required to tune into the signal with +/- 100 Hz
+accuracy. The modem will tell the actual frequency offset
+after it is synchronized. The operator <b>should not</b> try to correct
+this offset unless he is able to tune the radio receiver very slowly,
+because MT63 as a low rate phase modulated system cannot tolerate sudden
+frequency changes.
+<br>
+
+The MT63 is a synchronous system and it relies on the sampling rate to
+be the same at the receiver and the transmitter. At least the sampling
+rates should not be different by more that 10<sup>-4</sup>.
+<br>
+
+If you have calibrated your sound card to
+\ref digiscope_display_wwv_mode "WWV", then you will meet this requirement.
+<br>
+
+<br>
+\ref mt63_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/Macros.txt b/fldigi_doxygen/user_src_docs/Macros.txt
new file mode 100644
index 00000000..50fe4732
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Macros.txt
@@ -0,0 +1,439 @@
+/**
+\page  macros_sub_page Macros
+
+\tableofcontents
+
+Macros are short text statements that contain imbedded references to text
+data used by the program fldigi.   Macro definition files(s) are located
+in the $HOME/.fldigi/macros/ directory and all have the extention ".mdf". The
+default set of macros are contained in the
+file $HOME/.fldigi/macros/<b>macros.mdf</b>.
+
+Fldigi will create this file with a set of default macros on its first
+execution.
+<br>
+
+Fldigi supports up to 48 macro definitions in sets of 12.  Macro
+definitions are not recursive, that is; a macro cannot reference
+another macro or itself.
+<br>
+
+The imbedded references are similar to those used by DigiPan and other
+fine modem programs.  The imbedded reference is an uppercase plain
+text descriptor contained with the \<\> brackets.
+<br>
+
+
+\section macro_tags Macro tags
+
+<center>
+
+Macro       | Description
+:---------: | :----------------------------
+\<FREQ\>    | my frequency
+\<MODE\>    | mode
+\<MYCALL\>  | configuration call
+\<MYLOC\>   | configuration locator
+\<MYNAME\>  | configuration name
+\<MYQTH\>   | configuration QTH
+\<MYRST\>   | my RST
+\<ANTENNA\> | configuration antenna
+\<VER\>     | Fldigi version
+<br>
+
+Macro       | Description
+:---------: | :----------------------------
+\<CALL\>    | other stations callsign
+\<INFO1\>   | S/N or other data contained in first info field of status bar
+\<INFO2\>   | IMD or other data contained in second info field of status bar
+\<LOC\>     | other stations locator
+\<NAME\>    | other stations name
+\<QTH\>     | other stations QTH
+\<RST\>     | other stations RST
+<br>
+
+Macro       | Description
+:---------: | :----------------------------
+\<MAPIT\>   | map other stations locator on google
+\<MAPIT:adr \| lat \| loc\> | map other stations address, latitude-longitude <br> locator as specified
+<br>        | <br>
+\<CLRRX\>   | clear RX pane
+\<CLRTX\>   | clear TX pane
+<br>
+
+Macro       | Description
+:---------: | :----------------------------
+\<GET\>     | text to NAME/QTH
+\<TALK:on\|off\|t\> | Digitalk On, Off, Toggle; this is a Windows only tag <br> and Digitalk must be running
+\<LOG\>     | save QSO data to logbook immediately
+\<LNW\>     | log at xmt time
+\<CLRLOG\>  | clear log fields
+\<EQSL:[message\> |submit the current log entry to www.eQSL.cc This macro tag <br> should be put before \<LOG\> or \<LNW\>
+<br>
+
+Macro       | Description
+:---------: | :----------------------------
+\<QSOTIME\> | insert current logbook time HHMM, ie 0919
+\<ILDT\>    | insert current local date-time in iso-8601 format, ie 2011-08-28 04:16-0500
+\<LDT\>     | insert Local date-time, ie 2011-08-28 04:16-0500
+\<IZDT\>    | insert Zulu date-time in iso-8601 format, ie 08/28/2011 04:16 CDT
+\<ZDT\>     | insert Zulu date-time, ie 2011-08-28 09:16Z
+\<LT\>      | insert local time, ie 0416
+\<ZT\>      | insert zulu time, ie 0916Z
+\<LD\>      | insert local date, ie 2011-08-28
+\<ZD\>      | insert Zulu date, ie 2011-08-28
+\<WX\> <br> \<WX:xxxx\> | insert current weather data from METAR as specified on <br> WX configuration tab. see WX configure replace xxxx with the 4 letter <br> METAR designator for a report on a station other than the one specified on <br> the weather configuration tab.
+<br>
+
+Macro       | Description
+:---------: | :----------------------------
+\<CNTR\>    | insert current value of contest counter
+\<DECR\>    | decrement contest counter
+\<INCR\>    | increment contest counter
+\<XIN\>     | send exchange in string
+\<XOUT\>    | send exchange out string
+\<XBEG\>    | mark exchange in start
+\<XEND\>    | mark exchange in end
+\<SAVEXCHG\> | save marked text to contest exchange in
+<br>
+
+Macro     | Description
+:-------: | :----------------------------
+\<RX\>    | receive
+\<TX\>    | transmit
+\<TX/RX\> | toggle Transmit / Receive
+<br>
+
+Macro      | Description
+:--------: | :----------------------------
+\<SRCHUP\> | search UP for next signal
+\<SRCHDN\> | search DOWN for next signal
+<br>
+
+Macro       | Description
+:---------: | :----------------------------
+\<GOHOME\>   | return to waterfall cursor to sweet spot
+\<GOFREQ:NNNN\>  | move waterfall cursor to freq NNNN Hz
+\<QSYTO\>        | same as left-clk on QSY button
+\<QSYFM\>        | same as right-clk QSY button
+\<QSY:FFF.F[:NNNN]\> | Qsy to transceiver frequency in kHz, optional waterfall <br> (Audio) frequency in Hz (If not specified, it i not changed). Several QSY <br> frequencies, or ranges of frequencies provided by one increment, can be <br> proposed, in which case the first frequency after the current frequency <br> is chosen.
+<br>
+
+Macro       | Description
+:---------: | :----------------------------
+\<RIGMODE:mode\> | send CAT command to transceiver to change to a valid mode
+\<FILWID:width\> | send CAT command to transceiver to change to a valid filter <br> width example to QSY to sweetspot (center of bandpass filter) and select <br> narrow filter
+<br>
+
+Macro       | Description
+:---------: | :----------------------------
+\<QSYTO><FILWID:200\> <br> \<QSYFM><FILWID:2700\> | example to restore previous waterfall cursor frequency <br> and bandwidth
+\<FILE:\>              | insert text file; a file selection box will open when this tag is <br> selected during editing
+<br>
+
+Macro                    | Description
+:----------------------: | :----------------------------
+\<IDLE:NN.nn\>           | transmit idle signal for NN.nn sec
+\<TIMER:NN\>             | repeat this macro every NN sec
+\<TUNE:NN\>              | transmit single tone tune signal for NN sec
+\<WAIT:NN\>              | insert delay of NN seconds before transmitting
+\<REPEAT\>               | repeat macro continuously
+\<SKED:hhmm[:YYYYDDMM]\> | schedule execution to begin at time and optionally <br> date specified
+<br>
+
+Macro                 | Description
+:-------------------: | :----------------------------
+\<CWID\>              | transmit a CW callsign identifier
+\<ID\>                | transmit mode ID using waterfall video text
+\<TEXT\>              | transmit video text defined on ID configuration tab
+\<TXRSID:on\|off\|t\> | transmit RSID on, off, toggle
+\<RXRSID:on\|off\|t\> | receive RSID on, off, toggle
+\<NRSID:NN\>          | transmit multiple RsID bursts <br> NN < 0 will transmit NN bursts for current modem and then return to Rx <br>    NN > 0 will transmit NN bursts for current modem and continue in Tx <br>   NN = 0 will transmit 1 bursts and continue (same as NN = 1)
+\<DTMF:[Wn:][Ln:]\>   | tones transmit DTMF tone sequence at start of <br> transmission; options W-wait n msec, default 0 L-tone symbol length n <br> in msec; default 50 msec '-', ' ' and ',' insert silence symbol <br> eg: \<DTMF:W250:L100:1-256-827-3200\>
+<br>
+
+Macro                      | Description
+:------------------------: | :----------------------------
+\<POST:+/-nn.n\>           | CW QSK post-timing in milliseconds
+\<PRE:nn.n\>               | CW QSK pre-timing in milliseconds
+\<RISE:nn.n><RISE:nn.n\>   | CW rise time in milliseconds
+\<WPM:ww[:ff]\>            | CW WPM, ww = word rate, optional ff = Farnsworth rate
+<br>
+
+Macro                      | Description
+:------------------------: | :----------------------------
+\<RIGCAT:hex hex:retnbr\>  | RigCAT user commands
+\<RIGCAT:"string":retnbr\> | hex hex ... are sequential hexadecimal values <br> string is Ascii char sequence retnbr  <br> is number of bytes in xcvr response ':retnbr'  <br> is optional; retnbr set to 0 if missing
+<br>
+
+Macro               | Description
+:-----------------: | :----------------------------
+\<AFC:on\|off\|t\>  | AFC  on, off, toggle
+\<LOCK:on\|off\|t\> | lock waterfall cursor; on, off, toggle
+\<REV:on\|off\|t\>  | Reverse on, off, toggle
+<br>
+
+Macro            | Description
+:--------------: | :----------------------------
+\<QRG:text\>     | Insert current operating info with "text" into Rx stream, ie: <br> info text <<2013-01-12T21:18Z RTTY @ 14005000+0760>> which can be used to <br>return to a mode, rf, audio frequency.
+\<PAUSE\>        | Cause transmission to pause at place of occurance in macro <br> text.  "Pause/Break" key on keyboard resumes transmission
+\<TXATTEN:nn.n\> | set fldigi tx attenuator to value -30 dB <= val <= 0
+\<COMMENT:text\> | allow macro to contain a comment field; everything <br> between \< and \> is ignored by macro parser
+\<SAVE\>         | save the current macro definitions to the current file
+<br>
+
+Macro       | Description
+:---------: | :----------------------------
+\<MACROS:\> | load a new macro defs file; file prompt when editing macro
+
+<br>
+
+Macro            | Description
+:--------------: | :----------------------------
+\<CPS_TEST\>     | modem timing test internal string
+\<CPS_FILE:\>    | modem timing test, spec' file
+\<CPS_STRING:s\> | modem timing test, string 's'
+
+<br>
+
+Macro            | Description
+:--------------: | :----------------------------
+\<WAV_TEST\>     | WAV file; internal string
+\<WAV_FILE:\>    | WAV file; spec' file
+\<WAV_STRING:s\> | WAV file; string 's'
+
+</center>
+
+<br>
+
+\verbatim
+  * Added macro to insert QRG text into Rx stream
+	<QRG:text to insert>
+  * Added save macro <SAVE> tag
+  * Added export strings
+	- FLDIGI_LOG_FILE - current logbook file name
+	- FLDIGI_MACRO_FILE - current macro file name
+  * Added <PAUSE> tag
+	- returns to receive, but does not clear Tx buffer
+  * Added <TXATTEN:nn.n> <!TXATTEN:nn.n> tag to control
+	transmit attenuator control from within a macro.
+  * Added <COMMENT:text> macro tag
+	a do nothing that disappears from the transmitted
+	text
+\endverbatim
+
+<br>
+
+\section modem_macro_tags Modem macro tags
+
+Macro tags are also assigned to each supported modem type and sub-modem type
+that is supported by fldigi:
+
+<br>
+
+<center>
+<small>
+<br>             |<br>             | Data Modems      |<br>             | <br>
+:--------------: | :--------------: | :-------------: | :-------------: | :-------------:
+<MODEM:BPSK1000> | <MODEM:BPSK125>  | <MODEM:BPSK250> | <MODEM:BPSK31> | <MODEM:BPSK500>
+<MODEM:BPSK63>   | <MODEM:BPSK63F>  | <MODEM:CTSTIA:1000:16> | <MODEM:CTSTIA:1000:8> | <MODEM:CTSTIA:250:8>
+<MODEM:CTSTIA:500:16> | <MODEM:CTSTIA:500:8> | <MODEM:CTSTIA> | <MODEM:CW> | <MODEM:DOMEX4>
+<MODEM:DOMEX5>   | <MODEM:DOMEX8>   | <MODEM:DOMX11>   | <MODEM:DOMX16> | <MODEM:DOMX22>
+<MODEM:DOMX44>   | <MODEM:DOMX88>   | <MODEM:FELDHELL> | <MODEM:FSKH105> | <MODEM:FSKHELL>
+<MODEM:HELL80>   | <MODEM:HELLX5>   | <MODEM:HELLX9>   | <MODEM:MFSK11> | <MODEM:MFSK128>
+<MODEM:MFSK128L> | <MODEM:MFSK16>   | <MODEM:MFSK22>   | <MODEM:MFSK31> | <MODEM:MFSK32>
+<MODEM:MFSK4>    | <MODEM:MFSK64>   | <MODEM:MFSK64L>  | <MODEM:MFSK8> | <MODEM:MT63-1KL>
+<MODEM:MT63-1KS> | <MODEM:MT63-2KL> | <MODEM:MT63-2KS> | <MODEM:MT63-500L> | <MODEM:MT63-500S>
+<MODEM:NAVTEX>   | <MODEM:Olivia-16-1K> | <MODEM:Olivia-16-500> | <MODEM:Olivia-32-1K> | <MODEM:Olivia-4-250>
+<MODEM:Olivia-4-500> | <MODEM:Olivia-64-2K> | <MODEM:Olivia-8-1K> | <MODEM:Olivia-8-250> | <MODEM:Olivia-8-500>
+<MODEM:OLIVIA:1000:32> | <MODEM:OLIVIA:1000:8> | <MODEM:OLIVIA:250:8> | <MODEM:OLIVIA:500:16> | <MODEM:OLIVIA:500:8>
+<MODEM:OLIVIA>    | <MODEM:PSK1000C2>  | <MODEM:PSK1000R>   | <MODEM:PSK1000RC2> | <MODEM:PSK125C12>
+<MODEM:PSK125R>   | <MODEM:PSK125RC10> | <MODEM:PSK125RC12> | <MODEM:PSK125RC16> | <MODEM:PSK125RC4>
+<MODEM:PSK125RC5> | <MODEM:PSK250C6>   | <MODEM:PSK250R>    | <MODEM:PSK250RC2>  | <MODEM:PSK250RC3>
+<MODEM:PSK250RC5> | <MODEM:PSK250RC6>  | <MODEM:PSK250RC7>  | <MODEM:PSK500C2>   | <MODEM:PSK500C4>
+<MODEM:PSK500R>   | <MODEM:PSK500RC2>  | <MODEM:PSK500RC3>  | <MODEM:PSK500RC4>  | <MODEM:PSK63RC10>
+<MODEM:PSK63RC20> | <MODEM:PSK63RC32>  | <MODEM:PSK63RC4>   |  <MODEM:PSK63RC5>  | <MODEM:PSK800C2>
+<MODEM:PSK800RC2> | <MODEM:QPSK125>    | <MODEM:QPSK250>    | <MODEM:QPSK31>     | <MODEM:QPSK500>
+<MODEM:QPSK63>    | <MODEM:RTTY:170:45.45:5> | <MODEM:RTTY:170:50:5> | <MODEM:RTTY:850:75:5> | <MODEM:RTTY>
+<MODEM:SITORB>    | <MODEM:SLOWHELL>   | <MODEM:THOR100>  | <MODEM:THOR11>   | <MODEM:THOR16>
+<MODEM:THOR22>    | <MODEM:THOR25x4>   | <MODEM:THOR4>    | <MODEM:THOR5>    | <MODEM:THOR50x1>
+<MODEM:THOR50x2>  | <MODEM:THOR8>      | <MODEM:THRBX1>   | <MODEM:THRBX2>   | <MODEM:THRBX4>
+<MODEM:THROB1>    | <MODEM:THROB2>     | <MODEM:THROB4>   | <MODEM:WEFAX288> | <MODEM:WEFAX576>
+</small>
+</center>
+<br>
+
+\section other_modems Other Modems
+
+The following modems perform other functions not involving data
+transportation:
+<br>
+
+<center>
+Non Data Modems  | Description
+:--------------: | :--------------:
+<MODEM:NULL>     | Null modem - Rx stream is discarded. Tx stream is silent but PTT is enabled
+<MODEM:SSB>      | SSB modem (place holder)
+<MODEM:ANALYSIS> | \ref frequency_analyzer_page "Analyze Frequency"
+<MODEM:WWV>      | \ref digiscope_display_wwv_mode "Calibrate Sound Card"
+</center>
+<br>
+
+Local references are specified during the program configuration and can
+be changed during program operation.
+<br>
+
+Remote references are all part of the qso log field definitions and are
+routinely changed from contact to contact.
+<br>
+
+Global references are for items like Greenwich Mean Time.
+<br>
+
+The macros.mdf file can be edited with any ascii text editor such as
+kedit, gedit, geany, nano etc.  But it is much easier to use the
+built-in macro editor provided in the program.
+<br>
+
+\section macro_editor Macro Editor
+
+Right click on any macro key (or the alternate set) and a macro editing
+dialog opens with the current copy of that macro and its label. This looks
+very similar to the DigiPan macro editor at the urging
+of Skip Teller, KH6TY.
+<br>
+
+\image html macro-editor.png "Macro Editor"
+\image latex macro-editor.png "Macro Editor" width=6.0in
+<br>
+
+The Text box is a mini-editor with a very limited set of control
+functions.  You can mark, bound and select text for deletion
+(ctrl-X), copy (ctrl-C), and paste (ctrl-V).  Marked text can also
+be deleted with the delete or the backspace keys.  Marked text
+modification can also be invoked by using the mouse right click after
+highlighting.
+<br>
+
+The macro reference in the pick list can be transfered to the current editing
+cursor location.  Highlight the desired macro reference and then press the
+double \<\< arrow key for each occurance of the reference to be put into
+the macro text.  You can change the label name but any more than 8
+characters may exceed the width of the button for the default sized
+main dialog.
+<br>
+
+The \<TIMER:NN\> and \<IDLE:NN\> macro tags should have the NN
+replaced with the time interval in seconds.
+<br>
+
+<div>\<TX\>\<IDLE:5\>CQ CQ de
+\<MYCALL\> \<MYCALL\> k\<RX\>\<TIMER:20\><br>
+</div>
+
+<ul>
+	<li>will enable the PTT</li>
+	<li>cause 5 seconds of idle signal</li>
+	<li>send the CQ CQ de W1HKJ W1HKJ k</li>
+	<li>disable PTT</li>
+	<li>and count down 20 seconds before repeating the macro</li>
+	<li>after sending the text the count down timer button (upper right
+	hand corner of main dialog) will display the current timer value in
+	seconds.  Press this button to disable the timer. </li>
+	<li>the timer be disabled if the Escape key is pressed, the T/R is
+	pressed, and macro key is pressed, or if a callsign is copied from the
+	Rx text area to the callsign logbook entry.</li>
+	<li>the time will be disabled if any mouse activity occurs in the
+	waterfall control.</li>
+</ul>
+<br>
+
+The label associated with each macro key can be individually annotated
+with a symbol.  Here are the symbols that are recognized by the
+button label drawing routine:
+<br>
+
+\section macro_display_symbols Macro Display Symbols
+
+<center>
+\image html symbols.png "Symbols"
+\image latex symbols.png "Symbols" width=3.0in
+<br>
+</center>
+<br>
+
+The @ sign may also be followed by the following optional
+"formatting" characters, in this order:
+<br>
+
+<ul>
+	<li>'#' forces square scaling, rather than distortion to the widget's
+	shape.</li>
+	<li>+[1-9] or -[1-9] tweaks the scaling a little bigger or smaller.</li>
+	<li>'$' flips the symbol horizontally, '%' flips it vertically.</li>
+	<li>[0-9] - rotates by a multiple of 45 degrees. '5' and '6' do no
+	rotation while the others point in the direction of that key on a
+	numeric keypad. '0', followed by four more digits rotates the symbol by
+	that amount in degrees.</li>
+</ul>
+
+Thus, to show a very large arrow pointing downward you would use the
+label string "@+92-\>".
+
+Here are my macro buttons suitably annotated:
+<br>
+
+\image html macrobuttons.png "Macro Buttons"
+\image latex macrobuttons.png "Macro Buttons" width=6.0in
+<br>
+
+There are 4 sets of 12 macro functions.  You can move between the
+4 sets using the keyboard and the mouse.
+
+<ol>
+	<li>Left click on the "1" button to move to set #2.  Right click
+	on the "1" button to move to set #4.</li>
+	<li>Move
+	the mouse to anywhere on the macro buttons.  Use the scroll wheel
+	to move forward  &amp; backward through the macro sets</li>
+	<li>Press the Alt-1, Alt-2, Alt-3 or Alt-4 to immediately change to
+	that macro set.</li>
+</ol>
+<ul>
+	<li> The label for CQ is "CQ @\>|", denoting that both
+	\<TX\> and \<RX\> are present in the macro text. </li>
+</ul>
+<ul>
+	<li> The label for QSO is "QSO @\>\>", denoting that only
+	\<TX\> is present in the macro text. </li>
+</ul>
+<ul>
+	<li> The label for KN is "KN @||", denoting that only
+	\<RX\> is present in the macro text. </li>
+</ul>
+<br>
+
+You could use any label that is symbolic to the function required.
+Refer to the
+<a href="http://www.fltk.org/doc-1.1/common.html#labels">FLTK web site</a>
+for a full list of label types.
+<br>
+
+If you modify the macros and do not save them ("Files/Save Macros" on
+the main window) fldigi will prompt you to save the macros when you
+exit the program if you have the
+\ref ui_configuration_general_page "Exit Prompts" option selected.
+<br>
+
+\section contest_macro_tags Contest macro tags
+
+Refer to \ref contest_how_to_page "Contest-How-To"
+<br>
+
+<br>
+\ref macros_sub_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Menus.txt b/fldigi_doxygen/user_src_docs/Menus.txt
new file mode 100644
index 00000000..7210c915
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Menus.txt
@@ -0,0 +1,642 @@
+/**
+\page menus_page Menus
+
+\tableofcontents
+
+\image html menu-linux.png "Menu"
+\image latex menu-linux.png "Menu" width=6.0in
+<br>
+
+\section menu_heirarchy Menu Heirarchy
+
+\subsection s_files Files
+
+\subsubsection s_folders Folders
+
+\image html menu-files-folders.png "Folders"
+\image latex menu-files-folders.png "Folders" width=2.6in
+<br>
+
+<ul>
+	<li>Fldigi config... - open the OS native file explorer to
+	the folder containing the fldigi operating  &amp; data files. </li>
+	<li> NBEMS files... - open the OS native file explorer to the folder
+	containing the NBEMS data files</li>
+</ul>
+
+\subsubsection s_macros Macros
+
+\image html menu-files-macros.png "Macros"
+\image latex menu-files-macros.png "Macros" width=2.25in
+<br>
+
+<ul>
+	<li>Open Macros - open a macro definition file ... changes the MACRO
+	keys immediately</li>
+	<li>Save Macros - save the current macro definitions to a designated
+	file </li>
+</ul>
+
+Additional information:
+<br>
+\ref macro_page
+<br>
+\ref ui_configuration_macros_page
+<br>
+
+\subsubsection s_text_capture Text Capture
+
+\image html menu-files-text.png "Text Capture"
+\image latex menu-files-text.png "Text Capture" width=2.8in
+<br>
+
+Capture all received and transmitted text to a date-time stamped file.  Each
+day's data will be stored in a single file in which the text is appended:
+fldigiYYYYMMDD.log.  This file will be in the "Fldigi config..." folder which
+can be accessed per the File/Folders menu item.  A brief example log of Rx
+data:
+<br>
+
+\verbatim
+--- Logging started at Wed Jan  5 18:42:51 2011 UTC ---
+RX 14071955 : PSK31 (2011-01-05 18:42Z): d dx sk S
+RX 14071756 : PSK31 (2011-01-05 18:42Z): PSE -lr dACQ CQ de WX1GRS WX1GRS
+RX 14071756 : PSK31 (2011-01-05 18:42Z): CQ CQ de WX1GRS WX1GRS
+RX 14071756 : PSK31 (2011-01-05 18:42Z): CQ CQ de WX1GRS WX1GRS
+RX 14071756 : PSK31 (2011-01-05 18:42Z): PSE K aie =
+--- Logging stopped at Wed Jan  5 18:43:04 2011 UTC ---
+
+Each line contains the program state, RX or TX, the frequency, the mode,
+the date-time, and the data stream.
+\endverbatim
+
+<br>
+
+\subsubsection s_audio Audio
+
+\image html menu-files-audio.png "Audio"
+\image latex menu-files-audio.png "Audio" width=2.4in
+<br>
+
+<ul>
+	<li>Rx Capture - allows capturing the incoming audio to a wav file</li>
+	<li>Tx Generate - allows capturing the generated tx audio to a wav file</li>
+	<li>Playback - playback a previously captured or generated wav file</li>
+</ul>
+
+\subsubsection s_exit Exit
+
+\image html menu-files-audio.png "Exit"
+\image latex menu-files-audio.png "Exit" width=2.4in
+<br>
+
+Exit - exit the program closing down the various interfaces in a nice
+controlled manner.
+<br>
+
+\subsection s_op_mode Op Mode
+
+Op Mode - the current operating mode will show as a highlighted menu item.
+
+\image html menu-opmode.png "Op Mode"
+\image latex menu-opmode.png "Op Mode" width=1.0in
+<br>
+
+\subsubsection s_op_mode_cw CW
+
+<br>
+CW - receive CW 5 to 200 WPM and transmit on any audio frequency using AF CW.
+<br>
+
+Additional information:
+<br>
+\ref cw_page
+<br>
+\ref cw_configuration_page
+<br>
+
+
+\subsubsection s_op_mode_contestia Contestia
+
+\image html menu-contestia.png "Contestia"
+\image latex menu-contestia.png "Contestia" width=0.75in
+<br>
+
+<ul>
+	<li>Contestia 4 tones, 125 Hz wide</li>
+	<li>Contestia 4 tones, 250 Hz wide</li>
+	<li>Contestia 8 tones, 250 Hz wide</li>
+	<li>Contestia 4 tones, 500 Hz wide</li>
+	<li>Contestia 8 tones, 500 Hz wide</li>
+	<li>Contestia 16 tones, 500 Hz wide</li>
+	<li>Contestia 8 tones, 1000 Hz wide</li>
+	<li>Contestia 16 tones, 1000 Hz wide</li>
+	<li>Contestia 32 tones, 1000 Hz wide</li>
+	<li>Custom ... set on dialog</li>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref contestia_page
+<br>
+\ref contestia_configuration_page
+<br>
+
+\subsubsection s_op_mode_domino_ex DominoEX
+
+\image html menu-dominoex.png "DominoEX"
+\image latex menu-dominoex.png "DominoEX" width=1.0in
+<br>
+
+<ul>
+	<li>dominoex 4</li>
+	<li>dominoex 5</li>
+	<li>dominoex 8</li>
+	<li>dominoex 11 - the default calling mode for dominoEX</li>
+	<li>dominoex 16</li>
+	<li>dominoex 22</li>
+	<li>dominoex 44</li>
+	<li>dominoex 88</li>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref domino_ex_page
+<br>
+\ref domino_ex_configuration_page
+<br>
+
+\subsubsection s_op_mode_hell Hell
+
+\image html menu-hell.png "Hell"
+\image latex menu-hell.png "Hell" width=1.0in
+<br>
+
+<ul>
+	<li>Feld-Hell</li>
+	<li>Slow-Hell</li>
+	<li>Feld-Hell X5</li>
+	<li>Feld-Hell X9</li>
+	<li>FSK-Hell (also called FM-Hell by some programs)</li>
+	<li>FSK-Hell105</li>
+	<li>Hell-80</li>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref feld_hell_page
+<br>
+\ref feld_hell_configuration_page
+<br>
+
+\subsubsection s_op_mode_msfk MSFK
+
+\image html menu-mfsk.png "MSFK"
+\image latex menu-mfsk.png "MSFK" width=0.75in
+<br>
+
+<ul>
+	<li>MSFK 4</li>
+	<li>MSFK 8</li>
+	<li>MSFK 11</li>
+	<li>MSFK 16</li>
+	<li>MSFK 22</li>
+	<li>MSFK 31</li>
+	<li>MSFK 32</li>
+	<li>MSFK 64</li>
+	<li>MSFK 64L</li>
+	<li>MSFK 128</li>
+	<li>MSFK 128L</li>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref mfsk_page
+<br>
+
+\subsubsection s_op_mode_mt63 MT-63
+
+\image html menu-mt63.png "MT63"
+\image latex menu-mt63.png "MT63" width=0.75in
+<br>
+
+<ul>
+	<li>MT63-500S</li>
+	<li>MT63-500L</li>
+	<li>MT63-1000S</li>
+	<li>MT63-1000S</li>
+	<li>MT63-2000S</li>
+	<li>MT63-2000L</li>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref mt63_page
+<br>
+\ref mt63_configuration_page
+<br>
+
+\subsubsection s_op_mode_psk PSK
+
+\image html menu-psk.png "PSK"
+\image latex menu-psk.png "PSK" width=1.75in
+<br>
+
+\image html menu-psk-multi-carrier.png "Multi Carrier PSK"
+\image latex menu-psk-multi-carrier.png "Multi Carrier PSK" width=1.75in
+<br>
+
+<ul>
+	<li>psk 31 - phase shift keying - 31.625 baud</li>
+	<li>psk 63 - phase shift keying - 63.25 baud</li>
+	<li>psk 63F - phase shift keying with FEC - 63.25 baud</li>
+	<li>psk 125 - phase shift keying - 126.5 baud</li>
+	<li>psk 250 - phase shift keying - 253 baud</li>
+	<li>psk 500 - phase shift keying - 506 baud</li>
+	<li>psk1000 - phase shift keying - 1012 baud</li>
+	<li>MultiCarrier</li>
+	<ul>
+		<li>12 x psk 125 - 12 carrier psk125 - 126.5 baud - bandwidth 2000 Hz</li>
+		<li>6 x psk 250 - 6 carrier psk 250 - 253 baud - bandwidth 2000 Hz</li>
+		<li>2 x psk 500 - 2 carrier psk 500 - 506 baud - bandwidth 1200 Hz</li>
+		<li>4 x psk 500 - 4 carrier psk 500 - 506 baud - bandwidth 2600 Hz</li>
+		<li>2 x psk 800 - 2 carrier psk 800 - ~810 baud - bandwidth 2300 Hz</li>
+		<li>2 x psk 1000 - 2 carrier psk 1000 - 1012 baud - bandwidth 3200 Hz</li>
+	</ul>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref psk_page
+<br>
+
+
+\subsubsection s_op_mode_qpsk QPSK
+
+\image html menu-qpsk.png "QPSK"
+\image latex menu-qpsk.png "QPSK" width=0.75in
+<br>
+
+<ul>
+	<li>qpsk 31 - quadrature phase shift keying - 31.25 baud</li>
+	<li>qpsk 63 - quadrature phase shift keying - 63.25 baud</li>
+	<li>qpsk 125 - quadrature phase shift keying - 126.5 baud</li>
+	<li>qpsk 250 - quadrature phase shift keying - 253 baud</li>
+	<li>qpsk 500 - quadrature phase shift keying - 506 baud</li>
+
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref psk_page
+<br>
+
+\subsubsection s_op_mode_pskr PSKR
+
+\image html menu-pskr.png "PSKR"
+\image latex menu-pskr.png "PSKR" width=1.75in
+<br>
+
+All PSKR modes are phase shift keying, with FEC and interleaving.
+<br>
+
+<ul>
+	<li>psk 125R - 126.5 baud</li>
+	<li>psk 250R - 253 baud</li>
+	<li>psk 500R - 506 baud</li>
+	<li>psk 1000R - 880 baud</li>
+	<li>MultiCarrier</li>
+	<ul>
+		<li>4 x psk 63R - 4 carrier, bandwidth 330 Hz</li>
+		<li>5 x psk 63R - 5 carrier, bandwidth 416 Hz</li>
+		<li>10 x psk 63R - 10 carrier, bandwidth 550 Hz</li>
+		<li>20 x psk 63R - 20 carrier, bandwidth 1725 Hz</li>
+		<li>32 x psk 63R - 32 carrier, bandwidth 2775 Hz</li>
+		<li>4 x psk 125R - 4 carrier, bandwidth 352 Hz</li>
+		<li>5 x psk 125R - 5 carrier, bandwidth 440 Hz</li>
+		<li>10 x psk 125R - 10 carrier, bandwidth 1100 Hz</li>
+		<li>16 x psk 125R - 16 carrier, bandwidth 1760 Hz</li>
+		<li>2 x psk 250R - 2 carrier, bandwidth 440 Hz</li>
+		<li>3 x psk 250R - 3 carrier, bandwidth 660 Hz</li>
+		<li>5 x psk 250R - 5 carrier, bandwidth 1100 Hz</li>
+		<li>6 x psk 250R - 6 carrier, bandwidth 1320 Hz</li>
+		<li>7 x psk 250R - 7 carrier, bandwidth 1540 Hz</li>
+		<li>2 x psk 500R - 2 carrier, bandwidth 880 Hz</li>
+		<li>3 x psk 500R - 3 carrier, bandwidth 1320 Hz</li>
+		<li>4 x psk 500R - 4 carrier, bandwidth 1760 Hz</li>
+		<li>2 x psk 800R - 2 carrier, baud 800, bandwidth 1280 Hz</li>
+		<li>2x psk 1000R - 2 carrier baud 1012, bandwidth 1760 Hz</li>
+	</ul>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref psk_page
+<br>
+
+
+\subsubsection s_op_mode_olivia Olivia
+
+\image html menu-olivia.png "Olivia"
+\image latex menu-olivia.png "Olivia" width=0.75in
+<br>
+
+<ul>
+	<li>8/250 8tone, 250 Hz wide signal format</li>
+	<li>8/500 8 tone, 500 Hz wide signal format</li>
+	<li>16/500 16 tone, 500 Hz wide signal format</li>
+	<li>32/1000 32 tone, 1000 Hz wide signal format</li>
+	<li>Custom - tones and bandwidth configurable on Olivia tab</li>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref olivia_page
+<br>
+\ref olivia_configuration_page
+<br>
+
+
+\subsubsection s_op_mode_rtty RTTY
+
+\image html menu-rtty.png "RTTY"
+\image latex menu-rtty.png "RTTY" width=0.75in
+<br>
+
+<ul>
+	<li>RTTY-45  45 Baud Baudot, 170 Hz shift, used primarily in U.S.</li>
+	<li>RTTY-50  50 Baud Baudot, 170 Hz shift, used primarily in Europe</li>
+	<li>RTTY-75N 75 Baud Baudot, 170 Hz shift</li>
+	<li>RTTY-75W 75 Baud Baudot, 800 Hz shift</li>
+	<li>Custom - Baud Rate, Baudot/ASCII, Shift etc configurable on RTTY tab</li>
+</ul>
+
+Additional information:
+<br>
+\ref rtty_page
+<br>
+\ref rtty_fsk_configuration_page
+<br>
+
+\subsubsection s_op_mode_thor THOR
+
+\image html menu-thor.png "THOR"
+\image latex menu-thor.png "THOR" width=0.75in
+<br>
+
+<ul>
+	<li>Thor-4</li>
+	<li>Thor-5</li>
+	<li>Thor-8</li>
+	<li>Thor-16</li>
+	<li>Thor-22</li>
+	<li>Thor 25 x 4 - 4 x tone spacing, 2 second interleave</li>
+	<li>Thor 50 x 1 - 1 second interleave</li>
+	<li>Thor 50 x 2 - 2 x tone spacing, 1 second interleave</li>
+	<li>Thor 100 - 0.5 second interleave</li>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref thor_page
+<br>
+\ref thor_configuration_page
+<br>
+
+\subsubsection s_op_mode_throb THROB
+
+\image html menu-throb.png "throb"
+\image latex menu-throb.png "throb" width=0.75in
+<br>
+
+<ul>
+	<li>Throb1</li>
+	<li>Throb2</li>
+	<li>Throb4</li>
+	<li>ThrobX-1</li>
+	<li>ThrobX-2</li>
+	<li>ThrobX-4</li>
+</ul>
+
+Additional information:
+<br>
+\ref throb_page
+<br>
+
+\subsubsection s_op_mode_wefax WEFAX
+
+\image html menu-wefax.png "WEFAX"
+\image latex menu-wefax.png "WEFAX" width=1.0in
+<br>
+
+<ul>
+	<li>WEFAX-IOC576</li>
+	<li>WEFAX-IOC288</li>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref wefax_page
+<br>
+
+\subsubsection s_op_mode_navtex NAVTEX / SITOR
+
+\image html menu-navtex.png "NAVTEX / SITOR"
+\image latex menu-navtex.png "NAVTEX / SITOR" width=0.6in
+<br>
+
+<ul>
+	<li>Navtex</li>
+	<li>SitorB</li>
+</ul>
+
+Additional information:
+<br>
+\ref navtex_and_sitorb_page
+<br>
+
+\subsubsection s_op_mode_other SSB, WWV, and Freq Anal
+
+<ul>
+	<li>SSB - fldigi does not transmit, but can be used for rig control,
+	signal frequency analysis and logging</li>
+	<li>WWV - special receive only modem used for calibrating sound card</li>
+	<li>Freq Anal - used for carrier detection and frequency measurement</li>
+</ul>
+<br>
+
+Additional information:
+<br>
+\ref frequency_analyzer_page
+<br>
+\ref digiscope_display_wwv_mode
+<br>
+<br>
+
+
+\subsection s_configure Configure
+
+\image html menu-configure.png "Configure"
+\image latex menu-configure.png "Configure" width=1.4in
+<br>
+
+See \ref configuration_page Page
+<br>
+
+
+\subsection s_view View
+
+\image html menu-view.png "View"
+\image latex menu-view.png "View" width=1.4in
+<br>
+
+\image html menu-view-controls.png "View Controls"
+\image latex menu-view-controls.png "View Controls" width=3.5in
+<br>
+
+\image html menu-view-waterfall.png "View Waterfall"
+\image latex menu-view-waterfall.png "View Waterfall" width=2.9in
+<br>
+
+<ul>
+	<li>View/Hide Channels - Opens / Closes muli-signal viewer, shares space
+	with Rx/Tx panels</li>
+	<li>Floating Scope - Opens up a resizable, moveable scope display</li>
+	<li>MFSK Image - Opens the MFSK picture image (if being received)</li>
+	<li>Weather Fax Image - Opens WEFAX send/receive dialog </li>
+	<li>Signal browser - open the psk/rtty viewer dialog to display up to 30
+	simultaneously decoded psk signals Dialog viewer contains shared
+	data / control with the View/Hide Channel viewer</li>
+	<li>Countries - DXCC entities</li>
+	<li>Controls</li>
+	<ul>
+		<li>Full - show all logbook and rig controls</li>
+		<li>Rig control and logging - minimizes the logging panel for
+		normal QSO entries</li>
+		<li>Rig control and contest - minimizes the logging panel for
+		Contest entries</li>
+		<li>None - removes the Rig Control / Log panel from the main
+		User Interface</li>
+		<li>Contest fields - Display alternate 2nd line in qso logging
+		area; provides access to contest logging fields</li>
+	</ul>
+	<li>Waterfall</li>
+	<ul>
+		<li>Docked scope - toggles the visibility of the docked scope
+		display to the right of the waterfall</li>
+		<li>Min WF Controls - toggles the visibility of various waterfall
+		controls as configured by the user</li>
+	</ul>
+</ul>
+<br>
+
+\subsection s_logbook Logbook
+
+\image html menu-logbook.png "Logbook"
+\image latex menu-logbook.png "Logbook" width=1.0in
+<br>
+
+\image html menu-logbook-adif.png "Logbook ADIF"
+\image latex menu-logbook-adif.png "Logbook ADIF" width=2.25in
+<br>
+
+\image html menu-logbook-reports.png "Logbook Reports"
+\image latex menu-logbook-reports.png "Logbook Reports" width=2.3in
+<br>
+
+<ul>
+	<li>View - open the logbook dialog</li>
+	<li>New - create a new logbook</li>
+	<li>Open - open an existing logbook</li>
+	<li>Save - save the current logbook</li>
+	<li>ADIF / Merge - merge adif data from an ADIF file</li>
+	<li>ADIF / Export - export selected or all logbook records to an ADIF
+	formated file - see \ref exporting_logbook_data "Log Exports".</li>
+	<li>Reports / Text ... - export selected or all logbook records to a
+	text file suitable for printing</li>
+	<li>Reports / CSV ... - export selected or all logbook records to a
+	tab delimited file</li>
+	<li>Reports / Cabrillo ... - create a Cabrillo contest report.
+	- see \ref cabrillo_report_page "Cabrillo Reports".</li>
+</ul>
+<br>
+
+\subsection s_help Help
+
+\image html menu-help.png "Help"
+\image latex menu-help.png "Help" width=2.25in
+<br>
+
+<ul>
+	<li>Beginners' Guide</li>
+	<li>On line documentation... - open up default browser to the on-line
+	Help site</li>
+	<li>Fldigi web site... - open up default browser to the www.w1hkj.com
+	primary web page</li>
+	<li>Reception reports... - open up browser to the http://pskreporter.info
+	web page preset to your callsign</li>
+	<li>Command line options - display a list of all
+	\ref command_line_switches_page "command line switches" available to the
+	fldigi user</li>
+	<li>Audio device info - displays information about all audio devices
+	detected on the computer system</li>
+	<li>Build info - displays all relevant information regarding the
+	compilation and link for the application
+	- \ref build_info_page "build info"</li>
+	<li>Event log - opens a text display window that records various events
+	depending on the level of reporting depth selected.  This is a useful
+	window for reporting problems with the program to the developers.</li>
+	<li>Check for updates... fldigi silently opens a download web site,
+	checks and reports on whether a new version is available.</li>
+	<li>About - Version number and a little about the programmers</li>
+</ul>
+
+<br>
+
+\subsection s_other Spot, Tx RSID, Rx RSID, and Tune Buttons
+
+\image html menu-linux.png "Menu"
+\image latex menu-linux.png "Menu" width=6.0in
+
+<ul>
+	<li>Spot button - The "Spot" light button is visible if callsign spotting
+	is enabled.  Use this button to toggle the callsign spotting reporter
+	on and off.  It is automatically turned off when playback is selected
+	in the Files menu.  The main window text is not searched if the viewer
+	is active, i.e., if it is displayed and the current modem is PSK.
+	See <a href="Spotter.html">PskReporter</a>
+	and <a href="Notifier.html">Notifier</a>.
+	<li>RxID button - toggles the detection
+	of \ref id_configuration_page "Reed Solomon Identification" codes.</li>
+	<li>TxID button - toggles the transmission of the RSID signal.</li>
+	<li>Tune button - toggles the "Tune" mode which causes fldigi to
+	insert a tone at the current waterfall frequency.  The peak-to-peak
+	amplitude of this tone is the standard by which you should
+	\ref tune_page "set your transmitter drive" or adjust your antenna
+	matching network.</li>
+	<li>The right most button is normally not visible.  This is the
+	count-down timer button that is enabled when a macro button has been
+	configured to repeat after a specified number of seconds.  This
+	button shows the count-down to the next transmission.  Pressing
+	the button disables the count and restores fldigi to normal keyboard
+	operation.</li>
+</ul>
+
+
+<br>
+\ref menus_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/ModeTable.txt b/fldigi_doxygen/user_src_docs/ModeTable.txt
new file mode 100644
index 00000000..d0584583
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ModeTable.txt
@@ -0,0 +1,192 @@
+/**
+\page  mode_table_page Mode Table
+
+\tableofcontents
+
+\section psk_table PSK
+
+<small>
+ Mode      | Baud  | WPM  | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:--------: | :---: | :-:  | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+PSK31      | 31.25 | 50   | 80.00%     | 31      | 1-PSK      | <br> | 31HG1B    | 1      | <br>
+PSK63      | 62.5  | 100  | 80.00%     | 63      | 1-PSK      | <br> | 63HG1B    | 2      | <br>
+PSK63FEC   | 62.5  | 55   | 80.00%     | 63      | 1-PSK      | <br> | 63HG1B    | 22     | <br>
+PSK63RC4   | 63    | 220  | 80.00%     | 330     | 4-PSKR     | <br> | 330HG1BC  | 263    | 1
+PSK63RC5   | 63    | 275  | 80.00%     | 416     | 5-PSKR     | <br> | 416HG1BC  | 263    | 2
+PSK63RC10  | 63    | 550  | 80.00%     | 850     | 10-PSKR    | <br> | 850HG1BC  | 263    | 3
+PSK63RC20  | 63    | 1100 | 80.00%     | 1725    | 20-PSKR    | <br> | 1725HG1BC | 263    | 4
+PSK63RC32  | 63    | 1760 | 80.00%     | 2775    | 32-PSKR    | <br> | 2775HG1BC | 263    | 5
+<br>
+
+ Mode      | Baud  | WPM  | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-------:  | :---: | :-:  | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+PSK125     | 125   | 200  | 80.00%     | 125     | 1-PSK      | <br> | 125HG1B   | 4      | <br>
+PSK125R    | 125   | 110  | 80.00%     | 125     | 1-PSKR     | <br> | 125HG1B   | 183    | <br>
+PSK125RC4  | 125   | 352  | 80.00%     | 650     | 3-PSKR     | <br> | 650HG1B   | 10     | <br>
+PSK125RC5  | 125   | 440  | 80.00%     | 825     | 4-PSKR     | <br> | 700HG1BC  | 11     | <br>
+PSK125RC10 | 125   | 1100 | 80.00%     | 1700    | 10-PSKR    | <br> | 1700HG1BC | 12     | <br>
+PSK125RC16 | 125   | 1760 | 80.00%     | 2750    | 16-PSKR    | <br> | 2750HG1BC | 13     | <br>
+<br>
+
+ Mode      | Baud  | WPM  | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-------:  | :---: | :-:  | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+PSK250     | 250   | 400  | 80.00%     | 250     | 1-PSK      | <br> | 250HG1B   | 126    | <br>
+PSK250R    | 250   | 220  | 80.00%     | 250     | 1-PSKR     | <br> | 250HG1B   | 186    | <br>
+PSK250C6   | 250   | 2400 | 80.00%     | 2000    | 6-PSK      | <br> | 2000HG1B  | 263    | 63
+PSK250RC2  | 250   | 440  | 80.00%     | 600     | 2-PSKR     | <br> | 600HG1BC  | 263    | 20
+PSK250RC3  | 250   | 660  | 80.00%     | 950     | 3-PSKR     | <br> | 950HG1BC  | 263    | 21
+PSK250RC5  | 250   | 1100 | 80.00%     | 1650    | 5-PSKR     | <br> | 1760HG1BC | 263    | 22
+PSK250RC6  | 250   | 1320 | 80.00%     | 2000    | 6-PSKR     | <br> | 2000HG1BC | 263    | 65
+PSK250RC7  | 250   | 1540 | 80.00%     | 2350    | 7-PSKR     | <br> | 2350HG1BC | 263    | 23
+<br>
+
+ Mode      | Baud  | WPM  | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-------:  | :---: | :-:  | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+PSK500     | 500   | 800  | 80.00%     | 500     | 1-PSK      | <br> | 500HG1B   | 173    | <br>
+PSK500C2   | 500   | 1600 | 80.00%     | 1200    | 2-PSK      | <br> | 1200HG1B  | 263    | 27
+PSK500C4   | 500   | 3200 | 80.00%     | 2600    | 4-PSK      | <br> | 2600HG1B  | 263    | 28
+PSK500R    | 500   | 440  | 80.00%     | 500     | 1-PSKR     | <br> | 500-HG1BC | 187    | <br>
+PSK500RC2  | 500   | 880  | 80.00%     | 1400    | 2-PSKR     | <br> | 1400HG1BC | 263    | 24
+PSK500RC3  | 500   | 1320 | 80.00%     | 1900    | 3-PSKR     | <br> | 1900HG1BC | 263    | 25
+PSK500RC4  | 500   | 1760 | 80.00%     | 2600    | 4-PSKR     | <br> | 2600HG1BC | 263    | 26
+<br>
+
+ Mode      | Baud  | WPM  | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-------:  | :---: | :-:  | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+PSK800C2   | 800   | 2300 | 80.00%     | 1400    | 2-PSK      | <br> | 2300HGB1  | 263    | 57
+PSK800RC2  | 800   | 1280 | 80.00%     | 1400    | 2-PSKR     | <br> | 800HGB1C  | 263    | 54
+<br>
+
+ Mode      | Baud  | WPM  | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-------:  | :---: | :-:  | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+PSK1000    | 1000  | 1600 | 80.00%     | 1800    | 1-PSK      | <br> | 1800HG1B  | 263    | 50
+PSK1000R   | 1000  | 880  | 80.00%     | 1800    | 1-PSKR     | <br> | 1800HG1B  | 263    | 51
+PSK1000C2  | 1000  | 3200 | 80.00%     | 3600    | 2-PSK      | <br> | 3600HG1BC | 263    | 52
+PSK1000RC2 | 1000  | 1760 | 80.00%     | 3600    | 2-PSKR     | <br> | 3600HG1BC | 263    | 53
+<br>
+
+\section qpsk_table QPSK
+
+ Mode      | Baud  | WPM  | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-------:  | :---: | :-:  | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+QPSK31     | 31.25 | 50   | 80.00%     | 31      | 1-QPSK     | <br> | 31H0G1B   | 110    | <br>
+QPSK63     | 62.5  | 100  | 80.00%     | 63      | 1-QPSK     | <br> | 63HG1B    | 3      | <br>
+QPSK125    | 125   | 200  | 80.00%     | 125     | 1-PQSK     | <br> | 125HG1B   | 5      | <br>
+QPSK250    | 250   | 400  | 80.00%     | 250     | 1-PQSK     | <br> | 250HG1B   | 127    | <br>
+QPSK500    | 500   | 800  | 80.00%     | 500     | 1-PQSK     | <br> | 500HG1B   | <br>   | <br>
+<br>
+
+\section contestia_table Contestia
+
+ Mode             | Baud  | WPM | Duty Cycle | BW (Hz) | Modulation | S/N    | ITU     | RSID-1 | RSID-2
+:---------------: | :---: | :-: | :--------: | :-----: | :--------: | :----: | :-----: | :----: | :----:
+CONTESTIA-4-250   | 62.5  | 40  | 100.00%    | 250     | 4-FSK      | -10 dB | 250HF1B | 55     | <br>
+CONTSTIA-8-250    | 31.25 | 30  | 100.00%    | 250     | 8-FSK      | -13 dB | 250HF1B | 49     | <br>
+CONTESTIA-4-500   | 125   | 78  | 100.00%    | 500     | 4-FSK      | -8 dB  | 500HF1B | 54     | <br>
+CONTESTIA-8-500   | 62.5  | 60  | 100.00%    | 500     | 8-FSK      | -10 dB | 500HF1B | 52     | <br>
+CONTESTIA-16-500  | 31.25 | 30  | 100.00%    | 500     | 16-FSK     | -12 dB | 500HF1B | 50     | <br>
+CONTESTIA-8-1000  | 125   | 117 | 100.00%    | 1000    | 8-FSK      | -5 dB  | 1K00F1B | 117    | <br>
+CONTESTIA-16-1000 | 62.5  | 78  | 100.00%    | 1000    | 16-FSK     | -9 dB  | 1K00F1B | 53     | <br>
+CONTESTIA-32-1000 | 31.25 | 48  | 100.00%    | 1000    | 32-FSK     | -12 dB | 1K00F1B | 51     | <br>
+<br>
+
+\section domino_ex_table DominoEX
+
+ Mode      | Baud | WPM | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-------:  | :--: | :-: | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+DominoEX4  | 3.9  | 29  | 100.00%    | 173     | <br>       | <br> | 173HF1B   | 84     | <br>
+DominoEX5  | 5.4  | 44  | 100.00%    | 244     | <br>       | <br> | 244HF1B   | 85     | <br>
+DominoEX8  | 7.8  | 58  | 100.00%    | 346     | <br>       | <br> | 346HF1B   | 86     | <br>
+DominoEX11 | 10.8 | 80  | 100.00%    | 262     | <br>       | <br> | 262HF1B   | 87     | <br>
+DominoEX16 | 15.6 | 115 | 100.00%    | 355     | <br>       | <br> | 355HF1B   | 88     | <br>
+DominoEX22 | 21.5 | 160 | 100.00%    | 524     | <br>       | <br> | 524HF1B   | 90     | <br>
+DominoEX44 | 43   | 312 | 100.00%    | 1600    | <br>       | <br> | 1600HF1B  | 263    | 45
+DominoEX88 | 86   | 614 | 100.00%    | 1600    | <br>       | <br> | 1600HF1B  | 263    | 46
+<br>
+
+\section mfsk_table MFSK
+
+ Mode    | Baud  | WPM | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:----:   | :---: | :-: | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+MFSK4    | 3.9   | 18  | 100.00%    | 154     | 32-FSK     | <br> | 154HF1B   | <br>   | <br>
+MFSK8    | 7.8   | 36  | 100.00%    | 316     | 32-FSK     | <br> | 316HF1B   | 60     | <br>
+MFSK11   | 10.8  | 40  | 100.00%    | 218     | 16-FSK     | <br> | 218HF1B   | 148    | <br>
+MFSK16   | 15.6  | 58  | 100.00%    | 316     | 16-FSK     | <br> | 316HF1B   | 57     | <br>
+MFSK22   | 21.5  | 80  | 100.00%    | 435     | 16-FSK     | <br> | 435HF1B   | 152    | <br>
+MFSK31   | 31.3  | 55  | 100.00%    | 330     | 8-FSK      | <br> | 330HF1B   | <br>   | <br>
+MFSK32   | 31.3  | 120 | 100.00%    | 630     | 16-FSK     | <br> | 630HF1B   | 147    | <br>
+MFSK64   | 63    | 240 | 100.00%    | 1260    | 16-FSK     | <br> | 1260HF1B  | 263    | 30
+MFSK128  | 125   | 480 | 100.00%    | 1920    | <br>       | <br> | 1920HF1B  | 263    | 31
+MFSK64L  | 63    | 240 | 100.00%    | 1260    | 16-FSK     | <br> | 1260HF1B  | 263    | 30
+MFSK128L | 125   | 480 | 100.00%    | 1920    | <br>       | <br> | 1920HF1B  | 263    | 31
+<br>
+
+\section mt63_table MT-63
+
+ Mode      | Baud  | WPM  | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-------:  | :---: | :-:  | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+MT63-500   | 5     | 50   | 80.00%     | 500     | 64 x 2-PSK | <br> | 500HJ2DEN | 9      | <br>
+MT63-1000  | 10    | 100  | 80.00%     | 1000    | 64 x 2-PSK | <br> | 1K00J2DEN | 12     | <br>
+MT63-2000  | 20    | 200  | 80.00%     | 2000    | 64 x 2-PSK | <br> | 2K00J2DEN | 15     | <br>
+<br>
+
+\section olivia_table Olivia
+
+ Mode          | Baud | WPM | Duty Cycle | BW (Hz) | Modulation | S/N    | ITU       | RSID-1 | RSID-2
+:------------: |:---: |:---:| :--------: | :-----: | :--------: | :----: | :-------: | :----: | :----:
+OLIVIA-4-250   | 63   | 20  | 100.00%    | 250     | 4-FSK      | -12 dB | 250HF1B   | 75     | <br>
+OLIVIA-8-250   | 31   | 15  | 100.00%    | 250     | 8-FSK      | -14 dB | 250HF1B   | 69     | <br>
+OLIVIA-4-500   | 125  | 40  | 100.00%    | 500     | 4-FSK      | -10 dB | 500HF1B   | 74     | <br>
+OLIVIA-8-500   | 63   | 30  | 100.00%    | 500     | 8-FSK      | -11 dB | 500HF1B   | 72     | <br>
+OLIVIA-16-500  | 31   | 20  | 100.00%    | 500     | 16-FSK     | -13 dB | 500HF1B   | 70     | <br>
+OLIVIA-8-1000  | 125  | 58  | 100.00%    | 1000    | 8-FSK      | - 7 dB | 1K00F1B   | 116    | <br>
+OLIVIA-16-1000 | 63   | 40  | 100.00%    | 1000    | 16-FSK     | -10 dB | 1K00F1B   | 73     | <br>
+OLIVIA-32-1000 | 31   | 24  | 100.00%    | 1000    | 32-FSK     | -12 dB | 1K00F1B   | 71     | <br>
+<br>
+
+\section rtty_table RTTY
+
+ Mode   | Baud | WPM  | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-----: | :---:| :-:  | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+RTTY 45 | 45   | 60   | 100.00%    | 270     | <br>       | <br> | 270HF1B   | 39     | <br>
+RTTY 50 | 50   | 66   | 100.00%    | 270     | <br>       | <br> | 270HF1B   | 40     | <br>
+RTTY 75 | 75   | 100  | 100.00%    | 370     | <br>       | <br> | 370HF1B   | 41     | <br>
+<br>
+
+\section thor_table THOR
+
+ Mode    | Baud | WPM | Duty Cycle | BW (Hz) | Modulation | S/N  | ITU       | RSID-1 | RSID-2
+:-------:| :--: | :-: | :--------: | :-----: | :--------: | :--: | :-------: | :----: | :----:
+THOR4    | 3.9  | 14  | 100.00%    | 173     | <br>       | <br> | 173HF1B   | 136    | <br>
+THOR5    | 5.4  | 22  | 100.00%    | 244     | <br>       | <br> | 244HF1B   | 139    | <br>
+THOR8    | 7.8  | 28  | 100.00%    | 346     | <br>       | <br> | 346HF1B   | 137    | <br>
+THOR11   | 10.8 | 40  | 100.00%    | 262     | <br>       | <br> | 262HF1B   | 143    | <br>
+THOR16   | 15.6 | 58  | 100.00%    | 355     | <br>       | <br> | 355HF1B   | 138    | <br>
+THOR22   | 21.5 | 78  | 100.00%    | 524     | <br>       | <br> | 524HF1B   | 145    | <br>
+THOR25X4 | 24.3 | 88  | 100.00%    | 1800    | 4x tone spacing, 2 sec interleave | <br> | 1800HF1B | 263 | 40
+THOR50X1 | 48.6 | 176 | 100.00%    | 900     | 1 sec interleave                  | <br> | 900HF1B  | 263 | 41
+THOR50X2 | 48.5 | 176 | 100.00%    | 1800    | 2x tone spacing, 1 sec interleave | <br> | 1800HF1B | 263 | 42
+THOR100  | 97   | 352 | 100.00%    | 1800    | 0.5 sec interleave                | <br> | 1800HF1B | 263 | 43
+<br>
+
+\section throb_table THROB
+
+ Mode   | Baud  | WPM  | Duty Cycle | BW (Hz) | Modulation   | S/N   | ITU       | RSID-1 | RSID-2
+:-----: | :---: | :-:  | :--------: | :-----: | :----------: | :---: | :-------: | :----: | :----:
+THROB1  | 1     | 10   | 80.00%     | 72      | 1/2 of 9-FSK | <br>  | 72H0F1B   | 43     | <br>
+THROB2  | 2     | 20   | 80.00%     | 72      | 1/2 of 9-FSK | <br>  | 72H0F1B   | 44     | <br>
+THROB4  | 4     | 30   | 80.00%     | 144     | 1/2 of 9-FSK | <br>  | 144HF1B   | 45     | <br>
+THROBX1 | 1     | 10   | 80.00%     | 94      | 2 of 11-FSK  | <br>  | 94H0F1B   | 46     | <br>
+THROBX2 | 2     | 20   | 80.00%     | 94      | 2 of 11-FSK  | <br>  | 94H0F1B   | 47     | <br>
+THROBX4 | 4     | 40   | 80.00%    | 188      | 2 of 11-FSK  | <br>  | 188HF1B   | 146    | <br>
+<br>
+
+</small>
+
+<br>
+\ref mode_table_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/MousingKeyboardShortcuts.txt b/fldigi_doxygen/user_src_docs/MousingKeyboardShortcuts.txt
new file mode 100644
index 00000000..387942b9
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/MousingKeyboardShortcuts.txt
@@ -0,0 +1,199 @@
+/**
+\page  mouse_and_keyboard_shortcuts_page Mouse and Keyboard Shortcuts
+
+\tableofcontents
+
+
+Fldigi has a bewildering number of keyboard and mouse shortcuts, some
+of which may help make your particular style of operation more
+efficient.  You do not need to know them all to make effective use
+of the program!
+<br>
+
+\section main_window Main window
+<br>
+
+\subsection text_input_fields Text input fields
+<br>
+
+Most text fields use a combination of CUA (PC) and Unix-style
+keybindings.  Text can be marked, copied, pasted, saved to a file
+as well as transfer to other main panel controls.  A right click
+on any text control will open a context sensitive menu for that
+particular control.  A full list can be found on the
+<a href="http://www.fltk.org/doc-1.1/Fl_Input.html">FLTK web site</a>
+<br>
+
+The received/transmitted text widgets use CUA key bindings with some
+modifications:
+
+\subsubsection rx_text RX text
+
+This widget is read-only and ignores shortcuts that would modify its contents.
+See \ref qso_log_book_page "logbook" for details on the Rx right click
+popup menu system.
+<br>
+
+\subsubsection tx_text TX text
+
+The text that has already been sent is protected, but can be deleted one
+character at a time with the Backspace key.  Right clicking on the Tx text
+panel opens the following popup menu:
+<br>
+
+\image html menu-tx-popup.png "Fldigi Receiving Editing Tx text"
+\image latex menu-tx-popup.png "Fldigi Receiving Editing Tx text" width=1.0in
+<br>
+
+\image html menu-tx-popup2.png "Fldigi Transmitting"
+\image latex menu-tx-popup2.png "Fldigi Transmitting" width=1.0in
+<br>
+
+<ul>
+	<li>Transmit<br> put the program into the transmit operation</li><br>
+	<li>Receive<br>during a transmit or tune, end the transmit and restore
+	receive operation</li><br>
+	<li>Abort<br>during a transmit, receive without waiting for the modem to
+	finish sending</li><br>
+	<li>Send image<br>for MFSK only, send an image using MFSKpic mode</li><br>
+	<li>Clear<br>clear all of the text</li><br>
+	<li>Cut<br>delete the marked text (by left click drag over text)</li><br>
+	<li>Copy<br>copy the marked text to the clipboard</li><br>
+	<li>Paste<br>the clipboard text to the current text insertion point</li><br>
+	<li>Insert file<br>select a file from file browser to insert in text at
+	insertion point</li><br>
+	<li>Word wrap<br>turn word wrap on/off</li><br>
+</ul>
+
+The Tx panel is fully drag and drop aware.  That means you can add a
+file to the transmit text by simply opening up a file manager
+(different for different OS and choice of desktop).  Select the
+file from the manager and then drag and drop it onto the Tx panel. The mouse
+pointer will move the cursor insert point for the drop.
+<br>
+
+A number of additional shortcuts can be found in the
+\ref keyboard_operation_page "Keyboard Operation" section.
+
+
+\subsection waterfall_display Waterfall display
+<br>
+
+Most of fldigi's unusual shortcuts are specific to this widget.
+<br>
+
+
+\subsubsection waterfall_display_keyboard Waterfall display - Keyboard
+
+<ul>
+<li>Shift Left/Right - move the b/w marker by 1 Hz</li>
+<li>Ctrl  Left/Right - move the b/w marker by 10 Hz</li>
+</ul>
+
+\subsubsection waterfall_display_mouse Waterfall display - Mouse
+
+<ul>
+	<li>Left click/drag - move the b/w marker to, and start decoding at
+	the cursor frequency</li>
+	<li>Right click/drag - as above, but return to previous position on
+	release</li>
+	<li>Middle click - toggle AFC</li>
+	<li>Ctrl-Left click - replay audio history at b/w marker position</li>
+	<li>Ctrl-Right click - replay at cursor frequency and return on
+	button release</li>
+	<li>Ctrl-Middle click copy the frequency under the cursor to
+	the currently selected (or first) channel in the PSK viewer, and
+	select the next channel</li>
+	<li>Shift-Left click/drag  same as unmodified left click; no signal
+	search</li>
+	<li>Shift-Right click/drag  likewise, with a return to the previous
+	frequency when the button is released, no signal search</li>
+	<li>Shift-mouse wheel - move the squelch slider</li>
+	<li>Scroll wheel usage is dependent upon the
+	configuration (see \ref ui_configuration_waterfall_controls_page "ConfigWaterfall")</li>
+	<ul>
+		<li>None - no mouse wheel activity in waterfall panel</li>
+		<li>AFC range or BW - adjust the AFC range/BW up/down</li>
+		<li>Squelch level - adjust the squelch level up/down</li>
+		<li>Modem carrier - adjust the audio tracking point +/- Hz increments</li>
+		<li>Modem - select modem type from a full rotary of available modems</li>
+		<li>Scroll - move the waterfall left/right in 100 Hz increments
+		(for 2x, 4x expanded waterfall view)</li>
+		<li>Ctrl-mouse wheel - change the AFC search width in PSK modes,
+		or the bandwidth in CW and FeldHell</li>
+	</ul>
+    <li>Ctrl-Alt-Left click on the mouse when the mouse pointer is
+    in the waterfall - if operating with flrig and a supported transceiver
+    such as the FT-950, will set the transceiver manual notch frequency to
+    the frequency under the mouse cursor.  Repeat the Ctrl-Alt-Left click
+    to disengage the notch.  Disengagement is not dependent on where the
+    cursor is on the waterfall, just that it be in the waterfall.</li>
+</ul>
+
+\subsubsection waterfall_store_button Waterfall "Store" button
+
+<ul>
+	<li>Left click - Add a new item for the current frequency and modem</li>
+	<li>Shift-Left click - Delete all items</li>
+	<li>Middle click - Select last item in menu</li>
+</ul>
+
+<ul>
+	<li>Right click - Pop up menu</li>
+	<ul>
+		<li>Left/right click - Select item (and switch to that
+		frequency/modem)</li>
+		<li>Shift-Left/right click Delete item</li>
+		<li>Middle click - Update (replace) item</li>
+	</ul>
+</ul>
+
+\subsubsection digiscope_display Digiscope display
+
+<ul>
+	<li>Mouse wheel - Change AFC/BW, same as Ctrl-mouse wheel on the waterfall</li>
+</ul>
+
+\subsubsection rig_control_window Rig control window
+
+There are some shortcuts in addition to those described in the \ref rig_control_page "Rig Control"
+
+
+\subsubsection frequency_display Frequency display
+
+<ul>
+	<li>   Left/Right arrow key - change the frequency by one 1 Hz</li>
+	<li>   Up/Down arrow key - change the frequency by 10 Hz </li>
+</ul>
+
+\subsubsection frequency_list Frequency list
+
+<ul>
+<li>Shift-Left click - delete the line under the cursor</li>
+<li>Middle click - replace the line under the cursor with the current frequency/mode/modem</li>
+</ul>
+
+
+\subsubsection psk_viewer_window PSK viewer window
+
+<ul>
+	<li>Besides the bindings mentioned in the \ref signal_browser_page "PSK Viewer"
+	section, there are mouse shortcuts to change the nominal frequency of a
+	viewer channel:</li>
+	<ul>
+		<li> Middle click copy the current waterfall b/w marker frequency
+		to the channel under the cursor, overwriting that channel's nominal
+		frequency</li>
+		<li>Right click - restore a channel's nominal frequency</li>
+		<li>Right click on Clear - as above, for all channels</li>
+	</ul>
+</ul>
+
+
+<br>
+\ref mouse_and_keyboard_shortcuts_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Multiples.txt b/fldigi_doxygen/user_src_docs/Multiples.txt
new file mode 100644
index 00000000..d722d947
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Multiples.txt
@@ -0,0 +1,51 @@
+/**
+\page  operating_multiple_copies_page Operating Multiple Copies
+
+\tableofcontents
+
+\image html Dual-fldigi.png "Multiple Copies of FLDIGI"
+\image latex Dual-fldigi.png "Multiple Copies of FLDIGI" width=6.0in
+<br>
+
+There are times that you may need to simultaneously operate two or more
+instances of fldigi.  Or you might simply want to maintain two
+different configurations based on hardware usage.
+<br>
+
+The screen shot shows how this is done on Vista, but the process is
+nearly the same on XP, Win7 and Linux.  When you install fldigi it
+creates a desktop icon launcher.  Most of the Linux window
+managers allow you to create a desktop launch icon.  Make as many
+copies of the launcher as needed for your applications and rename them
+accordingly.  Then change the executable target entry to include
+the \ref command_line_switches_page "command line switch" '--config-dir'
+followed by the full pathname of the folder that will hold that
+particular configuration.  You do not need to create that folder
+as fldigi will do so the first time it is launched from that desktop
+icon.
+<br>
+
+If the various configurations all use independent hardware, i.e. sound
+cards and rig control ports, then you can have them operating
+simultaneously.  Each instance will have it's own configuration
+files, status file, macros, and logbook.  It is possible to have
+each instance use the same logbook, but then simultaneous operation is
+not possible as the logbook file is not currently designed to allow
+that type of sharing.
+<br>
+
+If each instance will be paired with a separate flarq (similarly set up
+for multiple operation) then you will also need to add the command line
+switch for \ref command_line_switches_page "arq-server address and port".
+The same is true for use with applications that talk to fldigi via it's
+xml-rpc socket port.  You change the address/port pairs on both
+the fldigi launcher and the paired application such as flarq or flrig.
+<br>
+
+<br>
+\ref operating_multiple_copies_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Navtex.txt b/fldigi_doxygen/user_src_docs/Navtex.txt
new file mode 100644
index 00000000..ea126b3b
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Navtex.txt
@@ -0,0 +1,188 @@
+/**
+\page  navtex_and_sitorb_page NAVTEX and SITOR-B
+
+\tableofcontents
+
+\image html Navtex-Choosing.png "Op Mode Select"
+\image latex Navtex-Choosing.png "Op Mode Select" width=1.1in
+<br>
+
+
+<b>NAVTEX</b> (Navigational Telex) is an international automated service for
+delivery of meteorological and marine safety information to ships. These
+broadcasts are sent with the
+<a href="http://en.wikipedia.org/wiki/SITOR" title="SITOR">SITOR collective B-mode</a>
+(Also known as AMTOR-B or AMTOR-FEC), using the
+<a href="http://en.wikipedia.org/w/index.php?title=CCIR_476&amp;action=edit&amp;redlink=1" class="new" title="CCIR 476 (page does not exist)">CCIR 476</a>
+ character set. SITOR-B is also used in <a href="http://en.wikipedia.org/wiki/Amateur_radio" title="Amateur radio">amateur radio</a>,
+ where it is known as <a href="http://en.wikipedia.org/wiki/AMTOR" title="AMTOR">AMTOR-B</a> or AMTOR-FEC.
+ <br>
+
+
+It transmits at 100 baud FSK modulation with a frequency shift of 170 Hz. The
+frequencies are:
+<br>
+
+<ul>
+	<li>518 kHz : International frequency, always in English.</li>
+	<li>490 kHz : Regional transmission, in local languages (Not used in the United States).</li>
+	<li>4209.5 kHz : Marine Safety Information.</li>
+</ul>
+<br>
+
+The implementation reflects this structure: The Navtex
+modem is a specialization of the SITOR-B modem. Fldigi supports
+both modes. We will specify when their behaviors are different.
+<br>
+
+\section transmitting_text Transmitting a text
+
+Transmitting a text is done with the usual GUI. The only difference
+between the SITOR-B and Navtex modes, is that data (Whether sent
+with the GUI or with XML/RPC) are untouched in SITOR-B. In Navtex,
+on the contrary:
+<br>
+
+<ul>
+	<li>They are preceded by a phasing signal of several seconds.</li>
+	<li>A \"ZCZC B<sub>1</sub>B<sub>2</sub>B<sub>3</sub>B<sub>4</sub>\"
+		preamble is sent.</li>
+	<li>Then the original message is transmitted.</li>
+	<li>... followed by the "NNNN" terminator,</li>
+	<li>... and another phasing signal.</li>
+</ul>
+
+\section receiving_text Receiving a text
+
+The only difference between the SitorB and Navtex modes, is that
+messages are processed (Parsed and optionally stored) only in Navtex
+mode. Here is a typical transmission showing:
+<br>
+
+<ul>
+	<li>The end of a previous message : "NNNN"</li>
+	<li>The preamble of a new message: "EA85": 85th
+	<i>navigational warning</i> ('A') of the Niton station in England ('E').</li>
+	<li>The message itself, without the terminator (Which should come soon). </li>
+</ul>
+<br>
+
+
+The modem has some flexibility when interpreting messages, and is able to
+deal with missing or incomplete preamble and terminator.
+<br>
+
+
+\image html Navtex-Reception.png "Navtex Reception"
+\image latex Navtex-Reception.png "Navtex Reception" width=6.0in
+<br>
+
+\section automatic_frequency_control AFC: Automatic Frequency Control
+
+As shown in the reception screen hard-copy, it is possible to tick
+"AFC". The consequence is that the frequency is continuously
+monitored.
+<br>
+
+
+\section logging_navtex_data Logging Navtex data to ADIF files
+
+
+Navtex messages are delimited with the usual separators ZCZC and NNNN.
+Their format is:
+<br>
+
+<code>
+ZCZC B<sub>1</sub>B<sub>2</sub>B<sub>3</sub>B<sub>4</sub>  <br>(message text ...)<br>NNNN<br>
+</code>
+
+These four characters are:
+<br>
+
+<ul>
+	<li>B<sub>1</sub> : The
+	station origin, used for lookups in the Navtex stations file. The same
+	character is associated to several stations. Therefore, we use other
+	criteria such as the frequency and the distance to the receiver, to
+	eliminate the ambiguity. It is therefore important to specify correctly
+	your Maidenhead locator.</li>
+	<li>B<sub>2</sub> : The subject indicator, used by the receiver to identify
+	the message class, such as ice reports or meteorological messages. </li>
+	<li>B<sub>3</sub>B<sub>4</sub>: A serial number between 00 and 99.</li>
+</ul>
+
+\section navtex_config Configuration
+
+\image html Navtex-Configuration.png "Navtex Configuration"
+\image latex Navtex-Configuration.png "Navtex Configuration" width=6.0in
+<br>
+
+As for any modem, there is a specific configuration tab for Navtex which allows:
+<br>
+
+<ul>
+	<li>To specify whether messages should be stored in the current
+	Adif log file.</li>
+	<li>To choose the Text file containing stations definitions.</li>
+</ul>
+
+\section adif_journal ADIF journal file
+
+\image html Navtex-Logged-Contacts.png "Logging Contacts"
+\image latex Navtex-Logged-Contacts.png "Logging Contacts" width=6.0in
+<br>
+
+Navtex messages can be logged to the ADIF file. This is done with other
+extra data:
+<br>
+
+<ul>
+	<li>Date and time of the contact.</li>
+	<li>Frequency and mode.</li>
+	<li>Station name, country, Maidenhead locator
+	and callsign deduced from the message header and the Navtex stations
+	file (See below). The locator is calculated using the station
+	coordinates.</li>
+	<li>The message content itself. Note that
+	carriage-returns which cannot be displayed on a single line, are
+	transformed into a tilda "~".</li>
+</ul>
+<br>
+
+\section station_file Stations file
+
+\image html Navtex-Choosing-Stations-File.png "Choosing Stations File"
+\image latex Navtex-Choosing-Stations-File.png "Choosing Stations File" width=5.0in
+<br>
+
+The emitter station is extracted from the Navtex message, and used to
+extract latitude, longitude, station name and other characteristics from
+a file containing well-known station, data/NAVTEX_Stations.csv. It is
+possible to edit this text file, or to choose another one.
+<br>
+
+\section xml_rpc_functions XML/RPC functions
+
+Two XML/RPC functions are create:
+
+<br>
+<table>
+<tr>
+<td>navtex.get_message</td>
+<td>Returns next Navtex/SitorB message with a max delay in seconds passed
+as an integer parameter. Empty string if timeout.</td>
+</tr>
+<tr>
+<td>navtex.send_message</td>
+<td>Send a Navtex/SitorB message, passed as a string. Returns an empty
+string if OK otherwise an error message</td>
+</tr>
+</table>
+
+<br>
+\ref navtex_and_sitorb_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/New-Install.txt b/fldigi_doxygen/user_src_docs/New-Install.txt
new file mode 100755
index 00000000..2ef73b21
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/New-Install.txt
@@ -0,0 +1,138 @@
+/**
+\page  new_installation_page New Installation
+
+\tableofcontents
+
+
+fldigi's opening screen looks like the following when starting fldigi for the
+first time or when setting up a second or subsequent instance using the
+--config-dir command line switch.  The Wizard has been completed and the
+callsign, W1HKJ, entered.
+<br>
+<br>
+
+\image html main-dialog-newinstall.png "Main Dialog New Install"
+\image latex main-dialog-newinstall.png "Main Dialog New Install" width=6.0in
+<br>
+
+
+Fldigi will create a working files folder, multiple sub folders and also
+populate them with a set of default files.  The working files folder is
+different on the different OS.
+
+<center>
+| Operating System  | Folder/Directory                                       |
+| :---------------: | :----------------------------------------------------- |
+| Windows           | C:\\Documents and Settings\\\<username\>\\fldigi.files |
+| Vista             | C:\\Users\\\<username\>\\fldigi.files                  |
+| Linux             | /home/\<username\>/.fldigi                             |
+| Macintosh         | /Users/User_Login_Name/.fldigi                         |
+</center>
+<br>
+
+After closing the application the working folder will contain the following
+folders and files:
+<br>
+
+\image html folder-working.png "Working Folder"
+\image latex folder-working.png "Working Folder" width=6.0in
+<br>
+
+The help, images, logs, scripts and temp folders will be empty.  They
+will contain program created files as you use the program or you may
+post files in those folders for use by fldigi.  Images to be sent
+with the MFSK pic mode should be placed in images.  Your logbook
+database will appear in logs.  If you are running on Linux then
+you can use various scripts to enhance the macro language that fldigi
+supports.  The temp directory holds files that are transitory and
+you can safely delete those files between sessions.  The 5 files
+that appear initially are:
+<br>
+
+
+<table>
+<tr>
+<td>fldigi.prefs</td>
+<td>contains
+variables that describe the status of fldigi when last used.  This
+is an ASCII text file that you can safely read.  You should not
+edit or change this file.</td>
+</tr>
+<tr>
+<td>fldigiYYYYMMDD.log</td>
+<td>this is an historical log of all the received and transmitted text
+during the day for which the log refers</td>
+</tr>
+<tr>
+<td>fldigi_def.xml</td>
+<td>contains
+variables that relate to all of fldigi's configurable items.  This
+is an ASCII text file that conforms with the XML specification.
+ You can safely read this file but should not edit or change it.</td>
+</tr>
+<tr>
+<td>frequencies2.txt</td>
+<td>an ASCII text file that contains the default (and / or modified)
+entries for fldigi's rig control process</td>
+</tr>
+<tr>
+<td>
+\ref working_logs_page "status_log.txt"
+</td>
+<td>a
+log of events for the most current fldigi execution.  This file
+will contain information relative to any errors that my occur and is
+important for debugging purposes.</td>
+</tr>
+</table>
+<br>
+
+The macros folder contains a single file:  macros.mdf.  This is
+an ASCII text file that contains the default macro definitions.
+ After running fldigi for a while and creating your own sets of
+macro definitions there will be additional *.mdf files located here.
+<br>
+
+The palettes folder contains the following files:
+<br>
+
+\image html folder-palettes.png "Folder Palettes"
+\image latex folder-palettes.png "Folder Palettes" width=5.0in
+<br>
+
+
+<br>Each
+of these is a palette definition file that is used to modify the
+appearance of the waterfall.  Fldigi has a palette editor that
+enables you to modify these default files or to create your own.
+ The file format of these files is identical to the palette files
+used by DigiPan.  The final color rendition might be a little
+different as a result of using different painting functions.  The
+file digipan.pal contains:<br>
+<br>
+
+<table>
+<tr>
+<td>  0;  0;  0<br>  0;  0; 62<br>  0;  0;126<br>  0;  0;214<br>145;142; 96<br>181;184; 48<br>223;226;105<br>254;254;  4<br>
+</td>
+</tr>
+</table>
+<br>
+
+Don't bother trying to modify these using an editor.  The palette editor
+is much easier to use and will keep you from wrecking havoc with the
+program.
+<br>
+
+The easiest way to find the working files folder is to start fldigi and then
+select the menu item File/Show config.
+<br>
+
+
+<br>
+\ref new_installation_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Notifier.txt b/fldigi_doxygen/user_src_docs/Notifier.txt
new file mode 100644
index 00000000..1ba16323
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Notifier.txt
@@ -0,0 +1,307 @@
+/**
+\page  notifier_page Notifier
+
+\tableofcontents
+
+
+This dialog available is used to specify search patterns and alerts that are triggered
+when the decoded Rx text matches those patterns.  This only happens
+when the Spot button on the main window is activated, as with the PSK
+Reporter client.
+<br>
+
+\image html Notifications.png "Notifications"
+\image latex Notifications.png "Notifications" width=5.0in
+<br>
+
+First, here's how it works in general.  You specify a regular
+expression (RE) that contains one or more parenthesised capturing
+groups.  Fldigi's spotter matches it against the incoming text (main
+window or Signal Browser, so it works with both PSK and RTTY) and, if
+the RE matches, it performs one or more of the following:
+<br>
+
+Displays an alert window with some text and a "go to that frequency" button.
+<br>
+
+Enters some arbitrary text into the Transmit pane.  The text may
+contain \<MACRO\>s and these will be expanded as usual.
+<br>
+
+Runs a program (Unix/Linux only for now).
+<br>
+
+The text described by the capturing group(s) can be used in all of the
+above.  There is an example of this at the end of this page.
+<br>
+
+Not everyone is at ease in writing regular expressions for the notifier
+to act upon.  So a few "canned" searches are coded into the
+notifier and are selected from the event chooser at the upper left of
+the dialog.
+<br>
+
+<ol>
+<li>My Callsign de CALL.  Can be used to alert you when CALL calls you.</li>
+<li>Station heard twice.  Pretty much the same search that the PSK reporter client does.</li>
+<li>Custom text search.  This reveals an input field where you type your own RE.</li>
+</ol>
+<br>
+
+Both (1) and (2) are special cases of (3), but with some extra
+processing available because in each case fldigi knows what it has just
+found.
+<br>
+<br>
+
+The Filter pane is available for the first two event types only, i.e.
+not the custom text search.  In this pane you can specify some
+properties that the spotted callsign must have for the actions to take
+place:
+<br>
+
+
+a) The Callsign radio button reveals a text field when selected.  If you
+enter something in that field, the event will be accepted only if the text
+matches the spotted callsign (I may change this to a RE match).
+<br>
+
+b) The "DXCC entity" radio button reveals a button that brings up a
+list of DXCC entities.  Select entities by clicking or
+dragging.  If you select any at all, the spotted callsign's
+country will have to be one of those or the event will be
+ignored.  Having no entities selected is the same as selecting all
+of them, i.e. any country, but is a more efficient.
+<br>
+
+The entity list can be sorted by clicking on the row headers, and there is a
+right click context menu that can (de)select by continent and CQ zone.  The
+buttons and search fields at the bottom behave as you'd expect.
+<br>
+
+The list is also available with the menu item "View / Countries" in the
+main window.
+<br>
+
+<b>You need cty.dat for all this to work</b>
+<br>
+
+c) The "Not worked before" check button
+asserts that, if you have selected (a) above, the callsign must not be
+in your logbook.  Same with (b), but now you must not have had any
+QSOs with stations from that country in the log.
+<br>
+
+d) The "LotW user" and "eQSL user" buttons specify that the callsign
+must be on one of these two lists (the documentation explains where to
+get the user lists from and where to put the files).
+<br>
+<br>
+
+The Action pane is where you choose how fldigi will alert you when an event
+matches the filter bits.
+<br>
+
+a) The text in the "Show alert text" box, if not empty, is shown in a pop-up
+window.  The alert window has a timer and dismisses itself after a
+configurable time interval (the "Hide after" control).  The user can
+click anywhere inside the window to stop the timer.
+
+\image html Notifier-popup.png "Notifier Popup"
+\image latex Notifier-popup.png "Notifier Popup" width=4.0in
+<br>
+
+
+The button next to the text box enters the default alert text for the event
+you have selected.  There are a few variables that are substituted
+when the window is displayed:
+<br>
+
+For all three event types: $MODEM (modem name), $DF_HZ (dial
+frequency), $RF_HZ (actual receive frequency), $RF_KHZ, $AF_HZ (modem
+audio frequency)
+<br>
+
+For the 1st event type (my call): $CALLSIGN, $TEXT (all matched text).
+<br>
+
+For the 2nd event type (station): $CALLSIGN, $TEXT, $COUNTRY.
+<br>
+
+For the 3rd event type (custom): you're on your own here, but fldigi
+will helpfully list all the possible substrings found in your RE.
+<br>
+
+The whole text is passed through strftime(3) so you can customize the
+date.  Here's a reference for the % characters:
+<br>
+
+<a href="http://www.opengroup.org/onlinepubs/007908799/xsh/strftime.html">
+http://www.opengroup.org/onlinepubs/007908799/xsh/strftime.html</a>
+<br>
+
+b) The "Append to TX text" box -- self explanatory.  The same variable
+substitutions apply, as well as macro expansion.  The nearby button shows
+the macro editor. The appended rx text is clickable.  Clicking it will move
+the waterfall frequency (and transceiver if under CAT) to the detected
+signal and change to the indicated mode.
+<br>
+
+\image html Notifier-rxtext.png "Notifier RX Text"
+\image latex Notifier-rxtext.png "Notifier RX Text" width=5.0in
+<br>
+
+c) The "Run program" field and browse button are only available on Unix
+systems.  Field contents are passed to the shell ("/bin/sh -c"),
+as with system(3).  No variable or \\backref substitution is done
+for this field, but all substrings are exported as environment
+variables, such as FLDIGI_NOTIFY_STR_1.  The usual \<EXEC\>
+macro variables are also there and your ~/.fldigi/scripts directory
+will be in the shell's path.  Try it out with a test script for
+the full list of variables.
+<br>
+
+d) The trigger limit box specifies how much time must pass
+between  subsequent invocations of whatever actions you have
+specified.
+<br>
+<br>
+
+The Duplicates pane has a check button that displays the rest of that
+group when checked.  If you enable this, fldigi will remember what
+it has seen and ignore the event if it is a duplicate.  The other
+controls in that pane determine what constitutes a duplicate:
+<br>
+
+a) The menu tells fldigi what to look
+at. For the first two event types, the menu will display "Callsign",
+and for the custom search it will contain a list of  \\X references
+for the RE.
+<br>
+
+b) The time box is also essential; it determines how close the events must
+be in time to be considered duplicates.
+<br>
+
+c) The Band and Mode check boxes further restrict the comparison.<br>
+<br>
+
+<b>An example:</b>
+
+You are looking at callsigns, with a dup time of 600s, and both Band
+and Mode checked.  A callsign is found once and fldigi alerts
+you.  Now if this callsign is spotted again, less than 600s later
+and in the same band and mode, it is a duplicate and will be
+ignored.  With (say) Band and Mode unchecked, it is a duplicate
+regardless of frequency band or mode as long as it's heard before the
+600s elapse.
+<br>
+
+Three of the four buttons at the bottom left are pretty much
+self-explanatory.  Add to the list an event you have just
+specified, or select an event from the list and Remove it, or change
+some of its parameters and Update it.
+<br>
+
+The Test... button allows you to test an event with some text of your
+choice.  This is particularly useful with the custom text search,
+as it's too easy to enter a RE that will never match.  The dialog
+will show you the default test string for the two fixed event
+types.  Careful: the "Station heard twice" event type expects a
+non-alphanumeric character at the end of its input.  The default
+test string has a space at the end.
+<br>
+
+If nothing happens, it may be because you have not specified any
+actions, or because the event's filter does not match, or because the
+trigger limit or dup handling are preventing the actions from happening. In
+the latter case, updating an event will reset its dup
+data.  But it's better to add the dup and trigger limits at the
+end, after you've tested the event.
+<br>
+
+The list at the bottom of the window shows the events you have
+added.  All contents are saved in the file ~/.fldigi/notify.prefs.
+<br>
+
+The list has a context menu for quick access to Update, Remove, and
+Toggle. The first two have the same effect as clicking on the button of
+the same name.
+<br>
+
+The Toggle item lets you flip the "Enabled" status of an event: this is
+like selecting an event, clicking on the "Enabled" button in the Event
+pane to (de)activate it, and then clicking "Update".  Disabled
+events are kept on the list but are not registered with the spotter and
+so they are never triggered.
+<br>
+
+If you disable all the events and there is nothing else using the
+spotter (e.g. PSK Reporter), the Spot button will disappear from the
+main window.
+<br>
+
+<b>A 2nd example:</b>
+
+Here's how to do the "my call" event using the custom text search:
+<br>
+
+a) Select "Custom text search" in the event pane
+<br>
+
+b) In the RE box, enter (without the quotes or leading white space):
+<br>
+
+<b>\"\<YOUR_CALL\>.+de[[:space:]]+([[:alnum:]]?[[:alpha:]/]+[[:digit:]]+[[:alnum:]/]+)\"</b>
+
+and remember to replace \<YOUR_CALL\> with your callsign.<br>
+
+c) In the actions pane you can now use \0 for the whole text matched by
+the above RE, and \1 for the first capturing group (the callsign).
+<br>
+
+d) Select "\1" in the duplicates menu if you want dup filtering.
+<br>
+
+e) Test with \"\<YOUR_CALL\> de \<SOME_OTHER_CALL\>\" and you should see the
+alert window with the text you specified.
+<br>
+
+<b>Addional examples:</b>
+
+Add a "My callsign de CALL" event with a script that will do something to
+get your attention when someone calls you.
+<br>
+
+Add a "Station heard twice" with the DXCC filter and the "Not worked
+before" option.  Also set the LotW or eQSL options if desired.
+<br>
+
+Add a "Station heard twice" with no callsign/dxcc/etc. filter but with
+duplicate filtering.  Write a script that sends the data to a DX
+cluster or similar.
+<br>
+
+Here is a simple Perl script that uses notify-send (in the package
+libnotify-bin on Debian) to display desktop notification
+"bubbles".  A better version would use the libnotify bindings for
+Perl or Python directly.
+
+\verbatim
+-----------------------------snip
+#!/usr/bin/perl
+exec("notify-send", "-t", "5000", "-i", "/usr/share/pixmaps/fldigi.xpm",
+     "Heard " . $ENV{"FLDIGI_NOTIFY_CALLSIGN"} . " ($ENV{FLDIGI_NOTIFY_COUNTRY})",
+     $ENV{"FLDIGI_NOTIFY_STR_0"});
+snip----------------------------
+\endverbatim
+
+
+
+<br>
+\ref notifier_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Olivia.txt b/fldigi_doxygen/user_src_docs/Olivia.txt
new file mode 100644
index 00000000..2d8a69c4
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Olivia.txt
@@ -0,0 +1,197 @@
+/**
+\page  olivia_page Olivia
+
+\tableofcontents
+
+
+fldigi can operate on the following Olivia modes without special setup by the
+operator:
+<br>
+
+<center>
+
+Mode           | Symbol Rate | Typing Speed        | Bandwidth
+:-------------:|:-----------:|:-------------------:|:----------:
+Olivia 8-250   | 31.25 baud  | 1.46 cps (14.6 wpm) | 250 Hz
+Olivia 8-500   | 62.5 baud   | 2.92 cps (29.2 wpm) | 500 Hz
+Olivia 16-500  | 31.25 baud  | 1.95 cps (19.5 wpm) | 500 Hz
+Olivia 32-1000 | 31.25 baud  | 2.44 cps (24.4 wpm) | 1000 Hz
+
+</center>
+<br>
+
+Unusual combinations of symbol rate and bandwidth can be selected
+using the \ref olivia_configuration_page "Olivia configuration tab".
+<br>
+
+These are unconnected, simplex chat modes with full time Forward Error
+Correction.  Olivia is a very robust mode with low error rates,
+but the penalty can be an annoyingly slow transfer of information. If you are
+a one finger typist then Olivia is your cup of tea.  The tones are spaced the
+same as the baud rate, for example 31.25 Hz for the default baud rates.  The
+default calling mode is 32-1000.   It has the following appearance on
+fldigi's waterfall:
+<br>
+
+\image html Olivia32-1000.png "Olivia 32/1000"
+\image latex Olivia32-1000.png "Olivia 32/1000" width=3.0in
+<br>
+
+<b>Excerpts from the web pages of
+<a href="http://www.oliviamode.com/" target="_blank">Gary, WB8ROL</a>
+</b>
+<br>
+
+Oliva Mode is a little different than PSK, RTTY, and many other digital
+modes. Below are tips on how to maximize your use of this mode.
+<br>
+
+<b>Disable your software squelch or turn it down as low as you can</b>
+<br>
+
+Generally turn your squelch setting in your software off or set it as
+low as it will go. You will see some "garbage" letters get printed out
+if there is NO Olivia signal present but it doesn't harm anything. When
+an Olivia signal is there it will start decoding it and print out the
+text without garbage at that time. It doesn't do much good to use a
+digital mode like Olivia that can decode signals -14 db below the noise
+lever IF you squelch it AT the noise level!  It would be like
+getting a pair of high power binoculars and using them only in a 10x10
+room with no windows.
+<br>
+
+<b>Be Patient!</b>
+<br>
+
+When you call CQ on this mode be patient and wait at least 45-60
+seconds before you put out another call. When the other person who
+hears your CQ clicks on the waterfall it may take 4-20 seconds or even
+longer before they might actually start decoding your signal.
+That varies a lot depending on the software they are using AND value
+they have their Sync Integration Period set to.
+<br>
+
+The Sync Integration Period setting determines how "deep" the Olivia
+decoding algorithm searches in the noise to get the signal.  A
+higher settings takes longer BUT usually decodes with more accuracy -
+at least to a point.  However, a higher setting (since it does
+more work and takes longer) will increase the delay factor.  So,
+when you finish your CQ and your transmitter switches to receive - the
+station listening to you (depending on his Sync Integration Periods
+setting) MAY NOT finish decoding your CQ for another 4-20
+seconds.  The same applies during a QSO when you pass it back to
+the other guy for his turn -- be patient if he doesn't come back right
+away because his software may still be decoding your signal long after
+you stopped transmitting.
+<br>
+
+It DOES NOT PAY to be impatient on this mode and send SHORT CQ's or NOT
+wait at least 45-60 seconds between CQ's.  Generally a a 2x2 CQ
+sent at least 2 or 3 times is going to work much better for you than a
+short one. Below is the normal CQ I use though on real fast Olivia
+formats (like 500/4) I will do a 3x3 and send it 3 times.
+<br>
+
+<tt>CQ CQ de WB8ROL WB8ROL</tt>
+<br>
+<tt>CQ CQ de WB8ROL WB8ROL</tt>
+<br>
+<tt>CQ CQ de WB8ROL WB8ROL pse K</tt>
+<br>
+
+<b>Don't set your Sync Integration Period setting TOO high</b>
+<br>
+
+If you set your Sync Integration Period too high it MAY take minutes
+before your software will start decoding a signal AND there is no or
+little benefit to doing that past a certain point.  I usually set
+mine so that the delay factor is abut 15-20 seconds.  I can time
+this delay factor by sending a very short test and then when it is done
+and the software switches back to receive - time the number of seconds
+before you see random garbage start appearing on the screen (assuming
+you have your SQUELCH OFF).  For the standard Olivia modes like
+2000/64, 1000/32, 500/16, 250/8, and 125/4 that usually means my Sync
+Integration Period is set between 3-5 most of the time.  If I use
+the faster formats I set it higher often between 6-10.  As long as
+my delay factor is approx. 15-20 seconds. Any higher than that and I
+don't see any real improvement in the quality of the decoding.
+But play with your own settings and see what does best for you.
+If you leave it always on one setting, though, and use standard and non
+standard formats of Olivia you are short changing yourself.
+<br>
+
+<b>Generally keep your Search (Tune Margin) setting to about 8</b>
+<br>
+
+The setting of 8 is usually good for most situations and this setting
+is usually not all that critical.  However, under a few band
+conditions it might (or might not) help to temporarily adjust
+this.  If you find other Olivia signals very very close to you -
+almost adjacent or even overlapping it might help to reduce this
+setting to 4 or even 2.  This setting determines how far, either
+side of your center frequency, Olivia will search for a signal to
+decode.  If you reduce this when another Olivia signal is close or
+overlapping it may keep it from locking onto the other signal instead
+of yours.  Also .... if you are trying to decode an extremely weak
+signal and can't even tell exactly WHERE to click on the waterfall
+because the trace is too faint or non existent then it might help to
+increase this setting to 16 or 32 temporarily. Then it would perhaps
+decode the signal even if you were OFF his center frequency by a large
+margin.
+<br>
+
+<b>If the slow speed of Olivia bothers you some ...</b>
+<br>
+
+If you find yourself wanting things to go a little faster then start
+using more (ham) common abbreviations like "hw" for how and "ur" for
+your.  Don't waste time sending words like "the" and "and" all the
+time.  An example : The weather here is nice and sunny today and
+the high will get to 85 degrees --- instead send : Wx nice + sunny -
+high 85 deg -- No need to spell out everything and use superfluous
+words like the, and, many others.  And why use words like HERE and
+TODAY in the above context when the other station already knows you are
+telling the weather for YOUR QTH for TODAY.  You aren't writing a
+novel, an article, or in a spelling bee.  Also after you establish
+the QSO don't send BOTH calls all the time at the beginning and end of
+every transmission.  After the QSO is in progress come back to the
+station like this : .. de WB8ROL  -- instead of : W9ZZZ de
+WB8ROL  -- and when you sent it back to the other guy send : BTU -
+de WB8ROL KN  -- That will help speed things up too.  You
+don't need to send the other stations call sign continually to fulfill
+your legal obligation to identify your own station.
+<br>
+
+<b>Don't be afraid to switch to a NON standard Olivia format if
+conditions warrant it.</b>
+<br>
+
+If signals are real strong and you prefer to be sending and receiving
+at a faster speed - don't be afraid to ask the other station if they
+would like to speed things up and switch to another Olivia format -
+even a non-standard one.  If you, for instance, were talking to me
+on 500/16 Olivia format and we both had very strong signals and not
+much QRM, QRN, etc. then ask me if I would like to go to 500/8 format
+or even 500/4 format.  500/16 format is approximately 20wpm while
+500/8 is close to 30wpm and 500/4 close to 40wpm. If you do end up
+switching to the faster modes you may also want to increase your Sync
+Integration Period setting substantially too - to maintain the best
+quality decoding.  If not, you might get more errors in the
+decoded text.  And if the band conditions become worse - go back
+to the original format AND remember to reset your Sync Integration
+Period setting or the delay in decoding will be way too long!
+Also, if the band starts getting real crowded and say, for example, you
+were on 500/16 mode - you might suggest to the other station to switch
+to 250/4 mode (increase Sync Integration Period setting too) to save
+space and be a "good neighbor" to all the other operators nearby.
+250/4 is the SAME speed as 500/16 and nearly as sensitive with the
+correct settings.
+<br>
+
+
+<br>
+\ref olivia_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/OperatingControls.txt b/fldigi_doxygen/user_src_docs/OperatingControls.txt
new file mode 100644
index 00000000..3d02bcea
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/OperatingControls.txt
@@ -0,0 +1,321 @@
+/**
+\page  operating_controls_page Operating Controls and Displays
+
+\tableofcontents
+
+
+\image html fldigi-controls.png "FLDIGI Controls"
+\image latex fldigi-controls.png "FLDIGI Controls" width=6.0in
+<br>
+
+The main display for fldigi is the waterfall display shown above in color
+and in scale x1.
+<br>
+
+The button <b>WF</b> toggles the display between a waterfall, a spectrum
+display and an oscilloscope type view of the Rx and Tx signals.  This
+button acts as a rotary.  Left clicking moves the display selection in one
+direction and right clicking in the other direction.  The three display modes
+are <b>WF</b> - waterfall, <b>FFT</b> - spectrum (Fast Fourier Transform)
+and <b>Sig</b> - oscilloscope time domain.  Let the mouse cursor hover over
+any one of the controls and a small hint box will open to help you navigate
+the various controls.
+<br>
+
+The <b>Norm</b> button controls the speed of the waterfall drop.   This is
+also a rotary type of button control.  The speeds available are SLOW, NORM,
+FAST and PAUSE.  The load on the cpu will be directly proportional to this
+selection.  If your cpu is slow you might want to select the SLOW
+or PAUSE option for the waterfall.
+<br>
+
+The scale control (X1, X2, X4) expands or contracts the view into the
+fast fourier transform that is displayed on the waterfall or the FFT
+display.  fldigi always computes the FFT to a 1 Hz resolution, and
+displays the results according to the scale control.
+<br>
+
+\image html psk-waterfallx1.png "PSK Waterfall X1 scale"
+\image latex psk-waterfallx1.png "PSK Waterfall X1 scale" width=1.75in
+<br>
+
+\image html psk-waterfallx2.png "PSK Waterfall X2 scale"
+\image latex psk-waterfallx2.png "PSK Waterfall X2 scale" width=2.5in
+<br>
+
+\image html psk-waterfallx4.png "PSK Waterfall X4 scale"
+\image latex psk-waterfallx4.png "PSK Waterfall X4 scale" width=3.0in
+<br>
+
+<br> The next three controls are positional conrols for the waterfall.  The
+waterfall can display 4096 data points, where each one can be thought
+of as a spectral line at the equivalent Hertz.  The ratio is actually
+8000/8192 and is related to the ratio of sound card sampling rate to
+Fast Fourier Transform length.  This ratio changes for some modems
+that require a sampling rate other than 8000 Hz.  The left arrow key
+will shift the display to the right (displays a lower section of the
+spectrum).  The right arrow key moves the display higher in frequency.
+ These two buttons are repeating buttons.  Hold them down and the
+display slews at about 20 shifts / sec.  The center button with
+the two vertical block lines is a "center the signal" button.  The current
+cursor (red signal cursor in the waterfall) will be centered in the
+display area.
+
+<b>NOTE:</b>  these controls are only functional if
+the current waterfall or spectrum view is smaller than the full view
+available.  This is usually the case when the X2 or X4 expansion
+is selected.  But it also might be the case when the width of the
+main dialog is reduced so that the waterfall display does not extend
+over the entire available width.
+
+Try moving the cursor around in the waterfall
+area.  You will see a set of yellow cursor blocks that show the center
+point and bandwidth of the current operating mode (psk31 = 31.25 Hz for
+example).  To capture a received signal just click near the signal and
+the AFC will perform a multi-step acquisition.  This will be very fast
+and should not require additional operator intervention.  <i>Casual tuning</i>
+ You can take a look at any received signal on the waterfall by
+right-clicking and holding the mouse button on or near the signal.
+ The modem will begin to decode that signal if it is in the
+currently selected mode.  The text will be a unique color on the
+Rx text widget so that you can discern the difference between casual
+and normal tracking.  Release the mouse button and the tracking
+returns to the previously selected normal tracking point.
+<br>
+
+<b>Audio History</b> Fldigi maintains a history buffer of the received
+audio.  This buffer is approximately 2 minutes in duration.  After tracking
+commences on a signal you can decode the audio history for that signal.  The
+audio history is invoked by a Ctrl-Left click anywhere on the waterfall.  You
+can also invoke the audio history for the casual tuning mode by pressing
+Ctrl-Right click on the waterfall.
+<br>
+
+The next control is your transceive audio frequency.  In the display above
+you can see that the audio signal is 1500 Hz.  The red cursor is
+centered beneath 14071.500 Mhz.  The transceiver was set to 14070 Mhz.  The
+arrow key pairs move up/down in cycles and tens of cycles.  You can
+fine tune the receive point using this control.
+<br>
+
+The next two controls to the right of the audio frequency control are for the
+receive signal processing.  The one that reads -10 is the max signal
+level for the waterfall/spectrum display.  The one that reads 51 is for
+the range over which that control will display signals.  Both of these
+are in dB.  The default of -10 / 40 is a good starting point, but you
+need to adjust these for band conditions.  You can see the impact of
+these controls most easily by putting the main display area in the
+spectrum mode.  Changes in these controls will effect the
+waterfall instantly and for all past history displayed on the
+waterfall.  You do not have to wait for new signal data to observe
+the affect.
+<br>
+
+The <b>QSY</b> button is very specific to rigs
+interfaced with either hamlib or the memory mapped i/o.  Each rig has a
+sweet spot associated with its bandwidth controller.  For the Argonaut
+V this is 1100 Hz.  For the the Kachina it is 1000 Hz.  As the
+transceivers bandwidth is changed the changes occur centered at this
+frequency.  So ....  let's say that I just started copying a rare dx at
+1758 Hz and I wanted to put the signal at the sweet spot so I could
+easily narrow the receiver bandwidth.  Click on the signal on the
+waterfall.  Let the AFC capture and then press the QSY button.  The
+tranceiver frequency will be shifted and the fldigi audio tracking
+point shifted in unison such that the signal is now at the receivers
+sweet spot.  Very fast and very convenient!  If you do not have hamlib
+enabled for your transceiver this button will be dimmed and not
+activated.
+<br>
+
+The <b>M\></b> button allows you to
+store, recall and manage mode/frequency pairs.  If you want to
+save the current mode and frequency simply left click the button.
+ A right click will enable a popup menu from which you can select
+a previously stored set.  You can quickly move between modes and
+audio sub carrier using this technique.  A shift-left click will
+clear the memory.  When the popup menu is visible you left click
+on an entry to select it.  You can shift-left click on an entry to
+delete that single entry.
+<br>
+
+The <b>T/R</b> button should be self-explanatory.  It's your
+transmit/receive button. Action is immediate, so if you were transmiting some
+text and hit the button the PTT is disabled, the transmit text area cleared
+and the program returned to receive mode.  The T/R button is a
+"lighted button" that shows when transmitting.  All other lighted buttons
+show YELLOW when they are in the active state.
+<br>
+
+The <b>Lck</b> button locks the transmit audio frequency to its present
+value.  You can then continue to QSY around your transmit position.  I have
+used this to reply to a DX station that wanted a +500 Hz  response.  The DX
+was at 690 Hz audio, and wanted a response at +500.  I moved the display
+cursor (or the audio frequency control) to 1190 Hz.  Hit the Lck button
+and then went back to 690 with the waterfall cursor.  Now the program
+is receiving on 690 Hz and transmitting on 1190 Hz.  Caught him on the
+first try.  Use this button also as a <i>Master Station</i>
+control.  Not all rigs are equal in their VFO performance.  Some
+exhibit a shift between receive and transmit.  If this occurs then the
+stations find themselves chasing each other with every t/r exchange.
+ Locking your transmit frequency with this control will inhibit that
+from happening.  Be sure to disable the control when that qso is over or
+<b>you may forget and transmit over top of another qso!</b>
+<br>
+
+If the "Lck" is enabled the TX frequency does not follow the AFC action
+applied to the RX frequency.
+<br>
+
+For transceivers which are either hamlib or memmap enabled, if the "Qsy"
+button is pressed BOTH the RX and TX frequencies are changed to synchronize
+to where the RX was positioned.
+<br>
+
+Perhaps some numbers will help to make that a little clearer.
+<br>
+
+
+"Lck" | Before "Qsy"    | <br>            | After "Qsy"     | <br>
+:----:|:---------------:|:---------------:|:---------------:|:---------------:
+<br>  | RX              | TX              | RX              | TX
+OFF   | 1002 / 7071.002 | 1002 / 7071.002 | 1500 / 7071.002 | 1500 / 7071.002
+ON    | 1002 / 7071.002 | 1000 / 7071.000 | 1500 / 7071.002 | 1500 / 7071.002
+ON    | 1000 / 7071.000 | 1800 / 7071.800 | 1500 / 7071.000 | 1500 / 7071.000
+
+<br>
+
+With "Lk" off the TX audio frequency is always synchronized with the
+RX frequency.
+<br>
+
+With "Lk" on the TX audio frequency is fixed with respect to the RX
+frequency UNLESS the "Qsy" button is pressed in which case it shifts to
+the RX frequency, the Transceiver VFO is shifted and both the RX and TX
+audio frequencies are shifted to put both into the middle of the
+transceiver passband.  The TX continues to be locked, but at the new
+audio frequency.
+<br>
+
+If the "Lk" is ON moving the cursor around will ONLY AFFECT the RX
+frequency and NOT the TX frequency.
+<br>
+
+The <b>AFC </b>and <b>SQL</b> buttons enable or disable the respective
+function in the software.  The slider just above the AFC \& SQL controls
+is the squelch level control.  The bar indicator just above it is the
+equivalent of received signal level and relates on a 1:1 basis with the
+squelch level slider.  The SQL button illuminates YELLOW when the SQL is
+selected, but the signal is below the squelch level.  It illuminates
+GREEN when the the SQL is selected and the signal is above the squelch level.
+<br>
+
+The indicator just to the left of the AFC button is the overload
+indicator.  It will be GREEN if your audio drive to sound card is
+satisfactory, YELLOW if the audio signal is marginally high and turn red
+when it is in overload.  Back down the mixer control or the audio pad from
+the rig to computer.  Fldigi will not perform well if the sound card is
+over driven.  You will see ghost signals on the waterfall and the modem
+decoders will not work correctly.
+<br>
+
+Receive audio level should be adjusted so that the overload indicator does
+not illuminate red.  When observing the received signals on the oscilloscope
+view you should expect that they do not exceed a peak-to-peak amplitude of
+3/4 of the full display height.
+<br>
+
+\section mode_status_indicators Mode Status Indicators
+
+The lower left corner of the main display (MFSK-16) in the view above is
+actually a button disquised as a status panel.  This button
+responds to the mouse in several ways:
+<br>
+
+<ul>
+	<li>Left Click - opens a quick pick list of associated modem types; you can
+	switch to a new modem type from this popup menu</li>
+	<li>Right Click - opens the configuration dialog at the tab associated with
+	the current modem type</li>
+	<li>Scroll Wheel - rotates forward and backwards through the various modem
+	types in accordance with the modem menu heirarchy.  Stop at the one you
+	want and you are now in that mode</li>
+</ul>
+
+The next status indicator to the right provides information relative to the
+current modem, for PSK it indicates the received signal strength in dB.
+<br>
+
+The third status indicator from the left provides additional information
+relative to the current modem, IMD for PSK measured in dB.
+<br>
+
+Note that for PSK these values are only measured during periods when the
+PSK idle signal is being received.
+<br>
+
+\section transmit_level_attenuator Transmit level attenuator
+<br>
+
+\image html TX-level.png "TX level"
+\image latex TX-level.png "TX level" width=2.5in
+<br>
+
+It is often difficult to adjust the audio drive for the point where ALC
+is just barely active.  Mixer controls are OK, but not usually
+designed for very small changes.  They are after all designed for
+adjusting listening levels.  fldigi provides the ability to
+control the audio drive in increments of 0.1 dB over a 30 dB
+range.  This control is located in the bottom right corner of the main dialog:
+<br>
+
+Set this control for -6 dB and then adjust the sound card mixer control
+for the best ALC level you can achieve.  Then adjust the Tx-level
+control for best "just visible" ALC on the transceiver.  That
+should give you a very clean PSK signal.
+<br>
+
+\section operating_split Operating split with fldigi / flrig
+<br>
+
+\image html tty-split-ops.png "TTY Split Ops"
+\image latex tty-split-ops.png "TTY Split Ops" width=4.5in
+<br>
+
+Note: In the above example most features are disable as they are not
+available for the indicated radio.
+
+
+On flrig:
+
+Unless specifically supported by the transceiver and implemented in flrig.
+
+<ul>
+	<li>VFO A is always the RX frequency.</li>
+	<li>VFO B is always the TX frequency.</li>
+	<li>Left Click on the A/B swaps A & B VFO frequencies.</li>
+	<li>Right Click on the A/B assignes A VFO frequency to B VFO.</li>
+	<li>Using the mouse wheel adjust VFO B to where you want to transmit.</li>
+	<li>Click the SPLIT button, it will change color when it is active.</li>
+	<li>Press the VFO B button to listen on the Tx frequency,
+	be sure to press Split again before capturing that rare DX station.</li>
+</ul>
+
+On fldigi:
+
+<ul>
+	<li>Tune the waterfall cursor to the Rx signal</li>
+	<li>Transmit as usual, be sure you are not doubling.</li>
+</ul>
+
+See <a href="http://www.w1hkj.com/flrig-help/index.html">FLRIG Help</a> for
+specific operating procedures.
+
+Some additional information can also be found here
+\ref rig_control_page "Rig Control Page"
+
+<br>
+\ref operating_controls_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/PseudoFSK.txt b/fldigi_doxygen/user_src_docs/PseudoFSK.txt
new file mode 100644
index 00000000..618f3b7d
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/PseudoFSK.txt
@@ -0,0 +1,63 @@
+/**
+\page  pseudo_fsk_page Pseudo FSK
+
+\tableofcontents
+
+<br>
+
+
+Using the FLdigi Pseudo FSK (Rt. Channel) function to key a transmitter
+<br>
+
+\image html config-rtty-tx.png "RTTY TX Configure"
+\image latex config-rtty-tx.png "RTTY TX Configure" width=5.0in
+<br>
+
+Select the PseudoFSK check boxes.
+<br>
+
+FLdigi is now ready to generate a 1000 hertz tone burst signal on the
+right channel of the stereo audio out of your sound card.
+<br>
+
+This tone burst is on when the RTTY bit is on and off when the RTTY bit is
+off.  The left channel will be the normal AFSK signal.
+<br>
+
+The following circuit may be used to take the FLdigi PSEUDO-FSK signal from
+the right channel of your SOUND CARD to key your transmitter's FSK
+input line.  You may find it necessary to invert the sense of the keying
+signal.
+<br>
+
+\image html CWkeyingCircuit.png "CW Keying Circuit"
+\image latex CWkeyingCircuit.png "CW Keying Circuit" width=6.0in
+<br>
+
+<b>NOTE:</b>
+
+L1 - Radio Shack has two items that may be used for this isolation
+transformer.
+
+<code>Catalog # 270-054, and Catalog # 273-1374</code>
+
+Attach an audio cable from the Rt. Channel out of the your computer's
+SOUND CARD to the input of this FSK  INTERFACE CIRCUIT (input of L1).
+<br>
+
+Attach another cable from the output of this circuit to your
+Rig's Keying FSK Jack.
+<br>
+
+Every PSEUDO-FSK tone that is generated by FLdigi is rectified by this FULL
+WAVE VOLTAGE DOUBLER circuit.  The resultant voltage turns the Q1 transistor
+on and "grounds" the collector.
+
+
+<br>
+\ref pseudo_fsk_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/PskViewer.txt b/fldigi_doxygen/user_src_docs/PskViewer.txt
new file mode 100644
index 00000000..2e05b9dc
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/PskViewer.txt
@@ -0,0 +1,122 @@
+/**
+\page  signal_browser_page Signal Browser
+
+\tableofcontents
+
+<br>
+
+PSK and RTTY signals can be viewed in a multi-channel context.
+You can open an embedded or a separate dialog to access the
+browser.  These browsers can help to locate a signal of interest
+on a busy band.  The browsers can be visible at any time, but are only
+active when fldigi is in one of the PSK or RTTY modes.  Open the external
+by clicking on the <b>View/Signal browser</b> menu item.
+<br>
+
+\image html view-menu.png "View Menu"
+\image latex view-menu.png "View Menu" width=2.0in
+<br>
+
+It looks like this:
+<br>
+
+\image html browser-panel.png "Browser Panel"
+\image latex browser-panel.png "Browser Panel" width=4.25in
+<br>
+
+Toggle the visibility of the embedded viewer by selecting the
+<b><i>View/Hide Channels</i></b> on the same menu list.  Your main fldigi
+screen then opens a browser panel on the left side of the Tx/Rx panel(s).
+<br>
+
+\image html main-dialog-browser.png "Main Dialog Browser"
+\image latex main-dialog-browser.png "Main Dialog Browser" width=6.0in
+<br>
+
+This panel can be resized horizontally by dragging the interface between the
+browser and the Rx panel to the left and right.  You can drag all the way to
+the left to close the panel (or use the menu button).  The drag to the
+right is limited to prevent sizing the Rx/Tx panels below their allowable
+limits.
+<br>
+
+The browser can decode up to 30 simultaneous signals.  As each signal is
+acquired within a 100 Hz channel width it is printed on the associated
+line.  The user can elect to have each line annotated with
+<br>
+
+a channel number,<br>
+the waterfall audio frequency,<br>
+the transceiver HF frequency + waterfall, or<br>
+no annotation.<br>
+<br>
+
+Left click on a line of received text to move the waterfall frequency
+and Rx panel tracking to that signal.  The contents of the line of
+text is transferred to the Rx text widget, and the main signal processing loop
+begins to track and decode that signal.  Right click on a line of received
+text and that line is cleared and the channel reset for a new
+detection.  You may have to do this occasionally if the detector
+for that channel has locked on to a sideband of a PSK signal.
+This is most likely to occur when the received signal as a marginal or
+bad IMD.  Use the ><b>Clear</b> button to clear and reset all of the
+channels.  Channel signal detection and processing should restart
+immediately.
+<br>
+
+Configuring the browser:
+<br>
+
+\image html config-ui-browser.png "Browser Configure"
+\image latex config-ui-browser.png "Browser Configure" width=5.0in
+<br>
+
+<ol>
+	<li>select the number of 100 Hz channels you want visible</li>
+	<li>select the start frequency for the browser (your transceiver may not
+	rx signals below this value)</li>
+	<li>select the inactivity timeout for the browser.  After this
+	number of seconds the channel will be cleared and prepared for the next
+	detection cycle.</li>
+	<li>select whether you want a Marque type of continuous scrolling, or simply
+	clear the line when it is filled.</li>
+	<li>select what kind of label annotation you want on each line</li>
+	<li>select the font and font size to be used in the browser</li>
+	<li>You can enter any text you want to search for in the <b>Seek
+	Regular Expression</b> widget.
+	<br>
+	This text can be a simple text snippet such as "CQ" or any
+	regular expression.  With a regex you can specify a more generic pattern,
+	which means that you can match more things and your search is somewhat noise
+	tolerant. Here is an example for a CQ from a US station (should match most
+	callsigns):
+	<br>
+	<br>
+	cq.+[aknw][a-z]?[0-9][a-pr-z][a-z]{1,2}
+	<br>
+	<br>
+	This says "cq followed by at least one character, followed by one A,
+	K, N, or W, followed by an optional letter, followed by a digit,
+	followed by a letter that is not q, followed by one or two letters".
+	The search is case-insensitive.
+	<br>
+	All plain text is a valid regular expression, unless you really had been
+	looking for these metacharacters:
+	<br>
+	<br>
+	.[{()\*+?|^$
+	<br>
+	<br>
+	These will have to be escaped with a backslash.<br></li>
+</ol>
+
+<br>
+<br>
+\ref signal_browser_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
+
+
diff --git a/fldigi_doxygen/user_src_docs/RST-RSQ.txt b/fldigi_doxygen/user_src_docs/RST-RSQ.txt
new file mode 100644
index 00000000..de8a1f87
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/RST-RSQ.txt
@@ -0,0 +1,105 @@
+/**
+\page  rst_rsq_page RST and RSQ Reporting
+
+\tableofcontents
+
+
+\section rst RST
+
+Is the traditional Readability, Strength, Tone reporting system used for
+CW operations for nearly as long as amateurs have enjoyed the airwaves.
+<br>
+
+\subsection rst_readability READABILITY
+
+<ol>
+<li>Unreadable</li>
+<li>Barely readable, occasional words distinguishable</li>
+<li>Readable with considerable difficulty</li>
+<li>Readable with practically no difficulty</li>
+<li>Perfectly readable (that is 100% print in todays jargon)</li>
+</ol>
+
+\subsection rst_signal_strength SIGNAL STRENGTH
+
+<ol>
+<li>Faint signals, barely perceptible</li>
+<li>Very weak signals</li>
+<li>Weak signals</li>
+<li>Fair signals</li>
+<li>Fairly good signals</li>
+<li>Good signals</li>
+<li>Moderately strong signals</li>
+<li>Strong signals</li>
+<li>Extremely strong signals</li>
+</ol>
+
+\subsection rst_tone TONE
+
+<ol>
+<li>Sixty cycle AC or less, very rough and broad</li>
+<li>Very rough AC, very harsh and broad</li>
+<li>Rough AC tone, rectified but not filtered</li>
+<li>Rough note, some trace of filtering</li>
+<li>Filtered rectified ac, but strongly ripple modulated</li>
+<li>Filtered tone, definite trace of ripple modulation</li>
+<li>Near pure tone, trace of ripple modulation</li>
+<li>Near perfect tone, slight trac of modulation</li>
+<li>Perfect tone, no trace of ripple, or modulation of any kind</li>
+</ol>
+
+\section rsq RSQ
+
+
+Give the report as RSQ for digital modes, but especially BPSK and QPSK; see:
+<a class="moz-txt-link-freetext" href="http://www.psb-info.net/RSQ-Reporting-Table.html">
+http://www.psb-info.net/RSQ-Reporting-Table.html</a>
+<br>
+
+
+\subsection rsq_readability READABILITY
+
+<ol>
+<li>0% undecipherable</li>
+<li>20% occasional words distinguishable</li>
+<li>40% considerable difficulty, many missed characters</li>
+<li>80% practically no difficulty, occasional missed characters</li>
+<li>95%+ perfectly readable</li>
+</ol>
+
+\subsection rsq_strength STRENGTH
+
+<ol>
+<li>Barely perciptible trace </li>
+<li>n/a</li>
+<li>Weak trace</li>
+<li>n/a</li>
+<li>Moderate trace</li>
+<li>n/a</li>
+<li>Strong trace</li>
+<li>n/a</li>
+<li>Very strong trace</li>
+</ol>
+
+\subsection rsq_quality QUALITY
+
+<ol>
+<li>Splatter over much of the visible waterfall</li>
+<li>n/a</li>
+<li>Multiple visible pairs</li>
+<li>n/a</li>
+<li>One easily visible pair</li>
+<li>n/a</li>
+<li>One barely visible pair</li>
+<li>n/a</li>
+<li>Clean signal - no visible unwanted sidebar pairs</li>
+</ol>
+
+
+
+<br>
+\ref rst_rsq_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/RTTYFSK.txt b/fldigi_doxygen/user_src_docs/RTTYFSK.txt
new file mode 100644
index 00000000..9142b67d
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/RTTYFSK.txt
@@ -0,0 +1,240 @@
+/**
+\page  rtty_page RTTY
+
+\tableofcontents
+
+The RTTY modulator and demodulator have been extensively changed with
+version 3.21.67.  The new design was a cooperative effort of
+Stefan, DO2SMF, and Dave, W1HKJ with extensive testing performed by Ed,
+W3NR, and Dick, AA5VU.  Chen, W7AY, was a silent contributor to
+the design by virtue of his excellent technical papers on RTTY
+modulation and demodulation, which he so generously placed in the
+public domain.
+<br>
+
+fldigi can operate on a wide range of RTTY symbol rates and bandwidths. The
+selection of symbol rate and bandwidth is made on
+the \ref rtty_fsk_configuration_page "RTTY configuration tab".  The three most
+common in amateur radio use can be selected from the mode menu.  These are
+<br>
+
+<center>
+
+Mode    | Symbol Rate | Typing Speed       | Bandwidth
+:------:|:-----------:|:------------------:|:----------:
+RTTY 45 | 45.45 baud  | 6.0 cps (60 wpm)   | 270 Hz
+RTTY 50 | 50.0 baud   | 6.6 cps (66 wpm)   | 280 Hz
+RTTY 75 | 75.0 baud   | 10.0 cps (100 wpm) | 370 Hz
+
+</center>
+<br>
+
+These modes were a result of mechanical and electrical
+designs of the early TTY machines.  The 45.45 baud and 75 baud
+machines were for the US / Canadian market and used 60 Hz
+synchronous motors.  The 50 baud machines were for the European
+market and used 50 Hz synchronous motors.
+<br>
+<br>
+
+fldigi can encode and decode many other symbol rates and bandwidths.  "Custom"
+combinations are set up on the RTTY configuration tab.  You
+probably will never have to do that unless you like experimenting with
+unusual RTTY modes.
+<br>
+
+\section rtty_modulator RTTY modulator
+
+
+All of the modem signals that fldigi produces are audio signals.  That
+includes the RTTY signal.  fldigi can encode and decode an RTTY signal
+that is anywhere within the passband of the sideband transceiver.  It is
+not limited to the traditional tone pairs around 2100 Hz.  Each of
+the generated Mark / Space signals are on-off-keyed (OOK), bandwidth
+limited signals.  The resultant waveform is not an FM type signal
+of constant amplitude.  Therefore the <b>transmit audio and RF
+amplifiers must be linear</b>, just like the requirement for PSK signals.
+There are performance gains using this approach.  The principal being a
+reduction in inter symbol interference which gives much improved
+performance by the receiver.  The waterfall, time domain, and
+spectrum signatures of the transmitted signal look like this:
+<br>
+
+\image html w1aw-rtty-80.png "W1AW on air signal"
+\image latex w1aw-rtty-80.png "W1AW on air signal" width=3.5in
+<br>
+
+\image html rtty-transmit.png "AFSK signal "
+\image latex rtty-transmit.png "AFSK signal " width=3.5in
+<br>
+
+\image html rtty-spectrum.png "Spectrum"
+\image latex rtty-spectrum.png "Spectrum" width=1.5in
+<br>
+
+
+
+
+You must operate your transceiver in the USB
+mode for the fldigi RTTY signal to be the correct polarity.  If your
+transceiver is set to LSB then use the fldigi "Rev" button to reverse
+the sense of the mark and space signals.
+<br>
+
+You must maintain transmitter LINEARITY in the AUDIO AMPLIFIERs.
+Do not think that you can improve performance by over driving the audio
+input.  A good operating procedure for most transceivers is the
+set the audio level to the level for which there is just barely a hint
+of ALC.  Then reduce the input to 80% of that power level.
+Over driving an AFSK signal is as disastrous as over driving a PSK
+signal.  This is an actual on air signal that was being over
+driven (but not on purpose):
+<br>
+
+
+\image html rtty_overdrive.png "Overdriven RTTY Signal"
+\image latex rtty_overdrive.png "Overdriven RTTY Signal" width=6.0in
+<br>
+
+
+Joe also performed a series of tests on an Icom 706 mkIIg transceiver.  The
+results of those tests are very enlightening.
+<br>
+
+"Two views - the 2 KHz span and a 10 KHz span.  The 10 KHz span
+shows the one failing of the IC-706mkIIg and other rigs with analog
+modulation - opposite sideband and carrier leakage.  This one
+isn't too bad but one can see carrier at -50 dBc and opposite sideband
+at -55 dBc +/-.   I do use a high audio frequency to minimize
+harmonic issues.
+<br>
+
+For fun I've attached versions at 70 W in 10K, 5K, and 2K spans.  The narrow
+spans clearly show the benefits of reducing the audio until output power
+drops 1.5 dB.
+<br>
+
+Audio was connected to the IC-706mkIIg via the "DATA" jack rather
+than the mic connector or "Mod In" pin of the ACC jack.  Using this
+input avoids several potential problems - including the constant
+swapping between mic and digital connections and remembering to turn off the
+compressor when switching to digital operation.  The "Data" input is
+also 6 dB less sensitive than "Mod in" making it that much less likely
+that one will significantly over drive the the transceiver and create
+distortion in the audio stages ahead of the modulator".
+<br>
+
+
+The green area is 400 Hz wide.
+
+<center>
+
+<br>
+\image html Icom_FSK.png "Image A"
+\image latex Icom_FSK.png "Image A" width=4.8in
+Transceiver operated in FSK mode<br>
+Power: 100 W<br>
+<br>
+<br>
+<br>
+\image html fldigi_Icom_AFSK.png "Image B"
+\image latex fldigi_Icom_AFSK.png "Image B" width=4.8in
+Transceiver in USB, fldigi AFSK audio drive<br>
+Space at 2125, Mark at 2295 Hz<br>
+Power: 100 Watts,  ALC just extinguished<br>
+<br>
+<br>
+<br>
+\image html fldigi_Icom_AFSK-1dB.png "Image C"
+\image latex fldigi_Icom_AFSK-1dB.png "Image C" width=4.8in
+Transceiver in USB, fldigi AFSK audio drive<br>
+Space at 2125, Mark at 2295 Hz<br>
+Power: reduced to 80 Watts (-1 dB)<br>
+<br>
+<br>
+<br>
+\image html fldigi_Icom_AFSK-1r5dB.png "Image D - 2 K span"
+\image latex fldigi_Icom_AFSK-1r5dB.png "Image D - 2 K span" width=4.8in
+Transceiver in USB, fldigi AFSK audio drive<br>
+Space at 2125, Mark at 2295 Hz<br>
+Power: reduced to 70 Watts (-1.5 dB)</td>
+<br>
+<br>
+<br>
+\image html fldigi_70W_1000Hz.png "Image F - 10 K span"
+\image latex fldigi_70W_1000Hz.png "Image F - 10 K span" width=4.8in
+Transceiver in USB, fldigi AFSK audio drive<br>
+Space at 830 Hz, Mark at 1000 Hz<br>
+Power: 70 Watts.  The LSB leakage is clearly <br>
+seen at approximately -55 dB<br>
+<br>
+<br>
+<br>
+\image html fldigi_70W_1000Hz_5K.png "Image G - 5 K span"
+\image latex fldigi_70W_1000Hz_5K.png "Image G - 5 K span" width=4.8in
+Transceiver in USB, fldigi AFSK audio drive<br>
+Space at 830 Hz, Mark at 1000 Hz<br>
+Power: 70 Watts.  The LSB leakage is clearly <br>
+seen at approximately -55 dB.<br>
+<br>
+<br>
+<br>
+\image html fldigi_70W_2stop.png "Image H - 2 K span"
+\image latex fldigi_70W_2stop.png "Image H - 2 K span" width=4.8in
+Transceiver in USB, fldigi AFSK audio drive<br>
+Space at 830 Hz, Mark at 1000 Hz<br>
+Stop Bits set to 2 vice 1.5<br>
+Power: 70 Watts.  Compare this to image D<br>
+<br>
+
+</center>
+
+\section rtty_demodulator RTTY demodulator
+
+Fldigi's demodulator uses a design based on theoretical work published by
+Kok Chen, W7AY,
+<a href="http://www.w7ay.net/site/Technical/ATC/">
+http://www.w7ay.net/site/Technical/ATC/.</a>
+<br>
+
+
+\image html RTTY-demodulator.png "Demodulator"
+\image latex RTTY-demodulator.png "Demodulator" width=5.0in
+<br>
+
+The mark and space signals are
+converted to base band and then filtered in a low pass filter.
+Each filter is a variant of Chen's enhanced Nyquist filter.  It is
+implemented using a Fast Overlap-and-Add Fourier Transform.
+<br>
+
+Each time the baud rate is selected the program must "rebuild" the
+digital RTTY filter.  The filter parameters are optimized for the
+baud rate.
+<br>
+
+The detector is an optimized Automatic Threshold Correcting (ATC) type
+described in Chen's paper.
+<br>
+
+To start decoding a signal simply left click on the signal and the AFC should
+lock on to the signal.
+<br>
+
+The digiscope display will extinguish when the Rx signal level falls below
+the squelch setting.
+<br>
+
+It is possible to use fldigi to generate the keying waveform for use with an
+FSK type of transmitter.  See \ref pseudo_fsk_page "Pseudo FSK for a
+description of how this can be accomplished.
+<br>
+
+See \ref rtty_fsk_configuration_page "RTTY Configuration Page"
+
+<br>
+\ref rtty_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Recognitions.txt b/fldigi_doxygen/user_src_docs/Recognitions.txt
new file mode 100644
index 00000000..7554c049
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Recognitions.txt
@@ -0,0 +1,145 @@
+/**
+\page recognitions_page Recognitions
+
+\tableofcontents
+
+This software would not have been possible without the contribution of many
+programmers who have given their best to the open source community.  The
+application is built upon the foundation of the Fast Light Tool
+Kit (http://www.fltk.org), a wonderfully fast and efficient graphical user
+interface design library.  Many have asked what the Fast Light means.  There
+are probably as many answers as there are programmers using the toolkit. I
+prefer to think of it as lightning fast and light on the code size.  Take a
+look at the size of the executable for fldigi and then compare it with
+similar applications.  I think you will be surprised by how small it is for
+what it does.
+<br>
+
+The active current development team consists of:
+<br>
+
+<ul>
+	<li>Dave Freese - W1HKJ</li>
+	<li>Stelios Bounanos - M0GLD</li>
+	<li>Remi Chateauneu - F4ECW</li>
+	<li>Leigh Klotz - WA5ZNU</li>
+	<li>Stephane Fillod - F8CFE</li>
+	<li>John Douyere - VK2ETA</li>
+	<li>Joe Veldhuis - N8FQ</li>
+	<li>Chris Sylvain - KB3CS</li>
+	<li>Gary Robinson - WB8ROL</li>
+	<li>Stefan Fendt - DO2SMF</li>
+    <li>John Phelps - KL4YFD</li>
+    <li>Andrej Lajovic - S57LN</li>
+	<li>Robert Stiles - KK5VD</li>
+</ul>
+
+Localization files:
+<br>
+
+<ul>
+  <li>French: Stephane Fillod - F8CFE</li>
+  <li>German: Marc Richter - DF2MR </li>
+  <li>Italian: Pierfrancesco Caci - IK5PVX</li>
+  <li>Spanish: Pavel Milanes Costa - CO7WT</li>
+  <li>Polish: Roman Bagi&nacute;ski - SP4JEU</li>
+</ul>
+<br>
+
+Several authors have placed their digital modem code and signal
+processing code in the public domain and their source was either an
+inspiration or in some cases formed the backbone of the code used
+in <i>Fldigi</i>.
+<br>
+
+<ul>
+	<li>AE4JY - WinPsk - a windows application </li>
+	<li>Tomi Manninen, OH2BNS - gmfsk - a great digital modem program for Linux</li>
+	<li>Hamish Moffatt, VK3SB - dominoEX code originally for gmfsk</li>
+	<li>Dr. Steven W. Smith - author of "Digital Signal Processing", who
+	has kindly placed an entire book on digital signal processing on the
+	internet.  (http://www.dspguide.com)</li>
+</ul>
+<br>
+
+If you make a side-by-side comparison between gmfsk and fldigi source code
+you will see that they follow the same general structure.  The primary
+difference is that gmfsk is written in the C language and uses the gnome/gtk
+libraries for the user interface.  <i>Fldigi</i> is a C++ application that
+uses the Fast Light Tool Kit (Fltk) gui library.  The design
+of <i>Fldigi</i> puts emphasis on separating the user interface from the
+sound card and transceiver input/output operations. Nearly all modern
+digital modem programs use a programming paradigm called "threads."  Threads
+are light weight processes that share the same memory space, but each has
+its own stack.  The use of threads makes the program look and feel
+responsive to the user while a lot of code is being executed in the
+background.
+<br>
+
+Many of the modem source code files are C to C++ rewrites from the
+gmfsk application.  They say that copying is the best form of
+flattery and gmfsk simply had the best explanations and the easiest
+source code to read and understand.  The author had also spent
+several months creating improvements and fixing bugs in the original
+gmfsk application.  That exercise was the impetus to create <i>Fldigi</i>.
+<br>
+
+The Fast Fourier Transform used by <em>Fldigi</em> is a rewrite of John Green's
+public domain FFT code (<a href="http://download.cnet.com/FFT-for-RISC/3000-2070_4-10003778.html">FFT for RISC for MAC</a>).
+The rewrite is in C++ and is implemented as a C++ template.
+Some of the signal processing algorithms used in <i>Fldigi</i>
+are from Dr. Smith's book.  His on-line publication is sufficient
+to allow you to become fluent in FFT analysis and the creation of
+digital filters.  I printed the relevant pdf files and then
+purchased the hard bound copy.  Improvements to the original gmfsk
+signal processing algorithms can all be attributed to this excellent
+source.
+<br>
+
+And last but certainly not least, I must thank the crew who perform
+alpha testing and on-line support of the application.  These are stalwart amateurs who
+risk their operating system and radio equipment in testing, testing and
+more testing.  Their only reward is in being able to influence the
+design of the application and the fun of seeing it work and the bugs
+disappear.  Thank you to:
+<br>
+
+Call Name      | Call  Name    | Call Name       | Call Name
+:-------------:|:-------------:|:---------------:|:---------------:
+4Z5ST  Boris   | K3GAU  David  | KU1T  Zibi      | VA3DB Dianne
+AA0HW  Chuck   | K4XTT  Victor | KV9U  Rick      | VE3IXI  Dave
+AC7JN  Dave    | K6KAR  Kirk   | N0NB  Nate      | VK2TMG  Brett
+CT1DRB  David  | K7BRK  Chris  | N2AMG Rick      | VK4BDJ David
+CX7BF  Walter  | K4RE  Brian   | N4UM  Tim       | W3NR  Ed
+DF4OR  Ekki    | K9AO  Rick    | N4ZNV  Mike     | W4ROS  Ross
+DK1JBE  Tom    | KB3FN  Lynn   | N6WFL  Jason    | W6JVE  Jim
+DL6XAZ  Fred   | KD0AR  Mike   | N8FQ  Joe       | WA3VPZ  Marshal
+DL8FCL  Walter | KD4O  Phil    | NN8B  Don       | WA4SXZ  Rich
+G0UZP  Paul    | KD8DKT  Mike  | NT1G  Skip      | WB8ROL  Gary
+G3TDJ  Andy    | KE3Y  Travis  | OZ4KK  Erik     | WD4FDW  Steve
+G6CKR  Roger   | KH6TY  Skip   | PA0R  Rein      | WD4FNY  Bill
+G8SQH  David   | KL7NA  Rob    | PA3GWH  Richard | WU9Q  Bob
+
+<br>
+and many others whose names are not listed, please accept my apology.
+<br>
+
+The test team is representative of users on Windows, Linux, Free
+BSD and OS X operating systems.  They have varying interests from
+very slow speed CW to high speed keyboard full break-in CW, from RTTY
+contesters to PSK rag chewers.  They have insisted that
+fldigi perform well under all of those operations.  I have been
+amazed by the global distribution of the testing team.  It is easy
+to think that the internet will be the death of amateur radio.  On
+the contrary it opens up so many additional ways for us to be
+cooperative.
+<br>
+
+
+
+<br>
+\ref recognitions_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/SignalViewers.txt b/fldigi_doxygen/user_src_docs/SignalViewers.txt
new file mode 100644
index 00000000..10840dad
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/SignalViewers.txt
@@ -0,0 +1,27 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+<title>Signal Viewers</title>
+</head>
+<body style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 204);" alink="#000099" link="#000099" vlink="#990099">
+<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
+
+    <tr>
+
+      <td style="vertical-align: top; text-align: left;">
+<img style="width: 822px; height: 676px;" alt="" src="file:///home/dave/W1HKJ/FldigiHelp-3.21/images/main-dialog-browser.png">
+<br>
+      </td>
+    </tr>
+<tr>
+      <td style="vertical-align: top;">
+<img style="width: 430px; height: 447px;" alt="" src="images/signal-viewer.png">
+</td>
+    </tr>
+
+
+</table>
+<br>
+</body>
+</html>
diff --git a/fldigi_doxygen/user_src_docs/SoundCardSetup.txt b/fldigi_doxygen/user_src_docs/SoundCardSetup.txt
new file mode 100644
index 00000000..93a7fc64
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/SoundCardSetup.txt
@@ -0,0 +1,307 @@
+/**
+\page  sound_card_configuration_page Sound Card Configuration
+
+\tableofcontents
+
+A few words about sound I/O on the PC.  "You are in a maze of
+twisty little passages, all alike".
+<br>
+
+PortAudio, PulseAudio and OSS are different ways in which fldigi can
+access your sound card through the various sound systems.
+<br>
+
+OSS was the first audio backend in fldigi. It works with the Linux sound
+system of the same name, which has now been replaced by ALSA but is
+still supported via an emulation layer.  Its only advantage, as an
+audio backend, is that it's simple and doesn't require any
+external libraries.
+
+<br>
+The PortAudio backend was written subsequently to support
+<a href="http://www.opensound.com/">OSS</a> on Linux and FreeBSD,
+<a href="http://www.alsa-project.org/">ALSA</a> and
+<a href="http://jackaudio.org/">JACK</a> on Linux, CoreAudio on OS X,
+and also the various sound APIs on Windows -- all through the same
+<a href="http://www.portaudio.com/">PortAudio</a> library.
+<br>
+
+<a href="http://www.pulseaudio.org/">PulseAudio</a> is more than an
+audio hardware access layer; refer to its website for a
+summary of what it does. Fldigi supports it mainly because many Linux
+distributions are now integrating it with their desktops, but also
+because it has a few interesting features:
+
+<ul>
+	<li>it can take care of the resampling and volume control for us,</li>
+	<li>it can stream audio over the network, and </li>
+	<li>it makes it easier to run multiple fldigi instances (all
+	accessing the same sound card).</li>
+	<li>it provides mixer controls for input and output audio streams</li>
+	<li>it remembers which hardware is used for each application it
+	serves, and it remembers the mixer levels associated with that
+	application</li>
+</ul>
+
+In the future it might be possible to replace all of these with a single
+backend, without any loss of functionality, performance, sound system
+or platform support. That'll be the day! Until then:
+<br>
+
+\image html config-audio-devices.png "Audio Devices"
+\image latex config-audio-devices.png "Audio Devices" width=5.0in
+<br>
+
+<b>On Linux:</b>
+
+<ul>
+	<li>Use	PulseAudio if your Linux distro ships it, and you already have the
+	pulseaudio daemon running (this is the case with Fedora 8/9 and Ubuntu
+	8.04, probably also with openSUSE 11.0). Or if you want networked
+	audio, etc. etc.</li>
+	<li>Otherwise, use PortAudio and select a device
+	from the list(s).  PortAudio is also the best way to access JACK,
+	through which you can use other programs as audio sources/sinks --
+	particularly useful with SDR software. As with PulseAudio, you can
+	select different capture and playback audio devices.</li>
+	<li>The OSS	backend should be used only as a last resort. Note that it
+	has not been updated to support user-configurable sample rates.</li>
+</ul>
+
+<b>On Windows:</b>
+
+Use the PortAudio and select the device from the list(s).
+
+Select the <i>SndCrd</i> tab on the configuration dialog.
+<br>
+
+On Linux Fldigi can interface to the sound card using either the OSS,
+the Portaudio, or the PulseAudio.  Each of the appropriate
+libraries must be present on the computer to use that particular sound
+i/o.
+<br>
+
+On Windows Fldigi uses the Portaudio sound driver only.
+<br>
+
+It is also possible to configure Fldigi with File I/O only, which is
+useful for testing the application without an interface to the sound
+card.  In the File I/O only configuration you can record and
+playback audio files in a number of different formats including the
+"wav" format associated with the Windows operating system.
+<br>
+
+The program will find all active sound cards and the associated drivers
+for both.  Select the sound card and driver type that will be used with the
+program.  I recommend using the Pulseudio device driver if that
+is available on your Linux distribution.
+<br>
+
+\image html config-audio-settings.png "Config Audio Settings"
+\image latex config-audio-settings.png "Config Audio Settings" width=5.0in
+<br>
+
+If Pulse or Port audio is selected then you can either allow the program to
+use the auto detect to determine the best sound card sampling rate, or
+you can pick from the drop down list.  If you know your RX and TX sound card
+oscillator correction factors you can enter them now.  If not you can
+determine the RX rate correction using a special WWV modem built
+into <i>Fldigi</i>.  The decoder and encoder logic for each of the various
+modems require a specific sound card sample rate which may not be the the
+actual sound card sample rate.  The conversion between the modem sample rate
+and the sound card sample rate is accomplished by one of a set of
+sample rate converters.
+<br>
+
+Sound card oscillators may have a slight error in frequency that causes their
+sampling rate to not be the value specified.  This error is usually small
+enough to be measured in a parts per million. Fldigi uses a technique called
+rate conversion to correct the sampled waveform for this error.  The error
+can be measured and the correction factor determined by using
+the \ref digiscope_display_wwv_mode "WWV calibration"
+modem.  The supporting library used for the converter provides
+several different levels of conversion, Best, Medium, Fastest and Linear
+Interpolator.  The default, Medium interpolator, will be
+satisfactory for most sound cards.  If you
+are running fldigi on a computer with limited cpu power you might find
+it necessary to select one of the more cpu efficient converters, either
+Fastest or Linear.  Each gives progressively poorer performance
+but use fewer cpu cycles to perform the frequency conversion.  You
+should also be sure that the cpu type is set to
+\ref miscellaneous_configuration_page "Slow cpu" on the miscellaneous
+configuration tab.
+<br>
+
+\image html config-audio-mixer.png "Audio Mixer"
+\image latex config-audio-mixer.png "Audio Mixer" width=5.0in
+<br>
+
+Mixer controls are only active on Linux using OSS, ALSA backends and if the
+distribution provides application layer mixer support.  Select whether you
+will be using Line-In or Mic-In for the audio connection from the receiver
+output.  Fldigi ALWAYS expects to use the Line-Out for driving the
+transmitter audio. Set the PCM level for your sound card.  If you check
+"Manage mixer" then the Tx and Rx "volume" controls on the main fldigi
+dialog will be active.
+<br>
+
+\section right_chanel_audio Right Channel Audio Output
+
+\image html config-audio-right.png "Right Audio Channel"
+\image latex config-audio-right.png "Right Audio Channel" width=5.0in
+<br>
+
+You may elect to make the right and left channels both contain the
+modem signal.  Or, you may reverse the right and left channel
+audio signals.  These two controls only change the function of the
+audio output.
+<br>
+
+
+\image html stereo-plug.png "Stereo Plug"
+\image latex stereo-plug.png "Stereo Plug" width=3.0in
+<br>
+
+<ol>
+	<li>Sleeve: usually ground</li>
+	<li>Ring: Right-hand channel for stereo signals, negative polarity for
+	balanced mono signals.  Fldigi uses this channel for special
+	controls signals.</li>
+	<li>Tip: Left-hand channel for stereo signals, positive polarity for
+	balanced mono signals.  Fldigi uses this channel for Rx and Tx
+	audio.</li>
+</ol>
+
+<br>
+
+The PTT, CW QSK and Pseudo-FSK items are found on their respective
+configuration tabs.  They are replicated here for your convenience
+and these controls may be changed on this or the other tabs.
+<br>
+
+\section wav_file_sample_rate WAV File Sample Rate
+
+\image html SavedWAVFileSampleRate.png "Sample Rate of Saved WAV Files"
+\image latex SavedWAVFileSampleRate.png "Sample Rate of Saved WAV Files" width=2.0in
+<br>
+
+User selectable WAV file sample rate.
+<br>
+
+\section multiple_sound_cards Multiple sound cards
+
+In systems with multiple sound cards they will not always be in the
+correct sort order on boot.  This may cause problems not only with
+fldigi, but other apps that depend on a certain sound card.  The
+work around is not that difficult and will reliably place the preferred
+sound card in the correct slot. Sound cards are numbered from 0 on to
+however many cards you have in your computer. Usually its only 2.
+<br>
+
+The 1st step is to determine the correct id of the cards in your
+system.  Open a terminal and issue the following :: aplay -l
+<br>
+
+Here is an example of what you may see.<br>
+<br>
+
+\verbatim
+
+**** List of PLAYBACK Hardware Devices ****
+card 0: ICH6 [Intel ICH6], device 0: Intel ICH [Intel ICH6]
+  Subdevices: 1/1
+  Subdevice #0: subdevice #0
+card 0: ICH6 [Intel ICH6], device 4: Intel ICH - IEC958 [Intel ICH6 -
+IEC958]
+  Subdevices: 1/1
+  Subdevice #0: subdevice #0
+card 1: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371
+DAC2/ADC]
+  Subdevices: 1/1
+  Subdevice #0: subdevice #0
+card 1: AudioPCI [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1]
+  Subdevices: 1/1
+  Subdevice #0: subdevice #0
+
+\endverbatim
+
+If it does not already exist you will need to create the following file:<br>
+<br>
+
+<tt>/etc/modprobe.d/alsa-options</tt>
+<br>
+
+You will have to root privileges to create the file, so a system such
+as Ubuntu that depends on sudo you would enter
+<br>
+
+<tt>$ sudo touch /etc/modprobe.d/alsa-options</tt>
+<br>
+
+Using the above example, you edit that file so that it's contents
+contain
+<br>
+
+\# Set preferred order of the sound cards<br>
+
+<tt>
+options snd-ICH6 index=0<br>
+options snd-AudioPCI index=1
+</tt><br>
+<br>
+
+The simplest terminal editor that is on just about every distribution is<br>
+"nano" so to edit the file you just created you can again use sudo<br>
+<br>
+
+<tt>$ sudo nano /etc/modprobe.d/alsa-options</tt>
+<br>
+
+If you want to test this new file, reboot and open a terminal and again
+issue the command :: aplay -l
+<br>
+
+You will normally find that your internet browser and/or Flash want to
+use card 0, so you then may want to consider using card 1 for fldigi
+<br>
+
+Here is another example with 3 sound systems; mother board ALC1200, a
+thumb-drive audio codec, and a SignaLink USB:
+<br>
+
+\verbatim
+
+**** List of PLAYBACK Hardware Devices ****
+card 0: NVidia [HDA NVidia], device 0: ALC1200 Analog [ALC1200 Analog]
+  Subdevices: 1/1
+  Subdevice #0: subdevice #0
+card 1: Set [USB Headphone Set], device 0: USB Audio [USB Audio]
+  Subdevices: 1/1
+  Subdevice #0: subdevice #0
+card 2: default [USB Audio CODEC ], device 0: USB Audio [USB Audio]
+  Subdevices: 1/1
+  Subdevice #0: subdevice #0
+\endverbatim
+
+The /etc/modprobe.d/alsa-options contains these lines
+<br>
+
+\verbatim
+
+options snd-NVidia index=0
+options snd-Set index=1
+options snd-CODEC index=2
+
+\endverbatim
+
+Notice that each line is uniquely related to the aplay -l report
+<br>
+
+
+<br>
+\ref sound_card_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/Spotter.txt b/fldigi_doxygen/user_src_docs/Spotter.txt
new file mode 100644
index 00000000..e2ab5d50
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Spotter.txt
@@ -0,0 +1,149 @@
+/**
+\page  psk_reporter_page PSK Reporter
+
+\tableofcontents
+
+The PSK reporter can generate reception reports from three different sources:
+<br>
+
+<ul>
+	<li>The decoded text, obtained from the Rx Panel text or the multi-channel
+	browser.  Note: <b>the psk browser must be visible</b> or
+	decoding and subsequent psk reporting will not occur.  If you do
+	not want the psk browser panel visible in the main dialog then use the
+	separate browser dialog.  It can be minimized and signal decoding
+	will continue.</li>
+	<li>The log data</li>
+	<li>Data entered manually</li>
+</ul>
+
+The configuration for the PSK reporter in in Misc/Spotting. PSKR needs the
+following fields from the Oper tab to be non-empty:
+<br>
+
+<ol>
+	<li>  Callsign     (freeform because it's impossible to verify, and
+	because we need to support SWLs without callsigns)</li>
+	<li>  Locator      (standard 6 character format)</li>
+	<li>  Antenna info (freeform, should be kept reasonably short)</li>
+</ol>
+
+Sources
+(1) and (2) are configurable from Misc/Spotting configuration tab,
+while (3) is always enabled. To keep the code sane, changing the PSKR
+options (or the above station info) does not take immediate effect.
+Instead, the Initialize button changes color to indicate that the
+changes have not been applied. Clicking on the button will do so (or
+display an error) for the current and future sessions. This is similar
+to the Initialize buttons in the rig control configuration.
+<br>
+
+Here are the options in some more detail:
+<br>
+
+\section auto_spot_calls Automatically spot callsigns in decoded text
+
+The text that is sent to the main window or the PSK browser is continuously
+searched for callsigns. If this option is enabled, the main window gets
+a "Spot" light button that can toggle the auto-spotter on and off. It
+is automatically turned off when playback is selected in the Files
+menu.  The main window text is not searched if the viewer is
+active, i.e., if it is displayed and the current modem is PSK.
+<br>
+
+\section send_report_on_qso Send reception report when logging a QSO
+
+A reception report is queued for every QSO as soon as it's logged
+<br>
+
+\section report_qrg Report QRG (etc.)
+
+This makes the reception reports include the current rig frequency, adjusted
+for modem audio frequency and rig sideband. It does not need a click on
+"Initialize" to take effect. This needs to be an option because it is
+impossible to tell whether the user has real or "fake" rig control with
+100% certainty. Besides that, users may want to run a dedicated spotter
+for a narrow modes sub-band, and in that case they won't have to
+synchronise fldigi's frequency display with the rig all that often.
+<br>
+
+\section host_and_port Host and port
+
+With the port set to 14739 the reports will not be entered in the main
+database, but instead will be analysed and displayed here:
+<br>
+
+<a class="moz-txt-link-freetext" href="http://pskreporter.info/cgi-bin/psk-analysis.pl">http://pskreporter.info/cgi-bin/psk-analysis.pl</a>
+<br>
+
+Probably of no interest to anyone who is not hacking on a PSKR client but
+may be useful for debugging. The PSKR protocol uses UDP with no
+acknowledgements or retransmissions, so don't be surprised if the
+occasional report never makes it to the server.  There should be
+enough coverage overlap to make packet loss irrelevant (and save a lot
+of bandwidth and CPU cycles).
+<br>
+
+The spotter needs to see a repeated callsign within a short search window,
+but stations do not always repeat their callsigns. In addition, some
+operators like to be creative with their macros, and as a result some
+signals will decode 100% but the callsign will never be auto-captured. Such
+callsigns can be reported manually.
+<br>
+
+The manual spotting is done by right-clicking the QRZ "globe" icon. This
+will generate a report for whatever is in the Call &amp; Loc fields, so make
+sure that those are correct! You should also verify the frequency (e.g. by
+placing the waterfall marker on the signal being spotted).
+<br>
+
+There is a confirmation popup that will open when you right click the "globe"
+button.  The aim of course is to avoid accidentally sending
+rubbish reports to the PSK reporter database.
+<br>
+
+Reception reports are filtered for duplicates among all data sources: a
+report is queued only once every hour for each callsign and frequency band.
+The queue is flushed every five minutes. You can see what the spotter is
+doing in the Event Log window or on the terminal if you set the log level to
+"Info". "Debug" will show all the gory details.
+<br>
+
+\image html activity-reports.png "Activity Reports"
+\image latex activity-reports.png "Activity Reports" width=2.0in
+<br>
+
+A button and popup text field on the rig control frame give access to
+the most recent receptions reports in your geographic area.The area is
+determined by the contents of the field to the right of the button, or
+by the locator text on the operator tab if the mini field is empty.
+ The first two characters of the locator are used.  If the
+locator is not set, the pskreporter.info uses the current IP
+geolocation to approximate it.
+<br>
+
+A popup is displayed when the user clicks the button or presses the Enter
+key from within the field.  The popup shows the frequencies by
+measure of activity that gives more weight to transmissions.  If
+rig control is active, the user can click on one of the lines to go to
+that band.  Clicking on the 18100000 (1 report) line would
+immediately QSY the transceiver to 18.1 MHz.
+<br>
+
+The data is retrieved from http://pskreporter.info/cgi-bin/psk-freq.pl
+<br>
+
+or with a filled text field, http://pskreporter.info/cgi-bin/psk-freq.pl?grid=TEXT
+<br>
+
+There is a link to the pskreporter.info map page in the Help menu.
+<br>
+
+
+<br>
+\ref psk_reporter_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/Synop.txt b/fldigi_doxygen/user_src_docs/Synop.txt
new file mode 100644
index 00000000..9616e4e0
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Synop.txt
@@ -0,0 +1,428 @@
+/**
+\page  synop_page SYNOP decoding
+
+\tableofcontents
+
+
+\section what_is_snyop What is Synop
+
+\subsection wether_data Weather data
+
+
+SYNOP, which stands for <a href="http://en.wikipedia.org/wiki/SYNOP">
+<b>surface synoptic observations</b></a> is a numerical code used for
+reporting weather<a href="http://en.wikipedia.org/wiki/Weather" title="Weather"></a>
+observations made by manned and automated fixed land weather stations. It
+is also called FM-12 by the
+<br>
+
+World Meteorological Organization. It is closely associated to
+FM 13-XIV SHIP, for report of surface observation from a sea station
+(Created in 1982) and FM 14-XIV SYNOP MOBIL, for reports of surface
+observation from a mobile land station.
+<br>
+
+
+Here is an example of undecoded SYNOP weather report:<br>
+
+<tt>
+13586 31530 80000 10036 20029 39821 40218 53002 71022 886//<br>
+333 20029 88715=<br>
+</tt>
+
+Many SYNOP reports are available on web sites such as
+<a href="http://www.ogimet.com/synops.phtml.en">Ogimet</a> .
+<br>
+
+\subsection synop_reports Synop reports broadcasts
+
+The most important broadcaster on SYNOP data is DWD, in RTTY mode.
+<br>
+
+\subsubsection deutsche_schedule Deutsche Wetterdienst schedule
+
+SYNOP reports are typically sent every six hours
+by <a href="http://en.wikipedia.org/wiki/Deutscher_Wetterdienst" title="Deutscher Wetterdienst">Deutscher Wetterdienst</a> on <a href="http://en.wikipedia.org/wiki/Shortwave" title="Shortwave" class="mw-redirect">shortwave</a> and <a href="http://en.wikipedia.org/wiki/Low_frequency" title="Low frequency">low frequency</a> using <a href="http://en.wikipedia.org/wiki/Radioteletype" title="Radioteletype">RTTY</a>.
+
+The baud rate must be 50 bauds.
+<br>
+
+Freq          | Station | Time        | <br>
+:-------------|:------|:--------------|:------------
+147,300 kHz   | DDH47 | 05.00 - 22.00 | + / - 42,5
+4583,000 kHz  | DDK2  | 00.00 - 24.00 | + / - 225,0
+7646,000 kHz  | DDH7  | 00.00 - 24.00 | + / - 225,0
+10100,800 kHz | DDK9  | 00.00 - 24.00 | + / - 225,0
+11039,000 kHz | DDH9  | 05.00 - 22.00 | + / - 225,0
+14467,300 kHz | DDH8  | 05.00 - 22.00 | + / - 225,0
+
+
+\subsubsection other_broadcasters Other broadcasters
+
+Until recently, many shore stations used to transmit Synop reports by
+Morse Code (\"<i>Ocean Yacht Navigator</i>\", Kenneth Wilkes, 1976 ). Still,
+according to
+<a href="http://www.wmo.int/pages/prog/www/ois/Operational_Information/VolD_en.html">
+WMO information for shipping</a>,
+a couple of maritime stations might broadcast these informations in
+different mode that RTTY, but this has not been tested yet. There are
+just anecdotically cited here.
+
+<b>Maritime Radio Station of Mumbai</b>
+
+Met codes: FM 12 - SYNOP, FM 13 - SHIP for Sea areas I.
+<br>
+
+Band     | Freq
+:--------|:--------
+WT (MF)  | 500 kHz
+WT (MF)  | 521 kHz
+WT (HF)  | 8630 kHz
+WT (HF)  | 12710 kHz
+
+<br>
+
+SYNOP decoding is not accessible fromMorse CW modem yet.
+<br>
+
+<b>Navtex station of Mumbai. COMCEN</b>
+
+FM 12 SYNOPSIS, FM 13 SHIP for sea area I (Time schedule 0900, 2100)
+<br>
+
+<br> | Freq
+:----|:---------------
+Navtex (Also called MSI as Maritime Safety Information) | 518 kHz
+
+<br>
+
+
+SYNOP decoding is not accessible from Navtex modem yet.
+<br>
+
+<b>Marine Rescue Co-ordination Centre: Guayaquil, Radio IOA (Instituto Oceanografico Armada) o Radio Naval</b>
+
+Meteorological information in process: Text, SHIP, SYNOP.
+<br>
+
+Mode | Freq
+:----|:---------------
+AM   | 1515 kHz
+
+
+<br>
+
+\section synop_parameters Parameters
+
+\image html RTTY-Config-Tab-With-Synop.png "Synop configuration in RTTY tab"
+\image latex RTTY-Config-Tab-With-Synop.png "Synop configuration in RTTY tab" width=5.0in
+<br>
+
+By default, there is not SYNOP decoding of RTTY reception, so its behavior
+does not change. However, it receives three new parameters related to
+Synop decoding.
+
+SYNOP reports can be saved to the current ADIF log file: They are visible in
+the journal of QSOs with the content of the report, the timestamp, and the
+Maidenhead locator equivalent to the geographical coordinates of the
+emitter of the report.
+
+SYNOP weather reports can also be plotted on KML files: They can then be
+visualized in KML viewers such as Google Earth.
+
+If SYNOP reports are saved either to ADIF or KML files, fldigi attempts to
+detect and decode RTTY messages. When these messages are detected, they are
+displayed in the reception window. An extra parameter allows to replace
+the coded Synop message, giving clarity at the risk of loosing
+information, or mix the decoded reports with the original group of
+digits (Interleaving of SYNOP and text).
+
+\section reception_window Reception window
+
+When SYNOP messages are detected, they are displayed in the reception
+window in \"red\" characters (depicted here in \"<i>italic</i>\"). Here are
+some examples (Interleaved text and SYNOP reports):
+<br>
+
+<tt>
+13661 16123 99276 70216 46///<br>
+<i>
+WMO Station=13661<br>
+WMO station=WMO_13661<br>
+ UTC observation time=2013-02-16 12:00<br>
+QLLLL token=Present<br>
+Longitude=-21.6<br>
+Latitude=27.6<br>
+</i>
+
+///// 40206 52011<br>
+222// 00203; <br>
+<i>
+Sea surface temperature=20.3 --C<br>
+Temperature type=Intake measurement<br>
+</i>
+<br>
+64522 16123 99591 70347 46/// <br>
+	<i>WMO Station=64522 <br>
+    WMO station=WMO_64522 <br>
+    UTC observation time=2013-02-16 12:00 <br>
+    QLLLL token=Present <br>
+    Longitude=-34.7<br>
+    Latitude=59.1 </i><br>
+    <br>
+///./ 49920 57004.<br>
+::(1056;<br>
+,
+26555 16123 998#6 <br>
+	<i>WMO Station=26555 <br>
+    WMO station=WMO_26555 <br>
+    UTC observation time=2013-02-16 12:00 </i><br>
+<br>
+70269 46/// ///// 40168 52008;  <br>
+	<i>WMO Station=70269 <br>
+    WMO station=WMO_70269 <br>
+    Precipitations=Omitted, no observation <br>
+    Station type=Automated station. No observation (No 7WW)<br>
+    Visibility=Missing <br>
+    Wind direction=No motion or no waves <br>
+    Wind speed=0 knots (Estimated)<br>
+    Sea level pressure=1016 hPa<br>
+    Pressure tendency=Increasing steadily. Raises <br>
+    Pressure change=0.8 hPa</i><br>
+<br>
+
+25617 16123 99867 1173!((6;  <br>
+	<i>WMO Station=25617 <br>
+    WMO station=WMO_25617 <br>
+    UTC observation time=2013-02-16 12:00 <br>
+    QLLLL token=Present </i><br>
+<br>
+149 52001;<br>
+<br>
+13660 16123 992!; <br>
+	<i>WMO Station=13660 <br>
+    WMO station=WMO_13660 <br>
+    UTC observation time=2013-02-16 12:00 </i><br>
+<br>
+).'/ ///// 40222 52&17<br>
+<br>
+52"// 08)02;<br>
+<br>
+44551 16123 99376 70378 46//.  <br>
+	<i>WMO Station=44551 <br>
+    WMO station=WMO_44551 <br>
+    UTC observation time=2013-02-16 12:00 <br>
+    QLLLL token=Present <br>
+    Longitude=-37.8 <br>
+    Latitude=37.6 </i><br>
+    <br>
+///// 40185 52022;   <br>
+	<i>Sea level pressure=1018 hPa<br>
+    Pressure tendency=Increasing steadily. Raises <br>
+    Pressure change=2.2 hPa</i><br>
+<br>
+
+62680 16123<br>
+9958"     <br>
+	<i>WMO Station=62680 <br>
+    WMO station=Atbara <br>
+    UTC observation time=2013-02-16 12:00 </i><br>
+<br>
+70265 66//? BMPROIIO TUPEQ<br>
+<br>
+222!/ 00078;<br>
+<br>
+64527 16123 99593 70483 46/// <br>
+	<i>WMO Station=64527 <br>
+    WMO station=WMO_64527 <br>
+    UTC observation time=2013-02-16 12:00 <br>
+    QLLLL token=Present <br>
+    Longitude=-48.3 <br>
+    Latitude=59.3 </i><br>
+///// 40095 52004<br>
+<br>
+</tt>
+
+
+\section data_files Data files
+
+Several data files containing public information are used to decrypt SYNOP
+data. They come from various places on the Internet, with redundancy.
+<br>
+
+<table style="text-align: left; width: 905px; height: 360px;" border="1" cellpadding="2" cellspacing="2">
+<tr>
+<td style="vertical-align: top;">NOAA</td>
+<td style="vertical-align: top;">WMO identifier, name and coordinates of thousands of weather stations in the world.</td>
+</tr>
+<tr style="font-family: Courier New,Courier,monospace;">
+<td colspan="2" rowspan="1">
+<a href="http://weather.noaa.gov/data/nsd_bbsss.txt">http://weather.noaa.gov/data/nsd_bbsss.txt</a>
+</td>
+</tr>
+<tr>
+<td style="vertical-align: top;">NOAA</td>
+<td style="vertical-align: top;">Weather, drifting, moored and wave riders  buoys. Oil platforms. Fixed and mobile offshore drilling unit.</td>
+</tr>
+<tr style="font-family: Courier New,Courier,monospace;">
+<td colspan="2" rowspan="1">
+<a href="ftp://tgftp.nws.noaa.gov/data/observations/marine/stations/station_table.txt">ftp://tgftp.nws.noaa.gov/data/observations/marine/stations/station_table.txt</a>
+</td>
+</tr>
+<tr>
+<td style="vertical-align: top;">UK's National Weather Service</td>
+<td style="vertical-align: top;">Name, country and description of weather ships</td>
+</tr>
+<tr style="font-family: Courier New,Courier,monospace;">
+<td colspan="2" rowspan="1">
+<a href="http://www.metoffice.gov.uk/media/csv/e/7/ToR-Stats-SHIP.csv">http://www.metoffice.gov.uk/media/csv/e/7/ToR-Stats-SHIP.csv</a>
+</td>
+</tr>
+<tr>
+<td style="vertical-align: top;">
+Joint WMO IOC Technical Commission for Oceanography and Marine Meteorology
+</td>
+<td style="vertical-align: top;">
+<a href="http://en.wikipedia.org/wiki/Argos_System">Argos</a> and <a href="http://en.wikipedia.org/wiki/Iridium_Communications">Iridium</a> buoys, with WMO identifiers.</td>
+</tr>
+<tr style="font-family: Courier New,Courier,monospace;">
+<td colspan="2" rowspan="1">
+<a href="ftp://ftp.jcommops.org/JCOMMOPS/GTS/wmo/wmo_list.txt">ftp://ftp.jcommops.org/JCOMMOPS/GTS/wmo/wmo_list.txt</a>
+</td>
+</tr>
+</table>
+
+<br>
+
+There is a specific window for downloading the latest version of these data
+files. It can be reached with the command "File/Folders":
+<br>
+
+\image html Opening-DataFiles-Menu.png "How to reach the data files sources menu"
+\image latex Opening-DataFiles-Menu.png "How to reach the data files sources menu" width=3.5in
+<br>
+
+These data files can also be found:
+<br>
+
+<ul>
+	<li>At installation time your fldigi binary comes with a package. All
+	data files are silently installed on your machine.</li>
+	<li>When building your own binary from the sources, with the
+	command <b>make install</b>. Similarly, all files are installed.</li>
+	<li>At first use and automatic installation, this opens the Data files
+	sources menus, where you can download all or some data files used by
+	fldigi.</li>
+</ul>
+
+
+\image html DataFilesSources.png "Downloading and updating data files used for various decodings"
+\image latex DataFilesSources.png "Downloading and updating data files used for various decodings" width=5.0in
+<br>
+
+
+\subsection synop_outputs Outputs
+
+
+Each message is a set of key-value pairs, associated to:
+<br>
+
+Description          | Measurement
+:--------------------|:----------------
+Wind direction       | 315 degrees
+Wind speed           | 8 m/s (Anemometer)
+Temperature          | 0.0 deg C
+Dew point temperature | -3.8 deg C
+Station pressure     | 1006 hPa
+Sea level pressure   | 1030 hPa
+
+
+\subsection output_formats Output formats
+
+\subsubsection ADIF
+
+
+When the option is ticked, SYNOP weather reports are saved in a new ADIF
+record, in the default logfile.
+<br>
+
+The report itself is saved with field <tt>\<NOTES:xx\></tt>.
+The length can be of several hundredth of chars, and accordingly to the
+ADIF standard, new-lines can appear in each report.
+<br>
+
+Example of <tt>\<NOTES\></tt> field in an ADIF record:
+
+\verbatim
+
+Header
+ICAO indicator=LOWM
+Identification and location
+Land station observation
+Land observations
+Precipitations=Precipitation omitted, no precipitation
+Station type=Manned station. 7WW omitted, not significant
+Cloud base=600 to 1000 m
+Visibility=15 km
+Cloud cover=7/8
+
+\endverbatim
+
+<br>
+
+\subsubsection KML
+
+SYNOP reports can generate \ref kml_page "KML"
+files for fixed stations, mobile weather ships, buoys etc... that is,
+every observation which can be associated to a set of coordinates.
+Several reports of the same station can be aggregated in a single
+place mark. Mobile stations have their path drawn, linking all
+coordinates spotted for a given station with an unique name.
+<br>
+
+
+KML data are are also saved in a display-independent format in
+<tt>\<description\></tt> tags, and thus can easily be reused by other
+software.
+<br>
+
+\section command_line_synop Command-line SYNOP decoder program : synop_tool
+
+
+The decoder comes with <tt>synop_tool</tt>,
+a command-line tool able to decode input text files and generate the
+same output files as fldigi. It is intended as a development for
+checking internal consistency, and accuracy of SYNOP decoding without
+the complexity of the graphical interface.
+
+It is accessible in the directory <tt>fldigi/src/synop-src</tt> and must
+be built with the command <tt>make</tt>.
+<br>
+
+Its command-line options are displayed with the option <tt>--help</tt>:
+<br>
+
+\verbatim
+
+[fldigi/src/synop-src]$ ./synop_tool --help
+
+Valid options are:
+    data_dir  # Where the data files are stored. For example /usr/local/share/fldigi/
+    kml_dir   # Out put directory of created KML files.
+    load_dir  # Input directory of KML files loaded at startup.
+    dbg       # Verbose mode.
+    usage     # Print this message.
+    test      # Decoding preceded by an internal test.
+    matrix    # KML output in aggregated matrices (See KML documentation).
+    regex     # text output of regular expressions, not decoded reports.
+    version   # Prints version number.
+    help      # Prints this messages
+
+\endverbatim
+
+<br>
+\ref synop_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Thor.txt b/fldigi_doxygen/user_src_docs/Thor.txt
new file mode 100644
index 00000000..9fec94a2
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Thor.txt
@@ -0,0 +1,75 @@
+/**
+\page  thor_page Thor
+
+\tableofcontents
+
+Thor is a new forward error correcting incremental frequency shift keyed
+communications mode.  It was developed specifically to meet the needs of ARQ
+transfers in the HF spectrum.  It is particularly well suited under
+conditions of atmospheric static noise.  Thor borrows from two current modem
+technologies, \ref mfsk_page "MFSK" and \ref domino_ex_page "DominoEX".
+<br>
+
+Thor emits a distinctive double rising tone sequence at the
+beginning of each transmission.  It is used to flush the receive
+decoder and also provides a visual and audible clue to its being used.
+<br>
+
+The modem code for Thor uses a wide band multiple frequency
+detector that can lock on and detect the incoming signal even when
+badly mistuned.  Frequency domain oversampling is used to allow
+proper tone detection without the need for AFC.  The AFC control does
+not alter the decoder in any way.
+<br>
+
+The waterfall and digiscope will appear as:
+<br>
+
+\image html Thor-1.png "Thor"
+\image latex Thor-1.png "Thor" width=6.0in
+<br>
+
+The text displayed in the status area is the secondary text being sent by the
+transmitting station.  When the keyboard buffer is empty the Thor modem
+transmits text from the secondary text buffer.  Your secondary text buffer
+can be edited on the Thor configuration tab.
+<br>
+
+The digiscope display is similar to the DominoEX display and represents the
+tone pairs moving through the tone filters.  You can also use an alternate
+digiscope display (left click on the digiscope display area).
+<br>
+
+
+\image html dominoex-1a.png "DominoEx"
+\image latex dominoex-1a.png "DominoEx" width=1.0in
+<br>
+
+In this display mode the red line represents the center of the multiple
+tone bins that are in the detector.  The dots will be blurry if the AFC is
+not locked on and become very distinct when AFC lock has been achieved.  The
+tone dots will move from bottom to top (opposite the direction of the
+waterfall).
+<br>
+
+This is the same signal mistuned:
+<br>
+
+\image html dominoex-2.png "DominoEx Mistuned"
+\image latex dominoex-2.png "DominoEx Mistuned" width=6.0in
+<br>
+
+and with the signal badly mistuned:
+<br>
+
+\image html dominoex-3.png "DominoEx Mistuned 2"
+\image latex dominoex-3.png "DominoEx Mistuned 2" width=6.0in
+<br>
+
+
+<br>
+\ref thor_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/TransceiverControl.txt b/fldigi_doxygen/user_src_docs/TransceiverControl.txt
new file mode 100644
index 00000000..c62f2dec
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/TransceiverControl.txt
@@ -0,0 +1,278 @@
+/**
+\page  rig_control_page Rig Control
+
+\tableofcontents
+
+
+\image html init-rig-setup.png "Initial Rig Setup"
+\image latex init-rig-setup.png "Initial Rig Setup" width=2.0in
+<br>
+
+CAT not enabled
+<br>
+
+
+\image html docked-rig-control.png "Docked Rig Control"
+\image latex docked-rig-control.png "Docked Rig Control" width=5.0in
+<br>
+
+CAT not enabled, Manual Entry of transceiver frequency
+<br>
+
+<b>Note: </b>The same control is also used for both manual entry of the
+transceiver frequency or with full CAT control.  When no CAT is available
+the control is simply a convenient way of keeping track of the transceiver
+USB/LSB suppressed carrier frequency, the mode and the audio tracking
+point.  If fldigi is being used with an FM transceiver you probably should
+enter the simplex frequency or the input frequency of a repeater being
+used.  This frequency value is used with the waterfall audio frequency to
+compute the logged frequency.  The logged frequency value will only be
+correct for LSB and USB operation.
+<br>
+
+The frequency/mode pick list is displayed when the book button is
+pressed.  Pressing the book button a second time will restore the
+original logging panel.
+<br>
+
+The pick list buttons control selecting, adding and deleting entries in
+the frequency/mode list.
+<br>
+
+<ul>
+	<li>add the current frequency / mode / audio track point to the list</li>
+	<li>select the current list entry</li>
+	<li>delete the highlighted entry from the list</li>
+	<li>delete all entries from the list (a warning prompt will appear)</li>
+	<li>show active frequencies based on either the entry field to the
+	right or the stations locator,
+	see \ref psk_reporter_page "pskreporter/spotter".</li>
+	<li>entry field for active frequencies search, for example "EM."</li>
+</ul>
+
+
+The browser list contains frequency, sideband, modem type and audio
+frequency.  The list is saved when fldigi is shut down.
+<br>
+
+The combo box on the left will allow the selection and control of the
+operating mode of the transceiver.
+<br>
+
+The combo box on the right will allow the selection and control of the
+transceiver bandwidth.
+<br>
+
+The frequency display is in fact a set of special buttons.  Each
+digit may be left-clicked to increment in frequency by that digit
+value, or right clicked to decrement by that digit value.  The leading
+digits will follow suit if a decade rollover occurs.  You can also place the
+mouse cursor on a digit and then use the mouse wheel to roll the frequency
+up and down.
+<br>
+
+Manual entry of frequency can be accomplished by clicking on any digit and
+then entering the numeric value in KHz.  Don't forget the decimal
+point if you are entering a fractional KHz value.
+<br>
+
+The mode combobox, the bandwidth combobox and the frequency display
+also annunciate the current transceiver status.  If you change
+operating mode on the transceiver, that will be annunciated in the
+respective combobox and fldigi will adjust any internal parameters
+accordingly.  Fldigi queries the transceiver 10 times per second
+to maintain a lock step with the transceiver.
+<br>
+
+\section rig_config  Rig Configuration
+
+<b>Hardware PTT control</b>
+
+\image html config-rig-hardware.png "Hardware PTT control"
+\image latex config-rig-hardware.png "Hardware PTT control" width=5.0in
+<br>
+
+<b>Right Channel VOX Signal</b>
+
+Fldigi can generate a 1000 Hz tone for the duration of the PTT keydown period.
+ A simple tone detector/filter and transistor switch can be used to generate
+a PTT signal from this sound card output.  Jim, W5ZIT, has provided
+details on building an \ref w5zit_rt_channel_page "interface" for this
+type of PTT control.
+<br>
+
+<b>Serial Port using DTR or RTS</b>
+<br>
+
+The simplest rig control is just being able to control the push to talk via
+an external transistor switch.  You set this type of control on the first
+configuration tab for rig control.
+<br>
+
+You select this operation by checking the "Use serial port PTT".
+ Select the serial port from the list (fldigi will have searched
+for available ports).  Then specify whether the h/w uses RTS or
+DTR and whether a + or - voltage is required to toggle PTT on.
+
+You can use a serial port for control with the RTS and DTR pins
+configured for you particular interface.
+The program allows you to use RTS, DTR or BOTH for the PTT
+signal.  Press the Initialize button to start the serial port.
+<br>
+
+<b>Parallel Port (Linux and Free BSD only)</b>
+<br>
+
+Fldigi sets and clears the parallel port pin, PARPORT_CONTROL_INIT, pin 16 on
+the 25 pin parallel port connector.  Keydown sets Pin 16 to +5
+volts and keyup sets the voltage to zero.
+<br>
+
+<b>&mu;H Router (MacOS X)</b>
+<br>
+
+Simular functionality can be achieved on the Macintosh operating system using
+'&mu;H Router' by Kok Chen, W7AY.   See
+<a href="http://www.w7ay.net/site/Applications/Router/index.html">&mu;H Router Website</a>
+for specific details and requirements. A selectable (check box) option will be
+available on the Rig->Hardware PTT Configuration panel.
+<br>
+
+<b>PTT delays</b>
+<br>
+
+You can accommodate delays in transceiver switching between
+receive and transmit by adjusting the PTT delays.  The control
+values are in milliseconds.  These controls have no effect on
+external PTT circuits such as those implemented in the SignaLink
+interfaces.  They rely on detecting the audio data stream.
+You can use a combination of macro tags in a macro key definition to
+achieve a resolution.  For example try a macro definition similar
+to this to insure that the RSID is sent via a slow FM xcvr (or via a
+VHF repeater)
+<br>
+
+\verbatim
+
+<TX><MODEM:NULL><IDLE:2.5>
+<!MODEM:MT63-500>
+<TXRSID:on>
+
+\endverbatim
+
+<br>
+
+Change the idle time value (in fractional seconds) to suit your needs.
+<br>
+
+\section rig_cat_control RigCAT control
+
+\image html config-rig-rigcat.png "RigCAT control"
+\image latex config-rig-rigcat.png "RigCAT control" width=5.0in
+<br>
+
+
+RigCAT is a rig control system similar to hamlib that was developed
+specifically for fldigi.  It uses command / response definitions that
+are found in various \ref rig_xml_page "rig.xml"
+files.  You can use a rig.xml file specific for your transceiver or
+write and test one yourself.  The easiest way is to adapt an existing
+rig xml file for a rig that is similar to your own.  ICOM almost
+identical command/response strings for all of its transceiver line.
+ Yaesu rigs have nearly all used unique command/response structures
+until just recently.  The TS-450, TS-950 and others share a similar set
+of commands and responses.
+<br>
+
+RigCAT commands and responses are defined in a rig specific xml file which
+contains all of the required queries and responses in extended markup
+language format. Please read the specification
+document \ref rig_xml_page "rigxml" to learn more about this new way of
+building generic rig interface definitions and how they are used with
+fldigi.  fldigi will look for a file in the $HOME/.fldigi/rigs directory for
+all files with extension ".xml".  These contain definitions for the
+transceiver indicated by the file name, ie: FT-450.xml, IC-756PRO.xml,
+etc.  You can download the appropriate xml files from the resource directory
+tree <a href="http://www.w1hkj.com/xmls">http://www.w1hkj.com/xmls</a>
+or from the
+archives <a href="http://www.w1hkj.com/xmlarchives.html">web page</a>.  Place
+the file in your rigs directory and fldigi will find it.
+<br>
+
+You will need to specify how your PTT will be triggered.  This can be
+using a CAT command, the RTS or DTR pins or none.  None would be
+appropriate if you are using the rig's VOX or an outboard sound card
+interface such as the SignalLink SL-1+ which produces its own VOX type of
+PTT.  In that case simply leave all of the PTT options unselected.
+<br>
+
+If you are using a transceiver or a rig interface such as CI-V that echos
+all serial data you check off the "Commands are echoed" box.  That
+will suppress fldigi trying to respond to a command it just sent to the
+transceiver.
+<br>
+
+You may need to try various values of retries, retry interval, and command
+interval to achieve consistent rigcat control.
+<br>
+
+Press the Initialize button after setting all of the parameters.  If the
+settings are all correct fldigi should start receiving frequency
+information from the rig and annunciating them on the rig control
+frequency display.
+
+\section hamlib_cat_control Hamlib CAT control
+
+Hamlib is a set of standard libraries for interfacing to a large number of
+transceivers.  The hamlib library system consists of a front end
+which acts on behalf of all rigs and backends which are specific to
+each rig.
+<br>
+
+\image html config-rig-hamlib.png "Hamlib CAT Control"
+\image latex config-rig-hamlib.png "Hamlib CAT Control" width=5.0in
+<br>
+
+Select your transceiver from the list of supported units.  Then select
+the serial port and baud rate.  If you are familiar with the
+hamlib library you can send various startup sequences to the rig using
+the advanced configuration.  PTT control can be achieved using CAT
+commands or via DTR / RTS on the same port as the control comms.
+ You might also need to specifiy whether RTS/CTS flow control is
+uses (Kenwood rigs use this quite often) or if Xon/Xoff flow control is
+used.
+<br>
+
+You may need to try various values of retries, retry interval, and command
+interval to achieve consistent hamlib control.
+<br>
+
+Press the Initialize button after setting all of the parameters.  If the
+settings are all correct fldigi should start receiving frequency
+information from the rig and annunciating them on the rig control
+frequency display.
+<br>
+
+\section xml_rpc_cat Xml-Rpc CAT
+<br>
+
+\image html config-rig-xmlrpc.png "Xml-Rpc CAT Control"
+\image latex config-rig-xmlrpc.png "Xml-Rpc CAT Control" width=5.0in
+<br>
+
+
+Xml-Rpc allows third party software to control various aspects of fldigi
+operation including but not limited to rig control.  This is the data
+interface that is also used by the program <b>flrig</b>, a fldigi
+companion transceiver control program.
+<br>
+
+If you are using a third party interface such as DxKeeper Bridge you might
+be instructed to select this method of CAT.
+<br>
+
+\ref rig_control_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/UTF8.txt b/fldigi_doxygen/user_src_docs/UTF8.txt
new file mode 100644
index 00000000..feef83bb
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/UTF8.txt
@@ -0,0 +1,44 @@
+/**
+\page  utf8_support_page UTF-8 support
+
+\tableofcontents
+
+
+Fldigi supports the UTF-8 character set in all of it's labels and
+widgets (controls).  The Rx and Tx text panels accept both keyboard
+and text stream that is in UTF-8 format.  Transmission of UTF-8
+characters is supported by these modes:
+<br>
+
+<ul>
+  <li>PSK, PSKR, and Multi-Channel PSK/PSKR</li>
+  <li>Olivia - must enable 8 bit extended characters</li>
+  <li>MT63 - must enable 8 bit extended characters</li>
+  <li>MFSK - all baudrates supported</li>
+</ul>
+<br>
+
+
+For example, the following Russian and annotated texts can be sent and
+received:
+<br>
+
+\image html UTF8-Example.png "UTF-8 Encoded Characters"
+\image latex UTF8-Example.png "UTF-8 Encoded Characters" width=3.5in
+<br>
+
+
+UTF-8 characters are represented by 2 bytes which means that a single
+character will take longer to transmit.  Transmission speed will
+be further reduced on modes like PSK where the character to bit stream
+conversion has been optimized for the English language.
+<br>
+
+
+<br>
+\ref utf8_support_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/WEFAX.txt b/fldigi_doxygen/user_src_docs/WEFAX.txt
new file mode 100644
index 00000000..9d4ff98c
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/WEFAX.txt
@@ -0,0 +1,359 @@
+/**
+\page  wefax_page WEFAX
+
+\tableofcontents
+
+
+This modem is able to receive and transmit HF-Fax images, traditionally used
+for weather reports.
+<br>
+
+More technical information is available on the wikipedia
+article <a href="http://en.wikipedia.org/wiki/Radiofax">Radiofax</a>.
+<br>
+
+Two modes are implemented IOC=576 or 288. The focus is made on
+black-and-white images, color mode is still experimental.
+<br>
+
+Many frequencies are available
+at <a href="http://www.hffax.com">http://www.hffax.com/</a> for example.
+<br>
+
+When entering any Wefax mode, the reception window opens, and optionally the
+transmit window. it is always possible to bypass this with the menu
+bar:
+<br>
+
+\image html Wefax-Tab.png "WEFAX"
+\image latex Wefax-Tab.png "WEFAX" width=6.0in
+<br>
+
+\section wefax_config Configuration.
+As for any modem, weather fax has its own tab in the configuration window.
+<br>
+
+\image html Wefax-Configuration.png "WEFAX Configuration"
+\image latex Wefax-Configuration.png "WEFAX Configuration" width=6.0in
+<br>
+
+\subsection embeded_wefax Embedded vs floating display mode
+
+There are two display modes for this modem:
+<br>
+
+<ul>
+	<li>Embedded mode: This is the default mode, the normal receipt and
+	transmit windows gets graphic (Like Hellschreiber mode).</li>
+	<li>Floating mode: There are two separate windows  for transmission and
+	reception. This was the only available mode until fldigi 3.21.49.</li>
+</ul>
+
+\image html Wefax-Detached-Windows.png "Detached WEFAX Window"
+\image latex Wefax-Detached-Windows.png "Detached WEFAX Window" width=6.0in
+<br>
+
+\subsection hide_tx_window Hide transmission window.
+
+This option, allows to closed by default, the transmission window, when
+entering Wefax mode. In embedded mode, this means that the entire
+window is used for reception (Most common mode). In floating mode, this
+implies that the transmission window is not opened by default.However,
+it is always possible to manually open or close the transmission window
+at any time.
+<br>
+
+\subsection logging_adif Logging messages to ADIF file
+
+Each time an image is saved, it is possible to log this event, with the
+frequency and reception time, to the Adif file. This option is disabled by
+default.
+
+\subsection fsk_adjust Frequency shift adjustment
+
+The default frequency is 800 Hz. However, it is possible to adjust for
+example to 850 Hz for Deutsche Wetter Dienst.
+<br>
+
+\subsection max_rows Maximum rows number
+
+It non-continuous (Non non-stop) reception mode, an image is
+automatically saved when it has more than this number of lines
+(Default 2500 lines). Once this number of rows is reached, the image
+is saved and a new image is read with the same parameters. This feature
+has two applications:
+<br>
+
+<ul>
+	<li>In automatic mode (APT control), if an image end is not detected, we
+	can guarantee that the result will take no more than, for example, the
+	size of two faxes. Typical faxes have about 1300 lines, so the max lines
+	parameters can be tuned to, for example, 200 lines.</li>
+	<li>In manual mode, where images are read continuously, this cuts the
+	received images into chunks of equal size.</li>
+</ul>
+
+\subsection dest_dir Destination directory for saved images
+
+Received images are saved in the default folder
+
+<tt>$HOME/.fldigi/images (Linux) or \<defaultpath\>/fldigi.files/images</tt>
+
+(Windows).
+<br>
+
+Additionally, they can be saved manually, at any time, using the
+button 'Save'. The PNG images  received some extra text comments which can be
+displayed, for example, with GIMP.
+<br>
+
+\subsection mono_images Monochrome images
+
+Fax images are monochromes and are saved as such by default. However, it is
+possible to bypass this parameter and save them as color RGB images.
+<br>
+
+\section tx_image Transmitting an Image
+
+To open the transmit window, you must of course select one of the two
+Wefax modems, and then right-click on the transmit (blue) window:
+<br>
+
+Then, the transmit window just opens. This is the same logic as sending MFSK
+images.
+<br>
+
+Then, you must open an image file using the button "Load". The image is then
+displayed, for example like that:
+<br>
+
+\image html Transmit_A.png "Transmitting"
+\image latex Transmit_A.png "Transmitting" width=3.0in
+<br>
+
+Now, to start the transmission, you just need to click "Tx B/W" for
+black-and-white images, etc... During transmission, image reception is
+paused. The window will display each image line as it is sent. Please
+be patient, this may take a while. You might note that FlDigi status
+line displays the estimation transmit time, and the current stage
+(Start, phasing etc...); Color transmission ('<i>Tx Color</i>') is
+intentionally disabled at the moment.
+<br>
+
+\image html Wefax-Sending.png "Sending"
+\image latex Wefax-Sending.png "Sending" width=6.0in
+
+
+\section rx_image Receiving an image
+<br>
+
+\image html Reception.png "Reception"
+\image latex Reception.png "Reception" width=6.0in
+<br>
+
+
+To enter reception mode, one can click the "View" menu tab, and select
+"Weather Fax Image".
+<br>
+
+At this time, the reception window opens. A big blank picture is visible,
+this is where the received image will be displayed. Several controls
+are available:
+<br>
+
+<ul>
+	<li>Save: This allows to save the current image as a PNG file at any
+	moment.</li>
+	<li>Non-stop: At startup, the modem goes into automatic mode, and the
+	text "Abort" is displayed. When clicking "Abort", this blanks the image
+	and resets the APT detection. When "Manual mode'" is clicked, no APT
+	detection is done. The Automatic/Manual mode is displayed in the
+	reception window label.</li>
+	<li>Pause/Resume: At any moment, the image reception can be paused
+	and resumed (State is displayed in the reception window label).</li>
+	<li>Zoom: This allows to zoom in/out the image.</li>
+	<li>FIR:
+	This allows to select an input FIR (Finite Impulse Response) filter.
+	Practically, the narrow filter (Default value) gives the best results.
+	The selected value is saved in the configuration file.</li>
+	<li>Skip
+	APT/Skip phasing: When in automatic mode, this allows to skip detection
+	steps. This is often necessary when the signal is not very good.</li>
+</ul>
+
+When receiving an image, either in manual or automatic mode (APT control),
+other controls are displayed:
+<br>
+
+<ul>
+	<li>Line: The number of the line currently received.</li>
+	<li>Width: The image width in pixels. This is usually 1809, if LPM
+	is 120.</li>
+	<li>LPM:
+	Lines per minute: Typically 120, can be 60, 90, 120 or 240. This is
+	detected in automatic mode, but can be manually adjusted.</li>
+	<li>Slant:
+	This is used to adjust the slant of the image due to a clock
+	inaccuracy. This value is saved in the configuration file, so it is
+	not	needed to reenter it each time.</li>
+	<li>Center: This is used to manually adjust the horizontal center of
+	the image, if it could not be detected in the phasing step.</li>
+	<li>Auto:
+	When this button is set, the image will be automatically centered. This
+	process starts after some hundredth of lines are received, by shifting
+	left and right the image. It takes some time to converge.</li>
+</ul>
+
+<br>
+\image html Wefax-File-Received.png "Received WEFAX File"
+\image latex Wefax-File-Received.png "Received WEFAX File" width=6.0in
+<br>
+
+\subsection apt_control_mode APT control reception mode
+
+This mode uses the APT start and STOP frequencies to detect the beginning
+and end of an image. Additionally, it tries to detect the phasing
+signal - a wide black band - to detect the center of the image. This
+method is helped by the estimation of the signal power of these
+frequencies.
+<br>
+
+\subsection manual_reception Manual reception mode (Non-Stop)
+
+In this mode, the image is continuously read and displayed. When the
+maximum number of lines is reached, the image is saved and blanked, and
+the line counter returns to one.
+<br>
+
+\subsection input_fir Input FIR filters
+
+There are three input Finite Impulse Response filters available. Here
+are their frequency characteristics:
+<br>
+
+Narrow filter, the default one, give the better results.
+<br>
+
+\image html narrow.png "Narrow filter response"
+\image latex narrow.png "Narrow filter response" width=3.0in
+<br>
+
+\image html middle.png "Middle filter response"
+\image latex middle.png "Middle filter response" width=3.0in
+<br>
+
+\image html wide.png "Wide filter response"
+\image latex wide.png "Wide filter response" width=3.0in
+<br>
+
+\subsection center_image Centering an image
+
+If the phasing was not automatically detected, the modem could not deduce
+the beginning of an image. The result is an image which is horizontally
+shifted. To correct this, one can use the "Center" slider.
+<br>
+
+\subsection picture_slant Picture with a slant
+
+If either the send, receive or both ends of the transmission are using an
+uncalibrated sound card whose sampling rate is not an exact multiple of the
+sample rate the resulting picture at the receive end will appear
+slanted.  The degree of slant is directly related to the accumulation of
+the frequency error at both ends of the transfer.  Stations wishing to
+receive Weather fax pictures should calibrate their sound card.
+
+The \ref digiscope_display_wwv_mode "WWV calibration mode" is used
+to measure and set the parts per million (ppm) correction factor for the
+sound card.
+<br>
+
+Your sound system may be fully corrected, but the sending station may have
+an uncorrected sound card.  You can usually correct for small
+errors during reception by using the slant slider. Its value (Typically
+between - 0.005 and 0.005) will be stored in fldigi configuration
+parameters.
+<br>
+
+\subsection auto_center Automatic centering.
+
+If the phasing signal could not be used for centering the image, the
+program waits for a string image signal anyway to go into reception
+mode, but it sets an internal flag allowing to automatically center the
+image. This feature can be freely enabled and disabled at any moment.
+it works by detecting a wide vertical band of about hundred pixels,
+where the sum of the contrast as the lowest among the complete image
+width.
+<br>
+
+That is: It computes for each row and each pixel, the
+absolute value of the horizontal derivate. It then sums these
+derivatives pixel-wise, row by row. Then, it computes an average of
+about hundred pixels along this single row. The column which has the
+lowest averaged contrast is considered to be the image margin, which is
+then shifted on the left of the window.
+<br>
+
+This method takes some time to stabilize, because at the beginning, there
+are many areas of the image, without details. It gets stable at the end,
+when only the margin stays with few contrasted details.
+<br>
+
+\subsection image_detection Image detection based on signal power
+
+The APT control - inherited from the Hamfax signal, does not work very
+well when the image is noised. On the other hand, fldigi provides ways
+to evaluate the signal power on a given bandwith. This is used because
+APT control relies on the emission on specific frequencies.
+<br>
+
+Therefore, in the APT start and phasing loops, when check for the presence of
+strong signals associated to APT control. This information is used to
+take a decision when the traditionally method does not detect anything.
+<br>
+
+These two methods are interchangeable but used together for better detection.
+<br>
+
+\subsection afc_control AFC: Automatic Frequency Control
+
+This option controls the frequency on the complete spectrum width. After
+several hunderads of lines have been correctly loaded (That is, with a
+high line-to-line correlation), the AFC locks until the frequency or
+mode is manually changed.
+<br>
+
+\subsection noise_elimination Noise elimination
+
+This option eliminates short-lived noise, individual pixels with a different
+value from their horizontal neighbors. They are modified using median
+values. This is based on the fact that no line should be narrower than
+two pixels, otherwise such an image would not be broadcast, because not
+correctly readable. It is therefore impossible to have one single
+pixel, simultaneously very different from its left and right neighbors.
+<br>
+
+\subsection binary_images Binary images
+
+Faxes can be stored as binary or grey level images. The cutoff level between
+black and white (Default 128) can be adjusted. No information is lost
+until the image is saved, therefore this level can be freely modified
+until image end. The purpose of this option is to save disk space.
+<br>
+
+\subsection display_files Displaying received files
+
+Each time the end of an image is detected, an image file is created and its
+name appears on the file list of the reception window. By clicking on a
+file name, it is displayed in the transmit window.
+<br>
+
+\image html Wefax-Display-And-Receive.png "Received Image"
+\image latex Wefax-Display-And-Receive.png "Received Image" width=6.0in
+<br>
+
+<br>
+\ref wefax_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/WWV-xmt.txt b/fldigi_doxygen/user_src_docs/WWV-xmt.txt
new file mode 100644
index 00000000..c34826e3
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/WWV-xmt.txt
@@ -0,0 +1,59 @@
+/**
+\page  wwv_tx_mode WWV transmit mode
+
+\tableofcontents
+
+The WWV mode is normally used to measure the offset of the sound card
+oscillator.  (see \ref digiscope_display_wwv_mode "WWV ppm measurement").
+<br>
+
+It can also be used to transmit time tick signals similar to the format
+that is used by WWV.  The WWV modem sends a time tick which is a
+200 msec wide pulse at a once per second rate when the T/R button is
+enabled.  This pulse is shaped with a 4 msec raised cosine shape
+on the leading and trailing edges to reduce key clicks.  The
+accuracy of the transmitted time tick is solely dependent on the
+accuracy with which the WWV ppm measurement was performed.
+<br>
+
+The purpose of the WWV time tick transmission is to allow other
+stations to calibrate their sound cards against your calibrated
+system.  This can be used to align all systems in a VHF/UHF net
+for example.  It is only necessary for one of the net members to
+be able to calibrate his or her sound card against WWV.  The
+other's would then be calibrated by proxy use of the WWV time tick
+transmit mode.  This can even be used in the case where no member has
+access to a HF transceiver.  The "master" station would set the Rx
+and Tx ppm settings to zero.  It would then transmit the time tick
+signal for the other stations to calibrate their sound cards against
+the master sound card.  Having all of the stations calibrated in
+this way will insure that the modem decoders will give maximum
+performance.  Here is an example of an \ref inline_macro_page "advanced macro"
+ that will send a CW announcement, 2 minutes of time ticks and end with
+another CW announcement.
+<br>
+
+\verbatim
+
+<MODEM:CW>
+<!GOFREQ:1000>
+<!WPM:24>
+QRZ QRZ de <MYCALL> <MYCALL>
+2 minute time tick cal run follows
+<IDLE:2>
+<!MODEM:WWV><!IDLE:120>
+<!MODEM:CW><!IDLE:2>
+end of time tick run
+de <MYCALL> k
+<TX><RX>
+
+\endverbatim
+
+
+<br>
+<br>
+\ref wwv_tx_mode "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/WindowsOS.txt b/fldigi_doxygen/user_src_docs/WindowsOS.txt
new file mode 100644
index 00000000..aaafaf6b
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/WindowsOS.txt
@@ -0,0 +1,146 @@
+/**
+\page  installing_on_windows_page Installing Fldigi on Windows
+
+\tableofcontents
+
+
+The port of fldigi to the Windows operating system is built using
+cross-compilers on Linux.  The cross-compilation environment is
+created using mingw32.
+<br>
+
+Installing fldigi on windows is very simple.  Simply execute the
+installer program and both fldigi and flarq will be installed in the
+default programs directory structure for the specific Microsoft version
+that is being targeted.  Desktop icons and desktop menu items will
+be created.  An uninstaller link will be created on the desktop
+menu.
+<br>
+
+
+Click on the desktop icon to start the application.  If this is a
+new installation you will be guided through the inital configuration
+with a \ref wizard_page "new install wizard".
+<br>
+
+
+Resize the main dialog to suit your screen.  Adjust the Rx/Tx divider to your
+liking.  Then set up the operator and sound card configuration
+items; \ref configuration_page "configuring fldigi".   When
+you have fldigi receiving and decoding signals you can exit the
+application which will allow you to save your configuration settings.
+<br>
+
+Now open up the following folder using your windows file explorer if you do
+not have a login name and password:
+<br>
+
+<table>
+	<tr><td>On XP </td>
+	<td>C:\\\"Documents and Settings\\<urlogin\>\\fldigi.files\"</td></tr>
+	<tr><td>On W2K</td>
+	<td>C:\\\"Documents and Settings\\<urlogin\>\\fldigi.files\"</td></tr>
+	<tr><td>On Vista/Win7</td>
+	<td>C:\\User\\<urlogin\>\\fldigi.files\</td></tr>
+</table>
+
+where \<urlogin\> is the name with which you log onto the computer.
+<br>
+
+All of these files were generated by fldigi when it first started.  The files
+with the extension pal are palette definition files.  The file "macros.mdf"
+contains the macro definitions which you can change using the macro editor.
+ fldigi.prefs and fldigi_def.xml are used for storing the application state
+and configuration items respectively.  With the exception of the location of
+this folder the operation of fldigi on windows is identical to linux.  In
+all instances where the help files make reference to $HOME/.fldigi you
+should be substitute the appropriate directory for XP or Vista/Win7.
+<br>
+
+Please take the time to read and reread the on-line help file.  Better
+yet download the Adobe Reader file so that you can view the help
+locally without needing access to the internet.  Fldigi is a large
+complex program with many ways for the user to customize its operation
+to his or her hardware environment.
+<br>
+
+
+\section special_note Special Note for Vista/Win7 from user!
+
+I am trying to install the latest and greatest version of FLDIGI and
+FLARQ on a new Toshiba laptop computer that runs Vista/Win7 / Win7.  The main
+screen of FLDIGI comes up ok and it says that no call sign has been set
+and down in the bottom center right there is an <b>error message about
+there not being the sound card that it thinks it should see</b>.
+I understand the messages as the program needs to be configured.
+The problem is that when I click on 'Configuration' the main screen
+grays out and it seems to go off into never never land and not comeback
+or put up the configuration window.  At that point the only thing
+that works on the main screen is the close button.  What am I
+missing?
+<br>
+
+I solved the mystery!  Cockpit error, kind of!  I tried
+installing MULTIPSK and got the "no sound card error" also.  Went
+into the Control Panel to see what was going on.  When I looked at
+sound input it said there was NO microphone plugged in.  Then the
+light came on and I remembered that you MUST have a microphone plugged
+in when using the Vista OS or it doesn't think there is a sound card in
+the computer!!!  Well this is my first encounter with Vista and
+how am I suppose to know or remember that little quark on an OS I've
+never used before??
+<br>
+
+Once I plugged a mic into the sound card input both programs worked
+just fine.
+<br>
+
+<b>Vista/Win7 requires</b> either a <b>microphone</b> or a <b>line-in</b>
+device actually plugged into the 8 mm audio jack before the sound
+driver reports that there is an audio capture device.
+<br>
+
+\section install_on_thumb_drive Installing fldigi programs on thumb drive
+
+Create a folder on a USB drive (any removable read/writable media).  Suggest
+using the folder name NBEMSapps.  Then copy the following files to
+that folder.
+<br>
+
+<ul>
+	<li>fldigi.exe</li>
+	<li>flarq.exe</li>
+	<li>flmsg.exe</li>
+	<li>flamp.exe</li>
+</ul>
+
+Optional installs are the remaining suite of FLDIGI programs.
+<br>
+
+<b>Note</b>: Dynamic libraries (mingwm10.dll, pthreadGC2.dll) are no longer
+required on current versions of the FLDIGI suite of programs.
+<br>
+
+Create a file in that folder named NBEMS.DIR.
+<br>
+
+Then start fldigi etc, from within that folder.  Double clicking
+on the executable from the File Explorer is probably the easiest way to
+do that.  The standard data folders for each application will be
+created and used from within this folder, for example if the thumb
+drive were mounted as drive E:
+<br>
+
+<tt>
+E:\\NBEMSapps\\fldigi.files<br>
+E:\\NBEMSapps\\NBEMS.files<br>
+</tt>
+<br>
+
+
+<br>
+\ref installing_on_windows_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/Wizard.txt b/fldigi_doxygen/user_src_docs/Wizard.txt
new file mode 100644
index 00000000..8b736a68
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/Wizard.txt
@@ -0,0 +1,53 @@
+/**
+\page  wizard_page New Install Wizard
+
+\tableofcontents
+
+New Install Wizard
+
+The new installation wizard borrows from the normal configuration
+dialogs.  You will find information on setting each of the wizard dialog
+pages on the associated configuration link.
+<br>
+
+<center>
+
+\image html wizard-page_1.png "Wizard Configuration"
+\image latex wizard-page_1.png "Wizard Configuration" width=5.0in
+<br>
+
+\image html wizard-page_2-Operator-Information.png "Operator Configuration"
+\image latex wizard-page_2-Operator-Information.png "Operator Configuration" width=5.0in
+<br>
+
+See \ref operator_configuration_page "Operator Configuration"
+<br>
+
+\image html wizard-page_3-AudioDevices-Device.png "Sound Card Configuration"
+\image latex wizard-page_3-AudioDevices-Device.png "Sound Card Configuration" width=5.0in
+<br>
+
+See \ref sound_card_configuration_page "Sound Card Configuration"
+<br>
+
+\image html wizard-page_4-txControl-RigCat.png "Transceiver Configuration"
+\image latex wizard-page_4-txControl-RigCat.png "Transceiver Configuration" width=5.0in
+<br>
+
+See \ref rig_control_page "Transceiver Configuration"
+<br>
+
+\image html wizard-page_5-Tabular-Data.png "Tabular Configuration"
+\image latex wizard-page_5-Tabular-Data.png "Tabular Configuration" width=5.0in
+<br>
+
+See \ref supporting_data_files_page "Tabular Data"
+
+</center>
+
+<br>
+\ref wizard_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/advanced_qsy.txt b/fldigi_doxygen/user_src_docs/advanced_qsy.txt
new file mode 100644
index 00000000..1a8a52aa
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/advanced_qsy.txt
@@ -0,0 +1,128 @@
+/**
+\page advanced_qsy_page  Advanced QSY operations
+
+\tableofcontents
+
+<br>
+The&lt;QSY:FFF.F[:NNNN]&gt;
+macro tag and its delayed flavour&lt;!QSY:FFF.F[:NNNN]&gt; allows
+the user to set the transceiver frequency to FFF.F (In kHz) and optionaly set
+the audio frequency to NNNN (In Hz).<br><br>It is possible to give
+several frequencies, which specify a frequency set. When the macro is
+executed, it choses the first frequency of this set greater than the
+current one. If the current frequency is greater than any frequency of
+the set, then the macro choses the smallest, first frequency of this
+set.<br><br>The utility of this feature is to allow a scan of a range of
+frequencies by re-executing the same macro over and over. Each time the
+macro is executed, the
+next frequency of the set is selected. It can typically be used to
+iteratively try several frequency for a given test.
+<br>
+<br>
+The frequency set can be specified in two distinct ways, which can be freely
+combined together.
+<br>
+<br>
+
+\section dist_freq Distinct frequencies
+
+Several distinct separated with a
+semi-column, in increasing order.
+For example:
+<br>
+<br>
+
+&lt;QSY:2616.6;3287.6;3853.1;4608.1;4780.1;7878.1;8038.1:1900&gt;
+<br>
+<br>
+It means that the transceiver frequency will be set to 2616.6 kHz, then at
+next execution to 3853.1 kHz etc... and will loop back to 2616.6 kHz.
+Each time the same (optional) audio frequency will be set to 1900 Hz.
+In this specific case, it allows to test several Weather Fax broadcast stations,
+until the operator finds an active one.
+<br>
+<br>
+
+\section freq_inc Frequencies with increments
+
+A frequency can come with an increment: This means an implicit range of
+frequencies from this one to the next frequency. If the last frequency
+has an increment, it is never taken into account: The last frequency is
+always an upper limit. Let's consider this
+example:
+<br>
+<br>
+&lt;QSY:89000+100;102000&gt;<br><br>It is equivalent to:
+<br>
+<br>
+&lt;QSY:89000;89100;89200;89300;...;101900;102000&gt;
+<br>
+<br>
+In this case, it allows fldigi to scan all FM frequencies by clicking
+the macro button.
+<br>
+
+\section combo_with Combination with \<TIMER\> macro tag.
+
+If the macro is automatically reexecuted using the &lt;TIMER&gt;, the
+same logic applies. At each run of the macro, the next frequency is
+chosen. The following macro transmits the same message on the
+frequencies 144800 MHz, 144900 ... until 146000 then loops back,
+waiting five seconds between each transmission.
+<br>
+<br>
+&lt;TX&gt;&lt;QSY:144800.00+100;146000&gt;&lt;MODEM:NULL&gt;&lt;!MODEM:PACKET&gt;
+<br>
+&lt;FREQ&gt; CQ CQ de &lt;MYCALL&gt;&lt;RX&gt;&lt;TIMER:5&gt;
+
+<br>
+\section exec_error Execution errors.
+
+Several error messages can be displayed in the macro editor in case of a
+parameter. If this happens, the execution of the macro is stopped. Here
+is the list of possible messages:
+<br>
+
+\section invalid_freq Invalid frequency range
+There must be valid frequencies. This macro will display the
+message:<br>&lt;QSY:abcdef&gt;
+
+<br>
+
+\section inc_pos Increment must be positive
+
+The frequency increment must be positive.
+This macro will fail:
+<br>
+&lt;QSY:89000-1000;88000&gt;
+<br>
+
+\section freeq_not_pos Frequency not positive
+All frequencies must be strictly positive.
+<br>
+\section freq_inc Frequencies must be increasing
+
+The sequence of frequencies must be strictly increasing. Thus, this error
+message can appear with a macro such as:
+<br>
+<br>
+&lt;QSY:89000;88000&gt;
+
+<br>
+\section inline_marco Inline Macro Tags
+
+Unless otherwise noted all of the macro tags discussed thus far are
+meant to be executed at the time that the macro is invoked by the
+button closure. It is possible by execution of the tag to be
+delated until it appears in the transmit data stream. This
+delayed execution capability is limited to a select number of
+tags. See \ref inline_macro_page "Inline Macro Tags"
+for a list of these tags and examples.
+
+<br>
+\ref advanced_qsy_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/buildinfo.txt b/fldigi_doxygen/user_src_docs/buildinfo.txt
new file mode 100644
index 00000000..bb568e67
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/buildinfo.txt
@@ -0,0 +1,68 @@
+/**
+\page build_info_page Build Information
+
+\tableofcontents
+
+\section sub_build_info Build Info
+
+The following is obtained by executing "fldigi --version"
+
+\verbatim
+Build information:
+built :
+
+Fri Dec 25 15:57:13 CST 2009 by dave@linux-dev on i686-pc-linux-gnu for
+i686-pc-linux-gnu
+
+ configure flags: '--without-asciidoc' '--enable-optimizations=native'
+
+ compiler : gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
+
+ compiler flags : -I$(srcdir) -I$(srcdir)/include
+-I$(srcdir)/irrxml -I$(srcdir)/fileselector -pthread
+-I/usr/local/include -I/usr/local/include -I/usr/include/freetype2
+-D_THREAD_SAFE -D_REENTRANT -D_REENTRANT -I/usr/local/include
+-I/usr/include/libpng12 -I/usr/local/include -pipe -Wall -fexceptions
+-O2 -ffast-math -finline-functions -fomit-frame-pointer -march=native
+-mfpmath=sse -DNDEBUG
+
+ linker flags : -L/usr/local/lib -lportaudio -lm
+-lpthread -L/usr/local/lib -lfltk_images -lpng -lz -ljpeg -lfltk -lXft
+-lpthread -ldl -lm -lXext -lX11 -lX11 -lsndfile -lsamplerate
+-lpulse-simple -lpulse -L/usr/local/lib -lhamlib -lm -lpng12
+-L/usr/local/lib -lxmlrpc_server_abyss++ -lxmlrpc_server++
+-lxmlrpc_server_abyss -lxmlrpc_server -lxmlrpc_abyss -lpthread
+-lxmlrpc++ -lxmlrpc -lxmlrpc_util -lxmlrpc_xmlparse -lxmlrpc_xmltok
+-ldl -lrt -lpthread
+
+ libraries : FLTK 1.3.2
+ libsamplerate 0.1.4
+ libsndfile 1.0.17
+ PortAudio 19
+ PulseAudio 0.9.14
+ Hamlib 1.2.10
+ XMLRPC-C 1.06.31
+
+Runtime information:
+system : Linux
+linux-dev 2.6.28-17-generic #58-Ubuntu SMP Tue Dec 1 18:57:07 UTC 2009
+i686
+
+ libraries : libsamplerate-0.1.4 (c) 2002-2008 Erik de Castro Lopo
+ libsndfile-1.0.17
+
+PortAudio V19-devel (built May 25 2009 06:36:24) 1899
+Pulseaudio 0.9.14
+
+Hamlib version 1.2.10
+
+\endverbatim
+
+
+<br>
+\ref build_info_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/cabrilloreporter.txt b/fldigi_doxygen/user_src_docs/cabrilloreporter.txt
new file mode 100644
index 00000000..e9441d6b
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/cabrilloreporter.txt
@@ -0,0 +1,145 @@
+/**
+\page cabrillo_report_page  Cabrillo Report
+
+\tableofcontents
+
+\image html CabrilloSetup.png "Cabrillo Report"
+\image latex CabrilloSetup.png "Cabrillo Report" width=4.0in
+<br>
+
+Fldigi can generate a basic Cabrillo report that meets most contest needs.
+<br>
+
+Selecting the "File/Log/Cabrillo report" menu item opens the following
+dialog:
+<br>
+
+If you want to export every record press the "Check All" in the left
+panel.
+<br>
+
+Select the Contest type from the pull down menu in the right panel.
+Fldigi knows how to format the various fields for each contest.
+When satisfied with the setup press OK. You will then have
+the opportunity to specify the location and name of the cabrillo output
+file.
+<br>
+
+If you use the \ref contest_how_to_page \<XBEG\>...\<XEND\> to
+capture your outgoing exchange, OR if you choose to capture all received
+exchange information in the "Exch" field on the  \ref qso_log_book_page "" panel then
+you should be careful not to duplicate the data in the Caprillo report. For
+example:
+<br>
+
+You captured outgoing exchange data as \<XBEG\>\<RST\> \<CNTR\>\<XEND\>. Do
+not enable the "RST sent" and "Serial # out" check boxes as this info is
+already contained in the "Exchange in" field.
+<br>
+
+You captured incoming exchange data into the Exch field as RST SER#
+TIME. Do not enable the "RST rcvd" or the "Serial # in" check
+boxes.
+<br>
+
+You must then open the file with a plain text editor and
+modify the appropriate entries. Check with each contest sponsor
+to see what their requirements are.
+<br>
+
+Here is an example of a generated cabrillo report format before being edited:
+
+\verbatim
+START-OF-LOG: 3.0
+CREATED-BY: fldigi 3.11
+
+# The callsign used during the contest.
+CALLSIGN: W1HKJ
+
+# ASSISTED or NON-ASSISTED
+CATEGORY-ASSISTED:
+
+# Band: ALL, 160M, 80M, 40M, 20M, 15M, 10M, 6M, 2M, 222, 432, 902, 1.2G
+CATEGORY-BAND:
+
+# Mode: SSB, CW, RTTY, MIXED
+CATEGORY-MODE:
+
+# Operator: SINGLE-OP, MULTI-OP, CHECKLOG
+CATEGORY-OPERATOR:
+
+# Power: HIGH, LOW, QRP
+CATEGORY-POWER:
+
+# Station: FIXED, MOBILE, PORTABLE, ROVER, EXPEDITION, HQ, SCHOOL
+CATEGORY-STATION:
+
+# Time: 6-HOURS, 12-HOURS, 24-HOURS
+CATEGORY-TIME:
+
+# Transmitter: ONE, TWO, LIMITED, UNLIMITED, SWL
+CATEGORY-TRANSMITTER:
+
+# Overlay: ROOKIE, TB-WIRES, NOVICE-TECH, OVER-50
+CATEGORY-OVERLAY:
+
+# Integer number
+CLAIMED-SCORE:
+
+# Name of the radio club with which the score should be aggregated.
+CLUB:
+
+# Contest: AP-SPRINT, ARRL-10, ARRL-160, ARRL-DX-CW, ARRL-DX-SSB, ARRL-SS-CW,
+# ARRL-SS-SSB, ARRL-UHF-AUG, ARRL-VHF-JAN, ARRL-VHF-JUN, ARRL-VHF-SEP,
+# ARRL-RTTY, BARTG-RTTY, CQ-160-CW, CQ-160-SSB, CQ-WPX-CW, CQ-WPX-RTTY,
+# CQ-WPX-SSB, CQ-VHF, CQ-WW-CW, CQ-WW-RTTY, CQ-WW-SSB, DARC-WAEDC-CW,
+# DARC-WAEDC-RTTY, DARC-WAEDC-SSB, FCG-FQP, IARU-HF, JIDX-CW, JIDX-SSB,
+# NAQP-CW, NAQP-RTTY, NAQP-SSB, NA-SPRINT-CW, NA-SPRINT-SSB, NCCC-CQP,
+# NEQP, OCEANIA-DX-CW, OCEANIA-DX-SSB, RDXC, RSGB-IOTA, SAC-CW, SAC-SSB,
+# STEW-PERRY, TARA-RTTY
+CONTEST: ARRL-RTTY
+
+# Optional email address
+EMAIL:
+
+LOCATION:
+
+# Operator name
+NAME:
+
+# Maximum 4 address lines.
+ADDRESS:
+ADDRESS:
+ADDRESS:
+ADDRESS:
+
+# A space-delimited list of operator callsign(s).
+OPERATORS:
+
+# Offtime yyyy-mm-dd nnnn yyyy-mm-dd nnnn
+# OFFTIME:
+
+# Soapbox comments.
+SOAPBOX:
+SOAPBOX:
+SOAPBOX:
+
+QSO: 14095 RY 2009-01-04 1952 W1HKJ 599 GA 12345   ND2T          599 CA 67890
+QSO: 14098 RY 2009-01-04 1949 W1HKJ 599 GA         W0SD          599 SD
+QSO: 14099 RY 2009-01-04 1948 W1HKJ 599 1234567890 KB7Q          599 1234567890
+QSO: 14100 RY 2009-01-04 1948 W1HKJ 599 GA         N6WS          599 CA
+QSO: 14103 RY 2009-01-04 1946 W1HKJ 599 GA         VE6AO         599 AB
+END-OF-LOG:
+
+\endverbatim
+
+<br>
+
+\ref cabrillo_report_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
+
diff --git a/fldigi_doxygen/user_src_docs/colorsandfonts.txt b/fldigi_doxygen/user_src_docs/colorsandfonts.txt
new file mode 100644
index 00000000..a70fdfad
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/colorsandfonts.txt
@@ -0,0 +1,188 @@
+/**
+\page colors_and_fonts_page Colors and Fonts
+\tableofcontents
+
+<br>
+"System colors" are set by command line switches. The default is black
+on a white background.
+<br>
+
+From the Menu <b>Configure/Defaults</b> select the menu item
+<b>Colors and Fonts</b> and then select one of the following tabs.
+<br>
+
+\section text_controls Text Ctrls
+
+\image html ColorsFonts-rxtx.png "Colors Fonts RX / TX"
+\image latex ColorsFonts-rxtx.png "Colors Fonts RX / TX" width=5.0in
+
+The initial color, font and font-size for the Rx and Tx panel are the
+default values. You can always return to these by pressing the Defaults
+button. The background color, font and font-size are independently
+selectable. The Rx panel displays text in one of 5 colors:
+<br>
+
+<ul>
+<li>normal received text - "Rx font" button</li>
+<li>transmitted text - XMIT button</li>
+<li>control characters - CTRL button</li>
+<li>skipped characters (Tx ON/OFF in Tx pane) - SKIP button</li>
+<li>quick view characters - ALTR button</li>
+<li>select text highlight - SEL button</li>
+</ul>
+
+The text widget used
+for Rx, Tx and Event log displays has been improved to give better
+performance with proportional fonts. Fixed width fonts still give
+better performance and are not as demanding on the cpu. There are
+several very good fixed width fonts that include a slashed zero which
+are available for both Windows and Linux. If you are using a
+proportional font and find that the Rx text display gets unresponsive
+with large amounts of text then you should change to a fixed width
+font. Do a search on the internet for "Andale Mono" or "Consolas".
+Both are excellent fonts for this use.
+
+
+\section character_set Character Set Selection
+
+\image html config-ui-rxtext-2.png "Character set"
+\image latex config-ui-rxtext-2.png "Character set" width=2.0in
+
+This setting affects how fldigi encodes the text that it transmits and how
+it interprets what it receives. This mainly matters if you intend to
+transmit and/or receive text containing characters that are not in the
+English alphabet (for example letters with diacritics, Cyrillic letters,
+Japanese script and similar). Successful transmission and reception of such
+symbols is only possible if both your and the correspondent's program are
+set to use the same encoding. Seeing "strange" characters instead of what
+you would expect for example "&amp;ccaron;" always turning up as
+\latexonly "\`{e}" \endlatexonly \htmlonly "&#232;" \endhtmlonly indicates
+that there is probably a mismatch between your encoding and the correspondent's.
+<br>
+
+Leaving this control set to UTF-8 (the default) is strongly recommended
+as this is a cover-all encoding that enables communication in almost
+any language and script imaginable. However, there are three cases in
+which you might want to switch encodings (at least temporarily):<br>
+
+
+<ul>
+<li>You never expect to transmit or view any character except
+for the lower 128 characters (ASCII) of the ANSI data set. This
+might be true for English to English communications in which you do not
+want to have decoded noise appear as UTF-8 character renditions.<br></li>
+<li>You want to communicate using non-English characters, but
+the correspondent's program does not support UTF-8. In such a case, you
+should find out what encoding the correspondent is using and change
+your setting accordingly.</li>
+<li>You expect to exchange a lot of traffic that mostly
+consists of non-English characters (communication in Cyrillic script
+being a notable example). UTF-8 encodes each non-English character into
+a symbol two to four bytes long. Such characters require more time to
+transmit and thus reduce the effective transmission speed. Choosing
+another encoding that requires less bytes to be sent might be
+beneficial if the transmission speed is crucial. For example, a pair of
+operators wanting to communicate in Cyrillic script might want to
+choose CP1251 to retain the maximum transmission speed.</li>
+</ul>
+
+Warning: transmission of non-English characters, regardless of the
+encoding used, requires that the digital mode used be capable of
+handling 8-bit traffic. The following modes suit this requirement:
+<br>
+
+<ul>
+<li>DominoEX</li>
+<li>MFSK</li>
+<li>MT63 (8 bit extended characters must be enabled)</li>
+<li>Olivia (8 bit extended characters must be enabled)</li>
+<li>PSK (all variants)</li>
+<li>THOR</li>
+</ul>
+
+<br>
+
+\section freq_display Frequency Display
+
+\image html ColorsFonts-dsp.png "Frequency Display"
+\image latex ColorsFonts-dsp.png "Frequency Display" width=5.0in
+
+The rig control panel uses a special button for each digit the represents
+the transceiver frequency. The buttons are responsive to mouse
+clicks on the upper and lower half with corresponding changes it that
+unit's value. Unit value is also controlled by the mouse wheel
+when the cursor is over a particular digit. Select the background
+and foreground colors to please your overall color scheme and for best
+visual acuity. The System colors are the same ones that are used
+by all input and output text controls.
+<br>
+
+\section logging_controls Logging controls
+
+\image html ColorsFonts-log.png "Logging controls"
+\image latex ColorsFonts-log.png "Logging controls" width=5.0in
+
+You can select the background color, the font, the font color and the
+font size for both the logging controls on the main dialog and the
+separate logbook dialog.
+
+\section func_keys Func keys
+
+\image html ColorsFonts-fkeys.png "Colors Fonts FKeys"
+\image latex ColorsFonts-fkeys.png "Colors Fonts FKeys" width=5.0in
+
+You can color code the macro (function key) buttons in groups of 4,
+F1-F4, F5-F8, and F9-F12. The background color for each group is
+adjusted by clicking the respective Bkgnd button. The text color
+for the button labels is adjusted by clicking on the Label Txt button.
+The colors will change on these buttons and also on the main
+dialog as you make these adjustments. The Defaults button
+restores the colors as shown in this view.
+
+\section tab_colors Tab Colors
+
+\image html ColorsFonts-tabs.png "Colors Fonts Tabs"
+\image latex ColorsFonts-tabs.png "Colors Fonts Tabs" width=5.0in
+
+Adjust the color of all tabs to suit your personal taste.
+
+\section light_botton_colors Light Buttons Colors
+
+\image html ColorsFonts-buttons.png "Colors Fonts Buttons"
+\image latex ColorsFonts-buttons.png "Colors Fonts Buttons" width=5.0in
+
+<ul>
+<li>Adjust the "on" color of Spot, RxID, TxID, Tune, Lk, Rev, T/R and AFC
+button</li>
+<li>Adjust the "enabled" and "on" colors of the Sql button</li>
+</ul>
+
+
+\section signal_level Signal Level
+
+\image html ColorsFonts-siglvl.png "Colors Fonts Signal Level"
+\image latex ColorsFonts-siglvl.png "Colors Fonts Signal Level" width=5.0in
+
+<br>
+You can select the low/normal/high/over-drive colors for the diamond signal
+level in the lower right hand corner of the main dialog.<br>.
+<br>
+\image html Level-Indicator.png "Level Indicator"
+\image latex Level-Indicator.png "Level Indicator" width=2.0in
+
+<br>
+
+Your audio Rx level should be set to allow the loudest signals to drive
+the indicator into the yellow and never into the red zone.<br>
+<br>
+
+
+
+<br>
+\ref colors_and_fonts_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/commandline.txt b/fldigi_doxygen/user_src_docs/commandline.txt
new file mode 100644
index 00000000..29bf1943
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/commandline.txt
@@ -0,0 +1,136 @@
+/**
+\page command_line_switches_page Command Line Switches
+
+\tableofcontents
+
+\verbatim
+
+Usage:
+    fldigi [option...]
+
+fldigi options:
+
+  --home-dir DIRECTORY
+    Set the home directory to full pathname of DIRECTORY
+    fldigi will put the file stores
+      .fldigi.files, and .nbems.files
+    in this directory
+    The default is: /Users/robert/
+
+  --config-dir DIRECTORY
+    Look for configuration files in DIRECTORY
+    The default is: /Users/robert/.fldigi/
+
+  --arq-server-address HOSTNAME
+    Set the ARQ TCP server address
+    The default is: 127.0.0.1
+
+  --arq-server-port PORT
+    Set the ARQ TCP server port
+    The default is: 7322
+
+  --flmsg-dir DIRECTORY
+    Look for flmsg files in DIRECTORY
+    The default is /Users/robert/.nbems/
+
+  --auto-dir DIRECTORY
+    Look for wrap_auto_file files in DIRECTORY
+    The default is /Users/robert/.nbems/WRAP/auto/
+
+  --xmlrpc-server-address HOSTNAME
+    Set the XML-RPC server address
+    The default is: 127.0.0.1
+
+  --xmlrpc-server-port PORT
+    Set the XML-RPC server port
+    The default is: 7362
+
+  --xmlrpc-allow REGEX
+    Allow only the methods whose names match REGEX
+
+  --xmlrpc-deny REGEX
+    Allow only the methods whose names don't match REGEX
+
+  --xmlrpc-list
+    List all available methods
+
+  --cpu-speed-test
+    Perform the CPU speed test, show results in the event log
+    and possibly change options.
+
+  --noise
+    Unhide controls for noise tests
+
+  --wfall-only
+    Hide all controls but the waterfall
+
+  --debug-level LEVEL
+    Set the event log verbosity
+
+  --debug-pskmail
+    Enable logging for pskmail / arq events
+
+  --debug-audio
+    Enable logging for sound-card events
+
+  --version
+    Print version information
+
+  --build-info
+    Print build information
+
+  --help
+    Print this option help
+
+Standard FLTK options:
+
+   -bg COLOR, -background COLOR
+    Set the background color
+   -bg2 COLOR, -background2 COLOR
+    Set the secondary (text) background color
+
+   -di DISPLAY, -display DISPLAY
+    Set the X display to use DISPLAY,
+    format is ``host:n.n''
+
+   -dn, -dnd or -nodn, -nodnd
+    Enable or disable drag and drop copy and paste in text fields
+
+   -fg COLOR, -foreground COLOR
+    Set the foreground color
+
+   -g GEOMETRY, -geometry GEOMETRY
+    Set the initial window size and position
+    GEOMETRY format is ``WxH+X+Y''
+    ** fldigi may override this setting **
+
+   -i, -iconic
+    Start fldigi in iconified state
+
+   -k, -kbd or -nok, -nokbd
+    Enable or disable visible keyboard focus in non-text widgets
+
+   -na CLASSNAME, -name CLASSNAME
+    Set the window class to CLASSNAME
+
+   -ti WINDOWTITLE, -title WINDOWTITLE
+    Set the window title
+
+Additional UI options:
+
+  --font FONT[:SIZE]
+    Set the widget font and (optionally) size
+    The default is: Arial:12
+
+
+\endverbatim
+
+
+
+<br>
+\ref command_line_switches_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/configCW.txt b/fldigi_doxygen/user_src_docs/configCW.txt
new file mode 100755
index 00000000..6530b00c
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configCW.txt
@@ -0,0 +1,288 @@
+/**
+\page cw_configuration_page  CW Configuration
+
+\tableofcontents
+<br>
+\image html config-cw-general.png "General CW Configuration"
+\image latex config-cw-general.png "General CW Configuration" width=5.0in
+<br>
+
+Fldigi can send and receive morse code from 5 wpm to 200 wpm. The
+operating controls for CW are found on the Config/CW tab. You can
+open that tab by selecting the "Configure/Modems" menu item and the
+clicking on the Modems/CW tab. You can also open up the CW tab by
+first selecting CW as the operating mode and then clicking on the
+left-most item "CW" on the status bar at the bottom of the fldigi main
+window. During operation the Rx and Tx WPM settings are
+annunciated on the status bar in the two boxes next to the mode
+indicator.<br>
+
+<br>The CW signals are converted to a baseband signal. It is the
+digital equivalent of tuning an analog USB transceiver so that the
+carrier is exactly at the CW carrier frequency. The CW decoder
+can use one of two different DSP filters. The Fast Fourier
+Transform (FFT) filter is implemented with a sin(x)/x
+impulse response. This is a very steep sided low pass
+filter. Unchecking the FFT filter causes the decoder to use a
+Finite Impulse Response (FIR) filter with a cutoff slope that is not as
+steep. The FFT filter is optimum when receiving CW in a white
+noise environment. The FIR filter may give better response with
+impulse noise. Selected a "Matched" filter for either the FFT or
+FIR implementation optimizes the filter bandwidth for white noise
+suppression. A lot of impuse noise (static) can cause either
+filter to ring and increasing the filter bandwidth might improve
+detection in that electrical environment.
+<br>
+<br>
+
+Fldigi can track the incoming signal. Enable Rx WPM tracking by enabling
+the check box "Enable Tx Trkg". The tracking range (+/- Hz around the
+TxWPM setting) can be set using the "Rx Trkg Rng" control. When
+tracking is enabled the tracking filter is reset every time the
+transmit WPM is adjusted.
+<br>
+<br>
+
+CW detection is basically an amplitude demodulator. You can set
+the threshold for detecting when the signal transitions from off-to-on
+and on-to-off. These signal levels are relative to the average
+signal level. The on-to-off is the "Lower" value and the
+off-to-on the "Upper." This implementation provides a hysteresis
+detector. Early fldigi CW decoders used this scheme but the
+detection levels were not adjustable.
+<br>
+<br>
+
+The RxWPM control is an indicator and is not used for setting the operation
+of the CW decoder.
+<br>
+<br>
+
+"SOM decoding" provides a fuzzy logic implementation to match the RX
+stream detected on-off sequence to a "best fit" character. It can
+increase the probability of correctly identifying the text character
+under very noisy conditions.
+<br>
+
+The TxWPM sliding controller is used to set the transmit WPM. To
+make the setting easier two additional controls are provided.
+"Lower" sets the lower limit of the slider and "Upper" sets the
+upper limit of the slider. The resolution of the TxWPM slider is
+1 WPM. The Lower/Upper controls are in in 5 WPM increments.
+<br>
+<br>
+
+The transmit encoder settings for WPM can also be adjusted with three hot
+keys:
+<br>
+
+<ul>
+<li>Numeric keypad "+" increases the TxWPM by 1</li>
+<li>Numeric keypad "-" decreases the TxWPM by 1</li>
+<li>Numeric keypad "*" toggles between the selected TxWPM and a default WPM</li>
+</ul>
+
+The "Default" control on the CW tab sets that default value. As
+shown above the TxWPM is 30 and the default is 18. If during a
+QSO you needed to slow down to give the other op a better chance to
+copy what you are sending, just hit the "*" on the numeric keypad and
+the CW code will immediately switch to sending CW at the set default
+value (18 wpm in this example). Press the "*" again to return to
+back to the CW speed that you were previously using.<br>
+
+\section subsec_timing Timing
+<br>
+
+\image html config-cw-qsk.png "Timing"
+\image latex config-cw-qsk.png "Timing" width=5.0in
+<br>
+<br>
+
+Fldigi generates CW by inserting a keyed tone at the current
+waterfall audio frequency. The transceiver should be operated in
+either USB (preferred) or LSB mode.
+The CW signal is completely generated in the software so it is possible
+to control many aspects of the CW signal. The actual transmitted
+signal will be at the USB carrier + the audio frequency, or the LSB carrier -
+the audio frequency. If fldigi is tracking and receiving a CW
+signal on the waterfall your transmitted signal will be exactly on the
+frequency of the other operator. The CW generated this way
+has a nearly ideal attack and decay time, controlled by the software modem.
+But ... a caveat ... your transmitter must never be
+overdriven and it should have excellent opposite sideband suppression.
+Overdriving the transmitter can cause multiple audio signals
+within the SSB passband, and cause unwanted interference to other ops.
+The same is true for a poorly designed or adjusted transmitter
+with bad sideband suppression. I recommend having a trusted
+and knowledgable operator assist you when first trying A2 CW.
+Have them carefully look for evidence of your signal above and below your
+primary signal (by at least +/- 3 Khz). If there is no
+evidence of extra signals then your are set to go. If there is you
+might want to have the transceiver adusted for sideband suppression, or check
+to be sure you are not over driving the audio.
+
+<ul>
+<li>Wt % control sets the weight of the CW. Normal CW is at 50%
+weight, ie: a dot is equal to the interval between dots or between code
+elements. It has a range of 20 to 80 percent.</li>
+
+<li>Dash/Dot controls the relative weight between a dash and a dot.
+The standard for CW is 3 to 1. The dash is 3 times the
+length of a dot. Some operators prefer the sound of either a
+heavier or lighter sounding CW. This control can be adjusted from
+2.5 to 4.0 in 0.1 increments.</li>
+
+<li>Edge shape provides two leading/trailing edge shapes (1) Hanning, or raised
+cosine, and (2) Blackman a modified raised cosine with a steeper attack
+and decay. Both of these edge shapes give a more narrow bandwidth
+CW signal than the traditional exponential waveform. They are
+very easy to listen to even at speeds exceeding 100 wpm.</li>
+
+<li>The Edge control sets the rise and fall times of the CW waveform.
+It can be set anywhere from 0.0 to 15.0 milliseconds in
+0.1 millisecond increments. DO NOT operate A2 CW with the control
+set below 4 msec. This is the control that sets the effective
+bandwidth and sound of your CW. If the edge is too steep you will
+have a clicky signal and be the bane of the CW bands. The
+purpose of being able to set the edge to 0.0 or a very quick rise/fall
+time is explained below. A good setting for nice sounding CW at
+40 WPM and below is 4 to 6 milliseconds.</li>
+
+<li>Edge decreases pulse width, when checked will give a slightly narrower dot
+length as the edge timing is increased. This is useful when
+operating QSK and listening between the character elements.</li>
+</ul>
+
+This is what the A2 signal should look like with various settings of
+weight, Dash/Dot and Edge. The audio frequency is 400 Hz and
+the TxWPM is 100 WPM.
+<br>
+<br>
+
+\image html cw-00-30.png "Dash/Dot = 3.0, Edge = 0.0"
+\image latex cw-00-30.png "Dash/Dot = 3.0, Edge = 0.0" width=3.0in
+<br>
+\image html cw-00-40.png "Dash/Dot = 4.0, Edge = 0.0"
+\image latex cw-00-40.png "Dash/Dot = 4.0, Edge = 0.0" width=3.0in
+<br>
+\image html cw-30-30.png "Dash/Dot = 3.0, Edge = 3 msec"
+\image latex cw-30-30.png "Dash/Dot = 3.0, Edge = 3 msec" width=3.0in
+<br>
+\image html cw-60-30.png "Dash/Dot = 3.0, Edge = 6 msec"
+\image latex cw-60-30.png "Dash/Dot = 3.0, Edge = 6 msec" width=3.0in
+<br>
+\image html cw-120-30.png "Dash/Dot = 3.0, Edge = 12 msec"
+\image latex cw-120-30.png "Dash/Dot = 3.0, Edge = 12 msec" width=3.0in
+<br>
+
+Changing the weight, dash/dot or edge of the waveform does not change
+the WPM at which the code is generated. When a conflict
+occurs between the various settings WPM takes first priority, and Edge second.
+In the above examples, the Edge setting could not exceed 12
+msec even if the control were set higher than 12.0. The figures
+were generated by capturing the output data being sent to the sound card and
+then formatting it using Gnumeric. An oscilloscope photo of
+the signal is virtually identical.<br>
+<br>
+
+The setting for inter-character and inter-word spacings are fixed at 3
+and 7 respectively. The 3 is achieved by sending a silent
+period of 1 dot (element) length at the beginning of each character and 2 at
+the end of each character (shown in the figures). This silent
+period is sufficient for most transceivers to respond to the PTT signal
+which occurs at the beginning of the transmission so that the first dit
+or dash is not lost in transmission.QRQ (high speed CW operation)<br>
+<br>
+
+You may wonder why fldigi can go as high as 200 WPM. It's hard to
+believe but there are CW operators who can decode 100+ WPM in their
+head. These operators also usually operate QSK (full
+breakin). A2 CW and PTT operation and QRQ/QSK are not a natural mix.
+But fldigi can be used for this type of operation if an
+external keyer is used. For that purpose the A2 Tx output from fldigi
+is full wave rectified and detected to create a keyline control.
+The outboard conversion from A2 to keyline requires a nearly square wave
+pulse output of audio at the CW keying rate. Setting the Edge
+control to 0.0 and then the audio frequency to about 1000 Hz provides
+the needed signal to effect this type of keyline control.<br>
+<br>
+
+If you are operating QSK with a separate receiver / transmitter you can
+very quickly stop your transmit signal with the TAB key. In
+the CW mode only the TAB key causes the program to skip over the remaining
+text in the transmit text buffer. The text that is skipped
+will be color coded blue. The program remains in the transmit mode
+(PTT enabled), but since the buffer is now empty no A2 CW signal is
+generated. Code transmission will then restart with the very
+next keyboard closure of a valid CW character. The Escape and
+Pause/Break keys still can be used to respectively abort and pause
+transmission.
+<br>
+
+\section subsec_qsk QSK
+<br>
+
+You might ask why fldigi doesn't simply provide a keyline output on
+one of the parallel port pins or on RTS or DTR via a comm port.
+The answer is quite simple. Linux is a multi-tasking
+operating system and the interaction between the OS and the application
+causes the timing to be adversely effected.  The driver
+implementation of the audio sub system must be responsive and so the OS
+gives that sub system a very high priority in its multi-tasking
+structure.
+<br>
+<br>
+
+Many QSK operators use high speed diode antenna switching between
+receiver and antenna. fldigi generates a signal that can be used
+for that purpose. The left audio channel is always theAFCW
+signal. When selected the right audio channel can be configured to
+generate a square wave signal that begins earlier and ends later than each
+of the CW elements. The square wave signal can be rectified and filtered
+to provide the diode switching signal for the Rx/Tx antenna switching.<br>
+<br>
+
+The right audio channel QSK signal is selected by checking the box and
+then adjusting the pre and post timing in millisecond increments.
+Additional information and a schematic diagram of a QSK keying circuit
+is described in \ref cw_keying_page "CW Keying". Setting
+up a QSK device can be quite difficult. Fldigi helps to ease the
+adjustment by generating a continuous series of characters. This
+allows a dual trace scope to be properly synched while making the
+adjustments to both the software and the associated QSK hardware.
+You enable continuous characters by selecting the checkbox, and
+then enabling the T/R button for transmit. The repeated character
+can be change on the fly with the pick control. It can be one of
+either E, I, S, T, M, O or V.
+<br>
+<br>
+
+\section subsec_prosigns PROSIGNS
+
+\image html config-cw-prosigns.png "CW Prosigns"
+\image latex config-cw-prosigns.png "CW Prosigns" width=3.0in
+<br>
+\image html config-cw-prosign-popup.png "Prosign Popup"
+\image latex config-cw-prosign-popup.png "Prosign Popup" width=1.0in
+
+You can assign keyboard characters to be used for Morse prosigns. The
+available characters are: ~ % &amp; + = { } &lt; &gt; [ ]
+<br>
+<br>
+
+The default assignments are shown above. You can also elect to send and
+receive the KN prosign as an open parenthesis '('. This is commonly
+used on MARS CW operations.
+<br>
+<br>
+
+See \ref cw_page "Operating CW" for additional information.
+<br>
+<br>
+
+\ref cw_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/configContestia.txt b/fldigi_doxygen/user_src_docs/configContestia.txt
new file mode 100644
index 00000000..91cca656
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configContestia.txt
@@ -0,0 +1,23 @@
+/**
+\page contestia_configuration_page Contestia Configuration
+
+\tableofcontents
+
+\image html config-contestia.png "Contestia Configuration"
+\image latex config-contestia.png "Contestia Configuration" width=5.0in
+<br>
+
+Configuration of Contestia is similar to Olivia as Contestia is a
+derivative of Oliva.
+<br>
+
+See \ref contestia_page for additional information.
+<br>
+
+<br>
+\ref contestia_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/configDomEX.txt b/fldigi_doxygen/user_src_docs/configDomEX.txt
new file mode 100644
index 00000000..110110d3
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configDomEX.txt
@@ -0,0 +1,49 @@
+/**
+\page domino_ex_configuration_page DominoEX Configuration
+
+\tableofcontents
+
+<br>
+\image html config-domino.png "DominoEX Configuration"
+\image latex config-domino.png "DominoEX Configuration" width=5.0in
+
+Enter the secondary text. This text will be sent during periods when
+your keyboard is inactive (between letters for slow typists). The
+default for this text will be your callsign when you have entered that
+in theOperator configuration tab.
+<br>
+<br>
+
+Set the BW factor for the decoding prefilter. 2.0 should be adequate
+unless you are experiencing nearby continuous wave interference (CWI).
+You can enable and disable the prefilter with the checkbox. Please note
+that the filter requires additional cpu cycles. Older and slower cpu
+models might give better decoding with the filter disabled.
+<br>
+<br>
+
+Fldigi can send and receive FEC in accordance with the DomEX-FEC specification
+for MultiPsk. This type of FEC is achieved by some loss of non
+printing characters in the primary character set. It is therefore
+not usable as an FEC mode for ARQ (automatic repeat request)
+transmissions.
+<br>
+<br>
+
+The DominoEX decoder can detect the presence of CWI within the passband set
+by the BW factor. Increasing the CWI threshold increases the
+sensitivity to such interference. When the interference is
+detected the associated data is culled using a technique called
+puncturing.
+<br>
+<br>
+
+DominoEX operations are described in \ref domino_ex_page .
+
+<br>
+\ref domino_ex_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/configFH.txt b/fldigi_doxygen/user_src_docs/configFH.txt
new file mode 100644
index 00000000..cd5e3223
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configFH.txt
@@ -0,0 +1,53 @@
+/**
+\page feld_hell_configuration_page  Feld Hell Configuration
+\tableofcontents
+
+<br>
+\image html config-feldhell.png "Feld Hell Config Panel"
+\image latex config-feldhell.png "Feld Hell Config Panel" width=5.0in
+
+The Hellschreiber modes all use a video display that is basically a
+character-by-character facsimile. The shape of the characters is
+determined at the transmitting station. You can select from 15
+different fonts, all of which have been designed for Feld Hell use.
+In normal use each dot of the character font is transmitted
+twice. You can increase the effective video s/n by transmitting
+the dots 2 or 3 times the normal. That is controlled by the
+Transmit width. <br>
+<br>
+
+FeldHell is a pulse amplitude modulated
+signal. The shape of the pulse is a raised cosine. This
+helps to control the bandwidth of the transmitted signal. It is
+customary to use a 4 millisecond risetime for the raised cosine,
+especially on HF. You can change that to 2 milliseconds.
+The video edges will be sharper, but the bandwidth twice as
+large. You might find 2 msec a better choice for VHF and above.<br>
+<br>
+
+Fldigi provides three controls for the receive function. The video is
+normally black on white. You can change that to white on black.
+You can also compress the horizontal scan rate of the video.
+You might find this effective in displaying received fonts that
+are broad (or if the other end is using a multiple dot transmit width).<br>
+<br>
+
+As
+you change Hellschreiber modes the optimum filter bandwidth will be
+set. You can change that and might find a narrower filter
+effective if you are experiencing CWI interference. FeldHell is
+susceptible to CWI. If you narrow the filter the received video
+will become blurred.<br>
+
+<br>
+\ref feld_hell_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
+<br>
+<br>
+
+
diff --git a/fldigi_doxygen/user_src_docs/configMT63.txt b/fldigi_doxygen/user_src_docs/configMT63.txt
new file mode 100644
index 00000000..d823ac70
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configMT63.txt
@@ -0,0 +1,53 @@
+/**
+\page mt63_configuration_page  MT63 Configuration
+\tableofcontents
+
+\image html config-mt63.png "Modems MT63 Config Panel"
+\image latex config-mt63.png "Modems MT63 Config Panel" width=5.0in
+<br>
+
+MT63 is an orthogonal frequency division multiplexed mode consisting of 64
+parallel carriers each carrying a part of the transmitted signal.
+There are 3 bandwidths and baudrates that fldigi implements in MT-63:
+<ul>
+<li> 500 Hz - 5  baud  </li>
+<li> 1000 Hz - 10 baud </li>
+<li> 2000 Hz - 20 baud </li>
+</ul>
+
+The lowest frequency transmitted is always 500 Hz. If you have a
+scheduled MT63 qso or are trying to copy what you think is MT63 you
+should tune the signal so that the lowest observable signal is at 500
+Hz. Fldigi is capable of decoding signals that are mistuned by as much
+as +/- 100 Hz.
+<br>
+
+Selection of interleave (short/long) is made from the modem menu;
+MT63-500S, MT63-500L, MT63-1000S, MT63-1000L, MT63-2000S, MT63-2000L.
+<br>
+
+Interleave and 8-bit extended characters are usually
+agreed upon before a QSO exchange begins. The default is to use
+the long interleave. 8-bit extended characters allow the
+transmission of Latin-1 accented characters.
+<br>
+
+To assist the Rx operator you can transmit a short tone at the lowest
+(and highest) tone frequencies. You can set the tone duration.
+<br>
+
+You may also elect to use manual tuning (position on the waterfall) of
+the Tx / Rx signal. Be careful when doing this so that the signal
+does not extend beyond the limits of your transceiver SSB filters.
+<br>
+
+MT63 is used extensively in the Military Affiliate Radio System (MARS).
+<br>
+
+\ref mt63_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/configOlivia.txt b/fldigi_doxygen/user_src_docs/configOlivia.txt
new file mode 100644
index 00000000..dae6bb6b
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configOlivia.txt
@@ -0,0 +1,35 @@
+/**
+\page olivia_configuration_page  Olivia Configuration
+\tableofcontents
+<br>
+
+\image html config-olivia.png "Description"
+\image latex config-olivia.png "Description" width=5.0in
+<br>
+
+Olivia is a family of MFSK modes with a high redundancy Forward Error
+Correction system similar to MT63. The family is very large, with 40 or
+more different options, which can make it very difficult to work out which is
+which. The mode works well on poor HF paths and has good sensitivity.
+There are three popular modes, which have 8-FSK, 16-FSK and
+32-FSK, thus having three, four or five bits per symbol. These
+three modes can be selected without additional configuration. The
+tone frequency spacing and integration period should always be left at
+8 and 4 respectively unless you are experimenting with another station
+running an Olivia modem that can be changed. These must always be
+the same at both ends of the Olivia QSO. The modes have two
+serious shortcomings - excessive bandwidth combined with slow typing
+rate, and excessive latency which is the apparent typing delay caused
+by the integration period.
+<br>
+
+See \ref olivia_page "Operating Olivia" for additional information.
+<br>
+
+<br>
+\ref olivia_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/configPSK.txt b/fldigi_doxygen/user_src_docs/configPSK.txt
new file mode 100644
index 00000000..439124ff
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configPSK.txt
@@ -0,0 +1,42 @@
+/**
+\page psk_configuration_page  PSK Configuration
+
+\tableofcontents
+
+\image html config-psk-general.png "Modems PSK General"
+\image latex config-psk-general.png "Modems PSK General" width=5.0in
+<br>
+
+You should set the acquisition search range for waterfall left click
+action. As you adjust this control you will see the red mode
+width change on the waterfall scale. You can also adjust this
+value by pointing the mouse to the waterfall. Hold down the
+Control key and rotate the mouse wheel. The search routine which
+finds the PSK signal operates on a s/n threshold detector as well as
+recognizing the PSK phase modulation. You can adjust the
+acquisition signal to ratio threshold for the search routine.
+<br>
+
+The PSK decoder estimates the signal to noise ratio, S/N, and the
+intermodulation distortion, IMD, of the received signal. This
+measurement is valid during periods when the other station is
+transmitting the idle signal. The estimates are displayed on the
+status bar. You can control how these values are displayed; <b>clear</b>
+or <b>dim</b> after NN seconds. Setting the seconds to 0 disables the
+clear/dim action.
+<br>
+
+Fldigi has a multi channel browser than can display simultaneous reception of
+up to 30 PSK signals. The browser is described here:
+<br>
+
+\ref signal_browser_page "Signal Browser"
+<br>
+
+<br>
+\ref psk_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/configRTTY.txt b/fldigi_doxygen/user_src_docs/configRTTY.txt
new file mode 100644
index 00000000..32c7803c
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configRTTY.txt
@@ -0,0 +1,95 @@
+/**
+\page rtty_fsk_configuration_page  RTTY / FSK Configuration
+
+\tableofcontents
+
+\image html config-rtty-rx.png "RTTY RX"
+\image latex config-rtty-rx.png "RTTY RX" width=5.0in
+<br>
+
+\image html config-rtty-tx.png "RTTY TX"
+\image latex config-rtty-tx.png "RTTY TX" width=5.0in
+<br>
+
+\image html config-rtty-synop.png "RTTY SYNOP"
+\image latex config-rtty-synop.png "RTTY SYNOP" width=5.0in
+<br>
+
+Fldigi operates RTTY using AFSK and the transceiver set to USB. The
+RTTY signal can be transmitted anywhere within the USB passband of the
+transceiver.
+<br>
+
+You can select from various Shifts, Bauds, Bits, Parity and Stop Bits
+for both AFSK and FSK keying of the transmitter. You can elect to
+have fldigi automatically insert a CFLF when it reaches character 72 on
+a line. You can also have it insert a CR-CR-LF sequence instead
+of the standard CR-LF sequence. This is very useful if you are
+communicating with someone using a hardware TTY printer. The
+extra carriage return will give the physical device time to move to the
+left margin before new characters arrive.
+<br>
+
+The RTTY decoder maintains an internal AFC system for tracking the
+desired signal. Depending on operating conditions you may need to
+adjust the action of the AFC loop.  Select from the Slow, Normal
+or Fast AFC loop. You can also disable AFC with the AFC button on
+the main panel.
+<br>
+
+The received signal processing consists of a tuned Raised Cosine Filter
+followed by an optimized Automatic Threshold Correcting (ATC)
+detector. The resulting bit stream is then processed to extract
+the byte data.
+<br>
+
+\image html config-rtty-classic-scope.png "Classic RTTY XY Scope"
+\image latex config-rtty-classic-scope.png "Classic RTTY XY Scope" width=1.5in
+<br>
+
+\image html config-rtty-pseudo-scope.png "Pseudo Signal XY Scope"
+\image latex config-rtty-pseudo-scope.png "Pseudo Signal XY Scope" width=1.5in
+<br>
+
+The Digiscope display can be defaulted to the X-scope or the Signal
+scope.
+<br>
+
+The classic XY-scope is similar to older hardware scopes that show
+the output of the separate Mark-Space filters, one applied to the horizontal
+and one to the vertical axis.
+<br>
+
+The Pseudo XY-scope is similar with the exception that the horizontal
+and vertical are phase related to the Mark-Space signals, but not the
+actual signal.
+<br>
+
+The Classis XY-scope will appear noisier than the Pseudo XY-scope.
+<br>
+
+PseudoFSK selection generates an additional audio signal on the right
+channel. This signal is a burst tone at the FSK keying rate.
+You can full wave rectify and filter the signal so that it can be
+used as the FSK keyline signal to a rig that supports FSK transmissions.
+See \ref pseudo_fsk_page "Pseudo FSK" for additional information and a
+suitable keying circuit.
+<br>
+
+Your log can record either the center frequency between the Mark and
+Space or the Mark frequency. You can also select the color that
+should distinguish the Mark frequency.
+
+\image html config-rtty-synop.png "RTTY SYNOP"
+\image latex config-rtty-synop.png "RTTY SYNOP" width=5.0in
+<br>
+
+See \ref synop_page "Synop" and \ref rtty_page "RTTY" for additional information.
+
+<br>
+\ref rtty_fsk_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/configThor.txt b/fldigi_doxygen/user_src_docs/configThor.txt
new file mode 100644
index 00000000..fbed01b9
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configThor.txt
@@ -0,0 +1,43 @@
+/**
+\page thor_configuration_page  Thor Configuration
+
+\tableofcontents
+
+\image html config-thor.png "Modems Thor"
+\image latex config-thor.png "Modems Thor" width=5.0in
+<br>
+
+The decoder can detect and defeat a modest amount of CWI that is within the
+BW set by the BW factor. Increasing the CWI threshold increasing
+the sensitivity for this correction. The offending tones are
+punctured thereby rendering them null to the Viterbi decoder.
+<br><br>Enter the secondary text. This text will be sent during periods
+when your keyboard is inactive (between letters for slow typists). The
+default for this text will be your callsign when you have entered that
+in the Operator configuration tab.
+<br>
+
+Set the BW factor for the decoding prefilter. 2.0 should be adequate
+unless you are experiencing nearby continuous wave interference (CWI).
+You can enable and disable the prefilter with the checkbox. Please note
+that the filter requires additional cpu cycles. Older and slower cpu
+models might give better decoding with the filter disabled.
+<br>
+
+The DominoEX decoder can detect the presence of CWI within the passband set
+by the BW factor. Increasing the CWI threshold increases the
+sensitivity to such interference. When the interference is
+detected the associated data is culled using a technique called puncturing.
+<br>
+
+Thor has been specifically designed to be used with ARQ text transmissions.
+It is also an easy to use keyboard chat mode. Thor operations
+are described in \ref thor_page "Operating Thor".
+
+<br>
+\ref thor_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/configcallsigndb.txt b/fldigi_doxygen/user_src_docs/configcallsigndb.txt
new file mode 100644
index 00000000..5547904f
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/configcallsigndb.txt
@@ -0,0 +1,77 @@
+/**
+\page callsign_db_configuration_page  Callsign DB Configuration
+\tableofcontents
+<br>
+
+\section qrz  QRZ
+<br>
+\image html config-qrz.png "QRZ"
+\image latex config-qrz.png "QRZ" width=5.0in
+<br>
+<br>
+Fldigi will open a web browser to either QRZ.com or Hamcall.net with the
+contents of the QSO Call field used as a query string to the on line
+service. You may find that your default browser needs to be
+triggered twice on the first such query. That behavior seems to
+be associated with IE7 but not IE6 for example.
+<br>
+
+If you have a CD
+with the QRZ database installed you can use that CD or its' stored
+contents on a hard drive. Simply specify where the CALLBK
+directory can be found and enable the QRZ radio button.
+<br>
+
+If you are a paid subscriber to either QRZ or Hamcall xml database service
+then you can specify that fldigi use that service for all Callsign data
+base queries.<br>
+<br>
+
+OK2CQR provides a very nice callsign lookup service on his hamqth.com
+web site. There is no subscriber fee to use this service.
+Simply register and then use your registered user name and password for
+access. You might want to provide monetary support to Petr if
+this service meets your needs.<br>
+<br>
+
+\section eqsl  EQSL
+<br>
+
+\image html config-eqsl.png "EQSL"
+\image latex config-eqsl.png "EQSL" width=5.0in
+<br>
+
+Configure the eQSL log entry upload with your user ID, password, and QTH
+nickname. See <a href="Macros.html">Macros</a> for additional
+information.<br>
+<br>
+
+\section fldigi_logging  FLdigi Logging
+<br>
+
+\image html log-it.png "Log It"
+\image latex log-it.png "Log It" width=0.5in
+<br>
+
+If you check the "send when logged" button then the logged record will be
+sent to eQSL when either the
+log it button is pressed, or when the macro tag &lt;LOG&gt; or &lt;LNW&gt;
+is executed.<br>
+<br>
+You may elect to use the default of date-time ON or date-time OFF for the
+eQSL submission.<br>
+<br>
+You may send a message with the log record. If you fill in the
+default message text then it will be used for that purpose. You
+might want to use something like:<br>
+<br>
+Tks for {MODE} qso {NAME}. 73, pse eQSL<br>
+<br>
+
+<br>
+\ref callsign_db_configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/copy-images.sh b/fldigi_doxygen/user_src_docs/copy-images.sh
new file mode 100755
index 00000000..da460633
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/copy-images.sh
@@ -0,0 +1,31 @@
+#!/bin/bash
+
+
+cp images/event-log-debug.png ../user_docs/latex/event-log-debug.png
+cp images/event-log-error.png ../user_docs/latex/event-log-error.png
+cp images/event-log-info.png ../user_docs/latex/event-log-info.png
+cp images/event-log-quiet.png ../user_docs/latex/event-log-quiet.png
+cp images/event-log-verbose.png ../user_docs/latex/event-log-verbose.png
+cp images/event-log-warning.png ../user_docs/latex/event-log-warning.png
+cp images/digiscope-psk-nosig.png ../user_docs/latex/digiscope-psk-nosig.png
+cp images/digiscope-psk.png ../user_docs/latex/digiscope-psk.png
+cp images/digiscope-psk-low.png ../user_docs/latex/digiscope-psk-low.png
+cp images/digiscope-psk-high.png ../user_docs/latex/digiscope-psk-high.png
+cp images/digiscope-psk-history.png ../user_docs/latex/digiscope-psk-history.png
+cp images/digiscope-psk-history-amplitude.png ../user_docs/latex/digiscope-psk-history-amplitude.png
+cp images/wwv3.png ../user_docs/latex/wwv3.png
+cp images/wwv1-lgneg.png ../user_docs/latex/wwv1-lgneg.png
+cp images/wwv2-000ppm.png ../user_docs/latex/wwv2-000ppm.png
+cp images/wwv2-lgpos.png ../user_docs/latex/wwv2-lgpos.png
+cp images/wwv2-125ppm.png ../user_docs/latex/wwv2-125ppm.png
+cp images/dcf77-0.png ../user_docs/latex/dcf77-0.png
+cp images/dcf77-0zoom.png ../user_docs/latex/dcf77-0zoom.png
+cp images/dcf77-1000.png ../user_docs/latex/dcf77-1000.png
+cp images/dcf77-65zoom.png ../user_docs/latex/dcf77-65zoom.png
+cp images/RWMpre-cal.png ../user_docs/latex/RWMpre-cal.png
+cp images/RWM+25361ppm.png ../user_docs/latex/RWM+25361ppm.png
+cp images/RWMpost-cal-x5.png ../user_docs/latex/RWMpost-cal-x5.png
+
+
+
+
diff --git a/fldigi_doxygen/user_src_docs/execmacro.txt b/fldigi_doxygen/user_src_docs/execmacro.txt
new file mode 100644
index 00000000..f4423b10
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/execmacro.txt
@@ -0,0 +1,234 @@
+/**
+\page  exec_macro_page Exec Macro
+
+\tableofcontents
+
+The \<EXEC\> ... \</EXEC\> macro is designed to be used on the
+Linux OS as it supports fully functional pipes.  Windows' version
+of file pipes is not fully POSIX compliant, but the function might work
+in the environment.  Consider all that the following allows you to
+do from within fldigi and you might want to consider changing over to
+Linux.The \<EXEC\> macro defines an external child process (or
+processes) that will be called by fldigi when the macro key is invoked.
+<br>
+
+\section export_variables Exported variables
+
+Fldigi exports a set of variables to the child process and
+adds ~/.fldigi/scripts to the PATH variable before running the shell
+code. This is the directory location for all executable scripts
+and programs which you might want to call from within the macro.  Some
+examples will be given later.  Open the macro editor for an undefined macro
+key and enter the following:
+<br>
+
+\verbatim
+<EXEC>env | grep FLDIGI</EXEC>
+\endverbatim
+<br>
+
+Save the macro; call it ENV.  Then press the newly defined macro key. All
+of the exported variables will be shown in the transmit window.
+<br>
+
+Here is an example of the results:
+<br>
+
+FLDIGI_RX_IPC_KEY=9876
+<br>
+FLDIGI_LOG_LOCATOR=FM02BT
+<br>
+FLDIGI_TX_IPC_KEY=6789
+<br>
+FLDIGI_LOG_RST_IN=
+<br>
+FLDIGI_LOG_FREQUENCY=3581.000
+<br>
+FLDIGI_AZ=108
+<br>
+FLDIGI_MY_CALL=W1HKJ
+<br>
+FLDIGI_LOG_TIME=2113
+<br>
+FLDIGI_MY_NAME=Dave
+<br>
+FLDIGI_VERSION=3.0preG
+<br>
+FLDIGI_LOG_NOTES=
+<br>
+FLDIGI_LOG_QTH=Mt Pleasant, SC
+<br>
+FLDIGI_MY_LOCATOR=EM64qv
+<br>
+FLDIGI_DIAL_FREQUENCY=3580000
+<br>
+FLDIGI_CONFIG_DIR=/home/dave/.fldigi/
+<br>
+FLDIGI_LOG_RST_OUT=
+<br>
+FLDIGI_MODEM=BPSK31
+<br>
+FLDIGI_LOG_CALL=KH6TY
+<br>
+FLDIGI_MODEM_LONG_NAME=BPSK-31
+<br>
+FLDIGI_AUDIO_FREQUENCY=1000
+<br>
+FLDIGI_LOG_NAME=Skip
+<br>
+FLDIGI_PID=14600
+<br>
+FLDIGI_FREQUENCY=3581000
+<br>
+
+All of the above envelope variables can be referenced in a shell script that
+is called from within fldigi.
+<br>
+
+\section detecton_of_scripts Detection of existing scripts
+
+In anticipation of a collection of useful "fldigi scripts", the
+macro browser contains a \<exec\> \</exec\> macro line for each
+executable file found in the scripts directory. The EXEC macro allows the
+text that is read from the child process to be
+parsed for more fldigi macros. For example, try this macro:
+<br>
+
+\verbatim
+<EXEC>cat foo</EXEC>
+\endverbatim
+
+where foo is a file that contains:
+<br>
+
+\verbatim
+<MYCALL>
+\endverbatim
+
+This may have some interesting uses but, if it is undesirable, it can be
+suppressed with an extra layer of redirection.  Instead of
+\<EXEC\>command\</EXEC\>, you would
+use \<EXEC\>noexp command\</EXEC\> where noexp is
+the following very simple script:
+
+\verbatim
+snip---------------------------------------
+#!/bin/bash
+echo -n "<STOP>"
+"$@"     # run the command
+r=$?     # save its exit code
+echo -n "<CONT>"
+exit $?
+snip---------------------------------------
+\endverbatim
+
+There are three additional MACRO definitions that expand the capability of
+the \<EXEC\> command: \<STOP\>, \<CONT\> and \<GET\>.
+The \<STOP\> and \<CONT\> macros stop and resume the expansion of all
+\<MACRO\> strings. For
+example, \<STOP\>\<MYCALL\>\<CONT\>\<MYCALL\>
+would only expand the second \<MYCALL\>.
+
+By wrapping the command output in this way we can be sure that
+no text will be expanded. You might even use
+<br>
+
+\verbatim
+"$@" | sed "s/<CONT>//g"
+\endverbatim
+<br>
+
+if you feel paranoid. You can "fork and forget" with an exec macro defined
+as: \<EXEC\>exec command -args \>/dev/null\</EXEC\>
+
+Any of the text that appears between the \<EXEC\> and \</EXEC\> can
+reference an executable program or shell command found in the
+~/.fldigi/scripts directory.
+
+Any text output that is returned by the program or script program (or the
+result of the in-line command) is always returned to the transmit
+buffer and appears as appended to the transmit window.
+
+
+\section querying_database Querying an external database
+
+The \<GET\> command captures returned text from the external process and
+parses it for the following content:
+
+$NAMEtext_name$QTHtext_qth
+
+If either $NAME or $QTH is present the trailing text is transferred to the
+LOG_NAME or LOG_QTH widgets respectively.  This means that you can create a
+script that accesses a local or net based database of callsign data and
+parse that data to form the above console output.  Fldigi will accept that
+output, parse it and populate the associated log entries. Cool!  Now
+for some examples.  Here is a perl script that performs the above for
+the University of Arkansas on-line callsign database,
+\ref ualr_telnet_page "ualr-telnet". The matching macro
+key definition for the above is:
+
+\verbatim
+<EXEC>ualr-telnet.pl $FLDIGI_LOG_CALL</EXEC><GET>
+\endverbatim
+
+which I named "ualr ?"
+
+\section google_earth_map Google Earth Map
+
+Here is a really cool perl script, \ref google_maps "Google Earth Mapping",
+that accepts the current "Loc" field in the logging area and generates
+a Google Earth map which is displayed in your default browser.
+
+The macro call is:
+
+\verbatim
+<EXEC>map.pl</EXEC>
+\endverbatim
+
+\section custom_dates_times Custom dates/times
+
+You can use \<EXEC\> to create custom date/time entries. For
+example, BARTG contesters use %H%M, but in other circumstances a user
+might prefer %H:%M or %H.%M etc.
+Create the following script file in the ~/.fldigi/scripts directory, call it mytime:
+
+\verbatim
+snip---------------------------------------
+#!/bin/sh
+date --utc "+%H:%M"
+snip---------------------------------------
+\endverbatim
+
+date calls strftime, the same C function used by fldigi for the ZDT/LDT
+expansion, so it has an equally vast number of format strings to choose
+from. Look for them in its manual page.
+
+Give "mytime" execute permissions with a file manager or with chmod:
+   chmod u+x ~/.fldigi/scripts/mytime.
+
+Test it on the command line and make sure it works correctly:
+   ~/.fldigi/scripts/mytime
+
+Restart fldigi. The mytime script will now appear at the end of the list in the
+macro browser, and can be entered with the \<\< button as usual.
+Test that macro and you will see that \<EXEC\>mytime\</EXEC\>
+inserts the datetime in the specified format.
+Of course you could have entered:
+<br>
+
+\verbatim
+<EXEC>date --utc "+%H:%M"</EXEC>
+\endverbatim
+
+in the macro body text directly Many other uses for the \<EXEC\>...\</EXEC\> macro pair
+can be imagined when used the with ENV parameters.  For example you could send
+Azimuth data to an automated antenna rotor.  The exported variables should be
+sufficient for a script writer to create custom loggers and clients.
+
+<br>
+\ref exec_macro_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/fldigi-static.txt b/fldigi_doxygen/user_src_docs/fldigi-static.txt
new file mode 100644
index 00000000..4aa91efb
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/fldigi-static.txt
@@ -0,0 +1,129 @@
+/**
+\page install_fldigi_page Installing Fldigi
+
+\tableofcontents
+
+\section precompiled_binary Precompiled Binary
+
+The precompiled binary is available with and without a dependency on
+PulseAudio.  Unless you know that your system uses PulseAudio
+for its sound card service you should not download that version.
+<br>
+
+You will need three shared libraries on your system, hamlib-1.2.10;
+libsamplerate; and libportaudio2.  Use the libraries available
+for your linux distribution.  Most current distributions use
+either deb or rpm files and can be accessed from a global repository.
+<br>
+
+Building the libraries from source should be a last resort unless you
+are a knowledgable Linux user and have performed a library build from
+source in the past.
+<br>
+
+\subsection hamlib_required Hamlib
+
+You will need to have hamlib-1.2.7 installed on your system before
+fldigi can be executed.  Most current distributions either
+have a deb or rpm distribution file for hamlib-1.2.10.  If you must
+compile from source you can find it at:
+<br>
+    <a href="http://www.hamlib.org/">http://www.hamlib.org</a>
+<br>
+
+Follow the instructions in the source code top directory to compile,
+link and install the library.
+<br>
+
+\subsection libsamplerate_required libsamplerate
+<br>
+
+You will need to have libsample installed on your system
+before fldigi can be executed.  Most current distributions either
+have a deb or rpm distribution file for libsamplerate.  If you must
+compile from source you can find it at:
+<br>
+
+<a href="http://www.mega-nerd.com/SRC/download.html">libsamplerate
+source</a>
+<br>
+
+Follow the instructions in the source code top directory to compile,
+link and install the library.
+<br>
+
+\subsection port_audio_required PortAudio
+
+You will need to have libportaudio2 installed on your system before
+fldigi can be executed.  Most current distributions either
+have a deb or rpm distribution file for libportaudio2.  If you must
+compile from source you can find it at:<br>
+<br>
+    <a href="http://www.portaudio.com">http://www.portaudio.com</a>
+<br>
+
+Follow the instructions in the source code top directory to compile,
+link and install the library.
+
+\section installing_fldigi Installing fldigi
+
+The static executables are tested on as many distributions
+as possible to insure that they work "out-of-the-box", but there are
+always a few Linux distributions that may have a missing link or
+library.  The precompiled binaries have been tested and work
+correctly on all of the Debian and Ubuntu/Kubuntu distributions. They
+have also been tested and confirmed to work on Suse 10.1,
+and Mandriva 2007.
+<br>
+
+Download the tarball for the binary version and unpack to a
+directory on your HD such as $HOME/bin or some other convenient
+directory of your choosing.  The least common denominator for
+unpacking a tarball is to download the file and save it to a convenient
+directory such as $HOME/downloads.  Then open up a terminal
+window.  Assuming you will be installing the executable to
+$HOME/bin do the following and that you have downloaded the tarball to
+$HOME/downloads
+<br>
+
+\verbatim
+cd
+cd bin
+tar xzf ../downloads/fldigi-D.dd.npa.bin.tgz
+\endverbatim
+
+where D.dd is the current version number as in 3.10
+<br>
+
+You can create a link to the fldigi executable on your desktop
+using the fldigi.png icon located at
+<br>
+
+<a href="http://www.w1hkj.com/fldigi-distro/fldigi-psk.png">http://www.w1hkj.com/fldigi-distro/fldigi-psk.png</a>
+<br>
+
+Creating a desktop link to an application is different for each desktop
+manager, so please refer to the documentation for your specific manager.
+<br>
+
+The first time that you execute fldigi either from the command line or
+by clicking on the executable in a file manager or the desktop icon it
+will create a new directory and file:
+<br>
+
+<ul>
+<li>$HOME/.fldigi</li>
+<li>$HOME/.fldigi/macros.mdf</li>
+</ul>
+
+If this is a new installation you will be guided through some necessary
+configuration by a \ref wizard_page "new install wizard".
+<br>
+
+<br>
+\ref install_fldigi_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/fldigi_configuration.txt b/fldigi_doxygen/user_src_docs/fldigi_configuration.txt
new file mode 100644
index 00000000..910ec7e7
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/fldigi_configuration.txt
@@ -0,0 +1,97 @@
+/**
+\page configuration_page Configuration
+
+\tableofcontents
+
+The first time you execute fldigi you should resize the main window to
+suit your screen dimensions. Then adjust the divider line
+between the Rx and Tx text widgets..
+<br>
+
+Fldigi contains many configurable items, to specify operator data, user
+interface, and modem characteristics. The application also saves
+many state variables between executions. It will start up in the
+state that it was last used.<br>
+<br>
+
+\section ui_configuation User Interface configuration
+
+You should initially configure the following:
+<br>
+
+<ul>
+	<li> \subpage operator_configuration_page </li>
+	<li> \subpage sound_card_configuration_page </li>
+	<li> \subpage rig_control_page </li>
+	<li> \subpage new_installation_page </li>
+</ul>
+
+\section windows_install_config Windows Specific Install / Config
+
+<ul>
+	<li> \subpage installing_on_windows_page </li>
+	<li> \subpage wizard_page</li>
+</ul>
+
+\section other_configuation_options Other Configuration options
+
+When the program receives and transmits digital signals and your rig control
+is satisfactory then you can continue configuring other aspects of the
+program:
+<br>
+
+<ul>
+	<li> \subpage callsign_db_configuration_page </li>
+	<li> \subpage colors_and_fonts_page </li>
+	<li> \subpage psk_mail_configuation_page </li>
+	<li> \subpage ui_configuration_broswer_page </li>
+	<li> \subpage ui_configuration_contest_page </li>
+	<li> \subpage ui_configuration_general_page </li>
+	<li> \subpage ui_configuration_macros_page </li>
+	<li> \subpage ui_configuration_waterfall_controls_page </li>
+	<li> \subpage ui_configuration_waterfall_page </li>
+	<li> \subpage working_logs_page </li>
+</ul>
+
+\section command_line_switches Command Line Switches
+
+Additional configurational items are available from the command line.
+
+See \ref command_line_switches_page "Command Line Switches" for details.
+
+\section modem_configuration_options Modem Configuration Options
+
+You can configure each modem type to suit your particular operating needs,
+but the defaults should be satisfactory for most users.
+<br>
+
+<ul>
+	<li> \subpage contestia_configuration_page </li>
+	<li> \subpage cw_configuration_page </li>
+	<li> \subpage domino_ex_configuration_page </li>
+	<li> \subpage feld_hell_configuration_page </li>
+	<li> \subpage id_configuration_page </li>
+	<li> \subpage miscellaneous_configuration_page </li>
+	<li> \subpage mt63_configuration_page </li>
+	<li> \subpage olivia_configuration_page </li>
+	<li> \subpage psk_configuration_page </li>
+	<li> \subpage rtty_fsk_configuration_page </li>
+	<li> \subpage thor_configuration_page </li>
+</ul>
+<br>
+
+
+When you have completed the configuration go to the <b>Configure</b> menu
+and select <b>Save config</b> or press the "Save Config" button on the
+configure dialog box. The program will write the
+file ~/.fldigi/fldigi_def.xml.
+<br>
+
+
+<br>
+\ref configuration_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/fldigi_developer.txt b/fldigi_doxygen/user_src_docs/fldigi_developer.txt
new file mode 100644
index 00000000..8202c105
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/fldigi_developer.txt
@@ -0,0 +1,16 @@
+/**
+\page developers_page Developers
+
+<ul>
+<li> \subpage build_info_page </li>
+<li> \subpage install_fldigi_page</li>
+<li> \subpage install_from_source_page </li>
+<li> \subpage parse_ualr_page </li>
+<li> \subpage pseudo_fsk_page </li>
+<li> \subpage rig_xml_page </li>
+<li> \subpage ualr_telnet_page </li>
+<li> \subpage xmlrpc_control_page </li>
+<li> \subpage google_maps </li>
+</ul>
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/fldigi_interprocess_comms.txt b/fldigi_doxygen/user_src_docs/fldigi_interprocess_comms.txt
new file mode 100644
index 00000000..9e81816d
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/fldigi_interprocess_comms.txt
@@ -0,0 +1,14 @@
+/**
+\page interprocess_communications_page Interprocess Communications
+
+<ul>
+<li> \subpage contest_how_to_page </li>
+<li> \subpage cw_keying_page </li>
+<li> \subpage digiscope_display_page </li>
+<li> \subpage digiscope_display_wwv_mode </li>
+<li> \subpage dxcc_list_page </li>
+<li> \subpage frequency_analyzer_page </li>
+<li> \subpage keyboard_operation_page </li>
+</ul>
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/fldigi_logging.txt b/fldigi_doxygen/user_src_docs/fldigi_logging.txt
new file mode 100644
index 00000000..36e43a6c
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/fldigi_logging.txt
@@ -0,0 +1,11 @@
+/**
+\page logging_page Logging
+
+<ul>
+<li> \subpage cabrillo_report_page </li>
+<li> \subpage exporting_logbook_data</li>
+<li> \subpage qso_log_book_page </li>
+<li> \subpage ui_configuration_log_server_page </li>
+</ul>
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/fldigi_macros.txt b/fldigi_doxygen/user_src_docs/fldigi_macros.txt
new file mode 100644
index 00000000..eacb503f
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/fldigi_macros.txt
@@ -0,0 +1,11 @@
+/**
+\page macro_page Macros
+
+<ul>
+<li> \subpage macros_sub_page </li>
+<li> \subpage inline_macro_page </li>
+<li> \subpage advanced_qsy_page</li>
+<li> \subpage exec_macro_page </li>
+</ul>
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/fldigi_modems.txt b/fldigi_doxygen/user_src_docs/fldigi_modems.txt
new file mode 100644
index 00000000..ea34afe4
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/fldigi_modems.txt
@@ -0,0 +1,24 @@
+/**
+\page modems_page Modems
+
+
+<ul>
+	<li> \subpage contestia_page </li>
+	<li> \subpage cw_page </li>
+	<li> \subpage domino_ex_page </li>
+	<li> \subpage feld_hell_page </li>
+	<li> \subpage mfsk_page </li>
+	<li> \subpage mt63_page </li>
+	<li> \subpage navtex_and_sitorb_page </li>
+	<li> \subpage olivia_page </li>
+	<li> \subpage psk_page </li>
+	<li> \subpage rtty_page </li>
+	<li> \subpage thor_page </li>
+	<li> \subpage throb_page </li>
+	<li> \subpage tune_page </li>
+	<li> \subpage wefax_page </li>
+	<li> \subpage wwv_tx_mode </li>
+	<li> \subpage mode_table_page </li>
+</ul>
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/fldigi_operating.txt b/fldigi_doxygen/user_src_docs/fldigi_operating.txt
new file mode 100644
index 00000000..74765757
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/fldigi_operating.txt
@@ -0,0 +1,30 @@
+/**
+\page operating_page Operating
+
+<ul>
+	<li> \subpage contest_how_to_page </li>
+	<li> \subpage cw_keying_page </li>
+	<li> \subpage digiscope_display_page </li>
+	<li> \subpage digiscope_display_wwv_mode </li>
+	<li> \subpage dxcc_list_page </li>
+	<li> \subpage frequency_analyzer_page </li>
+	<li> \subpage keyboard_operation_page </li>
+	<li> \subpage kml_page </li>
+	<li> \subpage menus_page </li>
+	<li> \subpage mouse_and_keyboard_shortcuts_page </li>
+	<li> \subpage notifier_page </li>
+	<li> \subpage operating_controls_page </li>
+	<li> \subpage operating_multiple_copies_page </li>
+	<li> \subpage psk_reporter_page </li>
+	<li> \subpage rig_control_page </li>
+	<li> \subpage rst_rsq_page </li>
+	<li> \subpage signal_browser_page </li>
+	<li> \subpage synop_page </li>
+	<li> \subpage utf8_support_page </li>
+	<li> \subpage w5zit_rt_channel_page </li>
+	<li> \subpage wwv_tx_mode </li>
+	<li> \subpage working_logs_page </li>
+	<li> \subpage supporting_data_files_page </li>
+</ul>
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/global_file_ext_rename.txt b/fldigi_doxygen/user_src_docs/global_file_ext_rename.txt
new file mode 100644
index 00000000..120af4d7
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/global_file_ext_rename.txt
@@ -0,0 +1 @@
+find . -depth -type f -name "*.png.png" -exec sh -c 'mv "$1" "$(dirname "$1")/$(basename "$1" .png.png).png"' _ {} \;
diff --git a/fldigi_doxygen/user_src_docs/global_tiff_file_convert_to.sh b/fldigi_doxygen/user_src_docs/global_tiff_file_convert_to.sh
new file mode 100644
index 00000000..ce92459a
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/global_tiff_file_convert_to.sh
@@ -0,0 +1,2 @@
+find . -depth -type f -name "*.tiff" -exec sh -c 'convert "$1" "$(dirname "$1")/$(basename "$1" .tiff).png"' _ {} \;
+find . -depth -type f -name "*.tiff" -exec sh -c 'convert "$1" "$(dirname "$1")/$(basename "$1" .tiff).png"' _ {} \;
diff --git a/fldigi_doxygen/user_src_docs/global_tiff_file_convert_to.txt b/fldigi_doxygen/user_src_docs/global_tiff_file_convert_to.txt
new file mode 100644
index 00000000..ce92459a
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/global_tiff_file_convert_to.txt
@@ -0,0 +1,2 @@
+find . -depth -type f -name "*.tiff" -exec sh -c 'convert "$1" "$(dirname "$1")/$(basename "$1" .tiff).png"' _ {} \;
+find . -depth -type f -name "*.tiff" -exec sh -c 'convert "$1" "$(dirname "$1")/$(basename "$1" .tiff).png"' _ {} \;
diff --git a/fldigi_doxygen/user_src_docs/hell.txt b/fldigi_doxygen/user_src_docs/hell.txt
new file mode 100644
index 00000000..0bda5199
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/hell.txt
@@ -0,0 +1,62 @@
+/**
+\page feld_hell_page  Hellschreiber
+
+\tableofcontents
+
+\section hell_modem  Hellschreiber modem
+
+All Hellschreiber modes are based on character scanning, reproducing
+characters in a similar way to a dot-matrix printer. This technique uses a
+digital transmission, yet allows the received result to be interpreted by
+eye, a similar concept to the reception of Morse by ear. The character is
+scanned upwards, then left to right. There are typically 14 pixels
+(transmitted dot elements) per column (although single pixels are never
+transmitted) and up to seven columns per character including
+inter-character space.
+<br>
+
+These remarkably simple modes are easy to use, easy to tune, and
+although not especially sensitive, are entirely
+suited to HF/VHF since they use no sync and the eye can discern the
+text even in high levels of noise. fldigi can operate in the
+following :
+
+\section hell_modes Hellschreiber modes
+
+<center>
+
+Mode         | Symbol Rate | Typing Speed         | Duty Cycle | Bandwidth
+:------------|:------------|:---------------------|:------|:--------
+Feld-Hell    | 122.5 baud  | ~ 2.5 cps (25 wpm)   | ~ 22% | 350 Hz
+Slow Hell    | 14 baud     | ~ 0.28 cps (2.8 wpm) | ~ 22% | 40 Hz
+Feld-Hell X5 | 612.5 baud  | ~ 12.5 cps (125 wpm) | ~ 22% | 1750 Hz
+Feld-Hell X9 | 1102.5 baud | ~ 22.5 cps (225 wpm) | ~ 22% | 3150 Hz
+FSK-Hell     | 245 baud    | ~ 2.5 cps (25 wpm)   | ~ 80% | 490 Hz
+FSK-Hell 105 | 105 baud    | ~ 2.5 cps (25 wpm)   | ~ 80% | 210 Hz
+Hell 80      | 245 baud    | ~ 5.0 cps (50 wpm)   | 100%  | 800 Hz
+
+</center>
+
+\section hell_waterfall Hellschreiber Waterfall
+
+Feld-Hell look like this when being received by fldigi:
+<br>
+
+\image html feld-hell.png "Feld-Hell, Slow Hell, Feld-Hell X5, and Feld-Hell X9 are all pulse"
+\image latex feld-hell.png "Feld-Hell, Slow Hell, Feld-Hell X5, and Feld-Hell X9 are all pulse" width=3.0in
+
+<p>Feld-Hell seems to be the most commonly used and use can usually be found
+on 80 and 40 meters at the high end of the digital sub bands.  Extreme
+linearity is required in the transmit path in order to control the bandwidth
+of the transmitted signal. Feld-Hell X5, Feld-Hell X9 and Hell 80 should
+probably not be used on HF in the US. They can be used on VHF
+and UHF.</p>
+
+<br>
+\ref feld_hell_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/imagetocopy.txt b/fldigi_doxygen/user_src_docs/imagetocopy.txt
new file mode 100644
index 00000000..b4ccd7ff
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/imagetocopy.txt
@@ -0,0 +1,31 @@
+Images to copy from script
+
+
+event-log-debug.png
+event-log-error.png
+event-log-info.png
+event-log-quiet.png
+event-log-verbose.png
+event-log-warning.png
+digiscope-psk-nosig.png
+digiscope-psk.png
+digiscope-psk-low.png
+digiscope-psk-high.png
+digiscope-psk-history.png
+digiscope-psk-history-amplitude.png
+wwv3.png
+wwv1-lgneg.png
+wwv2-000ppm.png
+wwv2-lgpos.png
+wwv2-125ppm.png
+dcf77-0.png
+dcf77-0zoom.png
+dcf77-1000.png
+dcf77-65zoom.png
+RWMpre-cal.png
+RWM+25361ppm.png
+RWMpost-cal-x5.png
+
+
+
+
diff --git a/fldigi_doxygen/user_src_docs/index.txt b/fldigi_doxygen/user_src_docs/index.txt
new file mode 100644
index 00000000..8860976b
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/index.txt
@@ -0,0 +1,46 @@
+/******************************************************************************
+ * Copyright (C) 2013 Robert Stiles, KK5VD.
+ *
+ * Permission to use, copy, modify, and distribute this software and its
+ * documentation under the terms of the GNU General Public License is hereby
+ * granted. No representations are made about the suitability of this software
+ * for any purpose. It is provided "as is" without express or implied warranty.
+ * See the GNU General Public License for more details.
+ *
+ * Documents produced by Doxygen are derivative works derived from the
+ * input used in their production; they are not affected by this license.
+ *
+ * Requires Doxygen for HTML output
+ * plus LiveTeX (LaTeX) for PDF output
+ *
+ */
+
+
+/*!
+
+\mainpage FLDIGI Users Manual - Version 3.21
+\anchor main_page
+
+<center>
+\image latex FLDigiWindow.png "" width=4.0in
+\image html FLDigiWindowHtml.png ""
+</center>
+
+\section fldigi_op_ins Fldigi Configuration and Operational Instructions
+
+<ul>
+<li>\ref configuration_page </li>
+<li>\ref modems_page </li>
+<li>\ref operating_page </li>
+<li>\ref logging_page </li>
+<li>\ref macro_page </li>
+<li>\ref developers_page </li>
+<li>\ref license_page </li>
+<li>\ref recognitions_page </li>
+</ul>
+
+<br>
+\ref main_page "Return to Top of Page"
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/index_order.txt b/fldigi_doxygen/user_src_docs/index_order.txt
new file mode 100644
index 00000000..89352037
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/index_order.txt
@@ -0,0 +1,24 @@
+fldigi_configuration.txt fldigi_developer.txt fldigi_logging.txt \
+fldigi_macros.txt fldigi_modems.txt fldigi_operating.txt \
+fldigi-static.txt New-Install.txt colorsandfonts.txt \
+configcallsigndb.txt configContestia.txt configCW.txt \
+configDomEX.txt configFH.txt ConfigID.txt ConfigMisc.txt \
+configMT63.txt configOlivia.txt ConfigOperator.txt configPSK.txt \
+configRTTY.txt configThor.txt ConfigUI-browser.txt \
+ConfigUI-contest.txt ConfigUI-general.txt ConfigUI-logserver.txt \
+ConfigUI-macros.txt ConfigUI-WF-controls.txt ConfigWaterfall.txt \
+SoundCardSetup.txt Contest-How-To.txt cabrilloreporter.txt \
+Logbook.txt LogExports.txt working_logs.txt Macros.txt \
+InlineMacroTags.txt advanced_qsy.txt execmacro.txt CW.txt \
+DominoEX.txt hell.txt Contestia.txt MFSK.txt MT63.txt \
+Navtex.txt psk.txt Olivia.txt RTTYFSK.txt Thor.txt \
+throb.txt tune.txt WEFAX.txt WWV-xmt.txt FrequencyAnalysis.txt \
+DigiscopeDisplay.txt DigiWWV.txt map.txt MousingKeyboardShortcuts.txt \
+Multiples.txt Notifier.txt OperatingControls.txt RST-RSQ.txt \
+Spotter.txt Synop.txt TransceiverControl.txt UTF8.txt \
+pskmail_config.txt PskViewer.txt DXCC_list.txt \
+KeyboardAndKeys.txt KML.txt Installing.txt WindowsOS.txt \
+Wizard.txt Menus.txt ModeTable.txt CWkeying.txt PseudoFSK.txt \
+w5zit-interface.txt rigxml.txt commandline.txt \
+buildinfo.txt xmlrpc-control.txt parseUALR.txt ualr-telnet.txt \
+License.txt Recognitions.txt
diff --git a/fldigi_doxygen/user_src_docs/map.txt b/fldigi_doxygen/user_src_docs/map.txt
new file mode 100644
index 00000000..38a63e56
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/map.txt
@@ -0,0 +1,127 @@
+/**
+\page  google_maps Google Maps
+
+\verbatim
+
+snip ------------ copy the following to ~/.fldigi/scripts/map.pl
+
+#!/usr/bin/perl
+
+# Author: Stelios Bounanos, M0GLD
+# Date:   20080625
+
+use warnings;
+use strict;
+use Getopt::Std;
+
+our $VERSION = "0.3141";
+our %opts = ( "e" => 0, "m" => 1, "z" => 4);
+
+cmdline();
+open(STDOUT, '>', "/dev/null");
+
+my $loc = exists($opts{'l'}) ? $opts{'l'} : $ENV{'FLDIGI_LOG_LOCATOR'};
+die "Invalid locator\n" unless ((defined($loc) && length($loc) =~ /[2-6]/));
+
+my $label = exists($opts{'t'}) ? $opts{'t'} : $ENV{'FLDIGI_LOG_CALL'};
+$label = $loc if (!defined($label) || $label eq "");
+
+my ($lon, $lat) = map { sprintf("%+.6f", $_) } mtoll($loc);
+if ($opts{'m'}) {
+    my $url = "http://maps.google.com/maps?q=${lat},${lon}(${label})&t=p&z=$opts{'z'}";
+#    $url =~ s/([(),])/sprintf("%%%02X", ord($1))/ge; # encode some chars
+    exec("xdg-open", $url);
+    die "Could not exec xdg-open: $!\n";
+}
+
+exit(0) unless ($opts{'e'});
+my $kml = (exists($ENV{'TMPDIR'}) ? $ENV{'TMPDIR'} : "/tmp") .
+    "/" . $loc . ".kml";
+open(KML, '>', $kml) or die "Could not write $kml: $!\n";
+print KML <<EOF
+<?xml version="1.0" encoding="UTF-8"?>
+<kml xmlns="http://earth.google.com/kml/2.2">
+  <Placemark>
+    <name>$label</name>
+    <description>
+      $label
+      $loc
+    </description>
+    <Point>
+      <coordinates>$lon,$lat,0</coordinates>
+    </Point>
+  </Placemark>
+</kml>
+EOF
+    ;
+close(KML);
+
+########################################################################
+
+sub cmdline
+{
+    $Getopt::Std::STANDARD_HELP_VERSION = 1;
+    my $old_warn_handler = $SIG{__WARN__};
+    $SIG{__WARN__} = sub { die $_[0]; };
+    getopts('t:l:mz:e', \%opts);
+    $SIG{__WARN__} = $old_warn_handler;
+}
+
+
+# Convert a 2, 4, or 6-character Maidenhead locator string
+# to decimal degrees. Return a (longitude, latitude) pair.
+sub mtoll
+{
+    my $len = length($_[0]);
+    $_[0] .= join("", ("A", "A", "0", "0", "A", "A")[$len .. 5]) if ($len < 6);
+    $_[0] = uc($_[0]);
+    die "Invalid locator\n" unless ($_[0] =~ /[A-R]{2}\d{2}[A-X]{2}/);
+
+    my @digits = split(//, $_[0]);
+    my ($lon, $lat) = (-180, -90);
+
+    $lon += (ord($digits[0]) - ord('A')) * 20 +
+            (ord($digits[2]) - ord('0')) * 2 +
+            (ord($digits[4]) - ord('A') + 0.5) / 12;
+    $lat += (ord($digits[1]) - ord('A')) * 10 +
+            (ord($digits[3]) - ord('0')) +
+            (ord($digits[5]) - ord('A') + 0.5) / 24;
+
+    return ($lon, $lat);
+}
+
+sub HELP_MESSAGE
+{
+print <<EOF
+
+Usage: $0 [-OPTIONS [-MORE_OPTIONS]] [--] [PROGRAM_ARG1 ...]
+
+The following single-character options are accepted:
+
+        -t LABEL  Use LABEL as the marker label
+                  The default is \$FLDIGI_LOG_CALL
+
+        -l LOC    Place marker at IARU locator LOC
+                  The default is \$FLDIGI_LOG_LOCATOR
+
+        -m        Show in Google Maps (default)
+        -z        Zoom level (Google Maps only)
+
+        -e        Write a Google Earth kml file in
+                  \$TMPDIR/LOC.kml
+EOF
+;
+}
+
+snip------------------------------------------------
+
+
+\endverbatim
+
+<br>
+\ref google_maps "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/parseUALR.txt b/fldigi_doxygen/user_src_docs/parseUALR.txt
new file mode 100644
index 00000000..2293ac59
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/parseUALR.txt
@@ -0,0 +1,100 @@
+/**
+\page  parse_ualr_page Parse UALR
+
+\tableofcontents
+
+A simple parser to create a formated console output for fldigi's \<EXEC\> macro:
+
+\verbatim
+
+snip------------------------------------------
+#include <ctime>
+#include <cstdio>
+#include <cstdlib>
+#include <unistd.h>
+#include <string>
+#include <iostream>
+#include <fstream>
+
+using namespace std;
+using std::cout;
+using std::cin;
+
+int main(int argc, char *argv[])
+{
+    size_t pos = 0, pos2 = 0, pos3 = 0, pos4 = 0, pos5 = 0;
+    string commandline = "";
+    string name = "";
+    string qth = "";
+    string answer = "";
+    char c = cin.get();
+
+    while (!cin.eof()) {
+        commandline += c;
+        c = cin.get();
+    }
+
+    if (commandline.find("No match found") != string::npos)
+    	goto noresponse;
+
+    pos = commandline.find(", ");
+
+    if (pos == string::npos)
+    	goto noresponse;
+
+    pos += 2;
+    pos2 = commandline.find("\n", pos);
+
+    if (pos2 == string::npos)
+        goto noresponse;
+
+    name = commandline.substr(pos, pos2 - pos);
+    pos3 = name.find(32);
+
+    if (pos3 != string::npos)
+        name = name.substr(0, pos3);
+
+    for (size_t i = 1; i \< name.length(); i++)
+        name[i] = tolower(name[i]);
+
+    answer = "$NAME";
+    answer.append(name);
+
+    pos4 = commandline.find(", ", pos2);
+    pos4 = commandline.rfind( "\n", pos4);
+    pos4 += 1;
+    pos5 = commandline.find("\n", pos4);
+
+    qth = commandline.substr(pos4, pos5 - pos4);
+
+    answer.append("$QTH");
+    answer.append(qth);
+
+    cout \<\< answer.c_str();
+
+    return 0;
+
+noresponse:;
+
+    cout \<\< "$NAME?$QTH?";
+
+    return 0;
+}
+snip-----------------------------------------------
+\endverbatim
+
+Save the above as "parseUALR.cxx" and then compile and link as follows:
+
+<code>g++ parseUALR.cxx -o parseUALR</code>
+
+Copy the "parseUALR" executable to a directory on your shell exec PATH.
+
+
+
+
+<br>
+\ref parse_ualr_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/psk.txt b/fldigi_doxygen/user_src_docs/psk.txt
new file mode 100644
index 00000000..f762de81
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/psk.txt
@@ -0,0 +1,100 @@
+/**
+\page psk_page PSK - BPSK, BPSKR, QPSK, and Multi-Channel Modems
+
+\tableofcontents
+
+\section bpsk_modem  BPSK and QPSK modems
+
+PSK are narrow band low symbol rate modes using either single or
+multiple carrier differential Binary Phase Shift Kying, BPSK, or Quadrature
+Phase Shift Keying, QPSK.
+<br>
+
+PSK63FEC and the PSKxxxR modes are forward error correcting modes. PSK63FEC
+is compatible with the MultiPsk mode of the same name. The PSKxxxR, or
+robust, modes use both forward error correction and interleaving to achieve
+about 4 dB s/n improvement over standard PSK. These modes are use primarily
+by the PskMail user community. They are the invention of John Douyere,
+VK2ETA, a member of the fldigi development team.
+<br>
+
+In addition to the binary phase shift keying the signal is 100%
+raised-cosine amplitude modulated at the symbol rate. This reduces the power
+to zero at the phase change. Because of this amplitude modulation, the
+signal bandwidth is relatively narrow. Synchronization at the receiver
+is straight forward because it can be recovered from the amplitude
+information. Differential PSK is used to provide continuous phase changes
+when idle (to maintain sync), and by allowing the receiver to measure phase
+difference from symbol to symbol, to reduce the effects of ionospheric
+Doppler phase changes which modulate the signal. The slower modes are
+more affected by Doppler, and the QPSK modes are particularly affected.
+<br>
+
+With no interleaver and limited coding length, the QPSK mode Forward Error
+Correction coding gain is limited, and under burst noise conditions on
+HF the performance is usually worse than the BPSK option at the same
+baud rate. In general the narrow-band BPSK modes work well on a quiet
+single-hop path, but give poor performance in most other conditions.
+<br>
+
+\image html psk-signal-oscope.png "PSK63 signal transmitting text data - oscilloscope view"
+\image latex psk-signal-oscope.png "PSK63 signal transmitting text data - oscilloscope view" width=5.0in
+<br>
+
+\image html psk-signal-waterfall.png "PSK63 signal transmitting text data - waterfall view"
+\image latex psk-signal-waterfall.png "PSK63 signal transmitting text data - waterfall view" width=1.0in
+<br>
+
+\image html qpsk-signal-oscope.png "QPSK63 signal transmitting text data - oscilloscope - waterfall view"
+\image latex qpsk-signal-oscope.png "QPSK63 signal transmitting text data - oscilloscope - waterfall view" width=5.0in
+<br>
+
+\image html qpsk-signal-waterfall.png "QPSK63 signal transmitting text data - waterfall view"
+\image latex qpsk-signal-waterfall.png "QPSK63 signal transmitting text data - waterfall view" width=1.0in
+
+<br>
+
+The two oscilloscope views above clearly show the combined phase and
+amplitude modulation of these modes.<br>
+
+<br>
+
+With these modes, a very linear transmitter is required. Over-driven
+operation results in excessive bandwidth, poorer reception and
+difficult tuning. Overdrive usually occurs by having the audio
+signal much too large. These are very sensitive modes and usually very little
+power is required. QRP operation of 80, 40, 30 and 20 meters can provide
+nearly 100% copy over multi-hop paths. In many instances PSK can provide
+better decoding than CW.
+<br>
+
+Setting up for a good clean on air signal that will receive the accolades
+of your QSO partners is easy. Follow the instructions on using the
+\ref tune_page "Tune" button</a> and you will have a clean on signal.
+<br>
+
+Good reception of PSK signals requires that the demodulator be phase locked
+to the incoming signal. Fldigi has both a fast acquire / slow tracking AFC
+system. Place the red bandwidth bar (see above) so that it overlies
+the desired signal and then press the left mouse button. The signal
+should quickly lock on a decoding should commence immediately. It is
+almost impossible to visually tell whether a BPSK or QPSK signal is
+being received. Under very high s/n you might be able to hear the
+difference, but that is even difficult for most operators. If you are not
+able to decode a signal that looks like a BPSK and the bandwidth of the
+signal matches the baud rate then it might be a QPSK signal. Just change
+mode a try reacquiring the signal.
+<br>
+
+\section multi_bpsk_modem  Multi-Channel PSK modems
+
+\image html MultiChannelBPSKWaterfall.png "PSK63R20C signal transmitting text data - waterfall view"
+\image latex MultiChannelBPSKWaterfall.png "PSK63R20C signal transmitting text data - waterfall view" width=4.0in
+
+<br>
+\ref psk_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/pskmail_config.txt b/fldigi_doxygen/user_src_docs/pskmail_config.txt
new file mode 100644
index 00000000..e3d1e4de
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/pskmail_config.txt
@@ -0,0 +1,26 @@
+/**
+\page  psk_mail_configuation_page PSKmail Configuration
+
+\tableofcontents
+
+
+Fldigi can act as both a server and a client for PskMail, a separate
+application from fldigi.  The PSKmail specific configuration
+parameters are all located on the Misc/Pskmail tab of the configuration
+dialog.
+<br>
+
+Instructions on setting these parameters are a part of the pskmail installation.
+<br>
+
+\image html config-psk-mail.png "PSK Mail Configuration"
+\image latex config-psk-mail.png "PSK Mail Configuration" width=5.0in
+<br>
+
+
+<br>
+\ref psk_mail_configuation_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/rigxml.txt b/fldigi_doxygen/user_src_docs/rigxml.txt
new file mode 100644
index 00000000..9c9bd075
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/rigxml.txt
@@ -0,0 +1,384 @@
+/**
+\page  rig_xml_page Rig Xml How to
+
+\tableofcontents
+
+This document describes the contents of the rig definition file \"rig.xml\".
+<br>
+
+A number of transceivers have rig definition files written and tested
+which you may use. These are found in the xmls directory on this
+site: <a href="http://www.w1hkj.com/xmlarchives.html">xml archives</a>.
+You will find subdirectories by manufacturer which contain files named
+by rig type, ie: TS-850.xml. If you create, test and verify the proper
+operation for a transceiver not yet posted please share that with
+others by sending it as an attachment to w1hkj@w1hkj.com and I will
+post it on the web site. You are encouraged to study the various rig
+definition files to learn more about how they are organized.
+
+Comments are contained within the tag pair:
+
+\<!-<br> --\>
+<br>
+
+and may appear anywhere in the rig definition file The entire rig definition
+must be contained within the tag pair
+
+\<RIGDEF\><br>\</RIGDEF\>
+
+The text within the tag pair \<RIG\>\</RIG\> specifies the transceiver to
+which this file applies, as in:
+
+\<RIG\>Icom 746 PRO\</RIG\>
+<br>
+
+The text within the tag pair \<PROGRAMMER\>\</PROGRAMMER\> is not used by the
+parser, but should as a minimum say who created and who tested the definition file, as in:
+<br>
+
+\<PROGRAMMER\>
+<br>
+
+Dave Freese W1HKJ Tested by: W1HKJ, Dave <br> \</PROGRAMMER\>
+
+The text within the tag pair
+
+\<STATUS\><br> \</STATUS\>
+
+is not used by the parser, but should as a minimum state whether the
+definition file has been \"Verified\", is \"Alpha&\", what the Version and
+Date of creation or update, as in:
+
+\<STATUS\> Verified Version: 1.0 Date: 2007 Jan 5 \</STATUS\>
+
+The \<TITLE\><br> \</TITLE\>
+
+tag pair contains the text which will be displayed on the window decoration bar, as in:
+
+\<TITLE\>Rig Control - IC-746 PRO\</TITLE\><br>
+
+The serial port parameters may be preset in the xml file and also set or
+changed on the rigcat configuration tab.
+<br>
+\<!--
+<br>
+default settings for initial setup
+<br>
+--\>
+<br>
+
+<table>
+    <tr>
+      <td>xml tag<br>
+      </td>
+      <td>parameter<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<TIMEOUT\>TT\</TIMEOUT\></td>
+      <td>TT in milliseconds<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<RETRIES\>NN\</RETRIES\></td>
+      <td>NN integer<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<WRITE_DELAY\>TT\</WRITE_DELAY\></td>
+      <td>TT in milliseconds<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<POST_WRITE_DELAY\>TT\</POST_WRITE_DELAY\></td>
+      <td>TT in milliseconds<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<BAUDRATE\>BAUD\</BAUDRATE\></td>
+      <td>BAUD = 1200, 2400, 4800, 9600, 19200, 38400 ...<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<STOPBITS\>B\</STOPBITS\></td>
+      <td>B = 1 or 2<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<RTSCTS\>BOOL\</RTSCTS\></td>
+      <td>BOOL = true, false; h/w handshake used for data flow control<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<RTSPLUS\>BOOL\</RTSPLUS\></td>
+      <td>BOOL = true, false; set RTS signal line to +12 V<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<RTSPTT\>BOOL\</RTSPTT\></td>
+      <td>BOOL = true, false; toggle RTS signal line for PTT<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<DTRPLUS\>BOOL\</DTRPLUS\></td>
+      <td>BOOL = true, false; set DTR signal line to + 12 V</td>
+    </tr>
+    <tr>
+      <td>\<DTRPTT\>BOOL\</DTRPTT\></td>
+      <td>BOOL = true, false; toggle DTR signal line for PTT<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<ECHO\>BOOL\</ECHO\></td>
+      <td>BOOL = true, false; xcvr/interface echoes all chars (typical of CI-V interface)<br>
+      </td>
+    </tr>
+    <tr>
+      <td>\<CMDPTT\>BOOL\</CMDPTT\></td>
+      <td>BOOL = true, false; use command string for PTT (not supported by all rigs)<br>
+      </td>
+    </tr>
+</table>
+<br>
+
+The transceiver modes are specified within the \<MODES\>\</MODES\> tag pair.
+Each entry or element associated with a mode has a symbol name (text) and a
+way to specify what the data transfer consists of. The data transfer might
+be a single byte, multiple bytes, or aa string
+<br>
+
+Example 1, for the Icom-746PRO
+<br>
+
+\<MODES\><br>
+      \<ELEMENT\>\<SYMBOL\>LSB\</SYMBOL\>\<BYTE\>00\</BYTE\>\</ELEMENT\><br>
+      \<ELEMENT\>\<SYMBOL\>USB\</SYMBOL\>\<BYTE\>01\</BYTE\>\</ELEMENT\><br>
+      \<ELEMENT\>\<SYMBOL\>AM\</SYMBOL\>\<BYTE\>02\</BYTE\>\</ELEMENT\><br>
+      \<ELEMENT\>\<SYMBOL\>CW\</SYMBOL\>\<BYTE\>03\</BYTE\>\</ELEMENT\><br>
+      \<ELEMENT\>\<SYMBOL\>RTTY\</SYMBOL\>\<BYTE\>04\</BYTE\>\</ELEMENT\><br>
+      \<ELEMENT\>\<SYMBOL\>FM\</SYMBOL\>\<BYTE\>05\</BYTE\>\</ELEMENT\><br>
+      \<ELEMENT\>\<SYMBOL\>CW-R\</SYMBOL\>\<BYTE\>07\</BYTE\>\</ELEMENT\><br>
+      \<ELEMENT\>\<SYMBOL\>RTTY-R\</SYMBOL\>\<BYTE\>08\</BYTE\>\</ELEMENT\><br>
+\</MODES\><br>
+<br>
+
+Example 2, for the Kenwood 850
+<br>
+
+\<MODES\><br>
+       \<ELEMENT\>\<SYMBOL\>LSB\</SYMBOL\>\<BYTE\>31\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>USB\</SYMBOL\>\<BYTE\>32\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>CW\</SYMBOL\>\<BYTE\>33\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>FM\</SYMBOL\>\<BYTE\>34\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>AM\</SYMBOL\>\<BYTE\>35\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>FSK\</SYMBOL\>\<BYTE\>36\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>CW-R\</SYMBOL\>\<BYTE\>37\</BYTE\>\</ELEMENT\><br>
+
+\<ELEMENT\>\<SYMBOL\>FSK-R\</SYMBOL\>\<BYTE\>39\</BYTE\>\</ELEMENT\><br>
+\</MODES\><br>
+<br>
+
+Example 3, for the FT-100
+<br>
+\<MODES\><br>
+       \<ELEMENT\>\<SYMBOL\>LSB\</SYMBOL\>\<BYTE\>00\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>USB\</SYMBOL\>\<BYTE\>01\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>CW\</SYMBOL\>\<BYTE\>02\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>CW-R\</SYMBOL\>\<BYTE\>03\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>AM\</SYMBOL\>\<BYTE\>04\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>DIG\</SYMBOL\>\<BYTE\>05\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>FM\</SYMBOL\>\<BYTE\>06\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>W-FM\</SYMBOL\>\<BYTE\>07\</BYTE\>\</ELEMENT\><br>
+\</MODES\><br>
+<br>
+
+The modes which are supported by lower sideband in the transceiver are
+specified in the \<LSBMODES\>\</LSBMODES\> tar pair. The string
+data for the LSB modes must match those given in the modes id specifier
+For example in the Icom 746 Pro:
+<br>
+
+\<LSBMODES\><br>
+       \<STRING\>LSB\</STRING\><br>
+       \<STRING\>RTTY\</STRING\><br>
+       \<STRING\>CW-R\</STRING\><br>
+\</LSBMODES\><br>
+<br>
+
+If the transceiver data stream uses identically the same format for the
+bandwidth data then it is specified in the \<BANDWIDTHS\>\</BANDWIDTHS\> tag
+pair
+<br>
+
+Example for the Icom 746 Pro:
+<br>
+
+\<BANDWIDTHS\><br>
+       \<ELEMENT\>\<SYMBOL\>50\</SYMBOL\>\<BYTE\>00\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>100\</SYMBOL\>\<BYTE\>01\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>150\</SYMBOL\>\<BYTE\>02\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>200\</SYMBOL\>\<BYTE\>03\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>250\</SYMBOL\>\<BYTE\>04\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>300\</SYMBOL\>\<BYTE\>05\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>350\</SYMBOL\>\<BYTE\>06\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>400\</SYMBOL\>\<BYTE\>07\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>450\</SYMBOL\>\<BYTE\>08\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>500\</SYMBOL\>\<BYTE\>09\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>600\</SYMBOL\>\<BYTE\>10\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>700\</SYMBOL\>\<BYTE\>11\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>800\</SYMBOL\>\<BYTE\>12\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>900\</SYMBOL\>\<BYTE\>13\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1000\</SYMBOL\>\<BYTE\>14\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1100\</SYMBOL\>\<BYTE\>15\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1200\</SYMBOL\>\<BYTE\>16\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1300\</SYMBOL\>\<BYTE\>17\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1400\</SYMBOL\>\<BYTE\>18\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1500\</SYMBOL\>\<BYTE\>19\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1600\</SYMBOL\>\<BYTE\>20\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1700\</SYMBOL\>\<BYTE\>21\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1800\</SYMBOL\>\<BYTE\>22\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>1900\</SYMBOL\>\<BYTE\>23\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2000\</SYMBOL\>\<BYTE\>24\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2100\</SYMBOL\>\<BYTE\>25\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2200\</SYMBOL\>\<BYTE\>26\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2300\</SYMBOL\>\<BYTE\>27\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2400\</SYMBOL\>\<BYTE\>28\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2500\</SYMBOL\>\<BYTE\>29\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2600\</SYMBOL\>\<BYTE\>30\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2700\</SYMBOL\>\<BYTE\>31\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2800\</SYMBOL\>\<BYTE\>32\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2900\</SYMBOL\>\<BYTE\>33\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>3000\</SYMBOL\>\<BYTE\>34\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>3100\</SYMBOL\>\<BYTE\>35\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>3200\</SYMBOL\>\<BYTE\>36\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>3300\</SYMBOL\>\<BYTE\>37\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>3400\</SYMBOL\>\<BYTE\>38\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>3500\</SYMBOL\>\<BYTE\>39\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>3600\</SYMBOL\>\<BYTE\>40\</BYTE\>\</ELEMENT\><br>
+\</BANDWIDTHS\><br>
+<br>
+
+If the bandwidth data stream is unique for send and receive data streams then
+they are specified separately with the \<BW-CMD\>\</BW-CMD\> tag pair for
+data sent to the transceiver, and the \<BW-REPLY\>\</BW-REPLY\> tag pair for
+data returned to the computer.
+<br>
+
+Example: FT-100:
+<br>
+
+\<BW-CMD\><br>
+       \<ELEMENT\>\<SYMBOL\>300\</SYMBOL\>\<BYTE\>00\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>500\</SYMBOL\>\<BYTE\>01\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2400\</SYMBOL\>\<BYTE\>02\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>6000\</SYMBOL\>\<BYTE\>03\</BYTE\>\</ELEMENT\><br>
+\</BW-CMD\><br>
+<br>
+\<BW-REPLY\><br>
+       \<ELEMENT\>\<SYMBOL\>300\</SYMBOL\>\<BYTE\>03\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>500\</SYMBOL\>\<BYTE\>02\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>2400\</SYMBOL\>\<BYTE\>01\</BYTE\>\</ELEMENT\><br>
+       \<ELEMENT\>\<SYMBOL\>6000\</SYMBOL\>\<BYTE\>00\</BYTE\>\</ELEMENT\><br>
+\</BW-REPLY\><br>
+<br>
+
+Fldigi can parse and decode message returned from the transceiver that define
+4 aspects of the transceiver operation:
+<br>
+
+<table>
+    <tr>
+      <td>OK</td>
+      <td>data accepted by the transceiver</td>
+    </tr>
+    <tr>
+      <td>BAD</td>
+      <td>data rejected by the transceiver</td>
+    </tr>
+    <tr>
+      <td>MODE</td>
+      <td>current operating mode of the transceiver</td>
+    </tr>
+    <tr>
+      <td>BW</td>
+      <td>current bandwidth setting of the transceiver</td>
+    </tr>
+    <tr>
+      <td>FREQ</td>
+      <td>frequency of the active VFO (might be either A or B for example)</td>
+    </tr>
+</table>
+<br>
+
+These are all contained within multiple \<REPLY\>\</REPLY\> tag pairs.  This
+is an example of a fixed format message with no variable fields. It is the
+OK message sent back by the Icom-746 PRO:
+<br>
+
+\<REPLY\><br>
+       \<SYMBOL\>OK\</SYMBOL\><br>
+       \<SIZE\>6\</SIZE\><br>
+       \<BYTES\>FE FE E0 66\</BYTES\><br>
+       \<BYTE\>FB\</BYTE\><br>
+       \<BYTE\>FD\</BYTE\><br>
+\</REPLY\><br>
+<br>
+
+The \<SYMBOL\>\</SYMBOL\> pair and the command definition are
+mandatory.  The \<SIZE\>\</SIZE\> field is mandatory and specifies the number
+of bytes contained in this reply. The above definition could also have been
+coded as:
+<br>
+
+\<REPLY\><br>
+       \<SYMBOL\>OK\</SYMBOL\><br>
+       \<SIZE\>6\</SIZE\><br>
+       \<BYTES\>FE FE E0 66 FB FD\</BYTES\><br>
+\</REPLY\><br>
+<br>
+
+When the reply contains variable data it is specified in a contained
+tag pair \<DATA\>\</DATA\>. This data field contains specifiers that describe
+the kind and size of the data. The \<DTYPE\>\</DTYPE\> tag pair may
+be one of:
+<br>
+
+BINARY or<br>
+DECIMAL<br>
+<br>
+
+This is an example for the reply to a mode query that is returned by the Icom-746 PRO:<br>
+<br>
+
+\<REPLY\><br>
+       \<SYMBOL\>MODE\</SYMBOL\>     specifies the response name<br>
+\<SIZE\>8\</SIZE\>
+8 bytes of data returned<br>
+       \<BYTES\>FE FE E0 66\</BYTES\>  4 bytes of preamble<br>
+
+\<BYTE\>04\</BYTE\>                       1
+additional byte for preample<br>
+       \<DATA\><br>
+
+\<DTYPE\>BINARY\</DTYPE\>   binary data field of
+1 byte<br>
+             \<SIZE\>1\</SIZE\><br>
+       \</DATA\><br>
+
+\<FILL\>1\</FILL\>
+a variable field (data) not used<br>
+
+\<BYTE\>FD\</BYTE\>                      1
+byte postamble<br>
+\</REPLY\><br>
+<br>
+
+Fldigi rigcat will check for both the preample and postamble to insure
+that a valid reply has been sent by the transceiver.
+<br>
+
+\ref rig_xml_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/signal-browser.txt b/fldigi_doxygen/user_src_docs/signal-browser.txt
new file mode 100644
index 00000000..130d2456
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/signal-browser.txt
@@ -0,0 +1,75 @@
+/**
+\page  signal_broswer_page Signal Browser
+
+\tableofcontents
+
+
+\image html view-menu.png "View Menu"
+\image latex view-menu.png "View Menu" width=2.0in
+<br>
+
+PSK and RTTY signals can be viewed in a multi-channel context.
+You can open an embedded or a separate dialog to access the
+browser.  These browsers can help to locate a signal of interest
+on a busy band.  The browsers can be visible at any time, but are only
+active when fldigi is in one of the PSK or RTTY modes.  Open the external
+by clicking on the <b>View/Signal browser</b> menu item.
+
+It looks like this:
+
+\image html browser-panel.png "Browser Panel"
+\image latex browser-panel.png "Browser Panel" width=4.3in
+<br>
+<br>
+
+Toggle the visibility of the embedded viewer by selecting the <b>
+View/Hide Channels</b> on the same menu list.  Your main fldigi screen
+then opens a browser panel on the left side of the Tx/Rx panel(s).  Both
+browsers can be viewed and used simultaneously.  When you click on a valid
+waterfall signal the browser will highlight the appropriate channel (if
+it is also tracking that signal).
+<br>
+
+\image html main-dialog-browser.png "Main Window"
+\image latex main-dialog-browser.png "Main Window" width=6.0in
+<br>
+
+This panel can be resized horizontally by dragging the interface between the
+browser and the Rx panel to the left and right.  You can drag all the way to
+the left to close the panel (or use the menu button).  The drag to the right
+is limited to prevent sizing the Rx/Tx panels below their allowable limits.
+<br>
+
+The browser can decode up to 30 simultaneous signals.  As each signal is
+acquired within a 100 Hz channel width it is printed on the associated
+line.  The user can elect to have each line annotated with
+<br>
+<br>
+a channel number, <br>
+the waterfall audio frequency, <br>
+the transceiver HF frequency + waterfall, or<br>
+no annotation.<br>
+
+<br>
+
+Left click on a line of received text to move the waterfall frequency
+and Rx panel tracking to that signal.  The contents of the line of
+text is transferred to the Rx text widget, and the main signal processing loop
+begins to track and decode that signal.  Right click on a line of received
+text and that line is cleared and the channel reset for a new
+detection.  You may have to do this occasionally if the detector
+for that channel has locked on to a sideband of a PSK signal.
+This is most likely to occur when the received signal as a marginal or
+bad IMD.  Use the <b>Clear</b> button to clear and reset all of the
+channels.  Channel signal detection and processing should restart immediately.
+<br>
+<br>
+\ref ui_configuration_broswer_page "Configuring the browser"
+
+<br>
+\ref signal_broswer_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/support_data.txt b/fldigi_doxygen/user_src_docs/support_data.txt
new file mode 100644
index 00000000..9dcaa30f
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/support_data.txt
@@ -0,0 +1,33 @@
+/**
+\page supporting_data_files_page  Supporting Data Files Acquisition
+
+\tableofcontents
+<br>
+
+\image html support_data_menu_item.png "Data File Menu"
+\image latex support_data_menu_item.png "Data File Menu" width=2.0in
+<br>
+
+To update support data file(s). Mouse click on the 'Data files..." menu item
+located in the above drop down menu.
+
+\image html support_data_dialog.png "Data File Source"
+\image latex support_data_dialog.png "Data File Source" width=4.5in
+<br>
+
+The dialog box contains a list of the available file(s) for downloading. Click
+on the 'Update' button to initiate the data transfer.
+
+The buttons under WWW column are direct links to the data source. Selecting
+them either displays or downloads the data from your web browser.
+
+<b>Note:</b> Data source selection contain a single entry. User selection not
+required.
+
+\ref supporting_data_files_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
+
diff --git a/fldigi_doxygen/user_src_docs/temp.txt b/fldigi_doxygen/user_src_docs/temp.txt
new file mode 100644
index 00000000..1e5de54f
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/temp.txt
@@ -0,0 +1,65 @@
+\documentclass{article}
+\usepackage[demo]{graphicx}
+\usepackage{caption}
+\usepackage{subcaption}
+
+\begin{document}
+
+\begin{figure}
+\centering
+\begin{subfigure}{.5\textwidth}
+  \centering
+  \includegraphics[width=.4\linewidth]{image1}
+  \caption{A subfigure}
+  \label{fig:sub1}
+\end{subfigure}%
+\begin{subfigure}{.5\textwidth}
+  \centering
+  \includegraphics[width=.4\linewidth]{image1}
+  \caption{A subfigure}
+  \label{fig:sub2}
+\end{subfigure}
+\caption{A figure with two subfigures}
+\label{fig:test}
+\end{figure}
+
+\begin{figure}
+\centering
+\begin{minipage}{.5\textwidth}
+  \centering
+  \includegraphics[width=.4\linewidth]{image1}
+  \captionof{figure}{A figure}
+  \label{fig:test1}
+\end{minipage}%
+\begin{minipage}{.5\textwidth}
+  \centering
+  \includegraphics[width=.4\linewidth]{image1}
+  \captionof{figure}{Another figure}
+  \label{fig:test2}
+\end{minipage}
+\end{figure}
+
+\end{document}
+
+\\begin{figure}
+\hfill
+\subfigure[Title A]{\includegraphics[width=5cm]{img1}}
+\hfill
+\subfigure[Title B]{\includegraphics[width=5cm]{img2}}
+\hfill
+\caption{Title for both}
+\end{figure}
+
+\begin{figure}
+\centering
+\parbox{5cm}{
+\includegraphics[width=5cm]{img1}
+\caption{First.}
+\label{fig:2figsA}}
+\qquad
+\begin{minipage}{5cm}
+\includegraphics[width=5cm]{img2}
+\caption{Second.}
+\label{fig:2figsB}
+\end{minipage}
+\end{figure}
diff --git a/fldigi_doxygen/user_src_docs/template.txt b/fldigi_doxygen/user_src_docs/template.txt
new file mode 100644
index 00000000..de15955f
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/template.txt
@@ -0,0 +1,65 @@
+-----------------------------------------------------------------------------
+/**
+\page  ID_TAG Description
+
+\tableofcontents
+-----------------------------------------------------------------------------
+\image html filename.png "Desc"
+\image latex filename.png "Desc" width=5.0in
+<br>
+-----------------------------------------------------------------------------
+<ol>
+<li> </li>
+<li> </li>
+<li> </li>
+</ol>
+-----------------------------------------------------------------------------
+
+
+<br>
+\ref id_tag "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
+-----------------------------------------------------------------------------
+\latexonly
+	\begin{figure}[H]
+
+		\centering
+
+		\begin{subfigure}[t]{0.5\textwidth}
+			\centering
+			\includegraphics[width=1.0in]{filename.png}
+			\caption{Caption}
+			\label{fig:fig_name}
+		\end{subfigure} ~
+		,...
+		\begin{subfigure}[t]{0.5\textwidth}
+			\centering
+			\includegraphics[width=1.0in]{filename.png}
+			\caption{Caption}
+			\label{fig:fig_name}
+		\end{subfigure}
+
+		\begin{subfigure}[t]{0.5\textwidth}
+			\centering
+			\includegraphics[width=1.0in]{filename.png}
+			\caption{Caption}
+			\label{fig:fig_name}
+		\end{subfigure} ~
+		,...
+		\begin{subfigure}[t]{0.5\textwidth}
+			\centering
+			\includegraphics[width=1.0in]{filename.png}
+			\caption{Caption}
+			\label{fig:fig_name}
+		\end{subfigure}
+		,...
+
+		\caption{Description}
+		\label{fig:figure_idtag}
+
+	\end{figure}
+\endlatexonly
+-----------------------------------------------------------------------------
diff --git a/fldigi_doxygen/user_src_docs/throb.txt b/fldigi_doxygen/user_src_docs/throb.txt
new file mode 100644
index 00000000..393295c2
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/throb.txt
@@ -0,0 +1,51 @@
+/**
+\page throb_page Throb
+
+\tableofcontents
+
+The THROB family of modes use two tones at a time. These tones are also
+amplitude modulated and can be a single tone for some symbols.
+<br>
+
+The mode has no Forward Error Correction, and is difficult to
+tune. It is fairly sensitive and moderately robust. Keyboard-to-keyboard QSOs
+are reasonably fast.
+<br>
+
+Tuning must be very accurate, and the software will not tolerate
+differences between transmit and receive frequency.
+<br>
+
+The amplitude modulation component of THROB is a raised cosine AM modulation
+of each symbol. This combined with two tones transmitted at the same time,
+means that a very linear transmitter is required. It also gives the mode its
+very unique sound. You will never mistake Throb for any other mode.
+<br>
+
+For THROB, nine tones are used, spaced 8 or 16 Hz. For THROBX, 11 tones
+are used, spaced 7.8125 or 15.625 Hz.
+<br>
+
+Fldigi supports the following:
+<br>
+
+\section throb_baud_table  Throb baud rates and tone spacings
+<br>
+
+  Mode  | Symbol Rate |   Typing Speed   | Bandwidth
+:------:|:-----------:|:----------------:|:----------------:
+THROB1  |   1.0 baud  | 1.0 cps (10 wpm) | 72 Hz
+THROB2  |   2.0 baud  | 2.0 cps (20 wpm) | 72 Hz
+THROB4  |   4.0 baud  | 4.0 cps (40 wpm) | 144 Hz
+THROBX1 |   1.0 baud  | 1.0 cps (10 wpm) | 94 Hz
+THROBX2 |   2.0 baud  | 2.0 cps (20 wpm) | 94 Hz
+THROBX4 |   4.0 baud  | 4.0 cps (40 wpm) | 188 Hz
+
+<br>
+
+
+\ref throb_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/tune.txt b/fldigi_doxygen/user_src_docs/tune.txt
new file mode 100644
index 00000000..5a8639f9
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/tune.txt
@@ -0,0 +1,74 @@
+/**
+\page tune_page TUNE - Transmit a single tone carrier.
+
+\tableofcontents
+
+\section tune TUNE Mode
+
+Too often you see an overdriven signals on the digital sub-bands;
+multiple audio sidebands on PSK, splatter from overdriven MFSK and
+RTTY. There is absolutely no reason for a transceiver driven
+by fldigi to exhibit this type of performance. You can set up
+your computer / transceiver for good solid performance without excessive
+drive.
+<br>
+
+The "TUNE" button generates a continuous single frequency audio signal
+at the exact frequency to which the waterfall cursor has been set. The peak
+amplitude of this signal is the peak amplitude of every modem signal
+generated by fldigi. None will exceed this value, even the simultaneous
+multi-tone modes like Throb. Every modern SSB transmitter uses some automatic
+level control ALC for preventing overdrive for SSB voice. A little overdrive
+on a voice channel can be tolerated to a degree. In fact, that is what
+an analog RF compressor does, overdrive and then subsequent filtering.
+But you absolutely cannot tolerate that with the digital modes. Here is the
+way to set up your transceiver for a clean signal. I recommend starting out
+with a dummy load, but an "off hour" for a band might work just as well if
+you do not have a dummy load.
+<br>
+
+<ul>
+	<li>For Windows users</li>
+	<ul>
+		<li>Set your sound card output level to the minimum on the Windows
+			mixer</li>
+	</ul>
+	<li>For Linux users</li>
+	<ul>
+		<li>Set your PCM level to about 80%</li>
+		<li>Set your Transmit Level control for minimum output level.</li>
+	</ul>
+	<li>Enable the "Tune" mode in fldigi ... you do have CAT or PTT set up ...right?</li>
+	<li>Make sure your transceiver's speech compression control is OFF</li>
+	<li>Slowly bring up the Mixer audio out until your rig's ALC just starts
+		to function (a light blinking or a meter showing this condition).</li>
+	<li>Reduce the Mixer audio output until the ALC is disabled.</li>
+	<li>You are now transmitting at maximum output power without distortion.</li>
+</ul>
+
+You can use any level below this and be assured that your output signal
+will be clean. All digital signals that fldigi generates will be limited to
+this peak-to-peak voltage. You should always use the minimum power necessary
+to maintain good comms, remember that even if you are clean at 100 W you
+signal will be so strong among the QRP signals that it will overpower the
+AGC on many receivers that are working another digital station within the
+same SSB bandwidth that you are on. You will appreciate this the first
+time that you are working a weak PSK DX station and someone blasts through
+and captures your AGC.
+<br>
+
+You should try the the above adjustments at different audio
+frequencies. Transceivers that achieve the SSB filtering with crystal or
+mechanical filters will have a considerable amount of variation across the
+passband of the filter. This will show up as a varying amount of ALC that is
+dependent on the audio frequency. Once you are comfortable with the process
+you can very quickly repeat the "Tune" and set the power for the frequency
+to which the waterfall is set.
+<br>
+
+\ref tune_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/ualr-telnet.txt b/fldigi_doxygen/user_src_docs/ualr-telnet.txt
new file mode 100644
index 00000000..d8e1ed8e
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/ualr-telnet.txt
@@ -0,0 +1,71 @@
+/**
+\page ualr_telnet_page ualr telnet
+
+\tableofcontents
+
+\verbatim
+
+snip ------------ copy the following to ~/.fldigi/scripts/ualr-telnet.pl
+
+#!/usr/bin/perl
+
+# Author: Stelios Bounanos, M0GLD
+# Date: 20090103
+#
+# ualr-telnet is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# ualr-telnetl is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+# ----------------------------------------------------------------------------
+
+use strict;
+use warnings;
+
+die "Usage: $0 CALLSIGN\n" unless (@ARGV == 1);
+
+use Net::Telnet ();
+
+sub error { print "\$NAME?\$QTH?\n"; exit(1); }
+my $t = new Net::Telnet( Host => "callsign.ualr.edu", Port => 2000, Timeout => 10,
+             errmode => \&error );
+$t->open();
+$t->waitfor('/LOOKUP>.*$/');
+$t->print($ARGV[0]);
+
+$_ = $t->getline();      # blank line
+$_ = $t->getline();      # call
+error() if (m/No match found/);
+
+$_ = $t->getline();      # name
+chomp; s/.+,\s+//; s/\s.+$//;
+print "\$NAME$_";
+$_ = $t->getline();      # addr
+$_ = $t->getline();      # qth
+chomp;
+$_ =~ ",";
+$_ = $`;
+
+print "\$QTH$_\n";
+
+$t->waitfor('/LOOKUP>.*$/');
+$t->print("bye");
+
+snip------------------------------------------------
+
+\endverbatim
+
+
+<br>
+\ref ualr_telnet_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/w5zit-interface.txt b/fldigi_doxygen/user_src_docs/w5zit-interface.txt
new file mode 100644
index 00000000..e914f030
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/w5zit-interface.txt
@@ -0,0 +1,62 @@
+/**
+\page  w5zit_rt_channel_page Using the FLdigi Rt. Channel for transmitter PTT
+
+\tableofcontents
+
+This interface is designed to take advantage of the Right Speaker tone
+output in FLDigi for actuating the PTT. It is especially useful for
+interfacing a small notepad with minimal I/O capability to
+a radio. It has been my experience that complete ground isolation
+between a laptop and the radio (including eliminating any kind of rig
+control) provides the minimum QRM to the receiver from the laptop. The
+Headphone and Mic connections are the only computer connections
+necessary.
+
+The tone output is coupled through a transformer to maintain complete ground
+isolation between the computer and the radio.  There is no external power
+required for this interface and an FET is used to provide the PTT output. I
+use transformers in both the audio input and output paths to complete the
+isolation.
+<br>
+
+Note that two of the transformers are wired to the single stereo jack
+from the Speaker output of the computer. The normal Left Speaker Output
+(TIP) is used to provide the modulating audio for the radio transmit
+input while the Right Speaker Output (RING) provides the tone output
+that drives the PTT circuit. The SHELL of the connector provides the
+return path for both signals.
+<br>
+
+Audio from the radio is supplied to the MIC input on the computer for
+demodulation by the FLDigi program.
+<br>
+
+Somewhat higher output from the computer is required to reliably operate
+the PTT circuit and the audio balance control in the computer is used to
+reduce the output to the radio to the level required for normal
+modulation. Since the right speaker tone output is not the same audio
+used to modulate the radio, no signal distortion is caused by the clipping
+action of the diode rectifiers used in the PTT circuit.
+<br>
+
+To configure FLDigi to use this interface go to
+(Configure/Rig Control/Hardware PTT) and check only the (PTT tone on right
+audio channel) box.
+<br>
+
+\image html W5ZIT-interface.png "W5ZIT Interface"
+\image latex W5ZIT-interface.png "W5ZIT Interface" width=6.0in
+<br>
+
+\image html w5zit-ts2000-interface.png "TS-2000 ACC-2 to DB9 Adapter"
+\image latex w5zit-ts2000-interface.png "TS-2000 ACC-2 to DB9 Adapter" width=6.0in
+<br>
+
+
+
+<br>
+\ref w5zit_rt_channel_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/working_logs.txt b/fldigi_doxygen/user_src_docs/working_logs.txt
new file mode 100644
index 00000000..be4a7c3a
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/working_logs.txt
@@ -0,0 +1,158 @@
+/**
+\page  working_logs_page  Working Logs
+
+\tableofcontents
+
+## Working Logs ##
+
+Fldigi maintains a number of working log files that are found in its default
+folder.  The default folder is easy to find, simply select the
+menu item "File/Show config" and your OS default files explorer will be
+opened to that location.
+
+### Rx/Tx Capture File ###
+
+Everytime you start or stop fldigi that event is recorded in a daily log file.
+The daily log is named as:
+<br>
+
+flidigYYYYMMDD.log
+<br>
+
+where YYYYMMDD is the current GMT date.  This log will also contain your
+entire session of Rx and Tx data annotated as to activity and time stamped.
+Here is a small example of the daily log:
+<br>
+
+\verbatim
+    --- Logging started at Tue Dec 30 11:37:21 2008 UTC ---
+
+    RX (2008-12-30 11:37Z): o ur property. No pwr even for a day is rough.
+    TX (2008-12-30 11:39Z):
+    TX (2008-12-30 11:39Z): CQ CQ CQ de W1HKJ W1HKJ W1HKJ
+    TX (2008-12-30 11:40Z): CQ CQ CQ de W1HKJ W1HKJ W1HKJ pse k
+
+    RX (2008-12-30 11:40Z): mG sk
+
+    --- Logging stopped at Tue Dec 30 11:48:11 2008 UTC ---
+\endverbatim
+
+This log is appended to with each start and stop.  That means that no data is
+ever overwritten.
+
+### Status log ###
+
+A log of errors, warnings and status reports is written for each session.  This
+file is overwritten each time the program is opened and subsequently closed.
+Its format is also ASCII text and will contain data such as:
+<br>
+
+\verbatim
+
+    Q: main: fldigi 3.04BV log started on Tue Dec 30 05:47:10 2008
+    W: dxcc_open: Could not read contest country file "/home/dave/.fldigi/cty.dat"
+\endverbatim
+
+This data is identical to that which can be viewed with the event log dialog
+which is opened using the menu item "Help/Event log"
+
+\image html event-log.png "Event Log"
+\image latex event-log.png "Event Log" width=5.0in
+<br>
+
+\image html event-log-menu.png "Event Log Menu"
+\image latex event-log-menu.png "Event Log Menu" width=1.75in
+
+There are six levels of event logging with increasing depth of reports:
+<br>
+
+\htmlonly
+<table>
+<tr><th>Event Logging Levels</th></tr>
+<tr>
+<td><img src="event-log-quiet.png"></td>
+<td><img src="event-log-error.png"></td>
+<td><img src="event-log-warning.png"></td>
+</tr>
+<tr>
+<td><img src="event-log-info.png"></td>
+<td><img src="event-log-verbose.png"></td>
+<td><img src="event-log-debug.png"></td>
+</tr>
+</table>
+\endhtmlonly
+
+\latexonly
+
+\begin{figure}[H]
+
+	\centering
+
+	\begin{subfigure}[t]{0.3\textwidth}
+		\centering
+		\includegraphics[width=\textwidth]{event-log-quiet.png}
+		\caption{Quiet}
+		\label{fig:quiet}
+	\end{subfigure} ~
+    \begin{subfigure}[t]{0.3\textwidth}
+		\centering
+    	\includegraphics[width=\textwidth]{event-log-error.png}
+        \caption{Error}
+        \label{fig:error}
+	\end{subfigure} ~
+    \begin{subfigure}[t]{0.3\textwidth}
+		\centering
+    	\includegraphics[width=\textwidth]{event-log-warning.png}
+        \caption{Warning}
+        \label{fig:warning}
+    \end{subfigure}
+
+	\begin{subfigure}[t]{0.3\textwidth}
+		\centering
+		\includegraphics[width=\textwidth]{event-log-info.png}
+		\caption{Info}
+		\label{fig:Info}
+	\end{subfigure} ~
+    \begin{subfigure}[t]{0.3\textwidth}
+		\centering
+    	\includegraphics[width=\textwidth]{event-log-verbose.png}
+        \caption{Verbose}
+        \label{fig:Verbose}
+	\end{subfigure} ~
+    \begin{subfigure}[t]{0.3\textwidth}
+		\centering
+    	\includegraphics[width=\textwidth]{event-log-debug.png}
+        \caption{Debug}
+        \label{fig:Debug}
+    \end{subfigure}
+
+	\caption{Event Logging Levels}
+	\label{fig:EventLevels}
+
+\end{figure}
+
+\endlatexonly
+
+<br>
+
+The default level for logging events is "warning."
+<br>
+
+The event log show above was captured during a period of psk-reporting.  Fldigi
+was set up to monitor and report all detected signals that satisfied the
+requirements of the psk reporter web site.  The "spotted" signals were then
+automatically sent to the web site.  A complete report of the recorded events
+was obtained by a right click in the text pane.  Select-all and Save as was
+chosen.
+<br>
+
+At the Debug level you will probably see more events than you need.  You can
+select which events to suppress using the "Log sources" menu button.  It
+defaults to all enabled.
+
+\ref working_logs_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+
+*/
diff --git a/fldigi_doxygen/user_src_docs/xmlrpc-control.txt b/fldigi_doxygen/user_src_docs/xmlrpc-control.txt
new file mode 100644
index 00000000..ab50c636
--- /dev/null
+++ b/fldigi_doxygen/user_src_docs/xmlrpc-control.txt
@@ -0,0 +1,231 @@
+/**
+\page  xmlrpc_control_page  Xmlrpc Control
+
+\tableofcontents
+
+XML-RPC data is transported via simple HTTP and client implementations
+exist for most programming languages.  A Perl client that can be
+used as a control script is included in the source tar ball as
+scripts/fldigi-shell.  This control method is currently used by several
+external programs including flrig, logger32 and Xlog.
+
+The following command line arguments become available when XML-RPC support is
+compiled into fldigi, as described in the \ref install_from_source_page
+"build instructions":
+
+\verbatim
+ --xmlrpc-server-address HOSTNAME
+   Set the XML-RPC server address. The default is 127.0.0.1.
+
+ --xmlrpc-server-port PORT
+   Set the XML-RPC server port. The default is 7362.
+
+ --xmlrpc-allow REGEX
+   Allow only the methods whose names match REGEX
+
+ --xmlrpc-deny REGEX
+   Allow only the methods whose names don't match REGEX
+
+ --xmlrpc-list
+   List all available methods
+\endverbatim
+
+The --xmlrpc-deny and --xmlrpc-allow switches can be used as a simple
+access control mechanism.  REGEX specifies a POSIX extended regular expression.
+This invocation disables the methods that may cause fldigi to transmit:
+
+\verbatim
+  --xmlrpc-deny 'main\.(tx|tune|run_macro)'
+\endverbatim
+
+By default all methods are allowed.
+
+The --xmlrpc-list switch outputs the method list and exits the program.  If
+preceded by --xmlrpc-deny or --xmlrpc-allow, it shows the list of methods as
+filtered by those switches.
+
+The methods are listed below.  The three columns are method name, signature
+(return_type:argument_types), and description.  Refer to the XML-RPC
+specification for the meaning of the signature characters
+
+\latexonly \pagebreak \endlatexonly
+
+\section sub_symbol_interpretation XML Command Symbol Interpretation
+<br>
+
+<center>
+Symbol  | Interpretation
+:------:|:---:
+      n | nil
+      b | boolean
+      i | integer
+      d | double
+      s | string
+      6 | bytes
+      A | array
+      S | struct
+<br>
+</center>
+
+\section sub_xml_commands Table of XML Commands
+<br>
+
+<center>
+Method Name                | Sig (ret:arg) | Description
+:----------                |:---:|:-----------
+fldigi.list                | A:n | Returns the list of methods
+fldigi.name                | s:n | Returns the program name
+fldigi.version_struct      | S:n | Returns the program version as a struct
+fldigi.version             | s:n | Returns the program version as a string
+fldigi.name_version        | s:n | Returns the program name and version
+fldigi.config_dir          | s:n | Returns the name of the configuration directory
+fldigi.terminate           | n:i | Terminates fldigi. ``i'' is bitmask specifying data to save: 0=options; 1=log; 2=macros
+modem.get_name             | s:n | Returns the name of the current modem
+modem.get_names            | A:n | Returns all modem names
+modem.get_id               | i:n | Returns the ID of the current modem
+modem.get_max_id           | i:n | Returns the maximum modem ID number
+modem.set_by_name          | s:s | Sets the current modem. Returns old name
+modem.set_by_id            | i:i | Sets the current modem. Returns old ID
+modem.set_carrier          | i:i | Sets modem carrier. Returns old carrier
+modem.inc_carrier          | i:i | Increments the modem carrier frequency. Returns the new carrier
+modem.get_carrier          | i:n | Returns the modem carrier frequency
+modem.get_afc_search_range | i:n | Returns the modem AFC search range
+modem.set_afc_search_range | n:i | Sets the modem AFC search range. Returns the old value
+modem.inc_afc_search_range | n:i | Increments the modem AFC search range. Returns the new value
+modem.get_bandwidth        | i:n | Returns the modem bandwidth
+modem.set_bandwidth        | n:i | Sets the modem bandwidth. Returns the old value
+modem.inc_bandwidth        | n:i | Increments the modem bandwidth. Returns the new value
+modem.get_quality          | d:n | Returns the modem signal quality in the range [0:100]
+modem.search_up            | n:n | Searches upward in frequency
+modem.search_down          | n:n | Searches downward in frequency
+modem.olivia.set_bandwidth | n:i | Sets the Olivia bandwidth
+modem.olivia.get_bandwidth | i:n | Returns the Olivia bandwidth
+modem.olivia.set_tones     | n:i | Sets the Olivia tones
+modem.olivia.get_tones     | i:n | Returns the Olivia tones
+main.get_status1           | s:n | Returns the contents of the first status field (typically s/n)
+main.get_status2           | s:n | Returns the contents of the second status field
+main.get_wf_sideband       | s:n | Returns the current waterfall sideband
+main.set_wf_sideband       | n:s | Sets the waterfall sideband to USB or LSB
+main.get_frequency         | d:n | Returns the RF carrier frequency
+main.set_frequency         | d:d | Sets the RF carrier frequency. Returns the old value
+main.inc_frequency         | d:d | Increments the RF carrier frequency. Returns the new value
+main.get_afc               | b:n | Returns the AFC state
+main.set_afc               | b:b | Sets the AFC state. Returns the old state
+main.toggle_afc            | b:n | Toggles the AFC state. Returns the new state
+main.get_squelch           | b:n | Returns the squelch state
+main.set_squelch           | b:b | Sets the squelch state. Returns the old state
+main.toggle_squelch        | b:n | Toggles the squelch state. Returns the new state
+main.get_squelch_level     | d:n | Returns the squelch level
+main.set_squelch_level     | d:d | Sets the squelch level. Returns the old level
+main.inc_squelch_level     | d:d | Increments the squelch level. Returns the new level
+main.get_reverse           | b:n | Returns the Reverse Sideband state
+main.set_reverse           | b:b | Sets the Reverse Sideband state. Returns the old state
+main.toggle_reverse        | b:n | Toggles the Reverse Sideband state. Returns the new state
+main.get_lock              | b:n | Returns the Transmit Lock state
+main.set_lock              | b:b | Sets the Transmit Lock state. Returns the old state
+main.toggle_lock           | b:n | Toggles the Transmit Lock state. Returns the new state
+main.get_rsid              | b:n | Returns the RSID state
+main.set_rsid              | b:b | Sets the RSID state. Returns the old state
+main.toggle_rsid           | b:n | Toggles the RSID state. Returns the new state
+main.get_trx_status        | s:n | Returns transmit/tune/receive status
+main.rx                    | n:n | Receives
+main.tx                    | n:n | Transmits
+main.tune                  | n:n | Tunes
+main.abort                 | n:n | Aborts a transmit or tune
+main.get_trx_state         | s:n | Returns T/R state
+main.run_macro             | n:i | Runs a macro
+main.get_max_macro_id      | i:n | Returns the maximum macro ID number
+rig.set_name               | n:s | Sets the rig name for xmlrpc rig
+rig.get_name               | s:n | Returns the rig name previously set via rig.set_name
+rig.set_frequency          | d:d | Sets the RF carrier frequency. Returns the old value
+rig.set_modes              | n:A | Sets the list of available rig modes
+rig.set_mode               | n:s | Selects a mode previously added by rig.set_modes
+rig.get_modes              | A:n | Returns the list of available rig modes
+rig.get_mode               | s:n | Returns the name of the current transceiver mode
+rig.set_bandwidths         | n:A | Sets the list of available rig bandwidths
+rig.set_bandwidth          | n:s | Selects a bandwidth previously added by rig.set_bandwidths
+rig.get_bandwidth          | s:n | Returns the name of the current transceiver bandwidth
+rig.get_bandwidths         | A:n | Returns the list of available rig bandwidths
+rig.take_control           | n:n | Switches rig control to XML-RPC
+rig.release_control        | n:n | Switches rig control to previous setting
+log.get_frequency          | s:n | Returns the Frequency field contents
+log.get_time_on            | s:n | Returns the Time-On field contents
+log.get_time_off           | s:n | Returns the Time-Off field contents
+log.get_call               | s:n | Returns the Call field contents
+log.get_name               | s:n | Returns the Name field contents
+log.get_rst_in             | s:n | Returns the RST(r) field contents
+log.get_rst_out            | s:n | Returns the RST(s) field contents
+log.get_serial_number      | s:n | Returns the serial number field contents
+log.set_serial_number      | n:s | Sets the serial number field contents
+log.get_serial_number_sent | s:n | Returns the serial number (sent) field contents
+log.get_exchange           | s:n | Returns the contest exchange field contents
+log.set_exchange           | n:s | Sets the contest exchange field contents
+log.get_state              | s:n | Returns the State field contents
+log.get_province           | s:n | Returns the Province field contents
+log.get_country            | s:n | Returns the Country field contents
+log.get_qth                | s:n | Returns the QTH field contents
+log.get_band               | s:n | Returns the current band name
+log.get_notes              | s:n | Returns the Notes field contents
+log.get_locator            | s:n | Returns the Locator field contents
+log.get_az                 | s:n | Returns the AZ field contents
+log.clear                  | n:n | Clears the contents of the log fields
+log.set_call               | n:s | Sets the Call field contents
+log.set_name               | n:s | Sets the Name field contents
+log.set_qth                | n:s | Sets the QTH field contents
+log.set_locator            | n:s | Sets the Locator field contents
+text.get_rx_length         | i:n | Returns the number of characters in the RX widget
+text.get_rx                | 6:ii | Returns a range of characters (start, length) from the RX text widget
+text.clear_rx              | n:n | Clears the RX text widget
+text.add_tx                | n:s | Adds a string to the TX text widget
+text.add_tx_bytes          | n:6 | Adds a byte string to the TX text widget
+text.clear_tx              | n:n | Clears the TX text widget
+spot.get_auto              | b:n | Returns the autospotter state
+spot.set_auto              | n:b | Sets the autospotter state. Returns the old state
+spot.toggle_auto           | n:b | Toggles the autospotter state. Returns the new state
+spot.pskrep.get_count      | i:n | Returns the number of callsigns spotted in the current session
+</center>
+
+Deprecated methods:
+
+<center>
+Method Name                | Sig | Resolution
+:----------                |:---:|:-----------
+main.get_sideband          | s:n | use main.get_wf_sideband and/or rig.get_mode
+main.set_sideband          | n:s | use main.set_wf_sideband and/or rig.set_mode
+main.rsid                  | n:n | use main.{get,set,toggle}_rsid
+main.set_rig_name          | n:s | use rig.set_name
+main.set_rig_frequency     | d:d | use rig.set_frequency
+main.set_rig_modes         | n:A | use rig.set_modes
+main.set_rig_mode          | n:s | use rig.set_mode
+main.get_rig_modes         | A:n | use rig.get_modes
+main.get_rig_mode          | s:n | use rig.get_mode
+main.set_rig_bandwidths    | n:A | use rig.set_bandwidths
+main.set_rig_bandwidth     | n:s | use rig.set_bandwidth
+main.get_rig_bandwidth     | s:n | use rig.get_bandwidth
+main.get_rig_bandwidths    | n:A | use rig.get_bandwidths
+log.get_sideband           | s:n | use main.get_wf_sideband
+</center>
+
+<br>
+\section sub_minimized_window Minimized WF Window
+<br>
+
+If your external control program duplicates some of the fldigi controls
+such as the Rx and Tx pane you can run fldigi in a fully minimized
+mode.  Fldigi then only provides the controls necessary for signal
+acquisition and waterfall management.  Minimization is
+accomplished by setting the command line switch ( --wo).  The user
+interface then has this appearance:
+
+\image html UI-minimized.png "Simplified WF Window Display"
+\image latex UI-minimized.png "Simplified WF Window Display" width=5.0in
+
+The documentation for the external control program will provide additional
+information if this user interface is desired.
+
+<br>
+\ref xmlrpc_control_page "Return to Top of Page"
+<br>
+\ref main_page "Return to Main Page"
+
+*/