Error in displaying zero in call sign

[MikleBas]

Hello!
There has been a floating bug for a long time - the display of zero in the call signal, accordingly, search in databases (qrz.com for example) does not work correctly
example https://www.qrz.com/db/RC%C3%98AT
and here is the real answer https://www.qrz.com/db/RC0AT
what does the zero sign look like in the log program, look at the screenshot, if I did not formulate the problem correctly

[MikleBas]

UPD
and DX-cluster stopped working (at all)
I get it from https://dxc.jo30.de/dxcache

[int2001]

hmm. interesting. and https://dxc.jo30.de/dxcache/spots returns nothing?

[MikleBas]

If you use a browser to follow the link, the data opens

[github-actions[bot]]

Uh oh! @MikleBas, the image you shared is missing helpful alt text. Check #2493 (reply in thread).

Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.

Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.

[MikleBas]

Is there any other public address like this?
I would test the work and post the results here

[int2001]

Cluster is working. Those is the data of the Cluster.
idk why CL isn't showing it.

[AndreasK79]

Hello! There has been a floating bug for a long time - the display of zero in the call signal, accordingly, search in databases (qrz.com for example) does not work correctly example https://www.qrz.com/db/RC%C3%98AT and here is the real answer https://www.qrz.com/db/RC0AT what does the zero sign look like in the log program, look at the screenshot, if I did not formulate the problem correctly

Hi. I can't reproduce this problem. Entering RC0AT links correctly here. The display uses Ø, but in the db, it is saved as RC0AT:

Are you logging with Ø or 0?

[dg9vh]

In my opinion callsigns with a Zero in it should be logged with 0 - the Ø is for display purpose and differ between 0 and O. Therefore we had a conversation in the displayed output that converts 0 to Ø but only on display. in Database and ADIF and so on there would be delivered a 0.

[AndreasK79]

I agree, and to my knowledge, that is how Cloudlog behaves now.

[magicbug]

Correct!

[MikleBas]

Okay, let's reproduce the error
let's go to the website https://tnxqso.com/#/stations
copy RØMR/P from there
paste it into our window in CloudLog
Let's save the QSO
As a result we get

1. qrz.com does not know such a call sign due to the differences between 0 and 0
2. will be written to the log with an incorrect zero
3. I don’t know what it will end up in the adinf file

[github-actions[bot]]

Uh oh! @MikleBas, the image you shared is missing helpful alt text. Check #2493 (comment).

Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.

Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.

[github-actions[bot]]

Uh oh! @MikleBas, the image you shared is missing helpful alt text. Check #2493 (comment).

Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.

Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.

[phl0]

Then you entered the callsign RØMR/P with slashed zero instead of 0. This is causing an error. Maybe we need the reverse replacement on callsing input to convert Ø to 0.

[MikleBas]

I just copied it from that site as is
By the way, when DXcluster was working, it seems to me that call signs from there were also displayed with such a zero (or not?, it doesn’t work for me now, I can’t check)

[dg9vh]

So you paste the Ø instead of 0? There is the problem!

So we may need some input-filter that converts Ø to 0 on database-queries.

[MikleBas]

Yes exactly

[phl0]

With #2495 we have a fix in dev branch now. Please test and report.