Even though it's not critical, I think it's important to fix this for hardy. It's a very bad advertising for an otherwise very good application (evince), and degrades the visibility of Ubuntu in general not to be able to properly handle what is expected to be a simple task, in the view of lay people (and indeed works with other apps).
I decided to try fool evince into using poppler3 from intrepid. Intrepid version compiles fine on Hardy, and I managed to replace them with an ugly hack with symlinks between libpoppler.so.3/libpoppler.so.2 and libpoppler-glib.so.3/libpoppler-glib.so.2. Not surprisingly, it was very unstable, and evince crashed on mouseover actions, so I couldn't select/copy to test for other bugs (bug #33288 for example). But it kind of worked. I'm attaching a new screenshot of the result. It's still not perfect, the "fi" string still appear as an undefined (to me at least) ascii character (look for the first sentence in the abstract: "We describe a unified ...". Also appear in the last two of the abstract). Even so, readbility has improved vastly in this case. Unfortunately, I can't use this hack for production use, since they cause evince to crash more often than not. Is there a way to backport the needed patch(es) to -updates, or should I file a bug to hardy-backports so the whole 0.8.x is backported? -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
