MobileRead Forums - View Single Post

ghostyjack · 03-03-2010, 05:43 PM

Yep, Sigil 0.2.0 is much faster will the new layout and although I did like the old single-flow look, I'm sure I'll get used to this new way of working as it allows me to concentrate on a much smaller block of text and stops me from loosing focus.

A few things I've noticed:
1. When importing a HTML file that includes the CSS code in it (and not in a separate CSS file) and then inserting a chapter break, all the css code now appears in the new xhtml file. I take it Sigil can't at present extract the CSS code and place it in a CSS file so that when splitting the file, I don't have to modify the CSS code in every split.

2. When splitting a file all the new files are xhtml files, but the first file is showing as a html file (a html file was opened in Sigil to create the book) and I can't rename it. Is this typical behaviour?

03-03-2010, 05:43 PM	#45
ghostyjack Guru Posts: 718 Karma: 1085610 Join Date: Mar 2009 Location: Bristol, England Device: PRS-T1, 1825PT, Galaxy Tab, One X, TF700T, Aura HD, Nexus 7	Yep, Sigil 0.2.0 is much faster will the new layout and although I did like the old single-flow look, I'm sure I'll get used to this new way of working as it allows me to concentrate on a much smaller block of text and stops me from loosing focus. A few things I've noticed: 1. When importing a HTML file that includes the CSS code in it (and not in a separate CSS file) and then inserting a chapter break, all the css code now appears in the new xhtml file. I take it Sigil can't at present extract the CSS code and place it in a CSS file so that when splitting the file, I don't have to modify the CSS code in every split. 2. When splitting a file all the new files are xhtml files, but the first file is showing as a html file (a html file was opened in Sigil to create the book) and I can't rename it. Is this typical behaviour?