Re: An aside: Some of the TR documents in epub3 (a.k.a. eating our own dog-food:-)

Tzviya,

the tool is in Python and is on github

https://github.com/iherman/tr2epub

I tried to document it:-)

I know that I ran the files through the epub checker back in the early days of the development, but there were some issues with the checker. You are right that I should do that again. I tested the files on three four different readers on my Mac and three on my iPad; any other check is good. Not surprisingly, I guess, my biggest headache was to set up a decent table of content...

Thanks!

Ivan



On 27 Feb 2014, at 17:07 , Siegman, Tzviya - Hoboken <tsiegman@wiley.com> wrote:

> Ivan,
> 
> This is excellent, and I'd love to have a look at the tool. I can supply some feedback on the files. I assume work on updating epubcheck to reflect RDFa has already begun, but the error log produced here would probably be a nice bug report for them. 
> 
> Tzviya
> ****************************
> Tzviya Siegman * Senior Content Technology Specialist * Wiley Content Management * John Wiley & Sons, Inc.
> 111 River Street, MS 5-02 * Hoboken, NJ 07030-5774 * 201-748-6884 * tsiegman@wiley.com
> 
> -----Original Message-----
> From: Ivan Herman [mailto:ivan@w3.org] 
> Sent: Thursday, February 27, 2014 10:54 AM
> To: W3C Digital Publishing IG
> Subject: An aside: Some of the TR documents in epub3 (a.k.a. eating our own dog-food:-)
> 
> I had a private project the past few weeks (actually I started a few months ago but I was on and off) to convert official W3C documents to EPUB3 automatically. For an individual document that is not all that interesting (although it does allow off-line usage), but it is great if one has a set of recommendations that belong together, so to say. In such a case a book is actually a collection of specs but can be considered as one.
> 
> The tool is pretty mature by now; it does all kinds of nice things like changing possible cross references to references within the book, including all the necessary css files, images, etc, in the book rather than referring to the Web address, etc. We just had a major publication of a new version of RDF a few days ago, and that prompted me to put up a number of such ebooks:
> 
> http://www.w3.org/dpub/ebooks/
> 
> I think we should definitely use this when we publish WG Notes, eg, latireq or annotation. Many groups have/had alternative formats for their specs and tese are referred to from the document header. In the past, hm, well, ehem, the alternative format was often a PDF file:-( I guess we ought to publish epub3 when the time comes; eating our own dog food...
> 
> Ivan
> 
> P.S. Needless to say: if you find some issues with those books, please tell me. This is the first time a seriously produce eBooks, looking at the spec and other ebooks...
> 
> Disclaimer: Of course, these are _not_ official documents, just a reproduction thereof!
> 
> 
> ----
> Ivan Herman, W3C 
> Digital Publishing Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> GPG: 0x343F1A3D
> FOAF: http://www.ivan-herman.net/foaf
> 
> 
> 
> 
> 
> 


----
Ivan Herman, W3C 
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
GPG: 0x343F1A3D
FOAF: http://www.ivan-herman.net/foaf