for evince, which uses libpoppler for text search in PDF, callgrind estimates 47% of time spent in pow(), called from cmsBuildSegmentedToneCurve() (56% in/below this function), which is some function for drawing curves? and further up in the call chain, there's Page::display()
-
-
Show this thread
-
so looks like it fully layouts every page it's searching through?
Show this thread -
Show this thread
End of conversation
New conversation -
-
-
is it faster if you do pdftotext [file] | grep [pattern] on the commandline?
-
somewhat - 20s for searching through the SDM in evince, 8s for pdftotext
End of conversation
New conversation -
-
-
Searching in intel data sheets grinds my laptop to a halt. It is only 2000 pages, what year is it?
-
Mupdf or Zathura
- 1 more reply
New conversation -
-
-
I think the costly part is establishing if two pieces of text follow each other
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You've looked at the format right.... I mean it's a mess. Crazy table of contents pointing to various encoded chunks...etc
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Worst case requires that every word is stiched together from individual letters based on glyph position, guessing spaces by horizontal distance and lines by vertical location.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.