Stefan Reinauer wrote:
Ok, I checked the script into the arch repository now, utils/optionlist.
I changed the xsl sheet slightly so it works with my version of xsltproc and saxon. Which xsl processor are you using?
Thanks for your work
Stefan
To be honest I tried so many different xsl processors that I really can't remember what I finally used. I think it was a good idea to make it XSLT 1.0 (again (I had it written in XSLT 1.0 first, too) as it seems a lot more processors can handle it. You might want to completely remove the xsl:choose stuff (so basically what is commented right now) it was a hack to get the xml (the unprocessed of course) to show correctly in firefox and is specific to XSLT 2.0 anyway because it uses xhtml as method.
Pardon me but, am I to understand that XML is implemented in a firmware environment?!
Steve M
On Sun, 20 Mar 2005, Florian Zeitz wrote:
Stefan Reinauer wrote:
Ok, I checked the script into the arch repository now, utils/optionlist.
I changed the xsl sheet slightly so it works with my version of xsltproc and saxon. Which xsl processor are you using?
Thanks for your work
Stefan
To be honest I tried so many different xsl processors that I really can't remember what I finally used. I think it was a good idea to make it XSLT 1.0 (again (I had it written in XSLT 1.0 first, too) as it seems a lot more processors can handle it. You might want to completely remove the xsl:choose stuff (so basically what is commented right now) it was a hack to get the xml (the unprocessed of course) to show correctly in firefox and is specific to XSLT 2.0 anyway because it uses xhtml as method.
LinuxBIOS mailing list LinuxBIOS@openbios.org http://www.openbios.org/mailman/listinfo/linuxbios
* Steve Milo slavik914@mrbrklyn.com [050320 20:39]:
Pardon me but, am I to understand that XML is implemented in a firmware environment?!
for the purpose of automatically creating up to date documentation from the code, yes indeed. There is no xml involved on the firmware level itself.
Stefan