On Fri, 17 May 2013 13:32:51 -0500 stefano franchi <stefano.fran...@gmail.com> wrote:
> this may be a silly question, but worth asking perhaps: could the > "tweaks" to the XHTML code that you carry out in Sigil be easily > avoided with some, perhaps minor, tweaks to the existing XHTML > export? In other words: could we perhaps *completely* replace an > ePub export function with a XHTML/Sigil export? Relatedly: can Sigil > be used latex-style, i.e. as a converter/validator from the command > line? Stefano, I don't think so: Sigil is not a command-line tool. Sigil has a GPL3 license, so I don't see that there would be any problem re-using code in it to create a command-line tool. But I think it would be simpler to create such a tool from scratch. If you just start Sigil from the command line with an HTML file as the argument, you get a usable EPUB book brought up in the GUI, but it has a few problems: firstly, the default text file is present but not referenced; then there are four items of required metadata missing; and the table of contents is inaccurate. There is also no cover. However, with no editing the saved EPUB would probably work in most readers. Fixing these problems takes no more than five minutes, unless you want a fancy cover image. Les
