View Single Post
Old 11-11-2018, 09:42 AM   #4
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,699
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by mrprobert View Post
Sorry, I don't know what you mean by "unpacked epubs".
That's because it's barely relevant to your question.

To answer your question: Yes. "CON" is a reserved file name on Windows. It has been since the days of DOS. Same with "NUL".

What Sarmat was cryptically alluding to is that Sigil doesn't work directly on the EPUB file (which is nothing more than a zip archive). It unzips the EPUB to a temporary working directory where all modifications are made. The changes are then written back to the original EPUB whenever a "Save" operation in performed (this is so one can always close without saving and not risk modifying the original EPUB). So while "con.css" is a perfectly acceptable filename inside of a zip archive (even on a Windows system), Sigil cannot rename a file to "con.*" in the temp directory where Sigil is enacting its changes because it violates Windows filesystem rules.

Last edited by DiapDealer; 11-11-2018 at 09:45 AM.
DiapDealer is offline   Reply With Quote