GNOME Bugzilla – Bug 696198
TOC and certain pages not rendered in a DjVu file
Last modified: 2013-04-04 20:45:43 UTC
Document Link: http://adf.ly/HNGRj When I open this file in WinDjVu, I am able to access the TOC links and all pages are rendered correctly. However, when I try to access the same file in linux using evince: 1. Some problem in rendering page 2 and 9. They show up as black pages 2. The Index is blank, wherein I expected to see the TOC listings.
What should be shown in page 2 and 9? I can not view anything neither with djview4 nor evince (master). If I convert the djvu file to PDF, I get the following errors (in the console): Corrupt JPEG data: 262144 extraneous bytes before marker 0xd9
Germán, the problem in 1) is already fixed in master :) In djvu, pages are images, and when a page is blank, you just skip the image. In evince 3.6, there was an bug in the rendering and when there was no image, we would render a complete black page. Now, in master it works as expected. the problem in 2) it is mostly solved, but there are still some fixes that didn't land for 3.8. I will upload the patches to the corresponding bugs once we are over the freeze.
(In reply to comment #2) > Germán, the problem in 1) is already fixed in master :) In djvu, pages are > images, and when a page is blank, you just skip the image. In evince 3.6, there > was an bug in the rendering and when there was no image, we would render a > complete black page. Now, in master it works as expected. Do I need a newer library for that? I run master by default and with that I could reproduce the issue. FWIW, I do not get a black page, just a white empty page. Although, the only time I open djvu files are when I check Evince's bugzilla. So, I am djvu-ignorant.
(In reply to comment #3) > FWIW, I do not get a black page, just a white empty page. I got a blank white page while viewing page 2 and 9 in WinDjView (not WinDjVu as I mentioned in the report, sorry), but the same were rendered as black pages in evince 3.6. However, José cleared up that issue.
I am pretty sure that this is a duplicate. *** This bug has been marked as a duplicate of bug 619410 ***