[Dx4win] Strange errors in ADIF export

[Jim Reisert AD1C]

On 12/28/2009 7:08 AM, Mel wrote:

> I may be wrong about this, but I don't believe DX4Win uses the numeric
> entity code.
>
> It's problematical anyway because it is NOT standard... there are 2
> lists, ADIF and ARRL DXCC. The trouble is ARRL only assigns the code
> after the country is recognized for DXCC. ADIF assigns the code as soon
> as possible. For some reason known only to themselves, ARRL DOESN'T
> follow the ADIF standard. As a result, the 2 lists are not exactly the same!

I would love to see an actual example of what you mean ("ARRL DOESN'T 
follow the ADIF standard").  I do not believe what you say is true.

> I believe the ADIF.PMP that Jim maintains assigns the ADIF codes during
> export.

ADIF.PMP is used for import/export. DX4WIN uses the primary prefix 
internally, i.e. KH8/S for Swains, FK/C for Chesterfield.  When a QSO is 
exported, DX4WIN converts that primary prefix, via the ADIF.PMP file, to 
a numerical country code (per the ADIF specification).  It works the 
same way on import, converting the numerical code to a primary prefix 
that DX4WIN recognizes.  That is why the DX4WIN.CTY and ADIF.PMP files 
must BOTH be updated at the same time, when there is a primary prefix 
change (i.e. a new DXCC entity is added).

I also find it hard to believe that DX4WIN is writing wrong numerical 
codes to the ADIF file on export.  I will ask Dave for a copy of his log 
to try to verify this.

73 - Jim AD1C

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us