From: Tony G. <Ton...@Su...> - 2006-03-15 00:05:22
|
Tony Graham <Ton...@Su...> writes: > "Mauro C." <inc...@ya...> writes: > ... >> I would to contribute to xmlroff project not only dev >> a php ext. > > That would be great. Any help you or anyone else can give is greatly > appreciated. > >> I just start to study source, too much source :) > > The good thing, and only sometimes the bad thing, about the source is that > most of it is autogenerated by the spec-dump module. The code for the FO and > properties is generated by the spec-dump module and then copied over to > xmlroff. > >> Tony if you could give me some hint so I can >> contribute also to implements xsl-fo. >> Simly give me .c file to study fist, expecially >> fo-area and fo-fo. There's a couple of things that need doing that don't require intimate knowledge of GObjects, if you're willing: for example, there's building libfo-compat.xsl into xmlroff. > The simplest file for any FO is probably fo-root.c, and the simplest property > is probably fo-property-media-usage.c. They're also the two files that I > tweak by hand first before modifying spec-dump to produce similar code. > > If you enable building the documentation with './autogen.sh --enable-gtk-doc' > (which is prebuilt in the xmlroff distributions), you'll find some minimal > documentation, including a discussion of fo-root.c. There used to be more on > the xmlroff wiki, back when the wiki worked, but I didn't keep it up because > it didn't seem to be being used, and now it's gone because the database > containing the wiki data was lost when SourceForge changed their database > setup. Thanks to the Way Back Machine (http://web.archive.org/), I was able to resurrect some of the old Wiki pages and add their content to the docs in the xmlroff CVS. There's also the start of a discussion of backends and FoDoc. After you've read the available docs, please tell me what are the biggest holes in the documentation. Regards, Tony. |