Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not accept FT8 QSOs if comment contains special characters #16

Open
DB4SCW opened this issue Oct 25, 2024 · 1 comment
Open

Does not accept FT8 QSOs if comment contains special characters #16

DB4SCW opened this issue Oct 25, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@DB4SCW
Copy link

DB4SCW commented Oct 25, 2024

Waveloggate does not accept any ADIF packets if there are special characters (like ä, ö, ü) in the comment of the QSO.

To reproduce, log a FT8 contact via WSJT-X and put a special character in the comment, like "Hütte".

Waveloggate will not accept the QSO and will not display any warning or error whatsoever.

@int2001 int2001 added the bug Something isn't working label Nov 6, 2024
@int2001 int2001 self-assigned this Nov 6, 2024
@int2001
Copy link
Contributor

int2001 commented Nov 9, 2024

Hi @DB4SCW - the problem is not really a waveloggate problem. it is located in the ADIF-Standard and the used ADIF-Library.
At ADIF there's a battle ongoing regarding UTF8 or only ASCII.

Besides that the issue has to be fixed at https://github.com/tcort/tcadif

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants