Message-ID: <12F714DEBAEC4DE68DB6650920998C09@White>
From: "Markus Vester" <markusvester@aol.com>
To: <rsgb_lf_group@blacksheep.org>
References: <50B76F28.6040103@princeton.edu> <50B7728C.9050004@iup.uni-heidelberg.de> <7F8CB52A336F4056AC2FC13D710A97A8@White> <B2A2F9300CF345408212B0DFE92BDE11@White> <50B7BE29.2000108@princeton.edu>
Date: Fri, 30 Nov 2012 00:11:01 +0100
MIME-Version: 1.0
Importance: Normal
X-AOL-SCOLL-URL_COUNT: 0  
X-Spam-Score: -0.4 (/)
X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 Content preview:  Joe, 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 familiarity ;-) [...] 
 Content analysis details:   (-0.4 points, 5.0 required)
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
                             trust
                             [205.188.91.97 listed in list.dnswl.org]
  0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                             (markusvester[at]aol.com)
 -0.0 SPF_PASS               SPF: sender matches SPF record
 -0.4 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
  0.0 HTML_MESSAGE           BODY: HTML included in message
  0.0 T_DKIM_INVALID         DKIM-Signature header exists but is not valid
X-Scan-Signature: 13abe497adcf17a4e25c5e2a2ff79111
Subject: Re: LF: WSJT-X v0.5 r2786 -  exit after message editing
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0049_01CDCE8F.2E7076E0"
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com
X-Spam-Level: 
X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE,
	MISSING_OUTLOOK_NAME autolearn=no version=2.63
X-SA-Exim-Scanned: Yes
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
X-Listname: rsgb_lf_group
X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
x-aol-global-disposition: G
X-AOL-SCOLL-AUTHENTICATION: mtain-ma03.r1000.mx.aol.com ; domain : mx.aol.com DKIM : pass
x-aol-sid: 3039ac1d600b50b7ebfb34e1
X-AOL-IP: 195.171.43.25
X-AOL-SPF: domain : blacksheep.org SPF : none


Dies ist eine mehrteilige Nachricht im MIME-Format.

------=_NextPart_000_0049_01CDCE8F.2E7076E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Joe,

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 familiarity ;-)

73 and best wishes,
Markus (DF6NM)

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!



From: Joe Taylor=20
Sent: Thursday, November 29, 2012 8:57 PM
To: rsgb_lf_group@blacksheep.org=20
Subject: Re: LF: WSJT-X v0.5 r2786 - exit after message editing


Hi Markus,

I have fixed the strange bug you reported.  It will be OK in the next=20
release.  I should have responded also to the question you posed:

> ... I'm often unsure about what is a predefined token and what is
> freetext. For example, I ran into the 13 character limit after
> editing a report into into something like "DK7FC DF6NM R +14".

"DK7FC DF6NM R+14" (with no space between "R" and the following number=20
and optional sign) is a properly structured JT9 message.  It will be=20
sent in compressed form: 28 bits for each callsign, 15 bits for the=20
grid-or-report fiels, and one bit to indicate it's a structured message: =

28+28+15+1 =3D 72 bits in all.

"DK7FC DF6NM R +14" is not a properly formatted structured JT9 message,=20
because of the space between "R" and "+".  It is therefore truncated to=20
13 characters and sent as free text.

These kinds of issues are what is meant in the (temporary and brief)=20
WSJT-X User's Guide when it says things like "This document assumes that =

you already have some familiarity with WSJT."

We'll get a properly complete User's Guide in shape, before too long.=20
In the meantime, if you have questions please ask!

-- 73, Joe, K1JT


