I like the idea since I like ebooks. However, I will be honest and say that for code development I would not be too likely to use it since on my desktop machines I don't have a great epub viewers.
So I guess I would say that if there was no extra effort or file space required go ahead and add it but if the extra effort is noticeable don't bother. Just my 2 cents worth. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- Rob Managan email managan at llnl.gov LLNL phone: 925-423-0903 P.O. Box 808, L-095 FAX: 925-422-3389 Livermore, CA 94551-0808 On 10/4/13 5:56 AM, "Dirk Bächle" <tshor...@gmx.de> wrote: >Hi devs, > >since we're now using DocBook as source format for all our >documentation, it would technically be relatively easy to publish things >like the MAN page or the UserGuide in EPUB format as well. >The latest versions of "pandoc" (> 1.12.x) offer a DocBook reader and do >a, more or less, good job in rendering the single markups. >Find a shortened version of the UserGuide attached, as a first example... > >The question now is: Should we go this route? Then I'd try to integrate >an "ebook" target into the build and bootstrapping process, such that >EPUBs get created automatically if "pandoc" can be found on the current >system. > >Note, how this would add a dependency to "pandoc" for all the >ReleaseManagers...and this currently means installing the full Haskell >platform package with approx 400MB. ;) > >Your comments? > >Best regards, > >Dirk > _______________________________________________ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
