Menu
▾
▴
#925 PDF export breaks standard, Docear drops support for Skim
http://www.docear.org/faqs/why-does-docear-not-support-preview-and-skim/
Export to PDF: object number generation is not compliant with the PDF standard.
Excerpt: “Together, the combination of an object number and a generation number
uniquely identifies an indirect object. The object retains the same object number
and generation number throughout its existence, even if its value is modified.”
If the standard is insufficient, please explain so that a bug report may be filed for Docear to support the extension of the standard.
Cheers,
Joe
I have started a thread on the Docear site regarding integration with Skim:
http://www.docear.org/support/forums/docear-support-forums-group3/general-feedback-questions-forum5/why-aren%E2%80%99t-mac-os-%E2%80%9Cpreview%E2%80%9D-and-%E2%80%9Cskim%E2%80%9D-supported-by-docear-thread285.0/#postid-987
And mentioned skimpdf and skimnotes as potential remedies to the Docear interface requirements.
Exported PDF (with embedded notes) is generated by Apple's code. We have no involvement. You should send the bug report to Apple. Apart from that, the complaint is not necessarily valid, because nobody says that the saved PDF is the same as the original PDF, because in fact it isn't, so thy don't necessarily need to be compared. Now this may not be ideal, but it's not necessarily a bug, and moreover a complaint for Apple. I think Docear's standpoint is stupid, because Adobe is not the standard program to use on MacOS, so they're essentially throwing away support for MacOS.