For along time third party software has been using the old ARRL format
named <callsign>.log to read CT logs.
Rather than break all that software, I used <callsign>.txt as Cabrillo
output because the Cabrillo spec (http://www.kkn.net/~trey/cabrillo)
recommends, but does not require the .LOG extension.
After many requests, in CT969 I changed the output file name to the
standard <callsign>.log. Of course I forgot to delete the code (ten
lines later) that writes the old format for ARRL contests. This
*overwites* the Cabrillo output.
I am removing the old ARRL format code, so I expect to take some heat
when other conversion software breaks.
- Ken
-----Original Message-----
From: ct-user-admin@contesting.com [mailto:ct-user-admin@contesting.com]
On Behalf Of N7MAL
Sent: Sunday, December 09, 2001 11:58 AM
To: ct-user@contesting.com
Subject: [ct-user] CABRILLO
Can someone explain, preferably AD1C or K1EA, why CT generates 2 similar
files, .LOG & .TXT ? It seems to my simple mind all this confusion about
which file to send could be eliminated if only one file were generated.
Perhaps Trey, N5KO, who fathered CABRILLO, could come up with a new,
dedicated, file extension .DUM. We would all know then all .DUM files go
to
contest committees.
(P.S. I forwarded a copy of this to my good friend N5KO)
MAL N7MAL
BULLHEAD CITY, AZ
http://www.ctaz.com/~suzyq/N7mal.htm
_______________________________________________
ct-user mailing list
ct-user@contesting.com
ct-user-request@contesting.com Subject=unsubscribe to unsubscribe
http://lists.contesting.com/mailman/listinfo/ct-user
|