From 07a67fa4bcc1b8bf2651ab41e5fc54a05059cf7e Mon Sep 17 00:00:00 2001
From: Mike Hommey
The original distribution comes from rpmfind.net or xmlsoft.org or gnome.org
Most Linux and BSD distributions include libxml, this is probably the safer way for end-users to use libxml.
@@ -230,7 +230,7 @@ libxml2You probably have an old libxml0 package used to provide the shared library for libxml.so.0, you can probably safely remove it. The libxml packages provided on rpmfind.net provide + href="ftp://xmlsoft.org/libxml2/">xmlsoft.org provide libxml.so.0
Check the following before posting:
The latest versions of libxml2 can be found on the xmlsoft.org server ( xmlsoft.org server ( HTTP, FTP and rsync are available), there is also +href="ftp://xmlsoft.org/libxml2/">FTP and rsync are available), there is also mirrors (Australia( Web), France) or on the win32 directory.
Binary ports:
There is the list of public releases:
+A quick note on the topic of subverting the parser to use a different -internal encoding than UTF-8, in some case people will absolutely want to -keep the internal encoding different, I think it's still possible (but the -encoding must be compliant with ASCII on the same subrange) though I didn't -tried it. The key is to override the default conversion routines (by -registering null encoders/decoders for your charsets), and bypass the UTF-8 -checking of the parser by setting the parser context charset -(ctxt->charset) to something different than XML_CHAR_ENCODING_UTF8, but -there is no guarantee that this will work. You may also have some troubles -saving back.
- -Basically proper I18N support is important, this requires at least -libxml-2.0.0, but a lot of features and corrections are really available only -starting 2.2.
-Table of Content:
@@ -4143,7 +4163,7 @@ literature to point at:should allow to process DocBook documentations without requiring network accesses for the DTD or stylesheets