[Valloric]

Originally Posted by JohnnyD

Hi Valloric,

first of all: thanks for Sigil, it looks like a perfect solution for creating epub documents.

Thanks.

Originally Posted by JohnnyD

- it's a bit slow when editing a document of 50 chapters (but if I'm correct, you're allready working on that)

Yes, working on it. Performance will go way up after the redesign to a multi-flow editing environment.

Originally Posted by JohnnyD

- a css-editor would be very much appreciated! At this moment, I open up the epub file (after renaming it to .zip) to get access to the css file inside. Quite tedious and risky!

All of your CSS files are copied to <style> tags which you can see (and edit) in Code View. The <style> tags are converted back to explicit CSS files on export.

But a dedicated CSS editor should come with the aforementioned redesign.

Originally Posted by JohnnyD

- something of a script engine would be nice, for example to automaticaly insert "drop capital" code at the start of every chapter

I've been thinking about exposing the internals of Sigil to an embedded version of Python (or Lua, or C# through embedded Mono). This should let you do what your asking, and much more.

What do others think of this?

Originally Posted by JohnnyD

(I'm not really sure about this, but my BeBook does not seem to find the Garamond font file which I copied to my Bebook font directory. However, when I manually include the font file in my epub file, it will display my Garamond text correctly).

See this thread for embedding permanent fonts on a Reading Device for use in all epubs. It's for the Sony Reader's, but maybe there's some information for BeBook users. Especially if BeBook uses ADE.

Originally Posted by JohnnyD

- font management. This would mean maintaining a font directory in the epub file and adjusting the css file accordingly.

I was planning on shipping 0.1.0 with font embeding support, but the Qt Framework (on which Sigil is built) has some bugs in this area so the feature was left out. Point being, some memory issues are causing Qt's version of WebKit to segfault on exit if the application uses localy referenced fonts. It's a bit complicated. Some font embedding functionality is still present in Sigil but is unsupported.

I've tested Sigil against the tech preview of the next version of Qt (4.6.0), and it doesn't seem to crash. Still fails to load alternate fonts though...

I'll take another look at this when 4.6.0 ships, which should be in about a month or two. If they haven't fixed it by then, I'll bloody well fix it myself in a forked version of Qt. Nokia is starting to piss me off on this and many other Qt issues.