There was a discussion about this somewhere around here. Calibre (I think) just links all entries in the TOC with fragment identifiers and this slows down TOC display on mobile devices a great deal. If your heading is further away from a chapter break, the TOC entry will lead directy to that heading (using fragment identifiers). If you put a heading tag within 1000 characters after a chapter break, the entry in the TOC for that heading will lead to the begining of that XHTML file. These too you can place wherever you want. The TOC is built from heading tags (, where # is from 1 to 6). You have full access to the XHTML code! The Sigil WYSIWYG action "Insert Chapter Break" places a "marker" (that red double line) where your want your XHTML source to be split into multiple files. You can specify page breaks anywhere you want. All other books are unaffected.īTW this can be replicated in Calibre's ebook viewer too, since it uses the Qt framework as well.Ĭan we specify page breaks other than at ToC points? Again, this only applies to books with embedded fonts. And even though the italic and bold version won't show up in Book View, they will be shown in ADE. That being said, you can still edit such books without a problem. I've reported the bug to Nokia and hopefully they'll fix it by the next release of Qt (which should be a couple of months away). As I've said, it's a bug in the Qt framework (I've replicated it directly in their example applications) and I can't fix it. This happens less often on Mac and Linux versions than on Windows. And when you close Sigil after loading such an EPUB book, Sigil will crash with a segfault. Sometimes they will, sometimes the won't. But if you specify several versions of the font (like for instance bold and italic versions) with rules, the other versions usually won't be displayed. currently Sigil supports loading of books with embedded fonts. There is one problem caused by a bug in the Qt Framework that Sigil uses and that users need to be aware of. You can also subscribe to RSS and Atom feeds here.Īlso feel free to check out Sigil's development blog. That file is linked directly from the repository, and it is updated as bugs are fixed and features are added. Request for documentation writers can be found here.įor those who want more up-to-date information on Sigil's development, you can always see the live ChangeLog here. MobileRead is by far the most awesome community I’ve ever been a part of and I know we’ll be able to come up with some great ideas. I want the community to say what should be changed, updated, improved and in what way. This is open source software, and it will hopefully be open source development. My TODO list of features and improvements fills up a book (literally), but I’m certainly more than willing to hear what other people think. Feel free to give any suggestions on how Sigil can be improved. The more info you give me, the better and sooner will I be able to help you. Be sure to include any and all relevant information. Report any bugs on the issue tracker on Sigil’s website (search the threads and the tracker first, please also, read this wiki page). Installation instructions can be found here. There is currently no documentation, so don’t waste your time looking for some (it will be added with time, don’t worry).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |