Open the working directory

[BetterRed]

Originally Posted by JimmXinu

Are you sure?

I see a temp directory created when I start Edit book, but all it contains is an equally randomly named file xxxxxx_worker_redirect.log -- which is empty, no matter what I do.

I don't see the exploded book there.

You're right, it's Sigil that unzips the entire epub to a 'temp' folder, which has its advantages - e.g. it enables editing of a 'book' in PageEdit.



When you open a file in an external editor from the calibre book editor then the file selected gets copied to 'a temp in the temp' folder.



If you need to externally edit multiple files you must open them one by one. Which is also true with Sigil, even though it exposes the entire book you can only externally edit the file selected.

BR

[JimmXinu]

Originally Posted by Comfy.n

On Windows, Editor unzips under C:\Users\user\AppData\Local\calibre-cache\ee\tmpXXX\a\00000-XXXXX

.... So it does.

Setting CALIBRE_TEMP_DIR does not control this dir. Setting CALIBRE_CACHE_DIRECTORY does. I've learned something new.

And this looks like the answer to jjk's original question.

But I would still suggest that for jjk's purposes, it would be safer to use 'Unpack book' rather than changing things in the temp dir. It looks like there's a lot going on in there. For a start, there's a copy per Edit book checkpoint.

[DNSB]

Originally Posted by BetterRed

If you need to externally edit multiple files you must open them one by one. Which is also true with Sigil, even though it exposes the entire book you can only externally edit the file selected.

Minor nit: With Sigil, if you open the content.opf and are using PageEdit, you can step forward/backward though the ePub. Personally, I haven'tr used the external editing capability since being burned by BookView and a couple of other WYSIWYG editors way back when.

[kovidgoyal]

Absolutely do not mess with the files in the editors temp directories, they are not normal files, they are hardlinks and the editor relies on nothing changing them outside its own code. If you want to access the files inside an ebook use unpack book, or better write a plugin for the editor that uses the container class do your work. That will be th emost robust and fleible solution.

[BetterRed]

I use PageEdit fairly often, always starting from the opf… mainly to correct transcription errors. Don't use it on xhtml files, occasionally use Notepad++ or Bowpad on them to shuffle slabs of text.

Never used Book View either… whenever I looked at it I'd ask myself "what is it for?"

[DNSB]

Originally Posted by BetterRed

I use PageEdit fairly often, always starting from the opf… mainly to correct transcription errors. Don't use it on xhtml files, occasionally use Notepad++ or Bowpad on them to shuffle slabs of text.

Never used Book View either… whenever I looked at it I'd ask myself "what is it for?"

BookView? It was intended to be a light weight visual editor for HTML files inside an ePub. Unfortunately, it had a nasty habit of messing up the files. For instance, if you selected a chunk of text, BookView would not be aware that part of it was already using an existing tag.

i.e. this <i>is a chunk of <span class="font>text that<i> should not be split</span>.

[BetterRed]

Never saw the point of wysiwg editing on a bit of a 'book', still don't.

[JSWolf]

However, given what the OP wants to do, I see no reason to need the uncompressed files of the ePub. Everything that needs to be done can easily be done in the calibre editor. I've done it plenty of times editing inDesign created ePub.

[theducks]

Bookview is for scrolling and spotting anomalies, then syncing the code LOCATION, so you can fix your screwup
I do not use a WYSWYG editor for code. (Only took 2 times when Sigil first came out, to see the mess it had left).

[DNSB]

I seem to remember BookView has not existed for several generations of Sigil. It was replaced after Sigil-0.9.14 by PageEdit (current version is 2.7.5) which does not have the issues that BookView had.