https://bugs.kde.org/show_bug.cgi?id=301774
nizamov.shaw...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nizamov.shaw...@gmail.com
--- Comment #13 from nizamov.shaw...@gmail.com ---
Thank all developers for the annotations feature working "right" - embedding
them into the file (how it is generally assumed). But it does not save them in
the same file, which was opened (no "save" option) - this is what this bug is
about. This really limuts the usefullness of the annotations feature.
However, reading the response of Albert, I realize that there might be a good
reason - if overwriting the existing file actually corrupts its content, then
the file is lost.
In this case the following two features would be really helpful:
1) pressing "Save as" or "Export as" should point exactly to the folder, where
the opened file is. Now (at least on my pc) it points to the last saved folder
and I have to find folder with the original file. Sometimes it is not easy -
e.g., I open pdf attachements from zotero/firefox and it stores pdf's in its
own file hierarchy with randomized folder names.
2) there may be an option of automatically saving the file with slightly
modified filename (***-annotated.pdf). This way the original file remains
intact, and all annotations go to the annotated file. Later if we open the
file, and its filename conatins already "annotated" mark and there also exists
a file with filename without this mark in the same folder (it means that we
opened already annotated file and we have also an original file nearby), than
the annotated file will be overwritten. What will you loose in the worst case
is your annotations. This is how it works in Goodreader - very popular pdf
annotation software which I use on ipad.
Preferably, both features should be combined - so that pressing "Save" will
point to the folder with original file and suggest a filename with defined
annotation mark. If it was detected that the file is already an annotated
version of original, then annotated file will be overwritten without asking
anything.
As an additional feature, one might think about always opening the annotated
version instead of original. On one hand it might be misleading - you clicked
on original in file browser but got an annotated version of it opened, on the
other hand you will not accidentally overwrite annotation made previously, if
you opened the original, made something to it and saved.
The advantage of such workflow is that original file is always retained - so
this is safe. And you can always give someone the original file without
annotations if required.
Sorry, if i am asking too much, and best wishes
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel
