1) Rewriting some Perl code that takes the defaults.xml document and converts it into multiple attribute.html-type documents ("splitting")
2) Deciding on a format or "look and feel" for the documentation
My plan was to spend this past weekend trying to learn enough Perl based on my PHP knowledge to be able to tackle number 1, but I'm afraid it's looking like too steep of a hill to climb in one weekend (especially considering it's Friday and I'm no further along than I was Saturday morning :-( ).
At the same time, I'm exploring the capabilities of XSLT, for this and other projects, as a solution to creating individual HTML files (one for each attribute). The goal is to produce _something_ that splits defaults.xml into it's component pieces, even if it only ends up in the Contributions section.
Alas, XSLT is really cool and certainly up to the task, but it too will require a few more weeks of study before I'm able to contribute anything worthwhile.
Converting the documentation to XHTML and changing the look and feel (and improving the usability)...
I could put together a style sheet (something I already know how to do and do with quite a bit of regularity) if you want, at least I'll be able to contribute _something_ while I work on the other piece...
Let me know...
Ted Stresen-Reuter
On Friday, January 31, 2003, at 03:21 AM, Gabriele Bartolini wrote:
Ciao Ted, Budd and Gilles,HyperCard and AppleScript and Lingo), I'll see if I can write the code for generating the documentation in Perl, but I would like to see Brian's scripts...I was trying to give a look at the situation of the XHTML porting of the documentation. Any news? I can volounteer. I was thinking about using an utility such as 'tidy' to help me moving forward, and also try to check it up from the accessibility point of view. First (sorry it is my fault), I'd remove the 'bold' effect when going over a link (when I put it, it was almost one of my first experiences with CSS!) which is really unaccessible!.
I'll try and put the 'lang' attribute in every page and the content type as well, and leave an empty 'body' in every page (I know some old versions may show the default color - usually white - but it doesn't prevent it from being viewed). Other changes will be made > consequently.
Sounds good?
Let me know. The only case which could have some problems is the automatically generated configuration file (please update me for this!).
Ciao ciao
-Gabriele
--
Gabriele Bartolini - Web Programmer - ht://Dig & IWA Member - ht://Check maintainer
Current Location: Prato, Tuscany, Italia
[EMAIL PROTECTED] | http://www.prato.linux.it/~gbartolini | ICQ#129221447
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
