I believe in .TXT is one of the best options, it can be easily
converted to other formats. Another option I was considering would be
a front-end to facilitate this work, we are still undergoing tests to
make the choices.

April this hbdoc2 supports the same features in the current hbdoc?

Brgds,
Vailton Renato

2009/7/19 Viktor Szakáts <harbour...@syenar.hu>:
>>>> instead organize in plain .txt  i suggest  organized in dbf
>>>> More easy to organize,order,publish
>>>> is a clear demo of harbour capability
>>>
>>> .dbf isn't very practical here IMO. .txt or some other
>>> simple source format is the best.
>>
>> The template doc/hdr_tpl.txt already exists and is used by various documents
>> around the source tree.
>>
>> I've been examining hbdoc, I've altered it to handle line endings like
>> hbextern, but I've also been working on a variation (hbdoc2) that uses
>> simple classes to encapsulate the common functionality.
>
> Sounds good.
>
>> The output source files will be heavily based on the originals in hbdoc; is
>> this okay?  I am not an expert on copyrights, I hope that as long as I
>> include the original copyright notices I am not doing something wrong.
>>
>> Example:
>>    * Copyright 2009 April White <april users.sourceforge.net>
>>    * www - http://www.harbour-project.org
>>    *
>>    * Portions of this project are based on hbdoc
>>    *    Copyright 1999-2003 Luiz Rafael Culik <cul...@uol.com.br>
>
> Perfect.
>
> Brgds,
> Viktor
> _______________________________________________
> Harbour mailing list
> Harbour@harbour-project.org
> http://lists.harbour-project.org/mailman/listinfo/harbour
>
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to