Linked by Thom Holwerda on Sun 31st Jul 2005 11:45 UTC, submitted by GhePeU
Gnome GNOME 2.12 will be released to the world on September 7th, 2005, culminating 6 months of very exciting work by members of the project. A number of exciting technologies come together in GNOME 2.12 that will set the standard for free software desktops to come. Here is a sample of some of the outstanding work that has gone into GNOME thanks to its many contributors.
Thread beginning with comment 11612
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Evince is awesome
by on Sun 31st Jul 2005 15:38 UTC in reply to "RE[2]: Evince is awesome"

Member since:

> XPDF and KPDF are glacially slow (I haven't tried the
> new one everybody is hyping though). Evince is based in
> libpoppler, which is a fork of the XPDF codebase
> integrated with Cairo.

This is pure bullshit, specially your first sentence. Poppler as you rightfully say is a fork of XPDF, now tell me how KPDF and XPDF can be slower ? Specially XPDF while it's the same code as Poppler ?

I find KPDF to be much faster and responsive than Evince. Evince in the recent past has caused a lot of problems for me, like not rendering large PDF documents correctly, you get white pages in the middle of your text.

Say you go from page 1 to page 5 in your document (a doc with 25 pages) and see that after page 5 everything shows up in white only. Or not being able to print a single page or their thumbnailer locking the entire application up and so on.

Another issue is that Poppler doesn't return the correct paper size to Evince. You need to apply the paper size to Poppler during configuration time, so if you live in US you don't add anything, if you live in germany and have A4 as paper size you need to configure --with-papersize-a4 or something and then compile Poppler and then Evince ontop of it. This makes the libgnomeprint/ui dialog become useless and you can select even postcard size if you want and it still prints either A4 or Letter format.

When you select 2 or 4 sheets on 1 physical page and you want to save this into a file (within the print dialog) then it doesn't work, when you want to print exactly that stuff then it doesn't work either.

There are a lot more issues with Evince, while it's a nice application and definately going into the right direction it still lacks behind compared to KPDF who makes usage of the KDE printing framework and strangely works perfectly, renders better, apply papersize correctly to the application.

Reply Parent Score: 4

RE[4]: Evince is awesome
by rayiner on Sun 31st Jul 2005 15:56 in reply to "RE[3]: Evince is awesome"
rayiner Member since:
2005-07-06

This is pure bullshit, specially your first sentence. Poppler as you rightfully say is a fork of XPDF, now tell me how KPDF and XPDF can be slower ? Specially XPDF while it's the same code as Poppler ?

What about the term fork do you not understand? A fork would be kind of pointless if it wasn't better. I have a version of XPDF sitting right here, and "glacially slow" is absolutely the right term. And that's on a dual-core Athlon64!

I find KPDF to be much faster and responsive than Evince.

As I said, I haven't tried the new version of KPDF that everyone's raving about. However, Evince is much faster than the old versions.

Evince in the recent past has caused a lot of problems for me, like not rendering large PDF documents correctly, you get white pages in the middle of your text.

I haven't encountered this problem. I'm using the version in Fedora Core 4, btw.

Another issue is that Poppler doesn't return the correct paper size to Evince. You need to apply the paper size to Poppler during configuration time, so if you live in US you don't add anything

We don't have A4 paper here in the US, so that's probably why I haven't noticed it. Again, I couldn't care less, since it works for me.

Reply Parent Score: -1

RE[5]: Evince is awesome
by on Sun 31st Jul 2005 16:09 in reply to "RE[4]: Evince is awesome"
Member since:

> What about the term fork do you not understand? A
> fork would be kind of pointless if it wasn't better.
> I have a version of XPDF sitting right here, and
> "glacially slow" is absolutely the right term. And
> that's on a dual-core Athlon64!

How can the forked XPDF aka Poppler be faster when it has CAIRO tied to it ? CAIRO is known to be dead slow, so the resulting output through Poppler automagically MUST be slower than through XPDF. Only exception would be if there was some code magic and some code refactoring that makes the code work faster.

> As I said, I haven't tried the new version of KPDF
> that everyone's raving about. However, Evince is much
> faster than the old versions.

But you are the person who shouted out first that EVINCE is faster than anything else, faster than Acro, XPDF and KPDF. So before throwing such arguments into the room, you should have made clear that this "non measured" experiences came from older applications.

> I haven't encountered this problem. I'm using the
> version in Fedora Core 4, btw.

> We don't have A4 paper here in the US, so that's
> probably why I haven't noticed it. Again, I couldn't
> care less, since it works for me.

You do care anyways, specially if you want to print 4 pages on 1 physical sheet and realize that it doesn't work, this is independant to paper size.

You also do care if you have a PDF file that has 20 or more pages and you figure out in the middle that after some pages the pages show up white only. Even this is independant to paper size.

Have you actually used or tested Evince with more than reading the one or other PDF file ? Or do you keep saying things about programs that don't reflect reality.

Now let's measure some values, you say that KPDF and XPDF are slower than EVINCE while all three apps are based on the same code and probably all three seem to inherit the latest changes from either XPDF, Poppler to be current and knowing that Poppler even has CAIRO tied to it. So how about some serious profiling and giving us some numbered values ?

Reply Parent Score: -1