We have moved to a new Sailfish OS Forum. Please start new discussions there.

UTF-8 problem with email list view

asked 2013-12-27 23:12:51 +0300

micko gravatar image

updated 2014-01-03 17:10:28 +0300

TeHeR gravatar image

I'm having problems with sending emails, but that problem might be on the server and not Jolla.

While testing the mail sending, I noticed there was a familiar looking UTF-8 problem with the 2-line abstract. Nothing serious and I can live with this, but it might be worse with other languages.

image description

edit retag flag offensive close delete


Retag: add "encoding".

TeHeR ( 2014-01-03 17:10:53 +0300 )edit

Maybe a font problem not supporting all utf-8 characters? There is a problem with this utf-8 subject line:

Subject: =?UTF-8?Q?Noch_=E2=9E=8C=E2=9E=8E=E2=9E=8C_Tage_in_2014.

That are 3 special utf-8 characters for the 3 digits '3' '5' '3' in a circle. Wrong symbols will be displayed instead unable to read it.

In another mail the utf-8 heart symbol "E2=99=A5" in the subject could be displayed correctly in the mail list view.

axaq ( 2014-01-20 02:34:10 +0300 )edit

I have the same problem with character "ä" on sender-field: =?utf-8?Q?Riihim=C3=A4ki?=

maake ( 2014-02-18 20:21:29 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2018-09-18 13:25:57 +0300

updated 2018-09-18 17:43:17 +0300

Edit 2018-09-18: after discussion with maintainer of messaging framework, the fix has been moved to nemo-qml-plugin-email and accepted. Thanks to @pvuorela for discussions and review. When landing in SFOS, the previous emails will still display wrong encoding, but newly written ones should be ok.

I've found the root issue in nemo-qml-plugin-email. It is using the following code path when building an email:

 QMailMessageContentType type;
 type.setType("text/plain; charset=UTF-8");

instead of writing:

QMailMessageContentType type;
type.addParameter("charset", "UTF-8");

Then, the generation of the preview is failing because the charset is not properly registered and it is falling back on ISO-8859-1.

Currently, I'm proposing a fix in messaging framework to ensure that the syntax used in nemo-qml-plugin-email can work also. Depending on review comment there, I may send a patch to nemo-qml-plugin-email instead to solve the issue there.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

1 follower


Asked: 2013-12-27 23:12:51 +0300

Seen: 225 times

Last updated: Sep 18 '18