Hi Daniel You are welcome Plesse help me understanding Rest&Sphinx Can we generate also a pdf Rest&Sphinx? can we integrate existing documentation in c\harbour\doc? Which is first step? Can try with a little part ?
we can follow your way using Rest&Sphinx becase we not have jet any valid way i suggest you subscribe developer mailing list can try with a little part of harbour 2010/2/16 Daniel Gonçalves <[email protected]> > Hello, > Why not use ReST [1] (Restructured Text) using the excelent Sphinx [2] > documentation tool. These are the tools used to document the Python > project [3][4]. > If I can help in any way, I'm available and very insterested in a > better/accessible Harbour documentation. > > [1] http://docutils.sourceforge.net/rst.html > [2] http://sphinx.pocoo.org/ > [3] http://www.python.org/ > [4] http://docs.python.org/library/index.html > > In the page [4], look at the "Show source" link on the left, to see > how the source documents looks like. > > Regards, > > 2010/2/16 Massimo Belgrano <[email protected]>: > > Yes i intend volunteers speaking (or better, writing) English for > > a collectors team > > > > > > One easy way of learning is start from al sample/source in various tests > > directory because each function have a demonstration > > start learn from sample instead that from documentation is used from most > > harbour developer > > subscribe Follow developer mailing list, > > hbide have a function for find in *.prg ,*.ch in c:\harbour (subdir) and > > start learn from sample with coloured syntax (find in file from iconbar) > > the search in mailing list,google,harbour dir is basic tools > > > > wich is better tools to create doc having same volunteers speaking (or > > better, writing) English joining a "collectors team"? > > > > > > 2010/2/16 Pete <[email protected]> > > > >> Hi Massimo, > >> > >> Sorry for the late reply, i was away. i did download hbide, than you, no > >> time yet to investigate. > >> About harbour's documentation i did post a message with my thoughts, > >> replying to Mr. Czerpak. (unfortunately that reply went wrongly to a new > >> thread -my fault and my yahoo's mailing client.) > >> > >> you say you need "english people" with harbour knowledge to write > >> documentation. by "english people" i think you mean volunteers speaking > (or > >> better, writing) English, and you are right! > >> > >> However, as has already been pointed out, most of the harbour's > >> documentation is already written and lies into several texts -old and > new > >> ones. If this is true, then the need is not "English writers" but a > >> small team of "collectors", who will find a way to extract/collect these > >> pieces of documentation, edit them (in cooperation to core-developers to > >> avoid mistakes) and to incorporate them into a flexible and easy handled > >> help system or to put it more "technologically descriptive" we need a > "HELP > >> MACHINE", with an easy to plug "slot", which would attract harbour > people to > >> feed this machine, bringing their contributions (documentation text, > >> samples, etc.). > >> > >> > >> P.S.: I really wonder, how can the harbour users to make use (without > >> documentation) of this very developed and so much enriched compiler, as > >> harbour has already become after all those many additions and > enhancements > >> that have been done by the unbelievable creative developers (czerzpak, > >> szakats and co.) during last months. I think that very few of users > utilize > >> the total of harbour's capabilities and features, not to mention that > this > >> documentation lack is an 'inhibitory factor' for new users to come, but > >> maybe i am wrong and it's only me that have difficulty to follow the > whole > >> process. > >> > >> regards, > >> > -- Massimo Belgrano _______________________________________________ Harbour-users mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour-users
