Regarding the images that weren't imported:
Quote:
Originally Posted by Valloric
Please create an issue and attach the HTML and the folder where the images are located (before import).
And yes, Sigil will import your images and transfer them to a "images" folder in the temporary folder where all your book's resources are being stored.
|
Opened, bug
#39
A note regarding issue
#21 TOC H1/Span issue, just wanted to note I'm seeing this too. Unfortunately the workaround of "Don't do it" isn't really a workaround. Many of us are format shifting and this weird kind of formatting happens with a lot of tools which convert to html.
Below is some other feedback/wishlist type stuff. I can open some bugs for anything that sounds amenable.
CSS handling:
- Would be awesome if all the css styles showed up in the drop down list of styles. Right now everything not in a heading tag just shows up as 'normal', regardless of the number of styles that are actually in the epub.
- Related to that, if that were supported it would be great if a user could create human readable names for the styles, but this could be mitigated if the styles in the drop-down just listed the attributes set in the style
- Equally great would be to be able to search or highlight document text by style. Often in format shifted content you get a large number of styles and it's difficult to tell the good from the bad so that one can homogenize them
Would be great to see the following types of things be inputs into the TOC editor:
- Support listing all items with specific css style(s) applied
- Support listing all items matching a regex
- Possibly support more generic things like bolded text, or text above a certain size, etc
Other formatting niceties
- Would be great to be able to insert page breaks as an alternative to Chapter markers
- Margin settings would be nice, though this could be delayed if css elements were automatically added to the drop-down list as requested above
- Being able to set Blockquotes with a button would be a nice alternative to margins as well
- Raised Caps and Drop Caps support would be great, one way to handle this would be for Sigil to create but not use a css style that does each. If the all the css styles showed up in the drop down list the user need only apply the style. If they prefer slightly different settings they need only edit the css from the default