View Single Post
Old 09-28-2017, 10:53 AM   #18
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,676
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
Or perhaps we create an unmanifested file additional Report?
That would probably be easy enough.

I've never really delved very deeply into the OpenWith code, so I have no idea what would be involved, but it doesn't seem to me that it would be impossible to employ an approach that:

1) copied the file in question to a new temp folder and opened that file in the external editor
2) after the editing is complete, copy ONLY the original filename back to the epub's scratch directory.

Checks could of course be made to determine whether the file was changed or not, and if the original file name is no longer present in the staging temp location (like with an unwise rename), a warning could be popped that nothing is being changed.

Just spit-balling, really. I just don't want to introduce anything into the Open With code that would require any kind of parsing/modification of the EPUB's manifest. File out ... same file name back in.

Last edited by DiapDealer; 09-28-2017 at 11:04 AM.
DiapDealer is offline   Reply With Quote