For Cabrillo, length of callsign does not matter
because Cabrillo uses spaces (or tabs) to deliniate
the fields. Therefore, the call (or any other
Cabrillo field) can be as long - or short - as needed.
Before anyone starts yelling about what the spec says,
I'll concede that the Cabrillo specs define specific
start and end columns. I'll then point out that CQWW
and ARRL have publicly said to ignore that
specification, just make it space delimited. Anyone
who has ever developed contest checking software that
reads Cabrillo has also learned this practicality as
well.
Tim - N9LF
--- Radiosporting Fan <radiosporting@yahoo.com> wrote:
> I'm seperating two issues: On-air legality (needing
> to
> ID in accordance with the country-rules) and logging
> (identifying that a QSO actually took place for
> contest credit) needs.
>
> As respects logging and reporting...
>
> By examining the Cabrillo format I notice that it
> allows for 10-13 bytes in the callsign field
> (depending on the event spec). How does one handle
> logging occurances when on-the-air "/" symbols take
> the callsign beyond that limit?
>
> Ev, W2EV
>
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
>
http://lists.contesting.com/mailman/listinfo/cq-contest
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|