thanks a lot for this explanation, this has made it
clear for me. I had erroneously assumed that one could mix
structured content and free text in one message, now I understand why it
must be either one or the other. Still need to aquire some of that
73 and best wishes,
PS In my opinion a software bug cannot be
embarassing, it's more a positive indication of progress - which
we've seen a lot of lately!
Sent: Thursday, November 29, 2012 8:57 PM
Subject: Re: LF: WSJT-X v0.5 r2786 - exit after message
fixed the strange bug you reported. It will be OK in the next
release. I should have responded also to the question you
> ... I'm often unsure about what is a predefined token and
> freetext. For example, I ran into the 13 character limit
> editing a report into into something like "DK7FC DF6NM R
"DK7FC DF6NM R+14" (with no space between "R" and the following
and optional sign) is a properly structured JT9 message. It
sent in compressed form: 28 bits for each callsign, 15 bits for the
grid-or-report fiels, and one bit to indicate it's a structured message:
28+28+15+1 = 72 bits in all.
"DK7FC DF6NM R +14" is not a properly
formatted structured JT9 message,
because of the space between "R" and
"+". It is therefore truncated to
13 characters and sent as free
These kinds of issues are what is meant in the (temporary and
WSJT-X User's Guide when it says things like "This document assumes
you already have some familiarity with WSJT."
We'll get a
properly complete User's Guide in shape, before too long.
In the meantime,
if you have questions please ask!
-- 73, Joe, K1JT