Summary: | A particular eps file isn't opend correctly in Okular | ||
---|---|---|---|
Product: | libspectre | Reporter: | Diego <diego.ml> |
Component: | general | Assignee: | Carlos Garcia Campos <carlosgc> |
Status: | RESOLVED MOVED | QA Contact: | Carlos Garcia Campos <carlosgc> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | EPS file that doesn't open correctly in Okular (wrong orientation, wrong paper size) |
Description
Diego
2009-02-16 05:07:11 UTC
The problem is that this document has a page bouding box bigger than the document bounding box. libspectre always takes the page bounding box when it's present for the given page. In this case the page bounding box is A4 size. And it's rendered horizontally oriented because there's also a PageOrientation: Landscape comment for the page. So, I don't think it's a bug. I see... so this file is a bit broken because it can lead to different interpretations (e.g. the different visualization between Gwenview and Okular). Which would be the best choice to have all the applications behave the same way? Should I file a bug against Gwenview to ask them to get the same behaviour as libspectre? Should I file a bug against Scribus so that the exported eps should not have different page and document bounding box? Thanks. Well, I'm not sure, and that's the reason why I haven't closed this bug as NOTABUG. I think we are following the PostScript spec. FWIW, gsview gives me the same output than libspectre, so I would probably file a bug to Scribus. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/libspectre/libspectre/issues/20. |
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.