[okular] [Bug 418520] Find function misses occurrences of target string that wrap from one line to next line of document text.

[avlas]

https://bugs.kde.org/show_bug.cgi?id=418520

--- Comment #9 from avlas <jsardid at gmail.com> ---
(In reply to avlas from comment #8)
> (In reply to avlas from comment #7)
> > (In reply to Albert Astals Cid from comment #5)
> > > di-vided has worked and still works, have you even tried it?
> > 
> > I use okular 19.12 and searching proposed detects proposed but does not
> > detect pro- \n posed
> > 
> > Also searching  pro-posed does not detect pro- \n posed
> 
> Ok, I tested this in a second pdf and works as you mentioned.
> 
> The problem I had was specific of a 2-column pdf file that is wrongly
> considered as 1 column. I assume the problem is with the specific pdf format
> as other 2-column pdfs work just fine in okular.
> 
> I assume there is no simple heuristic to workaround these wrongly formatted
> pdfs, which highly affect features such as searching, highlighting and
> selecting/extracting text.
> 
> But that's an entirely different issue than the one fixed here. Again,
> thanks for your contribution!


Further investigating that wrongly formatted pdf file I found the following
behavior when searching for "circum there":

https://i.imgur.com/92SWRjo.png

Does it mean okular detects a line break and nevertheless it jumps to the
different column instead of staying on the same column and jump to the next
line?

I assume this is a problem of the pdf and not of okular, but the behavior seems
very strange, I thought the same line covered the two columns (no line break in
between), but the hyphen is ommitted which only happens in line breaks, right?

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