Bill, Thanks for the minor correction here (and I knew that) ... but there is something that I am alerting everyone to and its your last statement:
* By using free text messages other information can be passed, limited only by the skill and patience of the QSO partners. The Australian Foundation-class licence is an introductory licence – and some say that it is at a lower technical level of competence than the US Technician’s class licence (and I am not entering into that argument as this is the wrong place). You in the UK have an equivalent that I believe that this class of licence is modelled off. The word here that you raise is “skill” .... many will not have it nor should be assumed to have it. [ And some of us “old ones” with over 10000 confirmed QSO’s also screw up as I was not watching the RR/73 loop that I was in while composing this while also Tx’ing on 40m ] Therefore as both of us are saying patience (and stomping on our own arrogant minor subset) is required. So ... if skill is required at the lowest of levels then this issue of complexity should be addressed – with priority – to take the skill out of the equation..... Perhaps addressing such issues in a standardised, transparent fashion should be looked at as core to the next major release? 73 and keep up the good work ! Steve I VK3VM / VK3SIR Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 ________________________________ From: Bill Somerville <g4...@classdesign.com> Sent: Thursday, September 26, 2019 10:23:46 PM To: wsjt-devel@lists.sourceforge.net <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] Note for Developers and Users On 26/09/2019 13:03, Stephen Ireland wrote: This will have developmental consequences as the prime "Call CQ" response works with 13 characters i.e. CQ VK3SIR QF11 ... And many have already observed that Australian F-Calls will not be able to send CQ with their maidenhead locator. Steve, for clarification: CQ VK3SIR QF11 is 14 characters including the embedded spaces. A limitation on including a grid square in various standard format messages is dependent on the callsign being a standard format as defined by the WSJT-X modes. In the case of FT4/FT8/MSK144 standard call shall contain a one- or two-character prefix, at least one of which shall be a letter, followed by a digit and a suffix of one to three letters. Many other non-standard callsigns may be used with some restrictions, one of those restrictions is that non-essential QSO information like grid squares may not be included in standard messages. There are a couple special exceptions that allow /P and /R prefixes on standard callsigns without these limitations. Despite these restrictions, these modes make it possible for holders of non-standard callsigns to at least have straightforward QSOs with standard callsign holders. By using free text messages other information can be passed, limited only by the skill and patience of the QSO partners. 73 Bill G4WJS.
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
