field population tricks (fldigi word delimiters)

David, K9DWR

There was a discussion a little while ago about what exchange info to
put in what field and some of the complications associated with getting
the text from the RX window to your log (handling weird characters
around callsigns, or odd separators between 070 and the actual number,
for example).

I wanted to make folks aware of one thing in fldigi that can help this
(that likely exists in other programs, too).

In the Fldigi configuration, under the "UI" Tab, there is a "Log" tab
("Logging" if you are using an older version of fldigi). There is an
"Rx Text" entry that has a field called "Word delimiters." What
delimiters do is they define where a word begins and ends. Why this is
important is because it tells the software where to start and stop when
grabbing text to populate the log info.

An example in the online documentation

describes it like this:

"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. Clicking on the 599 NJ and
Bozo would treat each as a separate word."

Where this gets interesting is when things like @ or # get used. A
common case seen during TDW was 070#1604. If you want just the number
(and not the 070), you could add # to the list of characters that define
where a "word" starts or stops, making it easier to just click-and-go.

If your software can't handle < or > around callsigns, this would be
another example of characters to add to the word delimiter list to help
pull out the callsign.

David, K9DWR
#1604 LONP #255