From c28208431ddef21670fb2af9afe07b0aa85e1547 Mon Sep 17 00:00:00 2001 From: Joe Taylor Date: Fri, 14 Dec 2018 14:13:19 -0500 Subject: [PATCH] Add to User Guide a caution about using nonstandard callsigns. --- doc/user_guide/en/make-qso.adoc | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/doc/user_guide/en/make-qso.adoc b/doc/user_guide/en/make-qso.adoc index 986583e7f..3c317477c 100644 --- a/doc/user_guide/en/make-qso.adoc +++ b/doc/user_guide/en/make-qso.adoc @@ -126,12 +126,12 @@ Either callsign (or both) may have /P appended. K1ABC W9XYZ RR73 [[COMP-CALL]] -=== Compound Callsigns +=== Nonstandard Callsigns *FT8 and MSK144* -Compound callsigns like xx/K1ABC or K1ABC/x and nonstandard callsigns -like YW18FIFA are supported for normal QSOs but not for the special +Compound callsigns like xx/K1ABC or K1ABC/x and special event +callsigns like YW18FIFA are supported for normal QSOs but not for contest-style messages. Model QSOs look something like this: CQ PJ4/K1ABC @@ -159,6 +159,11 @@ Except for the special cases involving /P or /R used in VHF contesting, _WSJT-X {VERSION_MAJOR}.{VERSION_MINOR}_ offers no support for two nonstandard callsigns to work each other. +TIP: Using a nonstandard callsign has definite costs. It restricts +the types of information that can be included in a message. It +prevents including your locator in standard messages, which +necessarily impairs the usefulness of tools like PSK Reporter. + *JT4, JT9, JT65, and QRA64* In the 72-bit modes, compound callsigns are handled in one of two