This is fixed in Ubuntu 12.04 Precise Pangolin beta 1.
Packages: evince 3.3.90-0ubuntu2
libpoppler19 0.18.4-1ubuntu1
libcairo2 1.10.2-6.1ubuntu2
** Changed in: poppler (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification
** Changed in: poppler
Status: Unknown = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/324579
Title:
Wrong PDF rendering, but correct in okular
--
desktop-bugs mailing list
** Changed in: poppler
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/324579
Title:
Wrong PDF rendering, but correct in okular
--
desktop-bugs mailing list
** Changed in: poppler
Importance: Medium = Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/324579
Title:
Wrong PDF rendering, but correct in okular
--
desktop-bugs mailing list
Well the bug has been marked as duplicate of bug
https://bugs.freedesktop.org/show_bug.cgi?id=11719, why has the status been
marked as invalid ?
the bug is valid, triaged and still open, waiting for clipToStrokePath() to
be implemented.
** Bug watch added: freedesktop.org Bugzilla #11719
** Changed in: poppler
Status: Confirmed = Invalid
--
Wrong PDF rendering, but correct in okular
https://bugs.launchpad.net/bugs/324579
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
The bug is still present in Karmic.
The lower part of the page now seems correct, but the upper is wrong.
--
Wrong PDF rendering, but correct in okular
https://bugs.launchpad.net/bugs/324579
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
The bug persists even in Jaunty Beta.
--
Wrong PDF rendering, but correct in okular
https://bugs.launchpad.net/bugs/324579
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
The bug has been sent to
https://bugs.freedesktop.org/show_bug.cgi?id=20487
** Changed in: poppler (Ubuntu)
Status: Confirmed = Triaged
** Changed in: poppler
Importance: Undecided = Unknown
Bugwatch: None = freedesktop.org Bugzilla #20487
Status: New = Unknown
--
Wrong
** Changed in: poppler
Status: Unknown = Confirmed
--
Wrong PDF rendering, but correct in okular
https://bugs.launchpad.net/bugs/324579
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Yes, that's correct.
--
Wrong PDF rendering, but correct in okular
https://bugs.launchpad.net/bugs/324579
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
confirmed on jaunty, will look upstream, thanks.
** Changed in: poppler (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Confirmed
** Also affects: poppler
Importance: Undecided
Status: New
--
Wrong PDF
I know that there are different bindings for QT and GLib, but I thought that
the backend was the same...
So the rendering can be completely different in the two cases?
--
Wrong PDF rendering, but correct in okular
https://bugs.launchpad.net/bugs/324579
You received this bug notification because
While it is true that both okular and evince use poppler, poppler has
separate backends for Qt and GTK.
** Changed in: poppler (Ubuntu)
Sourcepackagename: evince = poppler
--
Wrong PDF rendering, but correct in okular
https://bugs.launchpad.net/bugs/324579
You received this bug notification
14 matches
Mail list logo
