Robustness - Page 6

JimLL · 04-08-2012, 02:25 PM

Quote:

Originally Posted by Elfwreck

It's an open source program; feel free to do the programming yourself.

Cute. Clever. Brilliant.

Quote:

A crowd of people familiar with the software don't seem to see any need for the feature you want, which seems to be at cross purposes to the software itself.

Why use Sigil to edit & save HTML files? Why not use an HTML editor like Notepad++?

I don't get how you would pull the altered HTML out of Sigil with a separate app. Of course I could go through the process of copying from the HTML display, but coding a save wouldn't take much more time than going through that just once or twice.

And as far as the crowd is concerned, I already started another thread about having a disaster that HTML save would have prevented.

Of course I can see how my idea would cause SEVERE damage to Sigil.

Toxaris · 04-08-2012, 02:42 PM

Quote:

Originally Posted by JimLL

Apps like Jutoh, etc., are great for people who are making books commercially, but over the top for home stuff done by retirees.

Furthermore, the programming I suggested is trivial.

I fully disagree. People who are making books commercially should stay far away from programs like Jutoh. The quality of those programs is not just up to par for commerce.

Again, the programming you suggest is NOT trivial as various people, including me, have told you time and time again.

I really recommend reading up on the ePUB format and learn at least basic HTML/CSS. If you don't want to, fine. However, then Sigil is not for you and you should stick to Atlantis Word Processor or Jutoh.

Toxaris · 04-08-2012, 02:43 PM

Quote:

Originally Posted by JimLL

And as far as the crowd is concerned, I already started another thread about having a disaster that HTML save would have prevented.

Great, can't wait to read it. So far none of your threads describe such a disaster.

capidamonte · 04-08-2012, 04:27 PM

Solution in Sigil to extract HTML (in Code view):

1) Merge all separate HTML pages to a single page.
2) Remove all duplicate <html>, <head> and <body> tags. (Generally, there is no functional need for separate CSS pages for different sections of a book. However, retain all CSS links as necessary.)
3) Select All, Copy and Paste into your HTML editor.
4) Save appropriately to disk.
5) Repeat (3) and (4) for your CSS page(s). (Do not merge.)
6) Edit as you will.
7) Reopen in Sigil to create ePub.

Sunlite · 04-09-2012, 03:48 AM

Why so complicated?

1) Save as epub.
2) open the created epub with a zip tool.
3) take the html file you want a put it where ever you want.

If you started with one file and haven't split it yet. There will be only one file still.

You can even work on the file and the re-insert it in the epub using the zip tool and all your changes will show up in the epub.

JimLL · 04-09-2012, 02:54 PM

Quote:

Originally Posted by Toxaris

I fully disagree. People who are making books commercially should stay far away from programs like Jutoh. The quality of those programs is not just up to par for commerce.

Again, the programming you suggest is NOT trivial as various people, including me, have told you time and time again.

I really recommend reading up on the ePUB format and learn at least basic HTML/CSS. If you don't want to, fine. However, then Sigil is not for you and you should stick to Atlantis Word Processor or Jutoh.

OK, fine. Disagree. Jutoh is not for commercial operations. But it still costs too much for us fixed income folks. (Hmm. You got something against fixed income folks?)

As for reading up and learning, it's not a matter of wanting to, altho folks always seem to assume a poster they disagree with is lazy. I passed all chance of reading up and learning when the stroke hit 25 years ago. My short term memory is all but gone. Reading up sticks for about 2 minutes. Learning a new system is just not in the cards.

As for trivial coding, I've coded saves and it IS trivial unless you want to tie it in with all sorts of other stuff. I suggested auto saves. That would be trivial. You put the HTML filename in a variable (that's probably already done). You put on a timer. You save file by name. Trivial.

Even if you save it on keyboard input all the IF code about whether something has gone wrong or not isn't needed. Just tie the routine to a toolbar, watch for the keypress and do the save. My memory may be short, but I'm not stupid. It's still trivial, and it wouldn't damage ANY of the people who declare it would be an awful, horrible, terrible thing to do. It's just a button on a toolbar, for crying out loud. How is that going to damage a user?

Of course if you WANT it to be complicated so you can argue against it...

Perkin · 04-09-2012, 04:57 PM

Quote:

Originally Posted by JimLL

As for reading up and learning, it's not a matter of wanting to, altho folks always seem to assume a poster they disagree with is lazy. I passed all chance of reading up and learning when the stroke hit 25 years ago. My short term memory is all but gone. Reading up sticks for about 2 minutes. Learning a new system is just not in the cards.

So what are you trying to learn a new system (Sigil) for, I know you may want to learn to use it properly, but if you can't retain the memories of how to use it then it's going to be very difficult to use, whether there's auto save or not.

user_none · 04-09-2012, 07:12 PM

Quote:

Originally Posted by JimLL

As for trivial coding, I've coded saves and it IS trivial unless you want to tie it in with all sorts of other stuff. I suggested auto saves. That would be trivial. You put the HTML filename in a variable (that's probably already done). You put on a timer. You save file by name. Trivial.

And then you realize you deleted a section by accident. You close and reopen the file expecting it to restore your last save only to find out it auto saved with the missing section.

PeterT · 04-09-2012, 07:21 PM

Quote:

Originally Posted by user_none

