[Libreoffice-ux-advise] [Bug 152661] "Hybrid PDF" must share embedded media between the ODT and the proper PDF

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=152661

--- Comment #5 from V Stuart Foote <vsfoote at libreoffice.org> ---
You are asking for PDF filter export to pack ODF compliant elements into a  PDF
Object stream and individual xref entries. And to provide reverse PDF filter
import to parse those same Object streams back into a coherent ODF ready XML.

The current approach is a single export stream embedding a single ODF compliant
document as a PDF Object stream --the LibreOffice "Hybrid PDF". That is matched
by a filter import stream that reads the PDF xref table, recognizes the entry
for LO generated source ODF, and selectively parses that ODF stream rather than
the full PDF.

The current two-way filters are efficient and functional--suited to our needs
for Hybrid PDF. 

As noted in see also bug 95328 to refactor export/import filters and make the
ODF a PDF "attachment" might make sense to allow other PDF viewers to recognize
the attached ODF. 

However, refactoring PDF export filter to reliably embed ODF canvas internals
as PDF object streams would be non-performant--which elements go where?  While
the likely necessary use of /ActualText (as for bug 117428) tagging for *all*
text runs would negate any potential size reduction of embedding ODF elements
as PDF object streams.

And then there would be filter requirements to be able to roundtrip--rather
than a single fully ODF compliant source document, we would have to parse the
entire PDF xref table, identify where each PDF Object needs to be placed (and
on which page) individually extract and hold, and then reassemble in to some
semblance of the original source ODF.

It could be done, obviously--but it is not advantageous to the project in any
sense to do so! Not an imperative, certainly not worth the dev effort 
refactoring both PDF filters would require.

So again, NO!

-- 
You are receiving this mail because:
You are on the CC list for the bug.