Summary: | pdftohtml to generate outlines in -xml mode | ||
---|---|---|---|
Product: | poppler | Reporter: | Igor Slepchin <igor.redhat> |
Component: | pdftohtml | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
generate outlines in -xml mode
consistently check if outlines need to be generated |
Description
Igor Slepchin
2012-02-13 14:00:00 UTC
Created attachment 56993 [details] [review] generate outlines in -xml mode Created attachment 56994 [details] [review] consistently check if outlines need to be generated This should probably be applied to 0.18 branch as well; without it we will generate dangling outline references for pdfs that have Outlines entry with no OutlineItems in their catalog. (In reply to comment #2) > This should probably be applied to 0.18 branch as well; Just a clarification - this comment applies to the second attached patch only (it can be cleanly applied independently of the first one). Patch looks good but think <outline> should be reserved only for the toplevel one, inner ones should use something like <children> or some other name. (In reply to comment #4) > Patch looks good but think <outline> should be reserved only for the toplevel > one, inner ones should use something like <children> or some other name. I actually tend to like having the same names for both top and other levels since they do indeed have the exact same structure. If you really prefer having a separate top-level element, how about enclosing the XML outline output into another element, say, "outlines" (plural) or "toc" (for table of content")? Ok, no worries. I've commited the patch |
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.