[GH-ISSUE #412] Swedish characters generates attachment #317

New issue

Closed

opened 2026-05-07 00:23:01 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

2026-05-07 00:23:01 +02:00

Owner

Originally created by @PAYload1976 on GitHub (Sep 23, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/412

When using swedish characters åäöÅÄÖ, ntfy generates an attachment.txt instead of an notice..

Originally created by @PAYload1976 on GitHub (Sep 23, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/412 When using swedish characters åäöÅÄÖ, ntfy generates an attachment.txt instead of an notice..

BreizhHardware closed this issue

2026-05-07 00:23:01 +02:00

BreizhHardware commented

2026-05-07 00:23:01 +02:00

Author

Owner

@binwiederhier commented on GitHub (Sep 23, 2022):

UTF-8 is fully supported, so this is likely a problem with your terminal or code not sending a different character set.

@binwiederhier commented on GitHub (Sep 23, 2022): UTF-8 is fully supported, so this is likely a problem with your terminal or code not sending a different character set.

BreizhHardware commented

2026-05-07 00:23:01 +02:00

Author

Owner

@PAYload1976 commented on GitHub (Sep 23, 2022):

ahh, should say it's when i use curl. not the ntfy client and this is on windows.

@PAYload1976 commented on GitHub (Sep 23, 2022): ahh, should say it's when i use curl. not the ntfy client and this is on windows.

BreizhHardware commented

2026-05-07 00:23:01 +02:00

Author

Owner

@binwiederhier commented on GitHub (Sep 23, 2022):

Charset problems are always Windows, hehe. It's probably your terminal.

@binwiederhier commented on GitHub (Sep 23, 2022): Charset problems are always Windows, hehe. It's probably your terminal.

BreizhHardware commented

2026-05-07 00:23:02 +02:00

Author

Owner

@binwiederhier commented on GitHub (Sep 30, 2022):

Hoping you got this fixed. Closing this issue for now. Let me know if the problem persists.

@binwiederhier commented on GitHub (Sep 30, 2022): Hoping you got this fixed. Closing this issue for now. Let me know if the problem persists.