[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 #6 from Eyal Rozenberg <eyalroz1 at gmx.com> ---
(In reply to V Stuart Foote from comment #5)
> The current two-way filters are efficient and functional--suited to our
> needs for Hybrid PDF. 

They're not efficient - they about-double the amount of space necessary, when
the embedded media is significantly larger than the rest of the document. Hence
this bug.


As for the rest of your comment...

Right now, the PDF import filter, upon noticing a PDF is a "hybrid PDF" - e.g.
by some field/tag in the trailer or xref table, I guess - chucks all of the PDF
and keeps the embedded ODF document. So, there's already some parsing going on
which results in a coherent ODF - although, granted, it's limited. Also, the
PDF export filter (whether it's a hybrid PDF or not) already packs elements
into multiple PDF object streams and creates xref entries for them. The change
I'm proposing is that media references in the ODF saying "the PNG file named
foo.png packed into this ODF", we will have references saying, oh, maybe
something like "the indirect object 12345 foopng within the PDF this ODF is
in".

Indeed, this means there will need to be more parsing. But - that's nothing
compared to the amount of work done when importing MSO files! It's basically at
the level of complexity of a regexp application.

> However, refactoring PDF export filter to reliably embed ODF canvas
> internals as PDF object streams

I don't think I suggested doing that. I hope my last couple of paragraphs
illustrate what I mean

> would be non-performant--which elements go
> where?  While the likely necessary use of /ActualText (as for bug 117428)
> tagging for *all* text runs

I'm only talking about media such as images, sound, video and arbitrary binary
files. I really think you've misunderstood my suggestions.

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