Hi Smu, > This has been discussed a lot on this list, and it's really > not a technical problem, it simply needs contributors, > willing to give something (in this case documentation writing) > back to the project they're getting for free. > > Viktor, I would love to help out on the documentation project. I consider > myself a decent writer who can explain things clearly and give examples that > prove all nooks and cranny's of something. If you are interested in giving > me a task to start off with, I'd be very glad to help, since you and others > have been incredibly helpful, saving me days of hair-pulling frustration.
Thank you very much for volunteering. At the moment we use the NFLIB documentation "standard", which you can find many examples for in /doc/en-EN/ hierarchy. [ We also have an automated tool which can process it, called hbdoc2 (in examples). ] So this is the best we can offer in this area, anyhow if you have some more comfortable way to create documentation, please use it, my only guideline would be to use a format which can be processed with automated tools to make it possible to convert it to other formats (like pdf or html, etc) I'd also welcome _up to the point_, short ideas from other list members. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
