On Thursday 10 November 2005 12:00 am, Derek Atkins wrote: > Neil Williams <[EMAIL PROTECTED]> writes: > > There's no inherent reason why gnucash has to do this XSL work directly - > > it could be handed over to a perl or bash script. OK it might be nice to > > do it ourselves but that just means gnucash has to have some way of > > controlling or predicting / finding the stylesheets to use and further > > encourages the user to believe that it is *our* collective role as > > gnucash developers to keep those stylesheets updated with each budget > > cycle - across all financial and geographic boundaries. IMHO, that is a > > task to which we are currently not well suited. > > True, but I see no reason why not to write the code in gnucash to > take the output XML and run it through a user-defined XSL template.
Yes, that makes sense. > However I agree that we should make it > clear in the UI that WE are not responsible for the XSL templates. Absolutely! :-) -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
pgp8Jdpeursnn.pgp
Description: PGP signature
_______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
