tYYGH
tYYGH
See also https://github.com/openpaperwork/paperwork/issues/548#issuecomment-383544821 Just to say that the screen resolution is not always the window size ;-) (Which is why I am so annoyed when Gtk applications like Evince get...
While the idea is interesting, it would need to be associated with a per-document “OCR-lock” feature, so that the “redo all OCR” feature does not overwrite all the carefully edited...
In case someone is interested, I wrote a Web viewer, and I checked that it renders well on my Android phone: http://yalis.fr/cms/index.php/post/2016/01/21/Command-line-and-Web-Interface-for-Paperwork Cheers,
It could indeed be the first step to a whole new set of features based on “layers”/shares. Eg. * just like in ownCloud each user could have their own papers...
@tiramiseb Don't you mean "that becomes opaque when hovering"? Oh, I see! You mean the text would get displayed by default! And hovering would allow to see "below". This won't...
Later on, if the icon is always present, this interface could replace the extra-text part of the properties and become the standard way of entering extra text… if you don't...
Good idea. It’s like what the video editors do: they do not alter the sources, but remember instead what must be applied to the sources, and when, to produce the...
I’m not sure this is a good idea: * How will this put less stress on the filesystem? The overall size should be almost the same since PDF and JPEG...
That would be a reasonable compromise indeed.
I can confirm that Paperwork is not optimized for big documents. My stats are such: — 3 documents with >100 pages (max 158 pages) — 63 documents with 16–99 pages...