And then you realize you deleted a section by accident. You close and reopen the file expecting it to restore your last save only to find out it auto saved with the missing section.

Well obviously we need multiple versions of the autosave files; surely that will be easy to implement

Hitch · 04-09-2012, 08:11 PM

Quote:

Originally Posted by PeterT

Well obviously we need multiple versions of the autosave files; surely that will be easy to implement

I want the autosave that would have saved me all those PSOD's (Pink Screens O'Death) that I had my first YEAR of Sigil. I DEMAND the autosave that saved me from myself. I DEMAND the autosave that would have saved my ePUB in a corrupted format, immediately after the PSOD destroyed my entire ePUB and the hours spent on it.

I INSIST!

It's clearly trivial. I'm insulted you don't hop to and implement it immediately.

Hitch

theducks · 04-09-2012, 08:20 PM

Quote:

Originally Posted by Hitch

I want the autosave that would have saved me all those PSOD's (Pink Screens O'Death) that I had my first YEAR of Sigil. I DEMAND the autosave that saved me from myself. I DEMAND the autosave that would have saved my ePUB in a corrupted format, immediately after the PSOD destroyed my entire ePUB and the hours spent on it.

I INSIST!

It's clearly trivial. I'm insulted you don't hop to and implement it immediately.

Hitch

Lets face it
You are tired of all those backup clay tablets falling off the stack onto your toes

Elfwreck · 04-09-2012, 08:41 PM

Quote:

Originally Posted by JimLL

As for trivial coding, I've coded saves and it IS trivial unless you want to tie it in with all sorts of other stuff. I suggested auto saves. That would be trivial. You put the HTML filename in a variable (that's probably already done). You put on a timer. You save file by name. Trivial.

"The" HTML filename? When I make epubs with Sigil, every chapter and each of the front sections is its own HTML file. There's also the toc.ncx and contents.opf files, which I sometimes wind up tweaking, and of course any .css files I've included. Does the autosave make a backup of each separate file?

As already mentioned, it can't autosave the whole .epub unless it turns off the error-check feature. I'd rather have something that warned me "this can't save because it's not functional" than something that auto-saves. I can remember to hit ctrl-S every minute or two (and if I get an error message, be forced to go fix it); I don't want to think I've got a readable ebook when I don't.

DiapDealer · 04-09-2012, 09:01 PM

Trivial! Trivial, I say!

Hitch · 04-09-2012, 09:34 PM

Can we rename this Thread? Trivial Pursuit?

Quote:

"The" HTML filename? When I make epubs with Sigil, every chapter and each of the front sections is its own HTML file. There's also the toc.ncx and contents.opf files, which I sometimes wind up tweaking, and of course any .css files I've included. Does the autosave make a backup of each separate file?

Perzackly. What happens, with "THE" HTML filename, to the CSS file I imported automagically? The images? What about my oh-so-snazzy colophon image? The publisher's logo? The....yadda...

Quote:

Lets face it
You are tired of all those backup clay tablets falling off the stack onto your toes

Yes, Ducky, I'm busted. My wee Big toe is busted in more than 50 places (can you believe--nearly six damn weeks and it's still utterly bollixed?) and I AM sick of those clay tablets. They keep knocking over my abacus, dammit.

Hitch

JimLL · 04-10-2012, 02:06 AM

Quote:

Originally Posted by Elfwreck

"The" HTML filename? When I make epubs with Sigil, every chapter and each of the front sections is its own HTML file. There's also the toc.ncx and contents.opf files, which I sometimes wind up tweaking, and of course any .css files I've included. Does the autosave make a backup of each separate file?

Ah, I go out of my way to put everything into one single html file. It's way too much time to mess with bits and pieces. Yeah, that would make it more than trivial.

04-08-2012, 04:27 PM	#79
capidamonte Not who you think I am... Posts: 374 Karma: 30283 Join Date: Jan 2010 Location: Honolulu Device: PocketBook 360 -- Ivory	Solution in Sigil to extract HTML (in Code view): 1) Merge all separate HTML pages to a single page. 2) Remove all duplicate <html>, <head> and <body> tags. (Generally, there is no functional need for separate CSS pages for different sections of a book. However, retain all CSS links as necessary.) 3) Select All, Copy and Paste into your HTML editor. 4) Save appropriately to disk. 5) Repeat (3) and (4) for your CSS page(s). (Do not merge.) 6) Edit as you will. 7) Reopen in Sigil to create ePub. Last edited by capidamonte; 04-08-2012 at 07:14 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
iRiver Story HD robustness	gcobb	iRiver Story	0	08-18-2011 04:26 PM
DR800: robustness	alexxxm	iRex	13	08-10-2010 04:17 AM

04-09-2012, 03:48 AM	#80
Sunlite Addict Posts: 206 Karma: 547516 Join Date: Mar 2008 Location: Berlin, Germany Device: KObo Clara, Kobo Aura, PRS-T1, PB602, CyBook Gen3	Why so complicated? 1) Save as epub. 2) open the created epub with a zip tool. 3) take the html file you want a put it where ever you want. If you started with one file and haven't split it yet. There will be only one file still. You can even work on the file and the re-insert it in the epub using the zip tool and all your changes will show up in the epub.

04-09-2012, 09:01 PM	#88
DiapDealer Grand Sorcerer Posts: 28,621 Karma: 204624552 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Trivial! Trivial, I say!

Advert

Advert