When Calibre Goes to Sigil in HTML *and* XHTML

Tulpana · 07-08-2012, 07:43 PM

My 265-page WORD-generated manuscript was chopped up by Calibre into several chunks. Every new chunk opened in Sigil with one of the chapters identified as HTML--after which, the successive chapters were XHTML.

Is this something to worry about, and, if so, is there any way to get Sigil to turn the HTML into XHTML before you start heavy-editing?

I am a WYSIWIG user, or at least I know next-to-nothing about HTML (although I'm catching on).

Thank you.

theducks · 07-08-2012, 08:41 PM

Quote:

Originally Posted by Tulpana

My 265-page WORD-generated manuscript was chopped up by Calibre into several chunks. Every new chunk opened in Sigil with one of the chapters identified as HTML--after which, the successive chapters were XHTML.

Is this something to worry about, and, if so, is there any way to get Sigil to turn the HTML into XHTML before you start heavy-editing?

I am a WYSIWIG user, or at least I know next-to-nothing about HTML (although I'm catching on).

Thank you.

IMHO either is fine if it is there. There are slightly different rules for each. Sigil checks each by the proper rules.

mrmikel · 07-08-2012, 08:57 PM

It is important to leave the chunks, rather than try to reunite them. There are some readers that will choke on sections over 250k or so. Chunks for each chapter are generally convenient for editing and under the size limit. The reader will display all the chunks as if they were one.

Sigil is not shy in telling you if you goof up, though if you leave off the closing > of a paragraph command, it is likely to tell you that the end of the section needs a </p> instead of the actual location much farther back!

DiapDealer · 07-09-2012, 12:54 AM

The actual file extension that shows in Sigil isn't anything to get excited about. Files named with a .html or .htm extension are still XHTML internally. There's no pressing need to make all the extensions .xhtml.

Toxaris · 07-09-2012, 01:20 AM

Also, I would be careful in letting Calibre determine the chunks. Most crafters create a separate file for each chapter. Partially to avoid the size restrictions, partially because it is better maintainable.
By default Calibre will cut the file based on the length instead of the chapters. Altough I have been told you can ask Calibre to do it per chapter. That is, if Calibre can determine the chapters...

Tulpana · 07-09-2012, 07:44 AM

Again, thanks to everyone. I produced a fine product with Sigil and Calibre, using one huge file. I just wanted to know if I had anything to worry about, and apparently, I do not.

theducks · 07-09-2012, 10:03 AM

Quote:

Originally Posted by Toxaris

By default Calibre will cut the file based on the length instead of the chapters. Altough I have been told you can ask Calibre to do it per chapter. That is, if Calibre can determine the chapters...

That works when Calibre can determine it (via Xpath):

Code:

//*[((name()='h1' or name()='h2') and re:test(., 'chapter|book|section|part\s+', 'i')) or @class = 'chapter']

or Chapter mark
There are oh-so-many ways to confuse this feature

07-08-2012, 07:43 PM	#1
Tulpana Enthusiast Posts: 22 Karma: 470232 Join Date: Feb 2012 Device: Entourage Pocket Edge	*When Calibre Goes to Sigil in HTML and* XHTML** My 265-page WORD-generated manuscript was chopped up by Calibre into several chunks. Every new chunk opened in Sigil with one of the chapters identified as HTML--after which, the successive chapters were XHTML. Is this something to worry about, and, if so, is there any way to get Sigil to turn the HTML into XHTML before you start heavy-editing? I am a WYSIWIG user, or at least I know next-to-nothing about HTML (although I'm catching on). Thank you.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
html to epub via Sigil or Calibre?	Bigo2	Calibre	2	07-01-2012 02:07 AM
HTML Anchor in XHTML	arreke	Sigil	3	12-27-2010 01:28 PM
Several xhtml/html to a single epub file help.	clowe1028	ePub	3	03-21-2010 03:47 AM
Jetbook HTML (XHTML)	rogue_ronin	Ectaco jetBook	19	02-12-2010 09:13 PM
xml or xhtml to basic html converter	remjax	Reading and Management	11	07-14-2009 09:04 AM

07-08-2012, 08:57 PM	#3
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	It is important to leave the chunks, rather than try to reunite them. There are some readers that will choke on sections over 250k or so. Chunks for each chapter are generally convenient for editing and under the size limit. The reader will display all the chunks as if they were one. Sigil is not shy in telling you if you goof up, though if you leave off the closing > of a paragraph command, it is likely to tell you that the end of the section needs a </p> instead of the actual location much farther back!

07-09-2012, 12:54 AM	#4
DiapDealer Grand Sorcerer Posts: 27,546 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	The actual file extension that shows in Sigil isn't anything to get excited about. Files named with a .html or .htm extension are still XHTML internally. There's no pressing need to make all the extensions .xhtml.

07-09-2012, 01:20 AM	#5
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	Also, I would be careful in letting Calibre determine the chunks. Most crafters create a separate file for each chapter. Partially to avoid the size restrictions, partially because it is better maintainable. By default Calibre will cut the file based on the length instead of the chapters. Altough I have been told you can ask Calibre to do it per chapter. That is, if Calibre can determine the chapters...

07-09-2012, 07:44 AM	#6
Tulpana Enthusiast Posts: 22 Karma: 470232 Join Date: Feb 2012 Device: Entourage Pocket Edge	Again, thanks to everyone. I produced a fine product with Sigil and Calibre, using one huge file. I just wanted to know if I had anything to worry about, and apparently, I do not.

Advert

Advert