# The XSLT C library for Gnome ## Reporting bugs and getting help

Main Menu
Home Introduction Documentation Reporting bugs and getting help How to help Downloads FAQ News The xsltproc tool DocBook The programming API Python and bindings Library internals Writing extensions Contributions flat page, stylesheet
Related links
Tutorial Man page for xsltproc Mail archive XML libxml DOM gdome2 FTP Windows binaries Solaris binaries MacOsX binaries Pascal bindings Bug Tracker Xsldbg Debugger
API Indexes
Alphabetic Constructors Functions/Types Modules Symbols
If you need help with the XSLT language itself, here are a number of useful resources: I strongly suggest to subscribe to XSL-list, check the XSL-list archives The XSL FAQ. The tutorial written by Paul Grosso and Norman Walsh is a very good on-line introdution to the language. The only Zvon XSLT tutorial details a lot of constructs with examples. Jeni Tennison's XSLT pages provide links to a lot of answers the Gallery of XSLT Tricks provides non-standard use case of XSLT And I suggest to buy Michael Kay "XSLT Programmer's Reference" book published by Wrox if you plan to work seriously with XSLT in the future. Well, bugs or missing features are always possible, and I will make a point of fixing them in a timely fashion. The best way to report a bug is to use the Gnome bug tracking database (make sure to use the "libxslt" module name). I look at reports there regularly and it's good to have a reminder when a bug is still open. Be sure to specify that the bug is for the package libxslt. There is also a mailing-list xslt@gnome.org for libxslt, with an on-line archive. To subscribe to this list, please visit the associated Web page and follow the instructions. Alternatively, you can just send the bug to the xslt@gnome.org list, if it's really libxslt related I will approve it.. Please do not send me mail directly especially for portability problem, it makes things really harder to track and in some cases I'm not the best person to answer a given question, ask the list instead. Do not send code, I won't debug it (but patches are really appreciated!). Check the following too before posting: use the search engine to get informations related to your problem. make sure you are using a recent version, and that the problem still shows up in those check the list archives to see if the problem was reported already, in this case there is probably a fix available, similarly check the registered open bugs make sure you can reproduce the bug with xsltproc, a very useful thing to do is run the transformation with -v argument and redirect the standard error to a file, then search in this file for the transformation logs just preceding the possible problem Please send the command showing the error as well as the input and stylesheet (as an attachment) Then send the bug with associated informations to reproduce it to the xslt@gnome.org list; if it's really libxslt related I will approve it. Please do not send mail to me directly, it makes things really hard to track and in some cases I am not the best person to answer a given question, ask on the list. To be really clear about support: Support or help request MUST be sent to the list or on bugzilla in case of problems, so that the Question and Answers can be shared publicly. Failing to do so carries the implicit message "I want free support but I don't want to share the benefits with others" and is not welcome. There is no garantee for support, if your question remains unanswered after a week, repost it, making sure you gave all the detail needed and the informations requested. Failing to provide informations as requested or double checking first for prior feedback also carries the implicit message "the time of the library maintainers is less valuable than my time" and might not be welcome. Of course, bugs reports with a suggested patch for fixing them will probably be processed faster. If you're looking for help, a quick look at the list archive may actually provide the answer, I usually send source samples when answering libxslt usage questions. The auto-generated documentation is not as polished as I would like (I need to learn more about Docbook), but it's a good starting point. Daniel Veillard