Quote:
Originally Posted by DiapDealer
It doesn't matter a whit, functionally. The file's extension does not determine how Sigil treats the content.
Sigil should (depending on the version of course) create a new, Blank HTML File with a .xhtml extension (ironic, I know). Splitting, merging, or importing existing files will retain the original extension (whatever it was). But your Sigil epub will work equally well with all .html extensions, all .xhtml extensions or any mixture of the two.
Many just find a nice, consistent file extension to be aesthetically ... soothing. I hardly ever notice the file extensions myself...
...until I DO notice them...
...and then I can't un-notice them...
...not until they once again fade into the comforting obscurity that conformity provides, anyway. 
Bottom line is: if you don't mind ... Sigil doesn't either. It also doesn't mind if you DO mind. |
Thanks Diap. That's a big relief. Now I just have to make sure if I have links that they match up with the .html or .xhtml endings. What's weird though is I have several Sigil windows open right now and using the 'add blank html file' some of the windows create an html file and using the 'add blank html file' in other windows they create xhtml files.
I guess it really doesn't matter but I wonder why it's doing that.
Thanks man. I have a ton of work to do and your reply is really freeing me up.