------=_NextPart_000_0049_01CDCE8F.2E7076E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3Diso-8859-1>
<META content=3D"MSHTML 6.00.6000.17114" name=3DGENERATOR></HEAD>
<BODY id=3DMailContainerBody=20
style=3D"PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-TOP: 15px"=20
bgColor=3D#ffffff leftMargin=3D0 topMargin=3D0 CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3DArial size=3D2>Joe,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>thanks a lot for this explanation, this =
has made it=20
clear for me. I had erroneously&nbsp;assumed that&nbsp;one could mix=20
structured&nbsp;content and free text in one message, now I understand =
why it=20
must be either one or the other. Still need to&nbsp;aquire some of that=20
familiarity ;-)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>73 and best wishes,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Markus (DF6NM)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>PS&nbsp;In my opinion a =
software&nbsp;bug cannot be=20
embarassing,&nbsp;it's more a positive indication of progress =
-&nbsp;which=20
we've&nbsp;seen a lot of lately!</FONT></DIV>
<DIV style=3D"FONT: 10pt Tahoma"><FONT face=3DArial></FONT><FONT=20
face=3DArial></FONT><FONT face=3DArial></FONT><FONT =
face=3DArial></FONT>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><FONT face=3DArial></FONT><FONT face=3DArial></FONT><FONT=20
face=3DArial></FONT><FONT face=3DArial></FONT><FONT =
face=3DArial></FONT><FONT=20
face=3DArial></FONT><FONT face=3DArial></FONT><FONT =
face=3DArial></FONT><FONT=20
face=3DArial></FONT><FONT face=3DArial></FONT><FONT =
face=3DArial></FONT><FONT=20
face=3DArial></FONT><FONT face=3DArial></FONT><FONT =
face=3DArial></FONT><FONT=20
face=3DArial></FONT><FONT face=3DArial></FONT><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A =
title=3Djoe@Princeton.EDU=20
href=3D"mailto:joe@Princeton.EDU">Joe Taylor</A> </DIV>
<DIV><B>Sent:</B> Thursday, November 29, 2012 8:57 PM</DIV>
<DIV><B>To:</B> <A title=3Drsgb_lf_group@blacksheep.org=20
href=3D"mailto:rsgb_lf_group@blacksheep.org">rsgb_lf_group@blacksheep.org=
</A>=20
</DIV>
<DIV><B>Subject:</B> Re: LF: WSJT-X v0.5 r2786 - exit after message=20
editing</DIV></DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><FONT=20
face=3DArial size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT =
face=3DArial=20
size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2></FONT><FONT face=3DArial size=3D2></FONT><BR></DIV>Hi =
Markus,<BR><BR>I have=20
fixed the strange bug you reported.&nbsp; It will be OK in the next=20
<BR>release.&nbsp; I should have responded also to the question you=20
posed:<BR><BR>&gt; ... I'm often unsure about what is a predefined token =
and=20
what is<BR>&gt; freetext. For example, I ran into the 13 character limit =

after<BR>&gt; editing a report into into something like "DK7FC DF6NM R=20
+14".<BR><BR>"DK7FC DF6NM R+14" (with no space between "R" and the =
following=20
number <BR>and optional sign) is a properly structured JT9 =
message.&nbsp; It=20
will be <BR>sent in compressed form: 28 bits for each callsign, 15 bits =
for the=20
<BR>grid-or-report fiels, and one bit to indicate it's a structured =
message:=20
<BR>28+28+15+1 =3D 72 bits in all.<BR><BR>"DK7FC DF6NM R +14" is not a =
properly=20
formatted structured JT9 message, <BR>because of the space between "R" =
and=20
"+".&nbsp; It is therefore truncated to <BR>13 characters and sent as =
free=20
text.<BR><BR>These kinds of issues are what is meant in the (temporary =
and=20
brief) <BR>WSJT-X User's Guide when it says things like "This document =
assumes=20
that <BR>you already have some familiarity with WSJT."<BR><BR>We'll get =
a=20
properly complete User's Guide in shape, before too long. <BR>In the =
meantime,=20
if you have questions please ask!<BR><BR>-- 73, Joe, =
K1JT<BR><BR></BODY></HTML>

------=_NextPart_000_0049_01CDCE8F.2E7076E0--