diff --git a/CMakeLists.txt b/CMakeLists.txt
index a40ca3eee..19e72db17 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -1222,7 +1222,8 @@ install (TARGETS udp_daemon message_aggregator
   BUNDLE DESTINATION ${WSJT_BIN_DESTINATION} COMPONENT runtime
   )
 
-install (TARGETS jt9 jt65code qra64code qra64sim jt9code jt4code wsprd 
+install (TARGETS jt9 jt65code qra64code qra64sim jt9code jt4code
+  msk144code wsprd
   RUNTIME DESTINATION ${WSJT_BIN_DESTINATION} COMPONENT runtime
   BUNDLE DESTINATION ${WSJT_BIN_DESTINATION} COMPONENT runtime
   )
diff --git a/doc/user_guide/en/install-mac.adoc b/doc/user_guide/en/install-mac.adoc
index d2d5d6ca8..54a35d28c 100644
--- a/doc/user_guide/en/install-mac.adoc
+++ b/doc/user_guide/en/install-mac.adoc
@@ -1,7 +1,7 @@
 // These instructions are up-to-date for WSJT-X v1.4
 
 *OS X 10.7* and later: Download the file {osx} to your desktop,
-double-click on it and consult its +ReadMe+ file for important
+double-click on it and consult its `ReadMe` file for important
 installation notes.  
 
 If you have already installed a previous version, you can retain it by
diff --git a/doc/user_guide/en/logging.adoc b/doc/user_guide/en/logging.adoc
index 699e50c5b..ae657d23a 100644
--- a/doc/user_guide/en/logging.adoc
+++ b/doc/user_guide/en/logging.adoc
@@ -1,5 +1,5 @@
 A basic logging facility in _WSJT-X_ saves QSO information to files
-named +wsjtx.log+ (in comma-separated text format) and +wsjtx_log.adi+
+named `wsjtx.log` (in comma-separated text format) and `wsjtx_log.adi`
 (in standard ADIF format).  These files can be imported directly into
 other programs, for example spreadsheets and popular logging programs.
 As described in the <<INSTALL,Installation>> and <<PLATFORM,Platform
@@ -18,7 +18,7 @@ this option is checked _WSJT-X_ appends some additional information to
 all CQ messages displayed in the _Band Activity_ window.  The name of
 the DXCC entity is shown, abbreviated if necessary.  Your "`worked
 before`" status for this callsign (according to log file
-+wsjtx_log.adi+) is flagged with a single character and a change of
+`wsjtx_log.adi`) is flagged with a single character and a change of
 background color, as follows:
 
 [horizontal]
@@ -30,16 +30,16 @@ this station
 In this respect the program does not distinguish between modes, but it
 does differentiate between bands.
 
-_WSJT-X_ includes a built-in +cty.dat+ file containing DXCC prefix
+_WSJT-X_ includes a built-in `cty.dat` file containing DXCC prefix
 information.  Updated files can be downloaded from the {cty_dat} web
-site when required.  If an updated +cty.dat+ is present in the logs
+site when required.  If an updated `cty.dat` is present in the logs
 folder and readable, it will be used in preference to the built-in
 one.
 
-The log file +wsjtx_log.adi+ is updated whenever you log a QSO from
+The log file `wsjtx_log.adi` is updated whenever you log a QSO from
 _WSJT-X_.  (Keep in mind that if you erase this file you will lose all
 "`worked before`" information.)  You can append or overwrite the
-+wsjtx_log.adi+ file by exporting your QSO history as an ADIF file
+`wsjtx_log.adi` file by exporting your QSO history as an ADIF file
 from another logging program.  Turning *Show DXCC entity and worked
 before status* off and then on again will cause _WSJT-X_ to re-read
 the log file.  Very large log files may cause _WSJT-X_ to slow down
diff --git a/doc/user_guide/en/make-qso.adoc b/doc/user_guide/en/make-qso.adoc
index b9d527d45..f70fadd15 100644
--- a/doc/user_guide/en/make-qso.adoc
+++ b/doc/user_guide/en/make-qso.adoc
@@ -10,7 +10,7 @@ recommended basic QSO goes something like this:
  CQ K1ABC FN42                          #K1ABC calls CQ
                    K1ABC G0XYZ IO91     #G0XYZ answers
  G0XYZ K1ABC –19                        #K1ABC sends report
-                   K1ABC G0XYZ R–22     #G0XYZ sends R+report
+                   K1ABC G0XYZ R-22     #G0XYZ sends R+report
  G0XYZ K1ABC RRR                        #K1ABC sends RRR
                    K1ABC G0XYZ 73       #G0XYZ sends 73
 
diff --git a/doc/user_guide/en/protocols.adoc b/doc/user_guide/en/protocols.adoc
index 0670e0ab8..eac7c7932 100644
--- a/doc/user_guide/en/protocols.adoc
+++ b/doc/user_guide/en/protocols.adoc
@@ -25,19 +25,25 @@ which is less than 2^15^ = 32,768; so a grid locator requires 15 bits.
 
 Some 6 million of the possible 28-bit values are not needed for
 callsigns.  A few of these slots have been assigned to special message
-components such as CQ, CQ DX, DE, and QRZ. CQ may be followed by three
+components such as `CQ`, `DE`, and `QRZ`. `CQ` may be followed by three
 digits to indicate a desired callback frequency. (If K1ABC transmits
-on a standard calling frequency, say 50.280, and sends "`CQ 290 K1ABC
-FN42`", it means that s/he will listen on 50.290 and respond there to
-any replies.) A numerical signal report of the form "`–NN`" or
-"`R–NN`" can be sent in place of a grid locator.  (As originally
-defined, numerical signal reports were required to fall between -01
+on a standard calling frequency, say 50.280, and sends `CQ 290 K1ABC
+FN42`, it means that s/he will listen on 50.290 and respond there to
+any replies.) A numerical signal report of the form `–nn` or
+`R–nn` can be sent in place of a grid locator.  (As originally
+defined, numerical signal reports `nn` were required to fall between -01
 and -30 dB.  Recent program versions accommodate reports between
 -50 and +49 dB.) A country prefix or portable suffix may be
 attached to one of the callsigns.  When this feature is used the
 additional information is sent in place of the grid locator or by
 encoding additional information into some of the 6 million available
-slots mentioned above.  
+slots mentioned above.
+
+Finally, the message compression algorithm supports messages starting
+with `CQ AA` through `CQ ZZ`.  Such messages are encoded by
+sending `E9AA` through `E9ZZ` in place of the first callsign of a
+standard message.  Upon reception these calls are converted back to
+the form `CQ AA` through `CQ ZZ`.
 
 To be useful on channels with low signal-to-noise ratio, this kind of
 lossless message compression requires use of a strong forward error
@@ -220,14 +226,14 @@ pattern of four symbols at tone numbers 0, 1, 3, and 2, followed by
 two symbols with tone number corresponding to (message length) and
 (message length + 5), and finally 18 symbols conveying the user's
 message, sent repeatedly character by character.  The message always
-starts with +@+, the beginning-of-message symbol, which is not
+starts with `@`, the beginning-of-message symbol, which is not
 displayed to the user.  The sync pattern and message-length indicator
 have a fixed repetition period, recurring every 24 symbols.  Message
 information occurs periodically within the 18 symbol positions set
 aside for its use, repeating at its own natural length.
 
-For example, consider the user message +CQ WA9XYZ+.  Including the
-beginning-of-message symbol +@+, the message is 10 characters long.
+For example, consider the user message `CQ WA9XYZ`.  Including the
+beginning-of-message symbol `@`, the message is 10 characters long.
 Using the character sequence displayed above to indicate tone numbers,
 the transmitted message will therefore start out as shown in the first
 line below:
@@ -239,7 +245,7 @@ line below:
 
 Note that the first six symbols (four for sync, two for message
 length) repeat every 24 symbols.  Within the 18 information-carrying
-symbols in each 24, the user message +@CQ WA9XYZ+ repeats at its own
+symbols in each 24, the user message `@CQ WA9XYZ` repeats at its own
 natural length, 10 characters.  The resulting sequence is extended as
 many times as will fit into a Tx sequence.
 
diff --git a/doc/user_guide/en/settings-audio.adoc b/doc/user_guide/en/settings-audio.adoc
index 60f0f4e80..1b142d707 100644
--- a/doc/user_guide/en/settings-audio.adoc
+++ b/doc/user_guide/en/settings-audio.adoc
@@ -24,10 +24,10 @@ such a device, be sure to set the mic level in the Recording Device
 Properties to 0 dB.
 
 - _Save Directory_: _WSJT-X_ can save its received audio sequences as
-+.wav+ files.  A default directory for these files is provided; you
+`.wav` files.  A default directory for these files is provided; you
 can select another location if desired.
 
-- _AzEl Directory_: A file named +azel.dat+ will appear in the
+- _AzEl Directory_: A file named `azel.dat` will appear in the
 specified directory.  The file contains information usable by another
 program for automatic tracking of the Sun or Moon, as well as
 calculated Doppler shift for the specified EME path.  The file is
diff --git a/doc/user_guide/en/support.adoc b/doc/user_guide/en/support.adoc
index 68048d817..055d79286 100644
--- a/doc/user_guide/en/support.adoc
+++ b/doc/user_guide/en/support.adoc
@@ -4,7 +4,8 @@ The best source of help in setting up your station or configuring
 _WSJT-X_ is the {wsjt_yahoo_group} at email address
 wsjtgroup@yahoogroups.com.  The chances are good that someone with
 similar interests and equipment has already solved your problem and
-will be happy to help.
+will be happy to help.  To post messages here you will need to join
+the group.
 
 === Bug Reports
 
@@ -12,7 +13,8 @@ One of your responsibilities as a _WSJT-X_ user is to help the
 volunteer programmers to make the program better.  Bugs may be
 reported to {wsjt_yahoo_group} (email address
 wsjtgroup@yahoogroups.com) or the WSJT Developers list
-(wsjt-devel@lists.sourceforge.net).  To be useful, bug reports should
+(wsjt-devel@lists.sourceforge.net).  Again, you will need to join the
+group or subscribe to the list.  To be useful, bug reports should
 include at least the following information:
 
 - Program version
diff --git a/doc/user_guide/en/tutorial-example1.adoc b/doc/user_guide/en/tutorial-example1.adoc
index bee64ca5e..843fc877d 100644
--- a/doc/user_guide/en/tutorial-example1.adoc
+++ b/doc/user_guide/en/tutorial-example1.adoc
@@ -26,11 +26,11 @@ Tx frequency.
 Seven JT9 signals are present in the example file, all decodable.
 When this file was recorded KF4RWA was finishing a QSO with K1JT.
 Since the green marker was placed at his audio frequency, 1224 Hz, his
-message "`K1JT KF4RWA 73`" is decoded first and appears in the *Rx
+message `K1JT KF4RWA 73` is decoded first and appears in the *Rx
 Frequency* window. The *Band Activity* window shows this message plus
-all decodes at other frequencies.  By default lines containing CQ are
-highlighted in green, and lines with *My Call* (in this case K1JT) in
-red.
+all decodes at other frequencies.  By default lines containing `CQ`
+are highlighted in green, and lines with *My Call* (in this case K1JT)
+in red.
 
 [[X13]]
 .Decoding Controls
@@ -61,7 +61,7 @@ of the main window is selected.
 *Setup* menu, *Enable Tx* would be activated and a transmission would
 start automatically at the proper time.
 
-- Double-click on the decoded message "`K1JT N5KDV EM41`",
+- Double-click on the decoded message `K1JT N5KDV EM41`,
 highlighted in red.  Results will be similar to those in the
 previous step, except the Tx frequency (red marker) is not
 moved.  Such messages are usually in response to your own CQ, or from
@@ -73,8 +73,8 @@ line you can cause both Tx and Rx frequencies to be moved.  This
 behavior can also be forced by checking *Lock Tx=Rx*.
 
 - Double-click on the message from KF4RWA in either window. He is
-sending "`73`" to K1JT, signifying that the QSO is over.  Most likely
-you want to send 73 to him, so the message "`KF4RWA K1JT 73`" is
+sending `73` to K1JT, signifying that the QSO is over.  Most likely
+you want to send 73 to him, so the message `KF4RWA K1JT 73` is
 automatically generated and selected for your next transmission.
 (Alternatively, you might choose to send a free-text message or to
 call CQ again.)
diff --git a/doc/user_guide/en/tutorial-example2.adoc b/doc/user_guide/en/tutorial-example2.adoc
index 6b7f06ef1..1ea518bd3 100644
--- a/doc/user_guide/en/tutorial-example2.adoc
+++ b/doc/user_guide/en/tutorial-example2.adoc
@@ -79,17 +79,17 @@ JT9 message from IZ0MIT:
 |===
 
 - Scroll back in the *Band Activity* window and double-click on the
-message +CQ DL7ACA JO40+. The program will set *Tx mode* to JT65 and Tx
+message `CQ DL7ACA JO40`. The program will set *Tx mode* to JT65 and Tx
 and Rx frequencies to that of DL7ACA, 975 Hz.  If you had checked
 *Double-click on call sets Tx Enable* on the *Setup* menu, the program
 would configure itself to start a QSO with DL7ACA.
 
-- Double-click on the decoded JT65 message +CQ TA4A KM37+.  The program
+- Double-click on the decoded JT65 message `CQ TA4A KM37`.  The program
 will set Tx mode to JT9 and the Rx and Tx frequencies to 3567 Hz.  The
 program is now configured properly for a JT9 QSO with TA4A.
 
 .Reopen the First Sample File:
-- Select *File | Open* and navigate to +...\save\samples\130418_1742.wav+.
+- Select *File | Open* and navigate to `...\save\samples\130418_1742.wav`.
 
 Taking full advantage of the wide-band, dual-mode capability of
 _WSJT-X_ requires a receiver bandwidth of at least 4 kHz.  These
diff --git a/doc/user_guide/en/utilities.adoc b/doc/user_guide/en/utilities.adoc
index 337939af0..c076e26df 100644
--- a/doc/user_guide/en/utilities.adoc
+++ b/doc/user_guide/en/utilities.adoc
@@ -1,13 +1,11 @@
-// Status=review
-
-The _WSJT-X_ packages include program *+rigctl-wsjtx[.exe]+*, which
+The _WSJT-X_ packages include program *`rigctl-wsjtx[.exe]`*, which
 can be used to send CAT sequences to a rig from the command line, or
-from a batch file or shell script; and program *+rigctld-wsjtx[.exe]+*,
+from a batch file or shell script; and program *`rigctld-wsjtx[.exe]`*,
 which allows other compatible applications to share a CAT connection
 to a rig.  These program versions include the latest Hamlib rig
 drivers -- the same ones used by _WSJT-X_ itself.
 
-Additional utility programs *+jt4code+*, *+jt9code+*, and *+jt65code+*
+Additional utility programs *`jt4code`*, *`jt9code`*, and *`jt65code`*
 let you explore the conversion of user-level messages into channel
 symbols or "`tone numbers,`" and back again.  These programs can be
 useful to someone designing a beacon generator, for understanding the
@@ -15,7 +13,7 @@ permissible structure of transmitted messages, and for studying
 behavior of the error-control codes.
 
 Channel-symbol values for JT4 run from 0 to 3.  The total number of
-symbols in a transmitted message is 206.  To run +jt4code+, enter the
+symbols in a transmitted message is 206.  To run `jt4code`, enter the
 program name followed by a JT4 message enclosed in quotes.  In Windows
 the command and program output might look like this:
 
@@ -48,13 +46,13 @@ quotes:
   8 7 0 6 0 1 8 3 3 7 8 1 1 2 4 5 8 1 5 2 0 0 8 6 0 5 8 5 1 0
   5 8 7 7 2 0 4 6 6 6 7 6 0 1 8 8 5 7 2 5 1 5 0 4 0
 
-For the corresponding program *+jt65code+* only the
+For the corresponding program *`jt65code`* only the
 information-carrying channel symbols are shown, and the symbol values
 range from 0 to 63.  Sync symbols lie two tone intervals below data
 tone 0, and the sequential locations of sync symbols are described in
 the <<JT65PRO,JT65 Protocol>> section of this Guide.
 
-A typical execution of +jt65code+ is shown below.  The program
+A typical execution of `jt65code` is shown below.  The program
 displays the packed message of 72 bits, shown here as 12 six-bit
 symbol values, followed by the channel symbols:
 
@@ -73,9 +71,9 @@ symbol values, followed by the channel symbols:
 For an illustration of the power of the strong error-control coding in
 JT9 and JT65, try looking at the channel symbols after changing a
 single character in the message.  For example, change the grid locator
-from +FN42+ to +FN43+ in the JT65 message:
+from FN42 to FN43 in the JT65 message:
 
- C:\Users\joe\wsjt\wsjtx_install>jt65code "G0XYZ K1ABC FN43"
+ C:\WSJTX> jt65code "G0XYZ K1ABC FN43"
       Message                 Decoded                Err? Type
  ----------------------------------------------------------------------
   1.  G0XYZ K1ABC FN43        G0XYZ K1ABC FN43            1:    Std Msg
@@ -91,4 +89,58 @@ You will discover that every possible JT65 message differs from every
 other possible JT65 message in at least 52 of the 63
 information-carrying channel symbols.
 
+Execution of any of these utility programs with "-t" as the only
+command-line argument produces examples of all supported message
+types.  For example, using `jt65code -t`:
 
+ C:\WSJTX> jt65code -t
+ 
+      Message                 Decoded                Err? Type
+ --------------------------------------------------------------------------
+  1.  CQ WB9XYZ EN34          CQ WB9XYZ EN34              1:    Std Msg
+  2.  CQ DX WB9XYZ EN34       CQ DX WB9XYZ EN34           1:    Std Msg
+  3.  QRZ WB9XYZ EN34         QRZ WB9XYZ EN34             1:    Std Msg
+  4.  KA1ABC WB9XYZ EN34      KA1ABC WB9XYZ EN34          1:    Std Msg
+  5.  KA1ABC WB9XYZ RO        KA1ABC WB9XYZ RO            1:    Std Msg
+  6.  KA1ABC WB9XYZ -21       KA1ABC WB9XYZ -21           1:    Std Msg
+  7.  KA1ABC WB9XYZ R-19      KA1ABC WB9XYZ R-19          1:    Std Msg
+  8.  KA1ABC WB9XYZ RRR       KA1ABC WB9XYZ RRR           1:    Std Msg
+  9.  KA1ABC WB9XYZ 73        KA1ABC WB9XYZ 73            1:    Std Msg
+ 10.  KA1ABC WB9XYZ           KA1ABC WB9XYZ               1:    Std Msg
+ 11.  CQ 000 WB9XYZ EN34      CQ 000 WB9XYZ EN34          1:    Std Msg
+ 12.  CQ 999 WB9XYZ EN34      CQ 999 WB9XYZ EN34          1:    Std Msg
+ 13.  CQ EU WB9XYZ EN34       CQ EU WB9XYZ EN34           1:    Std Msg
+ 14.  CQ WY WB9XYZ EN34       CQ WY WB9XYZ EN34           1:    Std Msg
+ 15.  ZL/KA1ABC WB9XYZ        ZL/KA1ABC WB9XYZ            2:    Type 1 pfx
+ 16.  KA1ABC ZL/WB9XYZ        KA1ABC ZL/WB9XYZ            2:    Type 1 pfx
+ 17.  KA1ABC/4 WB9XYZ         KA1ABC/4 WB9XYZ             3:    Type 1 sfx
+ 18.  KA1ABC WB9XYZ/4         KA1ABC WB9XYZ/4             3:    Type 1 sfx
+ 19.  CQ ZL4/KA1ABC           CQ ZL4/KA1ABC               4:    Type 2 pfx
+ 20.  DE ZL4/KA1ABC           DE ZL4/KA1ABC               4:    Type 2 pfx
+ 21.  QRZ ZL4/KA1ABC          QRZ ZL4/KA1ABC              4:    Type 2 pfx
+ 22.  CQ WB9XYZ/VE4           CQ WB9XYZ/VE4               5:    Type 2 sfx
+ 23.  HELLO WORLD             HELLO WORLD                 6:    Free text
+ 24.  ZL4/KA1ABC 73           ZL4/KA1ABC 73               6:    Free text
+ 25.  KA1ABC XL/WB9XYZ        KA1ABC XL/WB9            *  6:    Free text
+ 26.  KA1ABC WB9XYZ/W4        KA1ABC WB9XYZ            *  6:    Free text
+ 27.  123456789ABCDEFGH       123456789ABCD            *  6:    Free text
+ 28.  KA1ABC WB9XYZ EN34 OOO  KA1ABC WB9XYZ EN34 OOO      1:    Std Msg
+ 29.  KA1ABC WB9XYZ OOO       KA1ABC WB9XYZ OOO           1:    Std Msg
+ 30.  RO                      RO                         -1:    Shorthand
+ 31.  RRR                     RRR                        -1:    Shorthand
+ 32.  73                      73                         -1:    Shorthand
+
+MSK144 uses a binary channel code, so transmitted symbols have the value
+0 or 1.  Even numbered symbols (index starting at 0) are transmitted on
+the I (in-phase) channel, odd numbered symbols on the Q (quadrature)
+channel.  A typical execution of `msk144code` is shown below.
+
+ C:\WSJTX> msk144code "K1ABC W9XYZ EN37"
+
+      Message                 Decoded                Err? Type
+ --------------------------------------------------------------------------
+  1.  K1ABC W9XYZ EN37        K1ABC W9XYZ EN37            1: Std Msg
+
+ Channel symbols (72 per line):
+ 110000100011001101010101001000111111001001001100110010011100001001000000
+ 010110001011101111001010111011001100110101011000111101100010111100100011
diff --git a/doc/user_guide/en/wsjtx-main.adoc b/doc/user_guide/en/wsjtx-main.adoc
index 3d497df2a..650810fdd 100644
--- a/doc/user_guide/en/wsjtx-main.adoc
+++ b/doc/user_guide/en/wsjtx-main.adoc
@@ -205,6 +205,9 @@ include::protocols.adoc[]
 == Astronomical Data
 include::astro_data.adoc[]
 
+[[UTIL]]
+== Utility Programs
+include::utilities.adoc[]
 
 ////
 [[TXRX]]
@@ -215,9 +218,6 @@ include::implementation.adoc[]
 == Troubleshooting
 To be added (?) ...
 
-[[UTIL]]
-== Utility Programs
-include::utilities.adoc[]
 ////
 
 [[SUPPORT]]
diff --git a/doc/user_guide/en/wspr.adoc b/doc/user_guide/en/wspr.adoc
index 976c6c29e..00365e35b 100644
--- a/doc/user_guide/en/wspr.adoc
+++ b/doc/user_guide/en/wspr.adoc
@@ -63,13 +63,13 @@ tuner (ATU) to tune a multi-band antenna to the newly selected band.
 require other switching besides retuning your radio. To make this
 possible in an automated way, whenever _WSJT-X_ executes a successful
 band-change command to a CAT-controlled radio, it looks for a file
-named +user_hardware.bat+, +user_hardware.cmd+, +user_hardware.exe+,
-or +user_hardware+ in the working directory. If one of these is found,
+named `user_hardware.bat`, `user_hardware.cmd`, `user_hardware.exe`,
+or `user_hardware` in the working directory. If one of these is found,
 _WSJT-X_ tries to execute the command
 
  user_hardware nnn 
 
-- In the above command +nnn+ is the band-designation wavelength in
+- In the above command `nnn` is the band-designation wavelength in
 meters. You must write your own program, script, or batch file to do
 the necessary switching at your station.
 
diff --git a/lib/msk144code.f90 b/lib/msk144code.f90
index 6ccada7e0..576bc321a 100644
--- a/lib/msk144code.f90
+++ b/lib/msk144code.f90
@@ -48,7 +48,7 @@ program msk144code
      if(itype.eq.4) msgtype="Type 2 prefix"
      if(itype.eq.5) msgtype="Type 2 suffix"
      if(itype.eq.6) msgtype="Free text"
-     if(itype.eq.7) msgtype="Hashed callsigns"
+     if(itype.eq.7) msgtype="Hashed calls"
 
      bad=" "
      if(msgsent.ne.msg) bad="*"
@@ -60,7 +60,7 @@ program msk144code
      n=144
      if(msg(1:1).eq."<") n=40
      write(*,1030) i4tone(1:n)
-1030 format(/'Channel symbols:'/(72i1))
+1030 format(/'Channel symbols (72 per line):'/(72i1))
   endif
 
 999 end program msk144code