Quote:
Originally Posted by JimLL
First, I am not an HTML programmer and am not determined to use HTML or whatever variations of HTML are out there. But the loaded XYZTML-whatever is altered in order to put out, via Sigil code, the epub. So it seems to me to be common sense that if something happens to the epub file it wouldn't make any sense at all to have to go back to the originally loaded HTML and start from scratch when a very simple HTML save would obviate the need. Of course there will always be those who say no such problem could arise. That's a lot like being told by a clerk that computers never make mistakes.
Interesting little assumption you've got going there.
I don't know xhtml from qwhtml. I'm just seeing an easy fix to a possible problem and a lot of people "bound and determined" to maintain the status quo.
|
Sigil doesn't save as html simply because it checks for, and saves, VALID ePUBs--not html files. That's the entire story. Whether you want to work in html, xhtml, etc.--you seem to be missing the point. All I said was, if you want to work in html, use an html editor, which Sigil isn't. This is simply
square peg-round hole-ing. Does it make sense that if you want to work in html, you'd use a tool designed for html? Sigil isn't. That's all I meant. Otherwise, you upload html and what you "save as" is an ePUB. Not html. If you've read the thread, you'll see that there are a number of very good reasons why it saves as an ePUB, all of which are part of its basic functionality. It's not an "easy fix," unless we all think that throwing out Sigil's essential validity-checking is a good idea, which I suspect most of us don't. It has nothing to do with maintaining the "status quo;" everyone around here contributes, one way or the other, to
improving Sigil
all the time. If enough OTHER people and users agree with you, then generally speaking, if it's possible, user_none, meme, etc., will make a change to the program--but thus far, it doesn't seem like anyone but you thinks that this is a big issue.
And your snarkiness on the topic seems
utterly disproportionate to the issue at hand. Want html? Use an html editor. Want an epub? Use an ePUB editor. Conflating them simply confuses the issue. In the alternative, maybe you'd be happier with Jutoh or Calibre, or, I suspect, AWP (Atlantis Word Processor). Then you really don't need to use html at all.
Lastly, you haven't explained, at ALL, why saving as an ePUB--which is nothing more than a bunch of zipped xhtml/html files--is such a big problem for you. So you save as an ePUB and keep working in Sigil? What, exactly, is the actual issue that this causes for you? You don't have to "go back to the original html" at all, after saving the epub, so, can you explain why this is so problematic? Save and keep editing. if you need to extract the file and put it back in an html editor, for whatever reason, simply explode the epub and grab the file you need and drag it into your html editor, OR, work in Sigil, OR, work in "tweak ePUB" in Calibre, depending upon your skill level. I don't think anyone understands--I certainly don't--why you find saving the file as an ePUB such a large hurdle, or how it negatively impacts your workflow.
Good luck.
Hitch