On Mon, Feb 13, 2012 at 10:13 AM, Iain Duncan <[email protected]> wrote: > On Mon, Feb 13, 2012 at 4:59 AM, Chris McDonough <[email protected]> wrote: > I think that is actually better. I've seen countless times books getting > negative reviews for duplicating the online API reference, and it just > doesn't make sense to have that in book form really, it's a case where the > hypertext part of the web is so much better.
There are people who prefer a printed manual, especially when reading offline or when their eyes are tired. And there are companies willing to pay money for such a book for their employees. If the organization is government, it can't donate money to a project but it can purchase a product at the prevailing price. I have the 5-volume PostgreSQL docs in book form, both because it made it easier to get my head around Postgres, and also because it's convenient to quickly look up a SQL command or program. In this age, you can even arrange for an on-demand publisher to print the current manual whenever a customer orders it. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
