Closed n4af closed 8 years ago
Hi Howie,
I have tried TR4W v4.43.01 and there is the following issue when exporting a Cabrillo file from a "DARC 10m contest" log:
QSO: 28000 CW 2015-11-23 2049 AB1CD 599 2 DL0TUM 599 1 C12 <-- currently it is like this QSO: 28000 CW 2015-11-23 2049 AB1CD 599 2 DL0TUM 599 1 C12 <-- rcvd DOK should be like this
What am I missing? I see no difference in those two lines (except for the comment after <—
On Dec 4, 2015, at 2:20 PM, Howie Hoyt notifications@github.com wrote:
Hi Howie,
I have tried TR4W v4.43.01 and there is the following issue when exporting a Cabrillo file from a "DARC 10m contest" log:
QSO: 28000 CW 2015-11-23 2049 AB1CD 599 2 DL0TUM 599 1 C12 <-- currently it is like this QSO: 28000 CW 2015-11-23 2049 AB1CD 599 2 DL0TUM 599 1 C12 <-- rcvd DOK should be like this
— Reply to this email directly or view it on GitHub https://github.com/n4af/TR4W/issues/25#issuecomment-162058149.
Formatting of the lines; this better illustrates QSO: 28000 CW 2015-11-23 2049 AB1CD 599 2 DL0TUM 599 1 C12 <-- currently it is like this QSO: 28000 CW 2015-11-23 2049 AB1CD 599 2 DL0TUM 599 1 C12 <-- rcvd DOK should be like this
I will need to generate a test cabrillo and check. Would be easier if they held to convention counting whitespace delineated fields RATHER than specific column numbers.
73, Howie
it is different in the original email. cut n paste into this box ruins it...
I’m a mainframe guy at my roots so fixed columns are not strange to me :) Principal Solutions Architect, ITIL®v3 Better Software Solutions, Inc. 727-437-BSS1 (727-437-2771) @BSSI_Consulting
On Dec 4, 2015, at 2:33 PM, Howie Hoyt notifications@github.com wrote:
Formatting of the lines; this better illustrates QSO: 28000 CW 2015-11-23 2049 AB1CD 599 2 DL0TUM 599 1 C12 <-- currently it is like this QSO: 28000 CW 2015-11-23 2049 AB1CD 599 2 DL0TUM 599 1 C12 <-- rcvd DOK should be like this
I will need to generate a test cabrillo and check. Would be easier if they held to convention counting whitespace delineated fields RATHER than specific column numbers.
73, Howie
— Reply to this email directly or view it on GitHub https://github.com/n4af/TR4W/issues/25#issuecomment-162061189.
DK9BN has been notified of build for testing http://tr4w.net/beta/tr4w_setup_4_43.07.exe
Positive f/b from DK9BN. Fix moved to build directory http://tr4w.net/4.43/tr4w_setup_4_43.07.exe
Hi Howie,
unfortunately we can not use white spaces for delineating since the 2nd exchange "DOK" may be present (DL stations) or may not be present (non-DL stations). This results in different word counts in all QSO lines depending on station A and B.
The same applies for other contests that support 2 exchanges such as IOTA.
It would be great if TR4W could follow Cabrillo's fixed-length column concept. Example files can be found here: http://www.darc.de/referate/dx/contest/10m/en/example-logs/
It would be great if you have a look. We get many TR4W logs (mostly from Russian stations) every year.
73 Chris DK9TN