Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kindle's version #27

Closed
netuh opened this issue May 10, 2012 · 3 comments
Closed

Kindle's version #27

netuh opened this issue May 10, 2012 · 3 comments

Comments

@netuh
Copy link

netuh commented May 10, 2012

hi diveintohtml5 team,

I reading your book "dive into html5", and i'm loving it. I really would like that all authors of technician books write as you write. I started to read it on the web site, however for me reading long text in web browsers is not easy. Then I brought the kindle's version of your book.

And I could notice some mistakes in this version that maybe you should fix:

  • All the pictures dont appear (They are so nice).
  • In chapter 2. There isn't the section "history Api".
  • In chapter 3. The link to the example at the very beginning of the chapter is broken. It pinpoints to "diveintohtml5.org", instead of "diveintohtml5.info"

Besides, the email that is on the web site is also broken. mark(at)diveintomark(dot)org

Well, I'm still reading, then I dont know if there are more mistakes.

Regards,
Neto

@naxa-zz
Copy link

naxa-zz commented Jul 31, 2012

The original author of Dive Into HTML5, Mark Pilgrim, has completely retired from the online community some time ago and removed his works from where he could. (As far as I know.) This site and account is an attempt to collect his works.
The (shocking) decision of his makes it unlikely that the e-book will be maintained, I think, as this (or any other) team can do nothing for it unfortunately.

@jonathantneal
Copy link
Member

Actually, this is something I've been wanting to do for a long time and it gives me the encouragement to get back to it.

@jonathantneal
Copy link
Member

The (shocking) decision of his makes it unlikely that the e-book will be maintained, I think, as this (or any other) team can do nothing for it unfortunately.

Actually, we have been actively maintaining this resource, both to add and improve the accuracy of the content, but even to improve the experience. Just look at our commit history!

Closing as a duplicate of Issue #24.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants