From: Daniel Veillard
Date: Mon, 13 Aug 2001 08:16:20 +0000 (+0000)
Subject: Added a few pointers to XSLT list, archive, FAQ and Michael Kay's book, Daniel
X-Git-Tag: v1.1.28~1196
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a02a4e36b33c63569bdfabaa8eed19edb2e9bdaa;p=platform%2Fupstream%2Flibxslt.git
Added a few pointers to XSLT list, archive, FAQ and Michael Kay's book, Daniel
---
diff --git a/doc/xslt.html b/doc/xslt.html
index 63c55c4..2441ea8 100644
--- a/doc/xslt.html
+++ b/doc/xslt.html
@@ -1,7 +1,9 @@
+
The XSLT C library for Gnome
-
+
@@ -40,9 +42,9 @@ alt="Red Hat Logo">
-This document describes libxslt, the
-XSLT C library developped for the Gnome project.
+This document describes libxslt,
+the XSLT C library developped for the
+Gnome project.
Here are some key points about libxslt:
@@ -70,35 +72,42 @@ href="http://www.gnome.org/">Gnome project.
doc).
- Look at the mailing-list
archive.
- - Of course since libxslt is based on libxml, it's a good idea to at least
- read libxml description
+ - Of course since libxslt is based on libxml, it's a good idea to at
+ least read libxml description
-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. Check the instructions on
-reporting bugs and be sure to specify that the bug is for the package
-libxslt.
+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. Check the instructions on reporting
+bugs and 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.
+href="http://mail.gnome.org/mailman/listinfo/xslt">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!).
+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!).
+
+If you need help with the XSLT language itself, I strongly suggest to
+subscribe to XSL-list,
+check the XSL-list
+archives, the XSL
+FAQ, and buy Michael Kay "XSLT Programmer's Reference" book published by
+Wrox.
Check the following too before posting:
@@ -106,8 +115,8 @@ appreciated!).
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, similary check the registered open
- bugs
+ there is probably a fix available, similary 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 redirrect the
standard error to a file, then search in this file for the transformation
@@ -121,10 +130,11 @@ 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.
+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.
@@ -166,8 +176,8 @@ href="http://rpmfind.net/linux/RPM/libxslt-devel.html">libxslt-devel
packages installed to compile applications using libxslt.) Igor Zlatkovic is now the maintainer
of the Windows port, he provides
-binaries
+href="http://www.fh-frankfurt.de/~igor/projects/libxml/index.html">he
+provides binaries
Contribs:
@@ -180,8 +190,8 @@ platform, get in touch with me to upload the package. I will keep them in the
The Gnome
CVS base. Check the Gnome CVS Tools page;
- the CVS module is libxslt.
+ href="http://developer.gnome.org/tools/cvs.html">Gnome CVS Tools
+ page; the CVS module is libxslt.
@@ -199,8 +209,8 @@ for a really accurate description
- fixed some variable evaluation problems (with William)
- added profiling of stylesheed excution accessible as the xsltproc
--profile option
- - fixed element-available() and the implementation of the various chunking
- methods present, Norm Walsh provided a lot of feedback
+ - fixed element-available() and the implementation of the various
+ chunking methods present, Norm Walsh provided a lot of feedback
- exclude-result-prefixes and namespaces output should now work as
expected
- added support of embedded stylesheet as described in section 2.7 of the
@@ -355,10 +365,11 @@ for a really accurate description
- second beta version, released at the same time as libxml2-2.3.1
- getting close to feature completion, lot of bug fixes, some in the HTML
and XPath support of libxml
- - start becoming usable for real work. This version can now regenerate the
- XML 2e HTML from the original XML sources and the associated stylesheets
- (in section I of the
- XML REC)
+ - start becoming usable for real work. This version can now regenerate
+ the XML 2e HTML from the original XML sources and the associated
+ stylesheets (in section I of the XML
+ REC)
- Still misses extension element/function/prefixes support. Support of
key() and document() is not complete
@@ -422,9 +433,9 @@ href="tutorial/libxslttutorial.html">tutorial.
Steps 2,3, and 5 will probably need to be changed depending on you
-processing needs and environment for example if reading/saving from/to memory,
-or if you want to apply XInclude processing to the stylesheet or input
-documents.
+processing needs and environment for example if reading/saving from/to
+memory, or if you want to apply XInclude processing to the stylesheet or
+input documents.
@@ -433,8 +444,8 @@ documents.
- William Brack was an early adopted, contibuted a number of patches and
spent quite some time debugging non-trivial problems in early versions of
libxslt
- - Igor Zlatkovic is now the
- maintainer of the Windows port, Igor Zlatkovic
+ is now the maintainer of the Windows port, he
provides binaries
- Thomas Broyer provided a lot of suggestions, and drafted most of the
@@ -443,20 +454,20 @@ documents.
for libxslt
- Matt
- Sergeant developped XML::LibXSLT, a perl wrapper for
- libxml2/libxslt as part of the AxKit XML
- application server
+ Sergeant
+ developped XML::LibXSLT, a perl
+ wrapper for libxml2/libxslt as part of the AxKit XML application server
- there is a module for libxml/libxslt support
in OpenNSD/AOLServer
- - Dave Kuhlman provides
- libxml/libxslt wrappers for
- Python
+ - Dave Kuhlman
+ provides libxml/libxslt wrappers
+ for Python
-I'm still waiting for someone to contribute a simple XSLT processing module
-for Apache :-)
+I'm still waiting for someone to contribute a simple XSLT processing
+module for Apache :-)