||*()*|| Hi, Gabor. >>> NL> There are still some problems with skins in the extended chm. >>> NL> The function.* pages give some errors with the phpZ skin and some >>> others. >>> NL> (with older xslt sheets, there were no errors) >>> >>> Customization hasn't finished yet. The main problem is that I don't have >>> document or RFC, which describes requirements for .html files to be >>> compatible with JavaScript layer. I'm trying to figure out from code >>> and comments, but they are scattered over JavaScript, XSL and PHP. >>> >>> Maybe it will take a form of an RFC for xCHM. I have some crude >>> sketches. =) >> >> That doesn't exist... Maybe the best option is to run a diff in old and >> new generated files :) (I'm able to do that, if you need)
GH> Yes, a diff probably helps. It might also be better to do a tidy run GH> before the diff on both files, so you can better see the differences :) My tools are Far Manager + Colorer + Winmerge + Examdiff. Quite convenient. Tidy is good only to detect errors as it modifies html structure a bit and I need that structure to be preserved to detect mistakes in php filters output. I've found the main point that all html files must have some div id's described in xCHM skinning section of manual. Stylesheets upgrade broke some html structures therefore some of php filters don't work. Now I'm deeply in the process of synchronizing these XSL and PHP filters layers. Not all modifications are in CVS now, because some of them are "alpha". =) I'd like to have a graph of typical html page layout to correct it as new details appear. Like this one: http://tikiwiki.org/tiki-index.php?page=MoreNeatLayoutSchema Perhaps I'll draw one myself when I make it work. =p t --
