[Dxbase] AXETTY and slashed zero

[Gary AL9A]

On Dec. 4 I had a QSO with UA0FAI on RTTY using AXETTY.  Everything went 
fine and the contact was logged into DXB without a problem.  However, today 
when I attempted to create a tq8 file for upload to LOTW I got an error 
message that UA0FIA (slashed zero in the call sign) was an invalid amateur 
call.  This puzzled me as I have worked Gennady before on SSB and CW and 
those contacts uploaded without a problem.

I went into the adi file itself and tried to find UA0FAI and got the message 
not found.  I then searched on the suffix FAI and found the call.  In 
looking at the info I noticed some errors in the adi file.  The length of 
the <PFX> field was 2, UA, not 3, UA0.  Also the <DXBPFX> field was 6, 
UA0FAI, the full call instead of just the 3 position prefix.  After studying 
this a bit I decided that the problem was the slashed zero in the call.  I 
edited all the slashed zeros to unslashed zeros and corrected the lengths of 
the two prefix fields and the associated data and saved the file.  This time 
when I used TQSL to create a tq8 file the process went without incident and 
the tq8 file uploaded to LOTW.

I just checked the Settings/General Setup tab in AXETTY and unchecked the 
use slashed zero font option.  The question though is why would this be a 
problem between AXETTY and DXB?  Has anyone else ever run into this before? 
BTW, I am not using a slashed font in DXB so maybe this is the problem? 
Perhaps Joe could shed some light on the subject.

73,
Gary AL9A