[Ham-Mac] Issue with fldigi ADIF Export Format

[Dick Kriss]

On Sep 17, 2012, at 1:12AM the Digest Number 2348 contained:

> > You are in control ... Do you build fldigi from source? If yes, then 
> > you can change the ADIF export code to satisfy your requirement.
> > 
> > The ADIF specification allows any program to use non standard tags.
> > 
> > Dave
> >
> 
> No, I don't build from source and have no knowledge to do so. You mentioned back in 2009 that the proposed 2.2.3 ADIF standard lists both stx_string and srx_string and said you'd change the MYXCHG and XCHG1 export fields to comply with the proposal. 
> 
> I understand that the specification allows non standard tags but surely it would be better if everyone uses the accepted norms?
> 
> FWIW, I've also emailed Andrew (author of Aether) to see if he can manage the alternate import fields.
> 
> If not, I'll just carry on editing the files. 
> 
> 73
> Keith, G6NHU

Like Keith, G6NJU, I do not compile fldigi from source.  I did run some tests and confirmed the issue with the fldigi non standard tags Keith reported. The issue seems to be within fldigi rather than in Aether. Changing from nonstandard to standard tags does not sound that complicated but I am not a programmer. There may some other reason fldigi uses nonstandard tags for use with other platforms and logging applicaitons. The workaround for OS X users is to use a text editor to find and replace the tags on fldigi exported .adif files.

Dick, AA5VU