VE5SF stated:
>TRlog is also faulty (or at least was faulty - have not seen all the
>most recent reports) in the manner in which columns are organized as
>it does not produce a Cabrillo report that meets the description for
>RAC - columns are misplaced. While these items sound trivial and
>picky, they do not become so when you are on the receiving end of
>contest logs and have to check each one for correct use of
>designated multiplier descriptions and column organization in the
>Cabrillo report (One quickly learns that in practical delivery,
>there is no such thing as adherence to Cabrillo standard - at least
>for the RAC reports). These minor issues quickly multiply the time
>it takes to process all the logs, even using automated means -
>unless that is TRlog users are ready to accept significant score reductions !
RAC is not in the Cabrillo spec - there is no defined
QSO template, nor contest name tag. It is therefore
impossible to make compliant Cabrillo for any RAC
contest.
RAC seems to have made up its own specification
& called it RAC Cabrillo.
I would suggest observed problems with adherence
are due to RAC's failure to abide with a very basic
principle of standards - sticking with them & not
making up your own & then expecting everyone
else to conform to that.
Imagine if a meter according to RAC was not the
same length as a meter is everywhere else in the
world (was that not one of the reasons for the
metric system to begin with? ;^).
That TR does not make compliant Cabrillo for
some defined & supported contests Tree maintains
is perfectly fine - but "the robot can deal with it"
or the like does not change the fact that there is a
specification & the output differs from that
specification.
Specifications used to mean something before
we had computers. ;^(
73, VR2BrettGraham
_______________________________________________
Trlog mailing list
Trlog@contesting.com
http://lists.contesting.com/mailman/listinfo/trlog
|