Something in the last few days of cauldron activity has resulted in TB displaying the combination "fl" as a strange single-character glyph that resembles a backwards epsilon. My impression was that this affected other apps as well, but when I specifically searched for examples, I could only find them in TB. I'll attach a screenshot. Reproducible: Steps to Reproduce:
Created attachment 4292 [details] TB screenshot showing error About a third of the way down the message window, note the rendering of what is supposed to be "Fox footy floats flagship app on Redmond Cloud"
Here is the HTML source for that area of text: <div class=3D"LeadStory"> <p class=3D"Headline"><a href=3D"http://go.reg.cx/news/27Fy">Fox footy floa= ts flagship app on Redmond cloud</a></p> <p class=3D"Standfirst">'Viable model for premium content', apparently</p> </div>
Created attachment 4293 [details] Second example affecting "ff" and "fi" Apparently the combinations "ff" and "fi" are also affected. The HTML for the sequence shown in this screenshot is: </div> <ul> <li> <p class=3D"Headline"><a href=3D"http://go.reg.cx/news/27Fr">Cryptome suffe= rs brief take-down over Japanese 'terror' files</a></p> <p class=3D"Standfirst">Bitten by attack dog, just a flesh wound</p> </li> <li>
well to honest I don't know what to do with such bugs
Keywords: (none) => Triaged
Keywords: Triaged => (none)
I guess the first port of call would be anyone who changed/updated any fonts lately, like in the last week. I know I didn't tell TB to switch fonts, so it should still be using whatever we ship it with.
Is this bug reproducible in Mageia 4 and 5?
Keywords: (none) => NEEDINFO
I haven't noticed this in a quite a while, so it appears whatever broke was fixed.
Status: NEW => RESOLVEDResolution: (none) => FIXED