What about ePub support

2013-05-17 Thread Jan Ulrich Hasecke
Hi, I want to publish ebooks and typeset books from the same source, because today nearly all new books are offered as ebooks and as printed books. Up to now I didn't find a good solution working out of the box. Sphinx, the documentation system written in Python offers multiple output formats

Re: What about ePub support

2013-05-17 Thread Les Denham
On Fri, 17 May 2013 12:31:31 +0200 Jan Ulrich Hasecke juhase...@googlemail.com wrote: Hi, I want to publish ebooks and typeset books from the same source, because today nearly all new books are offered as ebooks and as printed books. Up to now I didn't find a good solution working out of

Re: What about ePub support

2013-05-17 Thread stefano franchi
On Fri, May 17, 2013 at 1:19 PM, Les Denham lden...@hal-pc.org wrote: On Fri, 17 May 2013 12:31:31 +0200 Jan Ulrich Hasecke juhase...@googlemail.com wrote: So what are the plans for the future? I read about a GSOC project aiming to implement epub conversion in LyX. Is there a timeframe? In

Re: What about ePub support

2013-05-17 Thread Les Denham
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

Re: What about ePub support

2013-05-17 Thread Liviu Andronic
On Fri, May 17, 2013 at 8:32 PM, stefano franchi stefano.fran...@gmail.com wrote: export? Relatedly: can Sigil be used latex-style, i.e. as a converter/validator from the command line? A quick search turned up this CLI ePub validator: http://code.google.com/p/epubcheck/ And on Sigil's Issues

Re: What about ePub support

2013-05-17 Thread Les Denham
On Fri, 17 May 2013 22:56:17 +0200 Liviu Andronic landronim...@gmail.com wrote: Actually there's an *undocumented and unsupported* HTML-to-EPUB command line conversion option. See main.cpp for details. Did I mention the feature is *undocumented and unsupported*? :) It's there because a

What about ePub support

2013-05-17 Thread Jan Ulrich Hasecke
Hi, I want to publish ebooks and typeset books from the same source, because today nearly all new books are offered as ebooks and as printed books. Up to now I didn't find a good solution working out of the box. Sphinx, the documentation system written in Python offers multiple output formats

Re: What about ePub support

2013-05-17 Thread Les Denham
On Fri, 17 May 2013 12:31:31 +0200 Jan Ulrich Hasecke juhase...@googlemail.com wrote: Hi, I want to publish ebooks and typeset books from the same source, because today nearly all new books are offered as ebooks and as printed books. Up to now I didn't find a good solution working out of

Re: What about ePub support

2013-05-17 Thread stefano franchi
On Fri, May 17, 2013 at 1:19 PM, Les Denham lden...@hal-pc.org wrote: On Fri, 17 May 2013 12:31:31 +0200 Jan Ulrich Hasecke juhase...@googlemail.com wrote: So what are the plans for the future? I read about a GSOC project aiming to implement epub conversion in LyX. Is there a timeframe? In

Re: What about ePub support

2013-05-17 Thread Les Denham
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

Re: What about ePub support

2013-05-17 Thread Liviu Andronic
On Fri, May 17, 2013 at 8:32 PM, stefano franchi stefano.fran...@gmail.com wrote: export? Relatedly: can Sigil be used latex-style, i.e. as a converter/validator from the command line? A quick search turned up this CLI ePub validator: http://code.google.com/p/epubcheck/ And on Sigil's Issues

Re: What about ePub support

2013-05-17 Thread Les Denham
On Fri, 17 May 2013 22:56:17 +0200 Liviu Andronic landronim...@gmail.com wrote: Actually there's an *undocumented and unsupported* HTML-to-EPUB command line conversion option. See main.cpp for details. Did I mention the feature is *undocumented and unsupported*? :) It's there because a

What about ePub support

2013-05-17 Thread Jan Ulrich Hasecke
Hi, I want to publish ebooks and typeset books from the same source, because today nearly all new books are offered as ebooks and as printed books. Up to now I didn't find a good solution working out of the box. Sphinx, the documentation system written in Python offers multiple output formats

Re: What about ePub support

2013-05-17 Thread Les Denham
On Fri, 17 May 2013 12:31:31 +0200 Jan Ulrich Hasecke wrote: > Hi, > > I want to publish ebooks and typeset books from the same source, > because today nearly all new books are offered as ebooks and as > printed books. > > Up to now I didn't find a good solution

Re: What about ePub support

2013-05-17 Thread stefano franchi
On Fri, May 17, 2013 at 1:19 PM, Les Denham wrote: > On Fri, 17 May 2013 12:31:31 +0200 > Jan Ulrich Hasecke wrote: > > > So what are the plans for the future? I read about a GSOC project > > aiming to implement epub conversion in LyX. Is there a

Re: What about ePub support

2013-05-17 Thread Les Denham
On Fri, 17 May 2013 13:32:51 -0500 stefano franchi 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?

Re: What about ePub support

2013-05-17 Thread Liviu Andronic
On Fri, May 17, 2013 at 8:32 PM, stefano franchi wrote: > export? Relatedly: can Sigil be used latex-style, i.e. as a > converter/validator from the command line? > A quick search turned up this CLI ePub validator: http://code.google.com/p/epubcheck/ And on Sigil's

Re: What about ePub support

2013-05-17 Thread Les Denham
On Fri, 17 May 2013 22:56:17 +0200 Liviu Andronic wrote: > "Actually there's an *undocumented and unsupported* HTML-to-EPUB > command line conversion option. See main.cpp for details. Did I > mention the feature is *undocumented and unsupported*? :) > It's there because a