Hi!

> In article <cvsgoba979842990@cvsserver>, [EMAIL PROTECTED]  wrote:
> > Index: phpdoc/hu/make_chm_index_hu.html diff -u
> 
> is there a reason this file can't be generated, or is it just that nobody
> has gotten around to it?

I made a 'fancy manual generation' script. Look into make_chm.README
for details. Nearly all tasks of make_chm_fancy.php can be done with
a DSSSL style sheet, but I am not 'DSSSL compatible', so made a
conversion script from the DSSSL html output -> fancy HTML.

The fancy HTML is used for the generation of .chm (Windows HTML Help)
files. With the fancy method, the .chm files look much professional
(at least I think so). I thought we should use a special index.html
for the .chm versions, which is the front page of the .chm manuals.
It looks much better I think with that layout. 

I spent two days with finalizing the fancy method, activating
the special WinHelp functions, and testing, so was tired to
make some automation to generate the make_chm_index_lang.html
files.

Currently two .html files are there:

 make_chm_index_en.html and
 make_chm_index_hu.html (in the respective locations).

I thought that the frontpage of the manual rarely changes,
so it is not a problem, to make these static.

Also there is some special content (translators name,
language editor, and some language specific text) in
these html files. I thought there is no standard way of
including these plus information in the docs.

Maybe I am wrong. If you can find some automation
method to make these files, I would be happy to hear
that. My goal is to make the .chm version the best
format for windows users.

Try to build a normal and a fancy .chm file (see
make_chm.README for details), and you will see,
why I chosse the way to have a special index file.
You need MS Windows and MS HTML Help Workshop
to do the test...

Goba
__________________________________________________________________
Hungarian PHP Manual :: Hungarian PHP Mirror :: http://hu.php.net/
The starintg-point for Hungarian webmasters :: http://weblabor.hu/

Reply via email to