Log4OM

I guess the problem with special chars like & and # hasn't been fixed for QRZ uploads in 1.24.0.
They still won't upload to QRZ. Previous emails about this show that it is not QRZ's fault. The chars have to be escaped.

I've made some changes on that, but i haven't had enough time to extensively test the encoding.
This seems working but not everytime.

The ones I notice most is & and # in comments and address.
I have my QRZ account completely synced to my local logbook (that took several hours).
So I have to edit those with apartment and road #'s and "eQSL & LOTW" entries are most common.
This is the list of all reserved chars though that any free text field should encode
http://www.web2generators.com/html-base ... nd-decoder

I just tested on with & in it and see this:
This%20&That%20

So the & is not being escaped.

i'm doing some tests right now...

I found another place that either needs the support file changed or special chars allowed for.

The country name....
I worked 9Z4A last night -- "Trinidad & Tobago". Could not get it to upload to QRZ for anything (I removed the comments and address data). Had to manually add it on QRZ.

Basically sounds like all fields should be escaped if there's ANY possibility of special chars.

73
Mike W9MDB

Looks like it's all fixed in 1.25.0 now.
The problems from before all behave now.

"LOTW & EQSL" -- very common in comments now upload OK...had to remove the & before.
"#" in addresses -- for apartment #'s is OK now.
"&" in country names like "Trinidad & Tobago" now OK.

Thanks guys....
73
Mike W9MDB