Glad to hear that it worked! Current Tlf version supports specifying
Cabrillo header value through CABRILLO-* configuration parameters.
This avoids the need to enter all the values each time an export is made.
Have a look at share/logcfg.dat in the repo.
73,
Zoli
Tom:
Doh! Yes, that was it exactly.
--
--Alan (AB1XW)
--
Alan Dove, Ph.D.
alan.d...@gmail.com
917.273.0544
> Hi Alan,
>
> during preparation of the cabrillo file (:write) there is a first
> question about the exchange you gave. What did you enter here?
>
> It should only be the sp
Hi Alan,
during preparation of the cabrillo file (:write) there is a first
question about the exchange you gave. What did you enter here?
It should only be the specific part without the report - that would be
'MA' in your case.
Please check.
73, de Tom
Am Mon, 21 Feb 2022
18:37:02 -0500 schri
Zoli:
It's TLF 1.4.1 (I downloaded the tarball and just followed the
instructions on the site).
> Is this the expected format?
> QSO: 14038 CW 2022-02-19 1732 AB1XW599 MAHA8VV599 KW
>
Yes, that was what the ARRL bot wanted.
--
--Alan (AB1XW)
--
Alan Dove, Ph.D.
alan.d..
Hi Alan,
What Tlf version are you using?
Is this the expected format?
QSO: 14038 CW 2022-02-19 1732 AB1XW599 MAHA8VV599 KW
73,
Zoli
On Mon, Feb 21, 2022 at 09:29:58PM +, Alan Dove wrote:
> Hey, folks:
>
> I spoke too soon, here's one more issue. In trying to submit my log for
>
Hey, folks:
I spoke too soon, here's one more issue. In trying to submit my log for
ARRL DX CW, the bot threw it back in my face with a bunch of errors. It
seems TLF has inserted an extra column of RSTs, for example:
QSO: 14038 CW 2022-02-19 1732 AB1XW 599 599 MA
HA8VV 599 KW
It
