Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ct\-user\]\s+VHF\s+Contest\s+Cabrillo\s+Format\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ct\-user\]\s+VHF\s+Contest\s+Cabrillo\s+Format\s*$/: 4 ]

Total 4 documents matching your query.

1. [ct-user] VHF Contest Cabrillo Format (score: 1): Author: Philip Barber" <pfbarber@worldnet.att.net (Philip Barber); Date: Mon, 18 Jun 2001 23:36:44 -0400; For ARRL VHF contest I noticed the CT (9.57 and 9.63) Cabrillo file does not follow strict format as obtained via ARRL link. For example: Sent grid starts in CT column 42 vs. spec column 49. Rcvd cal; /archives//html/CT-User/2001-06/msg00066.html (7,739 bytes)
2. [ct-user] VHF Contest Cabrillo Format (score: 1): Author: Jim Reisert AD1C" <jjreisert@alum.mit.edu (Jim Reisert AD1C); Date: Tue, 19 Jun 2001 00:14:19 -0400; Are the fields in the correct order? Most "smart" parsing routines only care that fields are separated by spaces (or some other common delimter), the actual position within a line is usually not impo; /archives//html/CT-User/2001-06/msg00067.html (7,916 bytes)
3. [ct-user] VHF Contest Cabrillo Format (score: 1): Author: Philip Barber" <pfbarber@worldnet.att.net (Philip Barber); Date: Tue, 19 Jun 2001 23:56:13 -0400; Jim, I personally agree with your comment and others that relative order and at least one space delimiter should be sufficient. But I would hate to throw away a weekend of hard work because I didn't; /archives//html/CT-User/2001-06/msg00070.html (8,742 bytes)
4. [ct-user] VHF Contest Cabrillo Format (score: 1): Author: alsopb <alsopb@gloryroad.net> (alsopb); Date: Thu, 21 Jun 2001 11:18:40 +0000; While we are on topic of smart parsing, when will CT have the ability to parse the qso exchange so that one doesn't have to enter it in specific fields? Just type the complete exchange, in any order,; /archives//html/CT-User/2001-06/msg00075.html (8,487 bytes)

Current List: 1 - 4
Page: [1]