diff --git a/ChangeLog b/ChangeLog index 4b779cd9..bc9a1484 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +Thu Feb 15 14:03:18 PST 2007 William Brack + + * doc/xslt.html: Changed all + references to CVS to be SVN; changed corresponding links. + * doc/*html: regenerated the documentation for above + Wed Feb 14 01:21:38 PST 2007 William Brack * libxslt/pattern.c: Fixed problem with namespace on compound diff --git a/doc/API.html b/doc/API.html index 5fa0c785..6ed16a30 100644 --- a/doc/API.html +++ b/doc/API.html @@ -10,7 +10,7 @@ A:link, A:visited, A:active { text-decoration: underline } The programming API
Action against software patentsGNOME2 LogoW3C logoRed Hat Logo
Made with Libxslt Logo

The XSLT C library for GNOME

The programming API

Main Menu
Related links
API Indexes

Okay this section is clearly incomplete. But integrating libxslt into your application should be relatively easy. First check the few steps described -below, then for more detailed informations, look at the generated pages for the API and the source +below, then for more detailed information, look at the generated pages for the API and the source of libxslt/xsltproc.c and the tutorial.

Basically doing an XSLT transformation can be done in a few steps:

  1. configure the parser for XSLT:

    xmlSubstituteEntitiesDefault(1);

    xmlLoadExtDtdDefaultValue = 1;

    diff --git a/doc/bugs.html b/doc/bugs.html index 222a8893..b0b521b3 100644 --- a/doc/bugs.html +++ b/doc/bugs.html @@ -33,7 +33,7 @@ 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 +(but there is no guarantee and if a real issue is raised it should go on the mailing-list for archival).

    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 @@ -47,14 +47,14 @@ 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. Also please note that emails with -a legal warning asking to not copy or redistribute freely the informations +a legal warning asking to not copy or redistribute freely the information they contain are NOT acceptable for the mailing-list, such mail will as much as possible be discarded automatically, and are less likely to be answered if they made it to the list, DO NOT post to the list from an email address where such legal requirements are automatically added, get private paying support if you can't share -informations.

    Check the following too before -posting:

    • use the search engine to get informations +information.

      Check the following too before +posting:

      • use the search engine to get information related to your problem.
      • make sure you are using a recent version, and that the problem still shows up in those
      • @@ -68,7 +68,7 @@ posting:

        • use the search engine to get 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 +

      Then send the bug with associated information 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 @@ -78,10 +78,10 @@ answer a given question, ask on the list.

        To 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, +
      • There is no guarantee 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 + you gave all the detail needed and the information requested.
      • +
      • Failing to provide information 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.
      • diff --git a/doc/docbook.html b/doc/docbook.html index 44d6db81..8108687a 100644 --- a/doc/docbook.html +++ b/doc/docbook.html @@ -12,13 +12,13 @@ A:link, A:visited, A:active { text-decoration: underline } XML/SGML vocabulary particularly well suited to books and papers about computer hardware and software.

        xsltproc and libxslt are not specifically dependant on DocBook, but since a lot of people use xsltproc and libxml2 for DocBook formatting, here are a -few pointers and informations which may be helpful:

diff --git a/doc/extensions.html b/doc/extensions.html index 47585e64..04045af1 100644 --- a/doc/extensions.html +++ b/doc/extensions.html @@ -218,7 +218,7 @@ libxslt:test element, it will output a comment in the result tree:

/**
  * @ctxt:  an XSLT processing context
  * @node:  The current node
  * @inst:  the instruction in the stylesheet
- * @comp:  precomputed informations
+ * @comp:  precomputed information
  *
  * Process a libxslt:test node
  */
diff --git a/doc/internals.html b/doc/internals.html
index 54942f68..663fdada 100644
--- a/doc/internals.html
+++ b/doc/internals.html
@@ -62,7 +62,7 @@ indicates the kind of node it represents, the most common ones are:

  • d
  • text nodes

For the XSLT processing, entity nodes should not be generated (i.e. they should be replaced by their content). Most nodes also contains the following -"navigation" informations: