Al W6HGF Thanks for the heads up. Yes, there is a problem as my Nov 2009 shows two QSO's with VP2V/DL7VO that should have been logged as VP2V/DL7VOG. I just exported the QSO's to my logging program and added the G and will correct my upload to LoTW.
As a test I logged CE0Y/SM6CUK and like you you indicated fldigi-3.13BC.dmg cuts off the K. Hopefully, Dave will be able to increase the 10 character limit to 11 characters. 73 Dick AA5VU > Date: Wed, 25 Nov 2009 18:44:09 -0500 > From: Al Danis <w6hgf at cox.net> > Subject: Callsign Length problem > To: fldigi-alpha at lists.berlios.de > > Just worked CE0Y/SM6CUK But can not get his call into the logbook > correctly. I can enter it into the callsign blank but it cuts off the > last letter when it goes into the log. There seems to be a length > limit in the transfer. I think this call is extreme in length, but as I > look back I see I worked VP2V/DL7VOG and had the same problem. Maybe we > need to make the callsign field one additional character in length? > > Al W6HGF -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen shot 2009-11-26 at 8.53.26 AM.png Type: application/octet-stream Size: 80158 bytes Desc: not available Url : https://lists.berlios.de/pipermail/fldigi-alpha/attachments/20091126/d398fa2a/attachment-0001.obj
