eg.:
Glyph like this
http://www.unicode.org/cgi-bin/GetUniha ... 0%A0%84%9E
U+2011E
in Goldendict 1.0.1 can not be displayed:
* {
font-family: "Segoe UI","Tahoma",Verdana,"Lucida Sans Unicode","SimSun-ExtB";
}
body {
/* NOTE, since font fallback won't work, you can specifiy only one font here */
font-family: HanaMinB;
}
timonwong wrote:Sorry, my previous approach only got control font fixed, it won't work for the article, actually, it's a bug in QtWebKit (font fallback doesn't work at wall), and didn't got fixed for years.
I'm afraid this is a Qt 4.8.x bug. If you save your article into an HTML file (F2) and open it in any normal browser, the content is correctly displayed. Qt 4's browser seems to be picking the first font in the list and not bothering to perform a proper W3C recommended Font matching algorithm.
I tried Qt 5's webview, and it actually renders the results properly. So, as soon as we port/migrate GoldenDict to Qt 5, this bug will be fixed automatically.
Meanwhile, I don't have good workaround for this problem. You might put the "Arial Unicode MS" at the beginning of the list.
Tvangeste wrote:So, we need to upgrade to Qt5 sooner or later. See Issue #212 for Qt5-related updates.
timonwong wrote:I'll try to upgrade upgrade to Qt5 and keep the compatibility with Qt4 as well (4.7 at least, I think).
Users browsing this forum: No registered users and 123 guests