[okular] [Bug 400103] Feature Request remember last used directory in places (Save as dialog)
https://bugs.kde.org/show_bug.cgi?id=400103 --- Comment #9 from zep...@gmail.com --- This should hopefully be an easy fix -- as I mentioned in the bug Nate Graham just merged with this one, Okular's "save copy as" used to have very acceptable behavior. Thanks, Pat -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 400103] Feature Request remember last used directory in places (Save as dialog)
https://bugs.kde.org/show_bug.cgi?id=400103 Nate Graham changed: What|Removed |Added CC||zep...@gmail.com --- Comment #8 from Nate Graham --- *** Bug 420139 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 420139] "Save copy as"
https://bugs.kde.org/show_bug.cgi?id=420139 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #4 from Nate Graham --- "Save Copy As" is not really a standard thing and it wouldn't be obvious what the difference between it and the standard "Save As" feature is. I think it might make more sense to have the "Save As" action remember the last-used save directory, as many other apps do. We've had various other requests for this. Marking as a duplicate of those, since implementing that feature would resolve this issue. *** This bug has been marked as a duplicate of bug 400103 *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 420139] "Save copy as"
https://bugs.kde.org/show_bug.cgi?id=420139 zep...@gmail.com changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 419109] Preserve extended attributes when saving a file
https://bugs.kde.org/show_bug.cgi?id=419109 --- Comment #10 from Manu --- (In reply to Stefan Brüns from comment #8) > (In reply to Manu from comment #6) > > maybe out of my depth here, but I think that goes against the baloo > > philosophy: if you do that, then *every* program handling the file must know > > about those attributes (acrobat reader, e.g., would probably crash); > > extended attributes are handled by the file system and you don't have that > > problem > > How is this related to baloo? Baloo just takes any metadata there is, and > does not care if it is stored inside the file or in extended attributes. I was thinking about special Baloo stuff (such as tags and comments) which do not depend on the particular file type (I didn't mean e.g., the bit rate in an mp3 file or the width and height of an image). I think Baloo (since a few years ago, anyway) stores/extracts metadata of the first kind into/from extended attributes. But I don't know that much about this...so maybe I'm wrong -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 419109] Preserve extended attributes when saving a file
https://bugs.kde.org/show_bug.cgi?id=419109 --- Comment #9 from tagwer...@innerjoin.org --- (In reply to Stefan Brüns from comment #7) > There is no "if ..." here. The naive view is applications ought to read, copy, save info in the extended attributes _as_if_ it was embedded in the file. It's a least surprise thing. If it's not possible (because of the filesystem say), they ought to give a warning... -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 394775] Annotations in the separated XML files
https://bugs.kde.org/show_bug.cgi?id=394775 --- Comment #11 from David Hurka --- I just remembered about Xournal. It’s a notetaking application, which can use PDFs as background. I never used it, and I’m not sure how much this paragraph applies to Xournal, but: > Fileformat > The fileformat *.xopp is an XML which is .gz compressed. PDFs are not > embedded > into the file, so if the PDF is deleted, the background is lost. (From Xournal README) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 419109] Preserve extended attributes when saving a file
https://bugs.kde.org/show_bug.cgi?id=419109 --- Comment #8 from Stefan Brüns --- (In reply to Manu from comment #6) > maybe out of my depth here, but I think that goes against the baloo > philosophy: if you do that, then *every* program handling the file must know > about those attributes (acrobat reader, e.g., would probably crash); > extended attributes are handled by the file system and you don't have that > problem How is this related to baloo? Baloo just takes any metadata there is, and does not care if it is stored inside the file or in extended attributes. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 419109] Preserve extended attributes when saving a file
https://bugs.kde.org/show_bug.cgi?id=419109 --- Comment #7 from Stefan Brüns --- (In reply to tagwerk19 from comment #5) > What would happen if this information was part of the file (rather than in > the extended attributes)? It would be copied/saved as part of the file and > managed within the app... There is no "if ..." here. Any metadata part of the file is in the scope of the application. Applications may or may not preserve any metadata (and sometimes it is not possible to preserve metadata, i.e. when you convert files to a different format without (structured) metadata). -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 419109] Preserve extended attributes when saving a file
https://bugs.kde.org/show_bug.cgi?id=419109 --- Comment #6 from Manu --- maybe out of my depth here, but I think that goes against the baloo philosophy: if you do that, then *every* program handling the file must know about those attributes (acrobat reader, e.g., would probably crash); extended attributes are handled by the file system and you don't have that problem -- You are receiving this mail because: You are the assignee for the bug.
