Html entities in emails make them unreadable

Averell

It is annoying that issue #537 https://github.com/flarum/core/issues/537 has not yet been attributed a milestone, so I am looking for some help on the forum.

The question is :
Emails sent when you follow a discussion are defined with the following mime type :
Content-Type: text/plain; charset=utf-8

But the content is written in html. The result is that if a user wrote the following message :
Le problème de la ligne téléphonique est réparé
The email writes this message like that :
---
Le problème de la ligne téléphonique a ét&eacut=
e; réparé,
---
which is perfectly unreadable.

The technical details are explained in the issue on Github.

@luceos wrote : Mailer class automatically generates a text only variant if needed.

I would like to know how.
It may not solve the problem if this text only variant is not encoded in utf8.

It is a really annoying issue for most languages other than English.

Dominion

Averell It is annoying that issue #537 https://github.com/flarum/core/issues/537 has not yet been attributed a milestone, so I am looking for some help on the forum.

We've just added a new FAQ item that should help explain this situation.

The frustration experienced by users waiting for an issue to be fixed is understandable; I'm still waiting for a few of my pet issues to get fixed too! But we need to understand that the devs have a lot to do, and will have to prioritize their efforts in order to get the job done.

Since Flarum's still at the beta stage, the priority is to get the code complete and stable. Bugs that don't greatly impede the beta testing process will naturally take a back seat to more important matters. That's precisely why the devs have advised against using Flarum in production.

Flarum is open source, and development is driven by the efforts of people who aim for a great product, from vision to code. We are all here to make Flarum great, but to make our efforts count, we should stay focused on the goal, and keep our feedback constructive.

We're glad you took the time to investigate the issue; your remarks will certainly be useful when it comes time to implement a fix. If you feel you can contribute a solution, you're welcome to chat about your ideas via Gitter ... or submit a PR, if you like. Once an issue has been reported, however, it might be best to confine discussion to the issue tracker; adding a new forum thread to the mix may lead to confusion.

Averell

@Dominion I understand, thanks.

I just wanted to add something important : I was really surprised by the unalterable kindness @luceos , you and others, always showed in answering questions already answered ten times, or dealing with guys like me who are often outside the right path. Really a beautiful example and testimony ! I really appreciated. Grazie mille !