From c3e4f3c26035bc93a69e5aa2ad435809e8be8a4e Mon Sep 17 00:00:00 2001 From: Mike Hommey Date: Thu, 10 Sep 2009 22:10:39 +0200 Subject: Import upstream version 2.7.4 --- doc/encoding.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'doc/encoding.html') diff --git a/doc/encoding.html b/doc/encoding.html index b74ddbc..387f6f3 100644 --- a/doc/encoding.html +++ b/doc/encoding.html @@ -7,7 +7,7 @@ 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 } -Encodings support

The XML C parser and toolkit of Gnome

Encodings support

Main Menu

Related links

If you are not really familiar with Internationalization (usual shortcut +Encodings support
The XML C parser and toolkit of Gnome
Encodings support
Main Menu
Home
Reference Manual
Introduction
FAQ
Developer Menu
Reporting bugs and getting help
How to help
Downloads
Releases
XML
XSLT
Validation & DTDs
Encodings support
Catalog support
Namespaces
Contributions
Code Examples
API Menu
XML Guidelines
Recent Changes
Related links
Mail archive
XSLT libxslt
DOM gdome2
XML-DSig xmlsec
FTP
Windows binaries
Solaris binaries
MacOsX binaries
lxml Python bindings
Perl bindings
C++ bindings
PHP bindings
Pascal bindings
Ruby bindings
Tcl bindings
Bug Tracker
If you are not really familiar with Internationalization (usual shortcut is I18N) , Unicode, characters and glyphs, I suggest you read a presentation by Tim Bray on Unicode and why you should care about it.
If you don't understand why it does not make sense to have a string without knowing what encoding it uses, then as Joel Spolsky said please do not @@ -33,7 +33,7 @@ allows the document to be encoded in other encodings at the condition that they are clearly labeled as such. For example the following is a wellformed XML document encoded in ISO-8859-1 and using accentuated letters that we French like for both markup and content:
<?xml version="1.0" encoding="ISO-8859-1"?> -<très>là</très>
Having internationalization support in libxml2 means the following:
the document is properly parsed
+<trÃ¨s>lÃ </trÃ¨s>
Having internationalization support in libxml2 means the following:
the document is properly parsed

information about it's encoding is saved

it can be modified

it can be saved in its original encoding
@@ -51,7 +51,7 @@ an internationalized fashion by libxml2 too:
<!DOCTYPE HTML PUBLIC "- <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> </head> <body> -<p>W3C crée des standards pour le Web.</body> +<p>W3C crÃ©e des standards pour le Web.</body> </html>
The internal encoding, how and why
One of the core decisions was to force all documents to be converted to a default internal encoding, and that encoding to be UTF-8, here are the rationales for those choices:
keeping the native encoding in the internal form would force the libxml @@ -107,10 +107,10 @@ sequence:
when a document is processed, we usually don't know the enc You may end-up with a garbled document, or no document at all ! Example:
~/XML -> ./xmllint err.xml err.xml:1: error: Input is not proper UTF-8, indicate encoding ! -<très>là</très> +<trÃ¨s>lÃ </trÃ¨s> ^ err.xml:1: error: Bytes: 0xE8 0x73 0x3E 0x6C -<très>là</très> +<trÃ¨s>lÃ </trÃ¨s> ^

xmlSwitchEncoding() does an encoding name lookup, canonicalize it, and @@ -163,10 +163,10 @@ encoding:
if no encoding is given, libxml2 will look for an encoding portability is really crucial

Here are a few examples based on the same test document:
~/XML -> ./xmllint isolat1 <?xml version="1.0" encoding="ISO-8859-1"?> -<très>là</très> +<trÃ¨s>lÃ </trÃ¨s> ~/XML -> ./xmllint --encode UTF-8 isolat1 <?xml version="1.0" encoding="UTF-8"?> -<trÃ¨s>lÃ </trÃ¨s> +<trÃƒÂ¨s>lÃƒ </trÃƒÂ¨s> ~/XML ->
The same processing is applied (and reuse most of the code) for HTML I18N processing. Looking up and modifying the content encoding is a bit more difficult since it is located in a <meta> tag under the <head>, -- cgit v1.2.3