On Nov 3, 2011, at 6:51 AM, Ed wrote: > On 11/02/2011 10:53 PM, Dick Kriss wrote: >> The price is right for the recently added HamQTH option under the >> Callsign DB/Subscriber; however, there seems to be an issue with with >> where data is added to fldigi and the fldigi Logbook file >> >> For example, I worked E51Z (South Cook Island) on RTTY today and when >> I use the HamQTH lookup option, the data was not imported correct. I >> had the same issue with ZF2OE. For some reason the Country never goes >> to correct box. USA calls seem to work better than DX calls. The >> full name and address for US calls are displayed in the Notes that is >> helpful. >> >> I am not sure if this is a HamQTH or fldigi issue? >> >> Dick AA5VU > > I would say it depends on how often the information is updated. And > seeing as these 2 calls are less than a month old could be the problem. > If I understand it correctly this is a 1 man operation. > > Plus if you look under View > Countries and enter the prefix it will > display the country which you can copy/paste.
QSL… I also use the the sh/heading call on the AR-Cluster. Both fldigi and AR-Cluster use the current cty.dat data. > Ed W3NR Ed, The issue is not about updates to the HamQTH database for new calls. The issue is how the data is parsed (not sure this is the correct word) to or by fldigi for DX calls. The HamQTH works pretty good for US calls. Dick AA5VU _______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
