How to make Sigil live (in calibre)

[mrmikel]

The book check works well and is easy to use, but the effect of no doctype is to make all   invalid. Solved with a search and replace.

To avoid support headaches for yourself, it might be worthwhile to have an error message when these named entities are found which explains what to do.

[kovidgoyal]

@mrmikel: Errors caused by named entities with no doctypes should be automatically fixed, when you click the Try to fix automatically link in the error description. Or by the Fix HTML files tool.

[kovidgoyal]

@Divingduck: Unfortunately, the inability of the inspector to work in an undocked window is a limitation of Qt, I will see if I can find a workaround, but I'm not very hopeful.

[Divingduck]

Originally Posted by kovidgoyal

I have re-organized the menu to move delete to the bottom so that if the first action in the menu does get accidentally triggered by a bounce click it will be less harmful.

Short feedback. Problem solved. Thanks.

[Katsunami]

Originally Posted by kovidgoyal

@Katsunami: These kinds of problems are deep in Qt code and that makes debugging them a real pain. For something as trivial as this, it isn't wortht he effort.

If you think it best to just remove the ampersands, then I won't be the one complaining

Off the top of my head, the onlything I can think of is that are you using the calibre style or the system default widget style? Preferences->Look & Feel in calibre.

I'm using the system style. I like this better than the calibre style, but that is just a matter of taste of course.

[Perkin]

Thanks Kovid, my few problems (with Tweak Book ) have been fixed.

Just got to try and do full test.

[mrmikel]

Kovid, just how is the HTML fixed? Is HTML Tidy involved?

[kovidgoyal]

@mrmikel: No tidy is not involved. If XML parsing fails, the HTML 5 algorithm is used to parse and convert the tree into XHTML. Therefore, the end result of the fixing would be identical to viewing the html in a modern browser as text/html.

[theducks]

Originally Posted by kovidgoyal

Just uploaded some new betas to http://download.calibre-ebook.com/betas/

They include a new Book Check tool that finds well-formedness errors in XML/XHTML, invalid images, images in CMYK colorspaces and broken links. More checks will be added later.

Also fixed the bugs reported by arspr for css syntax highlighting and jackie_w for nbsp handling.

Finally, links in the preview panel are now clickable.

Getting there (fast)
I just beat the stuff out of 'Merge' (XP 1.14 beta version) and it was sweet.

(I over shot by 2 segments and had to do a Manual Split , Not so easy .)

[jackie_w]

@theducks,

Splitting files seems pretty nice and easy to me, or were you just joking?

[theducks]

Originally Posted by jackie_w

@theducks,

Splitting files seems pretty nice and easy to me, or were you just joking?

No!
I obviously, am missing something

[jackie_w]

Originally Posted by theducks

No!
I obviously, am missing something

Allow me to enlighten, then
1. Open the html file you want to split.
2. Press the little 'snapdragon' icon, 3rd from left, below the Preview pane.
3. Move mouse over Preview and a green horizontal line appears
4. Once it's in the place you want to split, left-click mouse.
5. Admire the ease and simplicity!

[arspr]

Originally Posted by kovidgoyal

Just uploaded some new betas to http://download.calibre-ebook.com/betas/

They include a new Book Check tool that finds well-formedness errors in XML/XHTML, invalid images, images in CMYK colorspaces and broken links. More checks will be added later.

Also fixed the bugs reported by arspr for css syntax highlighting and jackie_w for nbsp handling.

Finally, links in the preview panel are now clickable.

Just downloaded and performed a quick test with the new Book Check. I've found two strange things which I don't know if are intended or not:

• It gives a "Parsing failed: Entity 'nbsp' not defined" error/warning on   appearances
• It gives a "The linked resource 'page-template.xpgt' does not exist" in a css file. And I can swear that it exists and it is correctly included in content.opf (<item href="Misc/page-template.xpgt" id="page-template.xpgt" media-type="application/vnd.adobe-page-template+xml"/>). But the weirdest thing is that my actual CSS reference line is commented out (/*@import url(page-template.xpgt);*/)

I can confirm that CSS colors bug seems correctly fixed.


And now a feature request/suggestion if possible. I've followed the discussion about &nbsp; being substituted by unicode code. I suppose this issue will happen with a lot of similar "characters". This is probably the right decision if you've taken it BUT it causes a little additional trouble: How do I look for that new &nbsp; equivalent? I mean How do I type it?

And therefore my suggestion: please could you add an Insert symbol tool, similar to MS Word one as example, which contained every single possible character sorted in an user-friendly way? This new "typing" help should be active in both text editor AND in the search/replace text boxes. This feature would be also helpful when typing foreign letters in other keyboards (like specially accented letters, Spanish ñ, French ç, ...)

Feasible or interesting? Or right stupid suggestion?

[jackie_w]

@arspr,

The nbsp BookCheck error is (I think) because it is a named entity and the html file does not have a DOCTYPE. If you click 'Try to correct fixable error automatically' in the right BookCheck pane all the &nbsp entities will be converted to the unicode char \xA0 which doesn't need the DOCTYPE. Then that error will be gone.

The xpgt error may be because it isn't normally called by an @import into css but instead as a
<link href="../Styles/page-template.xpgt" rel="stylesheet" type="application/vnd.adobe-page-template+xml"/> statement in the header of each html file.

And if you want to Find the unicode nbsp char just type \xa0 in the Find: box and change search Mode to Regex.

[eschwartz]

Originally Posted by arspr

And now a feature request/suggestion if possible. I've followed the discussion about &nbsp; being substituted by unicode code. I suppose this issue will happen with a lot of similar "characters". This is probably the right decision if you've taken it BUT it causes a little additional trouble: How do I look for that new &nbsp; equivalent? I mean How do I type it?

And therefore my suggestion: please could you add an Insert symbol tool, similar to MS Word one as example, which contained every single possible character sorted in an user-friendly way? This new "typing" help should be active in both text editor AND in the search/replace text boxes. This feature would be also helpful when typing foreign letters in other keyboards (like specially accented letters, Spanish ñ, French ç, ...)

Feasible or interesting? Or right stupid suggestion?

Sounds reasonable. That's what Sigil does...