| Summary: | only titles displayed after first page | ||
|---|---|---|---|
| Product: | poppler | Reporter: | Pablo Rodríguez <freedesktop> |
| Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | PDF showing the lacking display | ||
We show exactly the same Adobe Reader and gs do, so i will say that unless proven otherwise we, gs and Adobe Reader are right and mupdf and xpdf are the ones buggy. I compared gs, pspcl6, mupdf, xpdf evince and acroread. That pdf has some ecmascript to alter the page on clicks, rather than having separate pdf pages for each step of the presentation. (in acro, put the pointer anywhere on the page and repeatedly left-click to see all of the content.) One /could/ argue that viewers which lack ecmascript support should display it as mupdf does. But this is mostly a dup of the »Please add ecmascript« bug. (In reply to comment #2) > I compared gs, pspcl6, mupdf, xpdf evince and acroread. > > That pdf has some ecmascript to alter the page on clicks, rather than > having separate pdf pages for each step of the presentation. (in acro, > put the pointer anywhere on the page and repeatedly left-click to see > all of the content.) > > One /could/ argue that viewers which lack ecmascript support should > display it as mupdf does. > > But this is mostly a dup of the »Please add ecmascript« bug. Thanks for your reply, James. I don't think this is a duplicate of “Please add ECMAScript”. Displaying the whole page contents (as both mupdf and xpdf do) is the only way the user has to get the contents. Untill ECMAScript is implemented, I guess this is the only workaround within poppler. Thanks for your help, Pablo > I don't think this is a duplicate of “Please add ECMAScript”. I wrote ‘mostly a dup’ because ecmascript is the only way to display the pdf as the author (apparently) indends. > Displaying the whole page contents (as both mupdf and xpdf do) is the > only way the user has to get the contents [w/o ecmascript]. > > Until ECMAScript is implemented, I guess this is the only workaround > within poppler. Yes. -JimC (In reply to comment #4) > > Until ECMAScript is implemented, I guess this is the only workaround > > within poppler. > > Yes. Thanks, James, for your reply. I'm afraid I have no patch to offer, since I cannot code. Could the bug report be reopened, so it could be fixed? Thanks again, Pablo |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 55993 [details] PDF showing the lacking display poppler only shows titles after the first page on the attached PDF document. mupdf and xpdf display all content in those pages. Just in case it helps, Pablo