These docs are/were primarily suited for the
developers (or close to developer users), so
I'm afraid it's not a matter of file format.
For usable end-user docs, the user-orientated
parts would need to be gathered, processed,
made into readable and organized form and put
in a properly formatted user documentation.
These could be put in /manual for example.
For these docs though, or their enhanced
versions in /docs, I'd keep .txt, as this is
the only format not suffering from all the
mess of doc handling softwares.
For /manual, I'd recommend Doxygene, or the
other one which I forgot this time (see
several previous mails about the same topic).
Brgds,
Viktor
On 2008.06.09., at 16:30, Massimo Belgrano wrote:
In Harbour\doc there is a few but important documentation files:
author.txt class_tp.txt cmdline.txt codebloc.txt
codestyl.txt
c_std.txt destruct.txt dirstruc.txt funclist.txt gmake.txt
gtapi.txt hbmake.txt hbpplib.txt hdr_tpl.txt
howtobld.txt
howtobsd.txt howtomak.txt howtorel.txt howtosvn.txt
hrb_faq.txt
lang_id.txt license.txt linux1st.txt pcode.txt pp.txt
pragma.txt readme.txt simplex.txt statics.txt
tracing.txt
transfrm.txt vm.txt whatsnew.txt windll.txt
Is possible convert in rtp,odf,XML (IMO by OpenOffice.org)
So it can be edited from linux/windows with better layout and image
with
Style Sheets
Massimo Belgrano
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
