sentences displayed with NORMAL characters in DEKKO 2
-
This day, with the RC 33 update, l have had a VERY GOOD surprise. It seems that now, french accented characters are normally displayed in DEKKO 2 and i cross my fingers, this issue https://gitlab.com/dekkoproject/dekko/issues/89 seems solved.
Some french user can confirm this ?
As there isn't yet a new update of DEKKO 2 , is somebody can explain the good surprise ? New UNITY 8 implemented in last RC UPDATE ? Something else ?Thank you developers for having solved this very annoying issue !! (a good effect of a development of something ?).
-
I not confirm !!! it appear again on my phone
-
@domubpkm have you gotten a NEW email that looks ok now, or are you looking at an old email that was definitely not ok in the past but is ok now?
-
@doniks Hi. I'm speaking about new mails after update.
Yes, i have received some new mails coming from a sender which were bad displayed before and are ok now but i'm prudent : multiple explanations..
Old mail are always displayed with bad characters but i haven't clear DEKKO 2 cache and reloaded old mails to see if they are ok now.
-
@domubpkm ok. I guess this means you are lucky that your sender has changed the encoding:)
-
I often receive mails from my colleagues, written in German with German Umlaut äöü... and written on a Microsoft OutLook and, as this is not already enough, written in HTML. Normally I would just delete mails in HTML, but as they are from my team, I have to read them.
Until today I was to lazy to check the source of the mail and the HTML coding to see if they're correct and only bad rendered by Dekko2. Next time I will investigate it.
-
The mail is mixed part:
Content-Type: multipart/alternative; boundary="_000_MN2PR06MB57092EBFFAF76FC5E5ACA32A867F0MN2PR06MB5709namp_" X-Envelope-To: guru@sisis.de Status: RO Content-Length: 1654 Lines: 55 --_000_MN2PR06MB57092EBFFAF76FC5E5ACA32A867F0MN2PR06MB5709namp_ Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable a=F6=E4 Bedeutsamkeit -- J=FCrgen --_000_MN2PR06MB57092EBFFAF76FC5E5ACA32A867F0MN2PR06MB5709namp_ Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <meta name=3D"Generator" content=3D"Microsoft Exchange Server"> <!-- converted from rtf --> <style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:= #800000 2px solid; } --></style> </head> <body> <font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;"> <div>a=F6=E4</div> <div><span style=3D"background-color:yellow;">Bedeutsamkeit</span></div> <div> </div> <div>-- </div> <div>J=FCrgen</div> ....In Dekko it the two German Umlaut 0xF6 and 0xE4 (coded in ISO 8859-1 8bit) are rendered wrong to
-
@doniks I'm not lucky !! It was a great expectation but a false hope ! NOT SOLVED !!
It is always uncertain for good display !
Maybe the problem could/should be solved after moving Oxide to Qtwebengine because the problem is linked to Oxide, see issue. Wait.Ps : Emojis should go on a low-calorie diet !