As you can see, all special characters are replaced with weird stuff and
is replaced with =3D.
I’ve read in my searches that = is a special character for the
quoted-printable enconding so I’ve tried to replace the encoding with
base64
but when I did it, my email was just a little string of weird characters
(little string = ~20-30 characters)
Subject: =?UTF-8?Q?R=C3=A9ponse_=C3=A0_un_de_vos_commentaires_sur_Syrinxoon?=
Tuts
Mime-Version: 1.0
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
R=C3=A9ponse =C3=A0 un de vos commentaires sur Syrinxoon Tuts<=
This actually looks normal, given that the Content-Transfer encoding
is quoted-printable.
=C3=A9 is quoted printable speak for the pair of bytes 0xC3, 0xA9,
which is the utf8 sequence for acute. Because = is special in this
encoding scheme, any literal = has to be encoded as =3D. Is your mail
client not displaying this properly?
I did not have tried to display it in my mails client because I’m still in
development.
You think the client will not be disturbed by this?
I don’t believe so, but you should definitely try that since it’s what
your users will be doing. By the way, the mailcatcher gem is pretty
good for viewing emails sent in development)
Fred
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.