long subject with utf8 char beaks the email in outlook

Hi,

When you send an email with a "long" object and non ascii chars, the mail isn't properly displayed as html (and the alt text being hidden), but you get the ascii display of the full email (ugly

How to reproduce/ create new email with the subject
"nouvelle procédure de demande de traduction"

You will receive an email with the subject troncated:
"nouvelle procédure de demande de tradu"

and the body of the mail:

=?utf-8?Q?ction?=
Content-Type: multipart/alternative;
boundary="=_e30189fdc8cd08d939f5fa151dd97e68"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

It should be noted that it works fine on gmail. The source of the mail is :

Subject: =?utf-8?Q?nouvelle=20proc=C3=A9dure=20de=20demande=20de=20tradu?=
=?utf-8?Q?ction?=
Content-Type: multipart/alternative;
boundary="=_7b1fbc117a0721abe246408ed2af0598"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
...

When I send this subject from outlook, it doesn't split it in several lines. However, if I copy it several time it does, and it does it this way:

Subject: =?iso-8859-1?Q?nouvelle_proc=E9dure_de_demande_de_traduction_nouvelle_p?=
=?iso-8859-1?Q?roc=E9dure_de_demande_de_traduction_nouvelle_proc=E9dure_d?=
=?iso-8859-1?Q?e_demande_de_traduction_nouvelle_proc=E9dure_de_demande_de?=
=?iso-8859-1?Q?traduction_nouvelle_proc=E9dure_de_demande_de_traduction?=
=?iso-8859-1?Q?nouvelle_proc=E9dure_de_demande_de_tr?=

ie. it seems that they insert a tab at the start of the second and subsequent lines of the subject.

Should we do the same ? Is civicrm using a lib for the mail and should I report it upstream ?

X+

P.S Why is microsoft using by default latin 1 on the latest version of outlook even so utf8 has been a standard since forever is a vibrant testament of their dynamism in adopting better technologies, and that they seems to have a personal goal of pissing me off (might be a collateral damage in all honesty)