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

V Stuart Foote <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #89 from V Stuart Foote <[email protected]> ---
(In reply to Eyal Rozenberg from comment #88)
> 
> That's probably because it's problematic and Writer's performance on the
> document it produces is kind of dismal. When I open the "PDF file"
> attachment in Writer - only 7 pages - it slows to a crawl with scroll delay
> times of ~ 10 seconds or higher. Is there a separate bug about that?
> 
> 
> Also, the Writer PDF import filter is hidden away; and when you try to open
> a PDF from Writer it defaults to opening in Draw for some reason; I'm sure I
> opened a bug about this at some point.
> 

Wrong tool for the job!  The PDF Import filter was designed to extract all the
presentation elements of a PDF as *Draw shape objects*--onto the Draw canvas.
Text runs recorded into the PDF (as either char sequences from the PDFs
ToUnicode chart, or as PDF /ActualText tags) are imported to draw textboxes.
The reconstructed textboxes sometimes contain just one glyph with *NO* lexical
context--just the sequence of characters as published into the PDF.

You should not expect directly "edit" the PDF text runs as laid down as draw
Shape textboxes as if they were text strings. They are a facsimile of the
original PDF publishing--not intended to be editable.

And of course using the alternate, and neglected, PDF Import to Writer filter
and placing thousand of draw shapes onto a Writer document canvas, it is going
to bog things down. Shapes including textboxes on Writer canvas are expensive
and nonperformant.


> If those two issues were resolved, I believe opening a PDF in Writer would
> become a common use case as well

To what end? The result of PDF import is not editable text! Even in Draw where
using the rudimentary "Consolidate text" utility (.uno:TextCombine, for bug
118370) takes the lexically broken text runs of multiple textboxes and merges
them, they are still in a textbox--no paragraph controls, minimal formatting,
etc.  To understand what you get to work with (Draw, Impress or Writer), open
the SB Navigator deck. Every shape object would need to be 

As an alternative, perhaps explore the very functional PDF "Insert as image"
filter. Completely different source based on pdfium rather than poppler but
very high fidelity to the original PDF, with its own set of enhancements, e.g.
bug 114234 bug 115811 and need to manually set the 'PDFIMPORT_RESOLUTION_DPI'
for more than the 96dpi default. 

Going to close this Resolved Fixed again. PDF Filter import for Draw and
Impress are addressed, opening a new issue for the refactoring of the Writer
import filter 'PDF - Portable Document Format (Writer) (*.pdf)'

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to