~mil/sxmo-tickets#112: 
Incoming texts with unicode content don't display

Incoming SMS messages don't display correctly in the text log when they contain non-ascii/unicode characters, only "--" is displayed. This is also the case after the suggested fix in #92 and #80

Status
RESOLVED CLOSED
Submitter
~proycon
Assigned to
No-one
Submitted
4 years ago
Updated
1 year, 5 months ago
Labels
bug

~proycon 4 years ago

Ok, I found the cause after a lot of debugging, I'm taking it upstream to modemmanager:

[1604350804.030308] [modem0] decoding SMS text with 34 elements [1604350804.046190] [modem0] converting SMS part text from UTF-16BE to UTF-8... [1604350804.061879] [modem0] couldn't convert SMS part contents from UTF-16BE to UTF-8: not decoding any text [1604350804.080185] [modem0] correctly parsed PDU (0)

~franck_stauffer 3 years ago

Do you have any news about this one?

~stacyharper 3 years ago

ModemManager reworked the decoding part and this is in master. It should be available in modemmanager-1.18.0 (next release).

I am trying to build it localy to test it without success (because I sucks I hope).

The issue is https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/274

~franck_stauffer 3 years ago

Okay ty, I will keep an eye on it ^^

~stacyharper 3 years ago

I officialy confirm that the future version of ModemManager will fix this issue :D

~bsduck 1 year, 9 months ago

This is still broken in postmarketOS v23.06. Accented characters in incoming messages are rendered properly in the notification popup, but show up as numeric codes in the conversation log. For example "è" is displayed as "\303\250", so "caffè" ends up as "caff\303\250" in the log file. This only applies to received messages, messages I sent myself are displayed correctly.

~bsduck 1 year, 9 months ago

... actually it's a rather recent regression. I tried the latest Arch Linux sxmo build available on https://github.com/dreemurrs-embedded/Pine64-Arch/releases (released in February) and things work as expected there. Then I upgraded the system (sxmo-utils was upgraded from 1.12 to 1.14) and new messages are now broken like on postmarketOS. Meanwhile, messages that were already in the conversation log before the upgrade are still displayed properly.

~bsduck 1 year, 7 months ago

Has anyone an idea what could be causing this regression? I'm surprised to be alone to bring this up, it's a real dealbreaker for me, and basically the only thing that prevents me from using sxmo on a daily basis.

~earboxer 1 year, 7 months ago

~bsduck: ~stacyharper fixed it in 2c0c56df. (which hasn't yet been tagged). You could apply that patch locally, or run master to get the latest fixes.

~bsduck 1 year, 7 months ago

That's great news! I can confirm that it works. Thank you very much :)

~stacyharper REPORTED CLOSED 1 year, 5 months ago

I close this so :)

Register here or Log in to comment, or comment via email.