Summary: | Add support for pdf tooltip! | ||
---|---|---|---|
Product: | poppler | Reporter: | 9u0h923nhu |
Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | oliver.sander |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | pdf file with a few tooltip annotations |
Description
9u0h923nhu
2018-03-02 12:12:49 UTC
Please attach a file. Created attachment 137770 [details]
pdf file with a few tooltip annotations
Extracted from the example file of the LaTeX 'pdfcomment' package.
Extracting one of the three annotations in the example file we get
<<
/Type /Annot
/Subtype /Widget /TU (Sulfuric\040acid) /T (tooltip zref@1) /C [ ] /FT/Btn /F 768 /Ff 65536 /H/N /BS << /W 0 >>
/Rect [417.169 745.106 451.341 754.196]
>>
So it looks like a merged Field and Annot dictionary...Aren't fields supposed to belong to Forms? I don't find the /T entry anywhere, so I don't know that the (tooltip zref@1) means
No, AnnotWidgets can also be standalone, see } else if(!strcmp(typeName, "Widget")) { in Annot.cc but it's true we don't see to support Widgets that don't belong to Forms very well "(tooltip zref@1)" means nothing, what you're interested in is the TU field that which we're not parsing in AnnotWidget::initialize. Basically this "tooltip" is implemented as an invisible button, kind of a hack if you ask me, but yeah we should try to support them. -- 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/poppler/poppler/issues/34. |
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.