CudaText: [Wayland Qt5 build] Pasting non-basic ASCII chars from some apps to CudaText doesn't work properly

I use openSUSE Tumbleweed (bleeding edge rolling release) with Wayland.

If I copy a string containing only chars from basic ASCII table it works, like letters and numbers. But if I copy a symbol which is not part of the table, the pasted content is not correctly represented in CudaText depending on the app it was copied from. Examples:

• “Euro: €”, copying this string from Firefox (Wayland by MOZ_ENABLE_WAYLAND=1) and pasting to CudaText produces “Euro: \u20ac”.
• “coração” copying this from Firefox Wayland to CudaText produces “cora??o”.

CudaText document is using UTF-8 encoding.

Depending on the origin app, it works. For instance, it’s not an issue if I copy from Kate to CudaText. But I never had such issue copying from Firefox to anything else, that’s why I believe it’s CudaText/Lararus fault.

I use CudaText Qt5 because I use KDE Plasma.

If I start CudaText as a XWayland window instead of Wayland by running QT_QPA_PLATFORM=xcb ./cudatext then I can’t reproduce the issue but others appear, for instance my compose keys don’t work in XWayland. Supposing CudaText supports Wayland, I shouldn’t use XWayland anyway.

Edit: I just tried CudaText Gtk2 and results are the same as running CudaText Qt5 as a XWayland window: pasting from Firefox works but has other issues e.g. my compose keys don’t work. Firefox, for instance, is also a GTK app and my compose keys work fine in it.