Thanks Kim,
My question was more related to the SIG string content.
I know by experience that a typo or even an invalid reference in the SIG_INFO field will cause upload abort, very right and necessary.
My doubts came considering a log with multiple Awards correspondents, thus giving in the raw station log many different strings(i.e. the awards names) in the SIG field, with corresponding non WWFF references listed in the related SIG_INFO .
Today I received such a log, and so tried to upload it “raw” that is, with all these different strings (awards names) in the SIG field, and not only the two fields for WWFF , as we usually did “cleaning” the raw logs received.
What I have seen, is that the upload checker does is task very fine: it ignores all SIG fields not containing the “WWFF” string and the related SIG_INFO field; and upload only these having the right string “WWFF” into the SIG field.
But, more important and the answer to my question, it does NOT abort if there are other SIG fields containing different strings not WWFF.
So, that soft does it very fine as it does: it uploads only the SIG and related subfields if these are for WWFF . Chapeau!
That was what I was looking for; I write it here, maybe it’s useful information for other hams, too .
Thanks Kim for your help!
73 44, Augusto I2JJR / HB9TZA
HBFF Staff