[aprssig] Yaesu FREQ OBJECT workaround

[Bob Bruninga]

The workaround for the FTM-350 not properly parsing the QSY in an APRS FREQ
OBJECT is suggested as follows:

1) Continune FREQ OBJECTS as before with Tnnn oXXX Rxxm... in the object
text. (if oXXX is omitted, then radios will use standard offsets).

2) For the FTM-350, also include the FFF.FFFMHz in the DIGIPEATERS beacon
text after the PHG data.  For example for WB4APR-1 digipeater, I might use:

PHG1234/147.105MHz T107 +060 R20m AARC
PHG1234/146.76 MHz T156 -060 R34m BRATS

OPEN ISSUE:  Does the FTM-350 properly decode the FREQUENCY when the "/"
separator is used after the PHG data???  Do the Kenwoods?  If not, do they
work with a SPACE separator?  If not, then we have to run them together.

This should work fine as a workaround since the FTM-350 has a wider display
and even if the DIGIPEATER CALLSIGN is used, the radio will still display
the FREQ on the front panel too.

The only thing we lose in the original DIGI text was "W2, SSn-N " which by
now, everyone should understand to limit their hops to 2 or less

Bob, WB4aPR