This is a discussion group for developers involved with the import or export of data formatted according to the ADIF standard for Amateur Radio Software.
Membership in the group is limited to developers of logging software, web sites, amateur radio applications, and others who have a vested interest in the ADIF standard and who will actively participate in its definition, maintenance, and promotion.
Membership is by approval only, and you should be prepared to e-mail the moderator a description of why you qualify to be a member of this group, i.e. the software package or web site you represent.
I'm sure we can make a XML definition very quickly - not a big complex definition, just a series of records using ADIF field names and field formats. I take
The lack of backward compatibility is what troubles me about the proposal for an ENCODING field. I agree that ADIF's restriction to ASCII in string fields is
Thinking about this a bit more, maybe one solution that can be offered is XML - that would be my preference. Failing that let the user know what's going on
... I don't know.... If a logger receives an UTF-8 adif file and does not how to handle it will bounce a lot of errors... If a logger receives an ISO-8859-1