Oh sorry, that was meant to be on a new thread.
On Sat, Dec 29, 2012 at 8:46 PM, Albert Astals Cid <[email protected]> wrote: > El Dissabte, 29 de desembre de 2012, a les 06:28:09, Jaydeep Solanki va > escriure: > > On Sat, Dec 29, 2012 at 5:25 AM, Albert Astals Cid <[email protected]> > wrote: > > > El Dissabte, 29 de desembre de 2012, a les 04:47:08, Jaydeep Solanki va > > > > > > escriure: > > > > All the libraries that Okular generators use, do all of them generate > > > > > > text > > > > > > > in the correct order ? > > > > By correct order I mean, following the layout (eg. two column, three > > > > column). > > > > As far as I have noticed poppler genereates in the correct order. > > > > > > I don't understand your question. > > > > 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. > > [image: Inline image 2] > > > > 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, > > > > [image: Inline image 3] > > So my question is do all the libraries that the generators of okular use, > > generate text in the proper order considering the layout ? > > What does this have to do with "Unfolded table of contents folds in upon > reloading of document"? > > Or you forgot to create a new thread and you indeed speaking about > something > different? > > Albert > > > > > > Cheers, > > > > > > Albert > > > > > > > On Fri, Dec 28, 2012 at 5:57 AM, Albert Astals Cid <[email protected]> > > > > > > wrote: > > > > > El Divendres, 28 de desembre de 2012, a les 01:48:55, Jaydeep > Solanki > > > > > > va > > > > > > > > escriure: > > > > > > I would like to give it a try, please point me to the source. > > > > > > > > > > You know where the source is ;-) > > > > > > > > > > Have you tried searching for where the code that is responsible of > > > > > this > > > > > before > > > > > asking? > > > > : > > > > :D you got me.. > > > > : > > > > > > & in the case where the toc is updated/changed, I guess that part > > > > > > should > > > > > > > > > remain folded & the rest should restore to it's previous state. > > > > > > What's > > > > > > > > your > > > > > > > > > > > opinion on this ?? > > > > > > > > > > Let's go the easy way for now "a) Keep the toc view in its present > > > > > > state > > > > > > > > if > > > > > the toc hasn't changed at all. Otherwise fold it completely" > > > > > > > > > > > btw is this for the reload action only, or is it about to store > it & > > > > > > restore when the document is opened again? > > > > > > > > > > Reload only. > > > > > > > > > > Cheers, > > > > > > > > > > Albert > > > > > > > > > > > -Jaydeep > > > > > > > > > > > > On Thu, Dec 27, 2012 at 2:35 AM, Albert Astals Cid < > [email protected]> > > > > > > > > > > wrote: > > > > > > > https://bugs.kde.org/show_bug.cgi?id=312138 > > > > > > > > > > > > > > Albert Astals Cid <[email protected]> changed: > > > > > > > What |Removed |Added > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > --> > > > > > > > > > > > > > > Keywords| |junior-jobs > > > > > > > > > > > > > > --- Comment #4 from Albert Astals Cid <[email protected]> --- > > > > > > > Marking this as a junior job, it should be pretty easy to store > > > > > > > the > > > > > > > > > > whole > > > > > > > > > > > > tree > > > > > > > of the TOC when we trigger the reload and check if the tree is > the > > > > > > > same > > > > > > > after > > > > > > > it has happened. Interested people in implementing the junior > job > > > > > > > > > > please > > > > > > > > > > > > contact the [email protected] mailing list if you decide to > > > > > > have a > > > > > > > > > > look at > > > > > > > this. > > > > > > > > > > > > > > -- > > > > > > > You are receiving this mail because: > > > > > > > You are the assignee for the bug. > > > > > > > _______________________________________________ > > > > > > > Okular-devel mailing list > > > > > > > [email protected] > > > > > > > https://mail.kde.org/mailman/listinfo/okular-devel > > > > > > > > > > _______________________________________________ > > > > > Okular-devel mailing list > > > > > [email protected] > > > > > https://mail.kde.org/mailman/listinfo/okular-devel > > > > > > _______________________________________________ > > > Okular-devel mailing list > > > [email protected] > > > https://mail.kde.org/mailman/listinfo/okular-devel > _______________________________________________ > Okular-devel mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/okular-devel >
_______________________________________________ Okular-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/okular-devel
