03-21-2010, 03:02 PM | #46 |
Fanatic
Posts: 549
Karma: 2928497
Join Date: Mar 2008
Device: Clara 2E & Sage
|
That's one. Any response to my other questions?
Your program looks potentially useful. Since it's in alpha stage, I would think you would welcome feedback and questions, instead of telling me to go use some other program. BTW, I did finally use eCub to generate my epub. However, eCub has it's own peculiarities. I was looking for a better tool and yours looked promising. |
03-21-2010, 05:19 PM | #47 | |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
Quote:
But if the files you import are valid Xhtml, most changes should be small. As for importing into a Generic Page, that is probably what you want. The Generic Page object is the one document object in ePubHub that doesn't have any special content requirements and should render just what you've added. I've changed the import feature to set the custom name the Generic Page to the filename of Xhtml document that is imported. As for drag-n-drop, right now you can drag items within ePubHub. Dragging Windows' desktop icons and things from other programs requires a lot more code to be written. At this time, I can't focus on that. But I might change the import feature so that if you hold down the shift key, it would change from importing a single document to importing any ".xhtml" documents inside a chosen folder. Last edited by awx; 03-22-2010 at 05:58 PM. |
|
Advert | |
|
03-21-2010, 05:26 PM | #48 |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
A new version was released which has made some small but important changes to the import Xhtml feature.
* The core 1.1 and 1.0 Xhtml Dtds are now embedded inside the application, preventing them from being downloaded from the w3 web site during import. * The import feature takes the filename of the imported document and sets the title of the Generic Page with it. * Common Xhtml attributes are now imported, including xml:lang, class, style, id and dir. * The import feature now recognizes more tags but there are still many that are not working, such as <a /> (hyperlinks). I hope to improve these over the next few days. * The <pre> tag is now properly (I hope) supported in ePubHub. It was incorrectly used as an inline element rather than a block level element. Last edited by awx; 03-21-2010 at 07:57 PM. |
03-22-2010, 12:30 AM | #49 |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
New version released with a single new feature.
If you hold down the Shift key while selecting the "Import Xhtml File..." menu item, it will allow you to select a folder. All files with the ".xhtml" extension will be imported. |
04-09-2010, 03:53 AM | #50 |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
New version released, still with some rough edges.
New features include: * Support for Opf Guide * Support for Ncx Page List. Pages are created with the PageMarkers. * Support for creating coverpage metadata (as recommended described here. Add a "Cover Image" in the metadata section and a "Cover Page" in the eBook section. * Added support for almost every tag from Xhtml 1.1. ePubHub should be getting close to having no invalid Xhtml. I'd like to know if it is possible to incorrectly nest any incompatible tags, such as <b><p></p></b>. * Error dialog instead of crashing. If the error is not "Not Implemented", it would be helpful if you posted the text here along with the steps to reproduce it. * Otf fonts and mp3 files can be added but you can't really use them yet. A few new problems are in this version: * Editor for preformatted text does not allow returns. * Some tags still missing a visual editor. |
Advert | |
|
04-13-2010, 01:49 AM | #51 |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
New version released, with these features:
* Css support. All stylesheets in the Stylesheet folder are referenced in every xhtml page. * @font-face support, src value must be a font embedded into the ePub. * <ins> & <del> tags now have an editor (though no support for rev date or reason just yet). * In options dialog, you can configure the <q> tag to also emit curly quotes for readers (such as my Sony PRS-600) that don't render the <q> with quotes. Currently, the characters are fixed to English-style curly quotes and cannot be customized. Screenshot of fontface editor with Css reference in body: The ePubHub source code is going to be moving to .Net 4.0 tomorrow and hopefully a version using 4.0 will be released soon if there are no problems. |
04-13-2010, 05:02 PM | #52 |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
New version released.
The only change is that this version is built with (and therefore requires) .Net 4.0 to be installed on the computer running ePubHub. You will have to install .Net 4.0 yourself before you can run new versions of ePubHub. .Net 4.0 Installer http://www.microsoft.com/downloads/d...displaylang=en By virtue of updating, ePubHub gets a few benefits: * icons in the Toolbox won't be blurry anymore * gets some speedups redrawing icons * Uses new Windows 7/Vista-style file open/save dialog boxes. Last edited by awx; 04-13-2010 at 07:53 PM. |
04-13-2010, 06:31 PM | #53 | |
Created Sigil, FlightCrew
Posts: 1,982
Karma: 350515
Join Date: Feb 2008
Device: Kobo Clara HD
|
Quote:
And Microsoft finally made WPF text rendering snap to pixel boundaries (goodbye blurriness)... I guess it's time to start taking WPF seriously... |
|
04-13-2010, 08:03 PM | #54 |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
Another big improvement in Wpf 4.0 is that it respects the ClearType settings from Windows, which previous versions ignored.
Blurry fonts affected some computers more than others. For instance, looking at the screenshot from .Net 3.5 two posts above, it's hard to find much fault with the font rendering. That screenshot came from my laptop, where I did a pretty close comparison between 3.5 and 4.0. On that laptop there is almost no difference. However my desktop computer saw a big improvement in font legibility. The icon improvements were actually in the Toolbox, not the toolbar as I originally wrote. ePubHub had been using a 3rd party icon class that did proper snap-to-pixel rendering of icons everywhere in the app but it wouldn't work in the toolbox. The new native snap-to-pixel rendering looks just as good and renders with a lot less overhead. |
04-14-2010, 07:24 AM | #55 | |
Created Sigil, FlightCrew
Posts: 1,982
Karma: 350515
Join Date: Feb 2008
Device: Kobo Clara HD
|
Quote:
It's what I've been waiting for (and a great deal of other people, too). WPF was so awesome before (XAML FTW), but I could never justify using it because of the text rendering issues. It just makes me cringe. I still remember VS 2010 beta1 coming out and the uproar over the text editor now being effectively unusable. I personally uninstalled beta1 three minutes after seeing for myself just how horrible the text looked like. But now I'll be switching from Windows Forms to WPF for my C# projects wherever possible. |
|
04-20-2010, 03:30 PM | #56 |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
New versions released with some minor bug fixes, including
* wrong paths for @font-face declarations in certain circumstances * Image & @font-face objects would forget the items selected in Comboboxes in certain circumstances. Css importing should be released later today. |
04-21-2010, 04:36 AM | #57 |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
Great, will try the version with css import later then. Any news when a basic save option will be active? I really hate to enter everything again while testing.
|
04-26-2010, 03:55 PM | #58 |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
It took a little longer than I anticipated but the Css import feature is done, with the following known limitations:
* @media directive is not supported and any rules inside of this will be ignored. * Css comments are ignored during import. * The Css rules are sorted in alphabetical order. This will change shortly to maintain their original order. If your css file won't work with those limitations, you should not import it but instead create a "Stylesheet (External)". External stylesheets will copied directly from disk into the ePub without modification. Please let me know if you have any problems while importing Css files. I've tested the import feature against somewhat complicated files without any parsing errors but it's likely there are situations that I didn't consider. My plan was to implement complete error-checking before opening/saving but I agree that opening/saving would be more useful at this point. Hopefully you're importing most everything and only doing cleanup inside ePubHub. I'll be expanding the import feature to support creating book structure based on divs to speed things up. So if you import an xhtml file that looks like this, you will get an eBook with two chapters instead of a single generic page: Code:
<html xmlns="http://www.w3.org/1999/xhtml"> <body> <div class="chapter"> <p>Blah blah blah</p> </div> <div class="chapter"> <p>Blah blah blah</p> </div> </body> </html> |
04-27-2010, 09:27 PM | #59 |
Connoisseur
Posts: 68
Karma: 56
Join Date: Oct 2009
Device: Sony PRS-650 & PRS-600
|
New version released, which includes improved import functionality and some bug fixes.
If you import an Xhtml file which: * has a single div inside the body, and * give that div the class "book-structure" * and inside that div are only other divs (each representing a section of the epub) then ePubHub will automatically try to create an appropriate book structure during the import. If the "book-structure" div is not used the import will place all content into a single generic page, just as before. Valid classes include: chapter, part, part-intro-page, cover-page and title-page. divs with any other class (or none) will get put into a generic page. Parts can only go one level deep (ie a part must be in the root of the book-structure and you can't nest a part inside anything else). Only chapters and part-intro-pages can go inside a part. And even though your page content is inside a div, it will be imported into the root of an Xhtml page body so all tags must be valid in that context. So "<div class="chapter"><img ... /></div>" could't be imported because <body> can't contain the <img> tag. If you need this, wrap the image in another div or p. Code:
<html xmlns="http://www.w3.org/1999/xhtml"> <body> <div class="book-structure"> <div class="part" title="PART ONE"> <div class="chapter"> <p>Blah blah blah</p> </div> <div class="chapter"> <p>Blah blah blah</p> </div> </div> </div> </body> </html> Last edited by awx; 04-27-2010 at 09:32 PM. |
04-28-2010, 01:02 AM | #60 |
Grand Sorcerer
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
I am surprised you don't just support H1, H2, H3 for chapter breaks.
Dale |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[old-topic]ebook-viewer: Open source, crossplatform viewer for EPUB, LIT, MOBI, etc | kovidgoyal | Calibre | 68 | 05-30-2011 08:46 PM |
any open source ebook reader apps? | kennyc | Android Developer's Corner | 15 | 12-23-2010 01:38 PM |
EPUB generated by ebook-convert does not open gracefully on windows | Heritage History | Calibre | 4 | 07-08-2010 01:37 PM |
OpenInkpot (open source ebook firmware) | davidw89 | Sony Reader | 9 | 11-15-2008 09:59 AM |
Proposal for an open source multi-format ebook authoring tool | Jon Noring | News | 15 | 09-12-2008 12:17 PM |