<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - exported PDF is invalid because of forbidden custom keys in the trailer" href="https://bugs.documentfoundation.org/show_bug.cgi?id=66580#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - exported PDF is invalid because of forbidden custom keys in the trailer" href="https://bugs.documentfoundation.org/show_bug.cgi?id=66580">bug 66580</a> from <a class="email" href="mailto:kurt.pfeifle@gmail.com" title="kurt.pfeifle@gmail.com">kurt.pfeifle@gmail.com</a> <pre>(In reply to Jos van den Oever from <a href="show_bug.cgi?id=66580#c9">comment #9</a>) > PDF documents created with version 5.1.2.2.0 on Linux 4.4 still add the key > /DocChecksum and /AdditionalStreams to the PDF files. Jos, the additional (proprietary) keys used by OpenOffice/LibreOffice to embed the original OpenDocument file into the Hybrid PDF are not doing any real h a r m: * As I showed in <a href="show_bug.cgi?id=66580#c6">comment #6</a> none of the 36 tested PDF viewers has any problem opening and displaying a Hybrid PDF! There are other reasons which would may M E want to modify the way LO creates a Hybrid PDF: * N O N E of the other PDF readers do have a way to detect that there is an embedded OpenDocument file in the PDF! The reason for this is that the way OO/LO implemented this feature was that they did it in a non-standard, "proprietary" way -- while they could have utilized the standards-defined "embed another file into the PDF"-feature. (See for example <a class="bz_bug_link bz_status_NEW " title="NEW - Hybrid PDF -- implement PDF 1.4 level support for Embedded File Streams to expose ODF object stream as Attachment to the PDF document" href="show_bug.cgi?id=95328">bug95328</a> and comments). And there A R E good use cases to be able to detect the embeddedness of the original OpenDocument file in a PDF even by non-OO/LO applications: - User(s) may not be aware of this when they open the PDF in a PDF reader. However, the reader may draw their attention to the fact of the original ODT/ODS document being embedded. After all, whoever embedded the original document into the Hybrid PDF most likely W A N T E D it to be editable. - Users may need/want to extract the embedded ODT/ODS file without switching to LibreOffice first (which may not even be installed on their currently used computer system). - I could easily think of more use cases, why it would be good to be able to D E T E C T the fact of the embedded original and editable file and also to E X T R A C T it from the PDF via a software other than OO/LO.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>