Hi Andy,
thanks for your quick analysis. I come to the same conclusion.
It seems that contest makers are very creative at defining new formats
for their cabrillo entries.
I am not sure if there will be an easy solution from TLF's point of
view. Maybe some sort of template or so. I put it on the TODO list.
In meantime I would suggest playing around with AWK. It is still
possible to simple parse the logfile, extract the needed informations
and put in a file with very few lines of awk code (maybe even with one
line). Add the cabrillo header to that file and you are ready.
I know that is one more tool to learn, but awk has proven useful in
some cases for me, so it seems no waste of time :). Fell free to ask
for help if you get difficulties with that.
73, de Tom.
Am Thu, 09 Jun 2011 21:46:31
+0100 schrieb Andy Summers g4kno.m...@gmail.com:
Hi Tom,
There's no rush. I have until next year, hi!
I had a quick look at the Cabrillo standard myself just now and can
see why it truncated to 6 chars. I was using the WPX rules and the
Cabrillo output for WPX is 6 chars only.
Unfortunately, there is no standard length for the exchange field and
different sponsors may require different length fields to deal with
their particular flavour of contest. The RSGB RoPoCo is an example of
this; the postcode field being specified as 11 chars long. The only
way to reliably deal with this is to have individual set-ups for
every contest supported (and I'm guessing RoPoCo won't be one of
them!). As a matter of fact, the field lengths are often wrong for
other RSGB contest entries I make, but the Robot accepts them fine. I
imagine this is because it's looking for the space delimiters rather
than assuming fixed field widths. If this were true for all Robots I
guess increasing the field width wouldn't make any difference, but I
don't think that's necessarily a good idea.
So, not sure how to tackle this. Maybe a rule file switch?
73 Andy, G4KNO.
On 09/06/11 20:16, Thomas Beierlein wrote:
Hi Andy,
thanks for the bug report.
Am Wed, 08 Jun 2011 20:48:07 +0100
schrieb Andy Summersg4kno.m...@gmail.com:
Bug report:
TLF can handle this, although some post processing of the Cabrillo
is necessary. There's enough space in the received exchange field,
but when the Cabrillo is generated it truncates that field to 6
chars. How about making the Cabrillo default to the displayed
field width?
I will have a look into it (but not before next week). If Cabrillo
standard allows it, I will see to implement your suggestion.
73, de Tom DL1JBE.
--
Do what is needful!
Ursula LeGuin: Earthsea
--
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel
