[Python-authors] Writing a technical book

[Michael Foord]

Thanks for the comments Wesley. I did find Manning helpful - but their 
processes are long.

Not going to be at OSCON but definitely interested in your talk and the 
toolchain you suggest.

Michael

wesley chun wrote:
>> I've written up my experiences of writing a technical book for Manning.
>> Despite it all I still recommend Manning if you really *have* to write a book...
>>
>> http://www.voidspace.org.uk/python/articles/technical-writing.shtml
>>     
>
>
> michael,
>
> thanks for your write-up... it is pretty educational and definitely
> brings back memories of my own writing. i haven't taken the
> opportunity as you have to document everything... goodness knows i
> already didn't have time to write the book(s) themselves! LOL
>
> on a somewhat related note, there was a similar thread a few years ago
> on the newsgroup where some people highlighted some of their
> frustrations with Manning:
>
> http://groups.google.com/group/comp.lang.python/browse_thread/thread/8527e080899a6246
>
> finally, regarding your comment about Word, DocBook, and XML, and can
> also understand your situation there. in fact, the way authors create
> their manuscript had become somewhat of a passion/interest area enough
> for me to have done some research on it. i shall reveal my results,
> both typical as well as perhaps mindblowing to some, at OSCON in a few
> weeks:
>
> http://en.oreilly.com/oscon2009/public/schedule/detail/8038
>
> best regards,
> -- wesley
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> "Core Python Programming", Prentice Hall, (c)2007,2001
> "Python Fundamentals", Prentice Hall, (c)2009
>     http://corepython.com
>
> "Python Web Development with Django", Addison Wesley, (c) 2009
> http://withdjango.com
>
> wesley.j.chun :: wescpy-at-gmail.com
> python training and technical consulting
> cyberweb.consulting : silicon valley, ca
> http://cyberwebconsulting.com
>   


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog