From 2ee13d9e464a1f5daccaff58f5d09d36b7c4f667 Mon Sep 17 00:00:00 2001 From: Aron Xu Date: Mon, 21 Sep 2015 22:58:06 +0800 Subject: Revert "Imported Upstream version 2.9.1+dfsg1" This reverts commit 7300193becde71a344c8ac0973dc290fa24d800d. --- doc/xmlio.html | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'doc/xmlio.html') diff --git a/doc/xmlio.html b/doc/xmlio.html index 31f5df5..51bb646 100644 --- a/doc/xmlio.html +++ b/doc/xmlio.html @@ -7,14 +7,16 @@ H1 {font-family: Verdana,Arial,Helvetica} H2 {font-family: Verdana,Arial,Helvetica} H3 {font-family: Verdana,Arial,Helvetica} A:link, A:visited, A:active { text-decoration: underline } -I/O Interfaces
Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
Made with Libxml2 Logo

The XML C parser and toolkit of Gnome

I/O Interfaces

Developer Menu
API Indexes
Related links

Table of Content:

  1. General overview
    2. +I/O Interfaces
    Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
    Made with Libxml2 Logo

    The XML C parser and toolkit of Gnome

    I/O Interfaces

    Developer Menu
    API Indexes
    Related links

    Table of Content:

      +
    1. General overview
    2. The basic buffer type
    3. Input I/O handlers
    4. Output I/O handlers
    5. The entities loader
    6. Example of customized I/O

    General overview

    The module xmlIO.h provides -the interfaces to the libxml2 I/O system. This consists of 4 main parts:

    • Entities loader, this is a routine which tries to fetch the entities +the interfaces to the libxml2 I/O system. This consists of 4 main parts:

        +
      • Entities loader, this is a routine which tries to fetch the entities (files) based on their PUBLIC and SYSTEM identifiers. The default loader don't look at the public identifier since libxml2 do not maintain a catalog. You can redefine you own entity loader by using @@ -33,7 +35,8 @@ the interfaces to the libxml2 I/O system. This consists of 4 main parts:

          handlers for certain names.

        The general mechanism used when loading http://rpmfind.net/xml.html for -example in the HTML parser is the following:

        1. The default entity loader calls xmlNewInputFromFile() with +example in the HTML parser is the following:

            +
          1. The default entity loader calls xmlNewInputFromFile() with the parsing context and the URI string.
          2. the URI string is checked against the existing registered handlers using their match() callback function, if the HTTP module was compiled @@ -102,7 +105,8 @@ int main(..) { }

            Example of customized I/O

            This example come from a real use case, xmlDocDump() closes the FILE * passed by the application and this was a problem. The solution was to redefine a -new output handler with the closing call deactivated:

            1. First define a new I/O output allocator where the output don't close +new output handler with the closing call deactivated:

                +
              1. First define a new I/O output allocator where the output don't close the file: 
                xmlOutputBufferPtr
 xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) {
-- 
cgit v1.2.3