http://swpat.ffii.org/
Action against software patents
http://www.gnome.org/
Gnome2 Logo
http://www.w3.org/Status
W3C logo
http://www.redhat.com
Red Hat Logo
http://xmlsoft.org/XSLT/
Made with Libxslt Logo
The XSLT C library for Gnome
Reporting bugs and getting help
Main Menu
index.html
Home
http://xmlsoft.org/wiki
Wiki
intro.html
Introduction
docs.html
Documentation
bugs.html
Reporting bugs and getting help
help.html
How to help
downloads.html
Downloads
FAQ.html
FAQ
news.html
News
xsltproc2.html
The xsltproc tool
docbook.html
DocBook
API.html
The programming API
python.html
Python and bindings
internals.html
Library internals
extensions.html
Writing extensions
contribs.html
Contributions
EXSLT/index.html
libexslt
xslt.html
flat page
,
site.xsl
stylesheet
html/index.html
API Menu
ChangeLog.html
ChangeLog
Related links
tutorial/libxslttutorial.html
Tutorial
,
tutorial2/libxslt_pipes.html
Tutorial2
xsltproc.html
Man page for xsltproc
http://mail.gnome.org/archives/xslt/
Mail archive
http://xmlsoft.org/
XML libxml2
ftp://xmlsoft.org/
FTP
http://www.zlatkovic.com/projects/libxml/
Windows binaries
http://garypennington.net/libxml2/
Solaris binaries
http://www.zveno.com/open_source/libxml2xslt.html
MacOsX binaries
http://bugzilla.gnome.org/buglist.cgi?product=libxslt
Bug Tracker
http://www.zend.com/php5/articles/php5-xmlphp.php#Heading17
XSLT with PHP
http://www.mod-xslt2.com/
Apache module
http://sourceforge.net/projects/libxml2-pas/
Pascal bindings
http://xsldbg.sourceforge.net/
Xsldbg Debugger
API Indexes
APIchunk0.html
Alphabetic
APIconstructors.html
Constructors
APIfunctions.html
Functions/Types
APIfiles.html
Modules
APIsymbols.html
Symbols
If you need help with the XSLT language itself, here are a number of
useful resources:
I strongly suggest to subscribe to
http://www.mulberrytech.com/xsl/xsl-list
XSL-list
, check
http://www.biglist.com/lists/xsl-list/archives/
the XSL-list
archives
The
http://www.dpawson.co.uk/xsl/xslfaq.html
XSL FAQ
.
The
http://www.nwalsh.com/docs/tutorials/xsl/xsl/slides.html
tutorial
written by Paul Grosso and Norman Walsh is a very good on-line
introdution to the language.
The
http://www.zvon.org/xxl/XSLTutorial/Books/Book1/index.html
only
Zvon XSLT tutorial
details a lot of constructs with examples.
http://www.jenitennison.com/xslt/index.html
Jeni Tennison's
XSLT
pages provide links to a lot of answers
the
http://incrementaldevelopment.com/xsltrick/
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
http://www.wrox.com/
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
http://bugzilla.gnome.org/enter_bug.cgi?product=libxslt
Gnome bug
tracking database
(make sure to use the "libxslt" module name). Before
filing a bug, check the
http://bugzilla.gnome.org/buglist.cgi?product=libxslt
list of existing
libxslt bugs
to make sure it hasn't already been filed. 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.
For small problems you can try to get help on IRC, the #xml channel on
irc.gnome.org (port 6667) usually have a few person subscribed which may help
(but there is no garantee and if a real issue is raised it should go on the
mailing-list for archival).
There is also a mailing-list
mailto:xslt@gnome.org
xslt@gnome.org
for libxslt, with an
http://mail.gnome.org/archives/xslt/
on-line archive
. To subscribe
to this list, please visit the
http://mail.gnome.org/mailman/listinfo/xslt
associated Web
page
and follow the instructions.
Alternatively, you can just send the bug to the
mailto:xslt@gnome.org
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!).
Please note that with the current amount of virus and SPAM, sending mail
to the list without being subscribed won't work. There is *far too many
bounces* (in the order of a thousand a day !) I cannot approve them manually
anymore. If your mail to the list bounced waiting for administrator approval,
it is LOST ! Repost it and fix the problem triggering the error.
Check the following too
before
posting
:
search.php
use the search engine
to get informations
related to your problem.
make sure you are
ftp://xmlsoft.org/
using a recent
version
, and that the problem still shows up in those
check the
http://mail.gnome.org/archives/xslt/
list
archives
to see if the problem was reported already, in this case
there is probably a fix available, similarly check the
http://bugzilla.gnome.org/buglist.cgi?product=libxslt
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
mailto:xslt@gnome.org
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. I will automatically Carbon-Copy the
xslt@gnome.org mailing list for any technical reply made about libxml2 or
libxslt.
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
http://mail.gnome.org/archives/xslt/
the list archive
may actually
provide the answer, I usually send source samples when answering libxslt
usage questions. The
html/libxslt-lib.html#LIBXSLT-LIB
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.
bugs.html
Daniel Veillard
