Version: 3.4.92 (using KDE 3.5 (RC1), Gentoo) Compiler: gcc version 3.3.5-20050130 (Gentoo Linux 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1) OS: Linux (i686) release 2.6.14-gentoo When navigating a site that uses utf-8 encoding, the encoding is lost when I go back in the site history. The utf-8 text is displayed as iso-8859-x (possibly my local encoding). Try: http://sf.euweb.cz/ . Click on the name of an article, and then go back. The text is then shown all garbled. I use kdelibs from 3.5.0_rc1.
I must say the site's html is buggy: there is a lot of banner-html before the real <html> element opens. Maybe that's the reason konqueror forgets the utf-8 encoding.
kde-3.5.0, got the same (mis)behaviour with linux.org.ru Strange bug, indeed. Some sites with utf-8 encoding work as expexted (say, gentoo.ru), the others are broken (linux.org.ru, etc.)
The same since 3.5beta1 to 3.5 release. there was no problem with 3.4 .. 3.3 .... anv lower versions ... http://linux.org.ru as example ...
Yes i found the same problem with a Greek site http://www.epe.org.gr/ If u follow a link and then press the "Back" button the encoding gets messed... Note that the aforementioned site has Valid HTML and Valid CSS.
SVN commit 486394 by orlovich: Don't loose server-specified encoding info when going back in history BUG:116320 M +2 -0 khtml_part.cpp --- branches/KDE/3.5/kdelibs/khtml/khtml_part.cpp #486393:486394 @@ -1667,7 +1667,9 @@ { long saveCacheId = d->m_cacheId; QString savePageReferrer = d->m_pageReferrer; + QString saveEncoding = d->m_encoding; begin( d->m_workingURL, d->m_extension->urlArgs().xOffset, d->m_extension->urlArgs().yOffset ); + d->m_encoding = saveEncoding; d->m_pageReferrer = savePageReferrer; d->m_cacheId = saveCacheId; d->m_workingURL = KURL();
*** Bug 117917 has been marked as a duplicate of this bug. ***
*** Bug 118615 has been marked as a duplicate of this bug. ***
*** Bug 119165 has been marked as a duplicate of this bug. ***
*** Bug 119187 has been marked as a duplicate of this bug. ***
*** Bug 127172 has been marked as a duplicate of this bug. ***