> But that's the licency reasoning. The whole problem with these
> standalone versions is that the book is a living document. It changes
> almost every day - why put users in a position of having outdated docs
> "Are you reading the book?" "sure" <hours pass> "oh THE book. no I've
> got some outdated pdf someone generated last year."
>
> If you want to put your efforts to good use - fork the book and create
> a shell to generate the pdf. That way anyone can update their local
> copy whenever they want AND the core team can publish a snapshot on a
> regular basis.
>
Outdated version is an issue, of course. But the online-only version
is a big issue in some places, just like here (Indonesia). But I still
hope someone implement your idea (fork the book and create a shell to
generate the pdf).
regards,
http://okto.silaban.net
No comments:
Post a Comment