Summary: | Okular complains about errors in PDF without details, online tools validate this PDF fine | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Yuri <yuri> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | aacid, kde, newuser |
Priority: | NOR | ||
Version First Reported In: | 21.12.3 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | FreeBSD | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Yuri
2022-04-12 17:39:49 UTC
Okular is not a validation tool, and the PDF is indeed faulty. Personally i don't see anything for us to do here. It should print what's wrong with it when it complains. This pdf was generated with Goodle Slides. > It should print what's wrong with it when it complains. That's your opinion, i disagree. > This pdf was generated with Goodle Slides. So what? I have the same issue, Okular complains it has found errors in a pdf file but doesn't give any details about what these errors are. Why would a program complain about errors without giving any clue about what these errors are to make it possible to fix them? Why show the error at all if you don't want to help the user, it is only about annoying the user instead of helping him? (In reply to newuser from comment #4) > I have the same issue, Okular complains it has found errors in a pdf file > but doesn't give any details about what these errors are. Why would a > program complain about errors without giving any clue about what these > errors are to make it possible to fix them? Why show the error at all if you > don't want to help the user, it is only about annoying the user instead of > helping him? If we were showing you the issue, it could be stuff like "Document stream empty" or "Catalog object is wrong type" or "Illegal character X at position Y" - what would you do with that knowledge? |