<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Dec 29, 2012 at 5:25 AM, Albert Astals Cid <span dir="ltr"><<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">El Dissabte, 29 de desembre de 2012, a les 04:47:08, Jaydeep Solanki va<br>
escriure:<br>
<div>> All the libraries that Okular generators use, do all of them generate text<br>
> in the correct order ?<br>
> By correct order I mean, following the layout (eg. two column, three<br>
> column).<br>
> As far as I have noticed poppler genereates in the correct order.<br>
<br>
</div>I don't understand your question.<br></blockquote><div><br></div><div>As you might be knowing that Poppler::Page::textList() generates text in the correct order (i.e. left to right). Now poppler not only generates it in the correct order but it also considers the layout, for example in a two column document, it follows the column layout while indexing the text.<br>
<img alt="Inline image 2" src="http://nightcrawlerinshadow.files.wordpress.com/2011/08/4-7_pdf_selection.png" width="382" height="420"><br><br></div><div>just of example consider the image above, see the selection, poppler doesn't generate textList() in that order, it generates the textList() as shown in the below image,<br>
<br><img alt="Inline image 3" src="http://nightcrawlerinshadow.files.wordpress.com/2011/08/selection_and_highlighting_pdf_selection.png" width="384" height="420"><br></div><div>So my question is do all the libraries that the generators of okular use, generate text in the proper order considering the layout ?<br>
</div><div><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Cheers,<br>
Albert<br>
<div><div><br>
><br>
> On Fri, Dec 28, 2012 at 5:57 AM, Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>> wrote:<br>
> > El Divendres, 28 de desembre de 2012, a les 01:48:55, Jaydeep Solanki va<br>
> ><br>
> > escriure:<br>
> > > I would like to give it a try, please point me to the source.<br>
> ><br>
> > You know where the source is ;-)<br>
> ><br>
> > Have you tried searching for where the code that is responsible of this<br>
> > before<br>
> > asking?<br>
> :<br>
> :D you got me..<br>
> :<br>
> > > & in the case where the toc is updated/changed, I guess that part should<br>
> > > remain folded & the rest should restore to it's previous state. What's<br>
> ><br>
> > your<br>
> ><br>
> > > opinion on this ??<br>
> ><br>
> > Let's go the easy way for now "a) Keep the toc view in its present state<br>
> > if<br>
> > the toc hasn't changed at all. Otherwise fold it completely"<br>
> ><br>
> > > btw is this for the reload action only, or is it about to store it &<br>
> > > restore when the document is opened again?<br>
> ><br>
> > Reload only.<br>
> ><br>
> > Cheers,<br>
> ><br>
> > Albert<br>
> ><br>
> > > -Jaydeep<br>
> > ><br>
> > > On Thu, Dec 27, 2012 at 2:35 AM, Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>><br>
> ><br>
> > wrote:<br>
> > > > <a href="https://bugs.kde.org/show_bug.cgi?id=312138" target="_blank">https://bugs.kde.org/show_bug.cgi?id=312138</a><br>
> > > ><br>
> > > > Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>> changed:<br>
> > > > What |Removed |Added<br>
> ><br>
> > --------------------------------------------------------------------------<br>
> ><br>
> > > > --><br>
> > > ><br>
> > > > Keywords| |junior-jobs<br>
> > > ><br>
> > > > --- Comment #4 from Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>> ---<br>
> > > > Marking this as a junior job, it should be pretty easy to store the<br>
> ><br>
> > whole<br>
> ><br>
> > > > tree<br>
> > > > of the TOC when we trigger the reload and check if the tree is the<br>
> > > > same<br>
> > > > after<br>
> > > > it has happened. Interested people in implementing the junior job<br>
> ><br>
> > please<br>
> ><br>
> > > > contact the <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a> mailing list if you decide to have a<br>
> > > > look at<br>
> > > > this.<br>
> > > ><br>
> > > > --<br>
> > > > You are receiving this mail because:<br>
> > > > You are the assignee for the bug.<br>
> > > > _______________________________________________<br>
> > > > Okular-devel mailing list<br>
> > > > <a href="mailto:Okular-devel@kde.org" target="_blank">Okular-devel@kde.org</a><br>
> > > > <a href="https://mail.kde.org/mailman/listinfo/okular-devel" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
> ><br>
> > _______________________________________________<br>
> > Okular-devel mailing list<br>
> > <a href="mailto:Okular-devel@kde.org" target="_blank">Okular-devel@kde.org</a><br>
> > <a href="https://mail.kde.org/mailman/listinfo/okular-devel" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
_______________________________________________<br>
Okular-devel mailing list<br>
<a href="mailto:Okular-devel@kde.org" target="_blank">Okular-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/okular-devel" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
</div></div></blockquote></div><br></div></div>