bobby wrote:

Graeme Geldenhuys wrote:

I was thinking in terms of release format for end users.  Editing
could be done exactly like the windows help formats. HLP is generated
from a rich text file (RTF).  I think CHM is as well.  We could
generate our final help file from XML.  DocBook also does it that way.

CHM means Compiled HTML, and it is a bunch of HTML pages + some compression (LZX I think). This concept isn't a bad start point, but some TOC in the help file, that can be accessed from the program, is also needed.

regards

A few months ago I wrote a chm viewer program using the LCL and also a package for Lazarus so pressing F1 started/focused the help viewer.

So far everything works afaik and it is faster than MS Help in loading files with large TOC's and indices. The only (major) thing left todo is implement the search capability (which works only if the chm was created to be searchable)

I am now pretty busy in the summer so there probably won't be much progress on it for some time.

However Patches are welcome :)

I checked out HTML Help Maker http://download.savannah.gnu.org/releases/hhm/ and it can only create the archive format that chms are. It cannot currently create the TOC or index file or any of the other special chm related files that are in a chm.

The following links I used as a reference to create the reader for the chm file format:

http://www.nongnu.org/chmspec/latest/

http://www.speakeasy.org/~russotto/chm/

I obtained the permission of the author of lzx.c to convert it to pascal and use the modified lgpl with it and with the help of Neli the lzx decompression is included so no external library is need to read chm files in linux or any of the other platforms that fpc will work on.

As Vincent said all this code is in /components/chmhelp in your lazarus directory. :)

Andrew

_________________________________________________________________
    To unsubscribe: mail [EMAIL PROTECTED] with
               "unsubscribe" as the Subject
  archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to