gtksourceview2 1.1.5-x86-mingw32 → 1.1.6-x86-mingw32

Sign up to get free protection for your applications and to get access to all the features.
Files changed (224) hide show
  1. data/lib/1.8/gtksourceview2.so +0 -0
  2. data/lib/1.9/gtksourceview2.so +0 -0
  3. data/vendor/local/bin/libxml2-2.dll +0 -0
  4. data/vendor/local/bin/xmlcatalog.exe +0 -0
  5. data/vendor/local/bin/xmllint.exe +0 -0
  6. data/vendor/local/include/libxml2/libxml/DOCBparser.h +9 -9
  7. data/vendor/local/include/libxml2/libxml/HTMLparser.h +25 -23
  8. data/vendor/local/include/libxml2/libxml/HTMLtree.h +19 -19
  9. data/vendor/local/include/libxml2/libxml/SAX.h +37 -37
  10. data/vendor/local/include/libxml2/libxml/SAX2.h +34 -34
  11. data/vendor/local/include/libxml2/libxml/c14n.h +1 -1
  12. data/vendor/local/include/libxml2/libxml/catalog.h +35 -35
  13. data/vendor/local/include/libxml2/libxml/debugXML.h +26 -26
  14. data/vendor/local/include/libxml2/libxml/dict.h +16 -5
  15. data/vendor/local/include/libxml2/libxml/encoding.h +28 -14
  16. data/vendor/local/include/libxml2/libxml/hash.h +24 -24
  17. data/vendor/local/include/libxml2/libxml/list.h +26 -26
  18. data/vendor/local/include/libxml2/libxml/nanoftp.h +44 -24
  19. data/vendor/local/include/libxml2/libxml/nanohttp.h +13 -13
  20. data/vendor/local/include/libxml2/libxml/parser.h +78 -73
  21. data/vendor/local/include/libxml2/libxml/parserInternals.h +106 -73
  22. data/vendor/local/include/libxml2/libxml/schemasInternals.h +2 -2
  23. data/vendor/local/include/libxml2/libxml/schematron.h +11 -11
  24. data/vendor/local/include/libxml2/libxml/tree.h +203 -152
  25. data/vendor/local/include/libxml2/libxml/valid.h +72 -72
  26. data/vendor/local/include/libxml2/libxml/xlink.h +7 -7
  27. data/vendor/local/include/libxml2/libxml/xmlIO.h +71 -65
  28. data/vendor/local/include/libxml2/libxml/xmlautomata.h +22 -22
  29. data/vendor/local/include/libxml2/libxml/xmlerror.h +6 -6
  30. data/vendor/local/include/libxml2/libxml/xmlexports.h +2 -2
  31. data/vendor/local/include/libxml2/libxml/xmlmodule.h +1 -1
  32. data/vendor/local/include/libxml2/libxml/xmlreader.h +24 -20
  33. data/vendor/local/include/libxml2/libxml/xmlsave.h +2 -1
  34. data/vendor/local/include/libxml2/libxml/xmlschemas.h +30 -2
  35. data/vendor/local/include/libxml2/libxml/xmlschemastypes.h +20 -20
  36. data/vendor/local/include/libxml2/libxml/xmlstring.h +3 -3
  37. data/vendor/local/include/libxml2/libxml/xmlversion.h +29 -7
  38. data/vendor/local/include/libxml2/libxml/xmlwriter.h +4 -1
  39. data/vendor/local/include/libxml2/libxml/xpath.h +47 -43
  40. data/vendor/local/include/libxml2/libxml/xpathInternals.h +81 -79
  41. data/vendor/local/include/libxml2/libxml/xpointer.h +23 -23
  42. data/vendor/local/lib/libxml2.def +16 -14
  43. data/vendor/local/lib/libxml2.dll.a +0 -0
  44. data/vendor/local/lib/libxml2.lib +0 -0
  45. data/vendor/local/lib/pkgconfig/libxml-2.0.pc +3 -3
  46. data/vendor/local/manifest/libxml2-dev_2.9.0-1_win32.mft +268 -0
  47. data/vendor/local/manifest/libxml2_2.9.0-1_win32.mft +2 -0
  48. data/vendor/local/share/doc/libxml2-2.9.0/Copyright +27 -0
  49. data/vendor/local/share/doc/libxml2-2.9.0/examples/testHTML.c +880 -0
  50. data/vendor/local/share/doc/libxml2-2.9.0/examples/testSAX.c +1198 -0
  51. data/vendor/local/share/doc/libxml2-2.9.0/examples/testXPath.c +229 -0
  52. data/vendor/local/share/doc/libxml2-2.9.0/examples/xmllint.c +3770 -0
  53. data/vendor/local/share/doc/libxml2-2.9.0/html/DOM.gif +0 -0
  54. data/vendor/local/share/doc/libxml2-2.9.0/html/FAQ.html +282 -0
  55. data/vendor/local/share/doc/libxml2-2.9.0/html/Libxml2-Logo-180x168.gif +0 -0
  56. data/vendor/local/share/doc/libxml2-2.9.0/html/Libxml2-Logo-90x34.gif +0 -0
  57. data/vendor/local/share/doc/libxml2-2.9.0/html/encoding.html +207 -0
  58. data/vendor/local/share/doc/libxml2-2.9.0/html/examples.xml +751 -0
  59. data/vendor/local/share/doc/libxml2-2.9.0/html/examples.xsl +174 -0
  60. data/vendor/local/share/doc/libxml2-2.9.0/html/html/book1.html +13 -0
  61. data/vendor/local/share/doc/libxml2-2.9.0/html/html/home.png +0 -0
  62. data/vendor/local/share/doc/libxml2-2.9.0/html/html/index.html +13 -0
  63. data/vendor/local/share/doc/libxml2-2.9.0/html/html/left.png +0 -0
  64. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-DOCBparser.html +51 -0
  65. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-HTMLparser.html +184 -0
  66. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-HTMLtree.html +73 -0
  67. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-SAX.html +125 -0
  68. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-SAX2.html +128 -0
  69. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-c14n.html +38 -0
  70. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-catalog.html +142 -0
  71. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-chvalid.html +72 -0
  72. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-debugXML.html +120 -0
  73. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-dict.html +58 -0
  74. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-encoding.html +124 -0
  75. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-entities.html +79 -0
  76. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-globals.html +152 -0
  77. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-hash.html +116 -0
  78. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-lib.html +13 -0
  79. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-list.html +120 -0
  80. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-nanoftp.html +94 -0
  81. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-nanohttp.html +65 -0
  82. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-parser.html +559 -0
  83. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-parserInternals.html +322 -0
  84. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-pattern.html +76 -0
  85. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-relaxng.html +162 -0
  86. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-schemasInternals.html +373 -0
  87. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-schematron.html +81 -0
  88. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-threads.html +72 -0
  89. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-tree.html +989 -0
  90. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-uri.html +73 -0
  91. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-valid.html +289 -0
  92. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xinclude.html +59 -0
  93. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xlink.html +82 -0
  94. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlIO.html +212 -0
  95. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlautomata.html +85 -0
  96. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlerror.html +864 -0
  97. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlexports.html +20 -0
  98. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlmemory.html +107 -0
  99. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlmodule.html +38 -0
  100. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlreader.html +330 -0
  101. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlregexp.html +143 -0
  102. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlsave.html +60 -0
  103. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlschemas.html +185 -0
  104. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlschemastypes.html +123 -0
  105. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlstring.html +108 -0
  106. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlunicode.html +512 -0
  107. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlversion.html +62 -0
  108. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xmlwriter.html +261 -0
  109. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xpath.html +310 -0
  110. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xpathInternals.html +394 -0
  111. data/vendor/local/share/doc/libxml2-2.9.0/html/html/libxml-xpointer.html +83 -0
  112. data/vendor/local/share/doc/libxml2-2.9.0/html/html/right.png +0 -0
  113. data/vendor/local/share/doc/libxml2-2.9.0/html/html/up.png +0 -0
  114. data/vendor/local/share/doc/libxml2-2.9.0/html/index.html +14 -0
  115. data/vendor/local/share/doc/libxml2-2.9.0/html/io1.c +166 -0
  116. data/vendor/local/share/doc/libxml2-2.9.0/html/io1.res +5 -0
  117. data/vendor/local/share/doc/libxml2-2.9.0/html/io2.c +58 -0
  118. data/vendor/local/share/doc/libxml2-2.9.0/html/io2.res +2 -0
  119. data/vendor/local/share/doc/libxml2-2.9.0/html/libxml.gif +0 -0
  120. data/vendor/local/share/doc/libxml2-2.9.0/html/parse1.c +56 -0
  121. data/vendor/local/share/doc/libxml2-2.9.0/html/parse2.c +72 -0
  122. data/vendor/local/share/doc/libxml2-2.9.0/html/parse3.c +60 -0
  123. data/vendor/local/share/doc/libxml2-2.9.0/html/parse4.c +143 -0
  124. data/vendor/local/share/doc/libxml2-2.9.0/html/reader1.c +107 -0
  125. data/vendor/local/share/doc/libxml2-2.9.0/html/reader1.res +14 -0
  126. data/vendor/local/share/doc/libxml2-2.9.0/html/reader2.c +122 -0
  127. data/vendor/local/share/doc/libxml2-2.9.0/html/reader3.c +120 -0
  128. data/vendor/local/share/doc/libxml2-2.9.0/html/reader3.res +13 -0
  129. data/vendor/local/share/doc/libxml2-2.9.0/html/reader4.c +122 -0
  130. data/vendor/local/share/doc/libxml2-2.9.0/html/reader4.res +3 -0
  131. data/vendor/local/share/doc/libxml2-2.9.0/html/redhat.gif +0 -0
  132. data/vendor/local/share/doc/libxml2-2.9.0/html/smallfootonly.gif +0 -0
  133. data/vendor/local/share/doc/libxml2-2.9.0/html/structure.gif +0 -0
  134. data/vendor/local/share/doc/libxml2-2.9.0/html/test1.xml +1 -0
  135. data/vendor/local/share/doc/libxml2-2.9.0/html/test2.xml +13 -0
  136. data/vendor/local/share/doc/libxml2-2.9.0/html/test3.xml +39 -0
  137. data/vendor/local/share/doc/libxml2-2.9.0/html/testWriter.c +1198 -0
  138. data/vendor/local/share/doc/libxml2-2.9.0/html/tree1.c +94 -0
  139. data/vendor/local/share/doc/libxml2-2.9.0/html/tree1.res +4 -0
  140. data/vendor/local/share/doc/libxml2-2.9.0/html/tree2.c +118 -0
  141. data/vendor/local/share/doc/libxml2-2.9.0/html/tree2.res +18 -0
  142. data/vendor/local/share/doc/libxml2-2.9.0/html/tst.xml +7 -0
  143. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/apa.html +8 -0
  144. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/apb.html +14 -0
  145. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/apc.html +82 -0
  146. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/apd.html +76 -0
  147. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ape.html +78 -0
  148. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/apf.html +67 -0
  149. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/apg.html +75 -0
  150. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/aph.html +76 -0
  151. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/api.html +4 -0
  152. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ar01s02.html +14 -0
  153. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ar01s03.html +47 -0
  154. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ar01s04.html +54 -0
  155. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ar01s05.html +55 -0
  156. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ar01s06.html +35 -0
  157. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ar01s07.html +30 -0
  158. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ar01s08.html +38 -0
  159. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ar01s09.html +63 -0
  160. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/blank.png +0 -0
  161. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/1.png +0 -0
  162. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/10.png +0 -0
  163. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/2.png +0 -0
  164. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/3.png +0 -0
  165. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/4.png +0 -0
  166. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/5.png +0 -0
  167. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/6.png +0 -0
  168. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/7.png +0 -0
  169. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/8.png +0 -0
  170. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/callouts/9.png +0 -0
  171. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/caution.png +0 -0
  172. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/draft.png +0 -0
  173. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/home.png +0 -0
  174. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/important.png +0 -0
  175. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/next.png +0 -0
  176. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/note.png +0 -0
  177. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/prev.png +0 -0
  178. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/tip.png +0 -0
  179. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/toc-blank.png +0 -0
  180. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/toc-minus.png +0 -0
  181. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/toc-plus.png +0 -0
  182. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/up.png +0 -0
  183. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/images/warning.png +0 -0
  184. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/includeaddattribute.c +64 -0
  185. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/includeaddkeyword.c +75 -0
  186. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/includeconvert.c +73 -0
  187. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/includegetattribute.c +72 -0
  188. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/includekeyword.c +79 -0
  189. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/includexpath.c +74 -0
  190. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/index.html +14 -0
  191. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/ix01.html +1 -0
  192. data/vendor/local/share/doc/libxml2-2.9.0/html/tutorial/xmltutorial.pdf +1336 -0
  193. data/vendor/local/share/doc/libxml2-2.9.0/html/w3c.png +0 -0
  194. data/vendor/local/share/doc/libxml2-2.9.0/html/writer.xml +2 -0
  195. data/vendor/local/share/doc/libxml2-2.9.0/html/xml.html +5715 -0
  196. data/vendor/local/share/doc/libxml2-2.9.0/html/xpath1.c +250 -0
  197. data/vendor/local/share/doc/libxml2-2.9.0/html/xpath1.res +5 -0
  198. data/vendor/local/share/doc/libxml2-2.9.0/html/xpath2.c +190 -0
  199. data/vendor/local/share/doc/libxml2-2.9.0/html/xpath2.res +30 -0
  200. data/vendor/local/share/gtk-doc/html/libxml2/general.html +1 -1
  201. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-HTMLparser.html +3 -1
  202. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-dict.html +16 -1
  203. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-encoding.html +11 -1
  204. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-nanoftp.html +15 -5
  205. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-parser.html +8 -4
  206. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-parserInternals.html +20 -5
  207. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-tree.html +72 -18
  208. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xmlIO.html +10 -0
  209. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xmlerror.html +5 -3
  210. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xmlmodule.html +2 -2
  211. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xmlreader.html +8 -3
  212. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xmlsave.html +2 -1
  213. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xmlschemas.html +15 -0
  214. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xmlversion.html +12 -2
  215. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xmlwriter.html +8 -3
  216. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xpath.html +3 -0
  217. data/vendor/local/share/gtk-doc/html/libxml2/libxml2-xpathInternals.html +9 -9
  218. data/vendor/local/share/gtk-doc/html/libxml2/libxml2.devhelp +42 -2
  219. data/vendor/local/share/man/man1/xml2-config.1 +0 -1
  220. data/vendor/local/share/man/man1/xmlcatalog.1 +204 -93
  221. data/vendor/local/share/man/man3/libxml.3 +1 -1
  222. data/vendor/local/src/dieterv/packaging/libxml2_2.9.0-1_win32.log +867 -0
  223. data/vendor/local/src/dieterv/packaging/libxml2_2.9.0-1_win32.sh +68 -0
  224. metadata +163 -7
@@ -0,0 +1,282 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3
+ <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><link rel="SHORTCUT ICON" href="/favicon.ico" /><style type="text/css">
4
+ TD {font-family: Verdana,Arial,Helvetica}
5
+ BODY {font-family: Verdana,Arial,Helvetica; margin-top: 2em; margin-left: 0em; margin-right: 0em}
6
+ H1 {font-family: Verdana,Arial,Helvetica}
7
+ H2 {font-family: Verdana,Arial,Helvetica}
8
+ H3 {font-family: Verdana,Arial,Helvetica}
9
+ A:link, A:visited, A:active { text-decoration: underline }
10
+ </style><title>FAQ</title></head><body bgcolor="#8b7765" text="#000000" link="#a06060" vlink="#000000"><table border="0" width="100%" cellpadding="5" cellspacing="0" align="center"><tr><td width="120"><a href="http://swpat.ffii.org/"><img src="epatents.png" alt="Action against software patents" /></a></td><td width="180"><a href="http://www.gnome.org/"><img src="gnome2.png" alt="Gnome2 Logo" /></a><a href="http://www.w3.org/Status"><img src="w3c.png" alt="W3C Logo" /></a><a href="http://www.redhat.com/"><img src="redhat.gif" alt="Red Hat Logo" /></a><div align="left"><a href="http://xmlsoft.org/"><img src="Libxml2-Logo-180x168.gif" alt="Made with Libxml2 Logo" /></a></div></td><td><table border="0" width="90%" cellpadding="2" cellspacing="0" align="center" bgcolor="#000000"><tr><td><table width="100%" border="0" cellspacing="1" cellpadding="3" bgcolor="#fffacd"><tr><td align="center"><h1>The XML C parser and toolkit of Gnome</h1><h2>FAQ</h2></td></tr></table></td></tr></table></td></tr></table><table border="0" cellpadding="4" cellspacing="0" width="100%" align="center"><tr><td bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td valign="top" width="200" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table width="100%" border="0" cellspacing="1" cellpadding="3"><tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Main Menu</b></center></td></tr><tr><td bgcolor="#fffacd"><form action="search.php" enctype="application/x-www-form-urlencoded" method="get"><input name="query" type="text" size="20" value="" /><input name="submit" type="submit" value="Search ..." /></form><ul><li><a href="index.html">Home</a></li><li><a href="html/index.html">Reference Manual</a></li><li><a href="intro.html">Introduction</a></li><li><a href="FAQ.html">FAQ</a></li><li><a href="docs.html" style="font-weight:bold">Developer Menu</a></li><li><a href="bugs.html">Reporting bugs and getting help</a></li><li><a href="help.html">How to help</a></li><li><a href="downloads.html">Downloads</a></li><li><a href="news.html">Releases</a></li><li><a href="XMLinfo.html">XML</a></li><li><a href="XSLT.html">XSLT</a></li><li><a href="xmldtd.html">Validation &amp; DTDs</a></li><li><a href="encoding.html">Encodings support</a></li><li><a href="catalog.html">Catalog support</a></li><li><a href="namespaces.html">Namespaces</a></li><li><a href="contribs.html">Contributions</a></li><li><a href="examples/index.html" style="font-weight:bold">Code Examples</a></li><li><a href="html/index.html" style="font-weight:bold">API Menu</a></li><li><a href="guidelines.html">XML Guidelines</a></li><li><a href="ChangeLog.html">Recent Changes</a></li></ul></td></tr></table><table width="100%" border="0" cellspacing="1" cellpadding="3"><tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Related links</b></center></td></tr><tr><td bgcolor="#fffacd"><ul><li><a href="http://mail.gnome.org/archives/xml/">Mail archive</a></li><li><a href="http://xmlsoft.org/XSLT/">XSLT libxslt</a></li><li><a href="http://phd.cs.unibo.it/gdome2/">DOM gdome2</a></li><li><a href="http://www.aleksey.com/xmlsec/">XML-DSig xmlsec</a></li><li><a href="ftp://xmlsoft.org/">FTP</a></li><li><a href="http://www.zlatkovic.com/projects/libxml/">Windows binaries</a></li><li><a href="http://opencsw.org/packages/libxml2">Solaris binaries</a></li><li><a href="http://www.explain.com.au/oss/libxml2xslt.html">MacOsX binaries</a></li><li><a href="http://lxml.de/">lxml Python bindings</a></li><li><a href="http://cpan.uwinnipeg.ca/dist/XML-LibXML">Perl bindings</a></li><li><a href="http://libxmlplusplus.sourceforge.net/">C++ bindings</a></li><li><a href="http://www.zend.com/php5/articles/php5-xmlphp.php#Heading4">PHP bindings</a></li><li><a href="http://sourceforge.net/projects/libxml2-pas/">Pascal bindings</a></li><li><a href="http://libxml.rubyforge.org/">Ruby bindings</a></li><li><a href="http://tclxml.sourceforge.net/">Tcl bindings</a></li><li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Bug Tracker</a></li></ul></td></tr></table></td></tr></table></td><td valign="top" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%"><tr><td><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table border="0" cellpadding="3" cellspacing="1" width="100%"><tr><td bgcolor="#fffacd"><p>Table of Contents:</p><ul><li><a href="FAQ.html#License">License(s)</a></li>
11
+ <li><a href="FAQ.html#Installati">Installation</a></li>
12
+ <li><a href="FAQ.html#Compilatio">Compilation</a></li>
13
+ <li><a href="FAQ.html#Developer">Developer corner</a></li>
14
+ </ul><h3><a name="License" id="License">License</a>(s)</h3><ol><li><em>Licensing Terms for libxml</em>
15
+ <p>libxml2 is released under the <a href="http://www.opensource.org/licenses/mit-license.html">MIT
16
+ License</a>; see the file Copyright in the distribution for the precise
17
+ wording</p>
18
+ </li>
19
+ <li><em>Can I embed libxml2 in a proprietary application ?</em>
20
+ <p>Yes. The MIT License allows you to keep proprietary the changes you
21
+ made to libxml, but it would be graceful to send-back bug fixes and
22
+ improvements as patches for possible incorporation in the main
23
+ development tree.</p>
24
+ </li>
25
+ </ol><h3><a name="Installati" id="Installati">Installation</a></h3><ol><li><strong><span style="background-color: #FF0000">Do Not Use
26
+ libxml1</span></strong>, use libxml2</li>
27
+ <p></p>
28
+ <li><em>Where can I get libxml</em> ?
29
+ <p>The original distribution comes from <a href="ftp://xmlsoft.org/libxml2/">xmlsoft.org</a> or <a href="ftp://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/">gnome.org</a></p>
30
+ <p>Most Linux and BSD distributions include libxml, this is probably the
31
+ safer way for end-users to use libxml.</p>
32
+ <p>David Doolin provides precompiled Windows versions at <a href="http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/ ">http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/</a></p>
33
+ </li>
34
+ <p></p>
35
+ <li><em>I see libxml and libxml2 releases, which one should I install ?</em>
36
+ <ul><li>If you are not constrained by backward compatibility issues with
37
+ existing applications, install libxml2 only</li>
38
+ <li>If you are not doing development, you can safely install both.
39
+ Usually the packages <a href="http://rpmfind.net/linux/RPM/libxml.html">libxml</a> and <a href="http://rpmfind.net/linux/RPM/libxml2.html">libxml2</a> are
40
+ compatible (this is not the case for development packages).</li>
41
+ <li>If you are a developer and your system provides separate packaging
42
+ for shared libraries and the development components, it is possible
43
+ to install libxml and libxml2, and also <a href="http://rpmfind.net/linux/RPM/libxml-devel.html">libxml-devel</a>
44
+ and <a href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml2-devel</a>
45
+ too for libxml2 &gt;= 2.3.0</li>
46
+ <li>If you are developing a new application, please develop against
47
+ libxml2(-devel)</li>
48
+ </ul></li>
49
+ <li><em>I can't install the libxml package, it conflicts with libxml0</em>
50
+ <p>You probably have an old libxml0 package used to provide the shared
51
+ library for libxml.so.0, you can probably safely remove it. The libxml
52
+ packages provided on <a href="ftp://xmlsoft.org/libxml2/">xmlsoft.org</a> provide
53
+ libxml.so.0</p>
54
+ </li>
55
+ <li><em>I can't install the libxml(2) RPM package due to failed
56
+ dependencies</em>
57
+ <p>The most generic solution is to re-fetch the latest src.rpm , and
58
+ rebuild it locally with</p>
59
+ <p><code>rpm --rebuild libxml(2)-xxx.src.rpm</code>.</p>
60
+ <p>If everything goes well it will generate two binary rpm packages (one
61
+ providing the shared libs and xmllint, and the other one, the -devel
62
+ package, providing includes, static libraries and scripts needed to build
63
+ applications with libxml(2)) that you can install locally.</p>
64
+ </li>
65
+ </ol><h3><a name="Compilatio" id="Compilatio">Compilation</a></h3><ol><li><em>What is the process to compile libxml2 ?</em>
66
+ <p>As most UNIX libraries libxml2 follows the "standard":</p>
67
+ <p><code>gunzip -c xxx.tar.gz | tar xvf -</code></p>
68
+ <p><code>cd libxml-xxxx</code></p>
69
+ <p><code>./configure --help</code></p>
70
+ <p>to see the options, then the compilation/installation proper</p>
71
+ <p><code>./configure [possible options]</code></p>
72
+ <p><code>make</code></p>
73
+ <p><code>make install</code></p>
74
+ <p>At that point you may have to rerun ldconfig or a similar utility to
75
+ update your list of installed shared libs.</p>
76
+ </li>
77
+ <li><em>What other libraries are needed to compile/install libxml2 ?</em>
78
+ <p>Libxml2 does not require any other library, the normal C ANSI API
79
+ should be sufficient (please report any violation to this rule you may
80
+ find).</p>
81
+ <p>However if found at configuration time libxml2 will detect and use the
82
+ following libs:</p>
83
+ <ul><li><a href="http://www.info-zip.org/pub/infozip/zlib/">libz</a> : a
84
+ highly portable and available widely compression library.</li>
85
+ <li>iconv: a powerful character encoding conversion library. It is
86
+ included by default in recent glibc libraries, so it doesn't need to
87
+ be installed specifically on Linux. It now seems a <a href="http://www.opennc.org/onlinepubs/7908799/xsh/iconv.html">part
88
+ of the official UNIX</a> specification. Here is one <a href="http://www.gnu.org/software/libiconv/">implementation of the
89
+ library</a> which source can be found <a href="ftp://ftp.ilog.fr/pub/Users/haible/gnu/">here</a>.</li>
90
+ </ul></li>
91
+ <p></p>
92
+ <li><em>Make check fails on some platforms</em>
93
+ <p>Sometimes the regression tests' results don't completely match the
94
+ value produced by the parser, and the makefile uses diff to print the
95
+ delta. On some platforms the diff return breaks the compilation process;
96
+ if the diff is small this is probably not a serious problem.</p>
97
+ <p>Sometimes (especially on Solaris) make checks fail due to limitations
98
+ in make. Try using GNU-make instead.</p>
99
+ </li>
100
+ <li><em>I use the SVN version and there is no configure script</em>
101
+ <p>The configure script (and other Makefiles) are generated. Use the
102
+ autogen.sh script to regenerate the configure script and Makefiles,
103
+ like:</p>
104
+ <p><code>./autogen.sh --prefix=/usr --disable-shared</code></p>
105
+ </li>
106
+ <li><em>I have troubles when running make tests with gcc-3.0</em>
107
+ <p>It seems the initial release of gcc-3.0 has a problem with the
108
+ optimizer which miscompiles the URI module. Please use another
109
+ compiler.</p>
110
+ </li>
111
+ </ol><h3><a name="Developer" id="Developer">Developer</a> corner</h3><ol><li><em>Troubles compiling or linking programs using libxml2</em>
112
+ <p>Usually the problem comes from the fact that the compiler doesn't get
113
+ the right compilation or linking flags. There is a small shell script
114
+ <code>xml2-config</code> which is installed as part of libxml2 usual
115
+ install process which provides those flags. Use</p>
116
+ <p><code>xml2-config --cflags</code></p>
117
+ <p>to get the compilation flags and</p>
118
+ <p><code>xml2-config --libs</code></p>
119
+ <p>to get the linker flags. Usually this is done directly from the
120
+ Makefile as:</p>
121
+ <p><code>CFLAGS=`xml2-config --cflags`</code></p>
122
+ <p><code>LIBS=`xml2-config --libs`</code></p>
123
+ </li>
124
+ <li><em>I want to install my own copy of libxml2 in my home directory and
125
+ link my programs against it, but it doesn't work</em>
126
+ <p>There are many different ways to accomplish this. Here is one way to
127
+ do this under Linux. Suppose your home directory is <code>/home/user.
128
+ </code>Then:</p>
129
+ <ul><li>Create a subdirectory, let's call it <code>myxml</code></li>
130
+ <li>unpack the libxml2 distribution into that subdirectory</li>
131
+ <li>chdir into the unpacked distribution
132
+ (<code>/home/user/myxml/libxml2 </code>)</li>
133
+ <li>configure the library using the "<code>--prefix</code>" switch,
134
+ specifying an installation subdirectory in
135
+ <code>/home/user/myxml</code>, e.g.
136
+ <p><code>./configure --prefix /home/user/myxml/xmlinst</code> {other
137
+ configuration options}</p>
138
+ </li>
139
+ <li>now run <code>make</code> followed by <code>make install</code></li>
140
+ <li>At this point, the installation subdirectory contains the complete
141
+ "private" include files, library files and binary program files (e.g.
142
+ xmllint), located in
143
+ <p><code>/home/user/myxml/xmlinst/lib,
144
+ /home/user/myxml/xmlinst/include </code> and <code>
145
+ /home/user/myxml/xmlinst/bin</code></p>
146
+ respectively.</li>
147
+ <li>In order to use this "private" library, you should first add it to
148
+ the beginning of your default PATH (so that your own private program
149
+ files such as xmllint will be used instead of the normal system
150
+ ones). To do this, the Bash command would be
151
+ <p><code>export PATH=/home/user/myxml/xmlinst/bin:$PATH</code></p>
152
+ </li>
153
+ <li>Now suppose you have a program <code>test1.c</code> that you would
154
+ like to compile with your "private" library. Simply compile it using
155
+ the command
156
+ <p><code>gcc `xml2-config --cflags --libs` -o test test.c</code></p>
157
+ Note that, because your PATH has been set with <code>
158
+ /home/user/myxml/xmlinst/bin</code> at the beginning, the xml2-config
159
+ program which you just installed will be used instead of the system
160
+ default one, and this will <em>automatically</em> get the correct
161
+ libraries linked with your program.</li>
162
+ </ul></li>
163
+
164
+ <p></p>
165
+ <li><em>xmlDocDump() generates output on one line.</em>
166
+ <p>Libxml2 will not <strong>invent</strong> spaces in the content of a
167
+ document since <strong>all spaces in the content of a document are
168
+ significant</strong>. If you build a tree from the API and want
169
+ indentation:</p>
170
+ <ol><li>the correct way is to generate those yourself too.</li>
171
+ <li>the dangerous way is to ask libxml2 to add those blanks to your
172
+ content <strong>modifying the content of your document in the
173
+ process</strong>. The result may not be what you expect. There is
174
+ <strong>NO</strong> way to guarantee that such a modification won't
175
+ affect other parts of the content of your document. See <a href="http://xmlsoft.org/html/libxml-parser.html#xmlKeepBlanksDefault">xmlKeepBlanksDefault
176
+ ()</a> and <a href="http://xmlsoft.org/html/libxml-tree.html#xmlSaveFormatFile">xmlSaveFormatFile
177
+ ()</a></li>
178
+ </ol></li>
179
+ <p></p>
180
+ <li><em>Extra nodes in the document:</em>
181
+ <p><em>For an XML file as below:</em></p>
182
+ <pre>&lt;?xml version="1.0"?&gt;
183
+ &lt;PLAN xmlns="http://www.argus.ca/autotest/1.0/"&gt;
184
+ &lt;NODE CommFlag="0"/&gt;
185
+ &lt;NODE CommFlag="1"/&gt;
186
+ &lt;/PLAN&gt;</pre>
187
+ <p><em>after parsing it with the function
188
+ pxmlDoc=xmlParseFile(...);</em></p>
189
+ <p><em>I want to the get the content of the first node (node with the
190
+ CommFlag="0")</em></p>
191
+ <p><em>so I did it as following;</em></p>
192
+ <pre>xmlNodePtr pnode;
193
+ pnode=pxmlDoc-&gt;children-&gt;children;</pre>
194
+ <p><em>but it does not work. If I change it to</em></p>
195
+ <pre>pnode=pxmlDoc-&gt;children-&gt;children-&gt;next;</pre>
196
+ <p><em>then it works. Can someone explain it to me.</em></p>
197
+ <p></p>
198
+ <p>In XML all characters in the content of the document are significant
199
+ <strong>including blanks and formatting line breaks</strong>.</p>
200
+ <p>The extra nodes you are wondering about are just that, text nodes with
201
+ the formatting spaces which are part of the document but that people tend
202
+ to forget. There is a function <a href="http://xmlsoft.org/html/libxml-parser.html">xmlKeepBlanksDefault
203
+ ()</a> to remove those at parse time, but that's an heuristic, and its
204
+ use should be limited to cases where you are certain there is no
205
+ mixed-content in the document.</p>
206
+ </li>
207
+ <li><em>I get compilation errors of existing code like when accessing
208
+ <strong>root</strong> or <strong>child fields</strong> of nodes.</em>
209
+ <p>You are compiling code developed for libxml version 1 and using a
210
+ libxml2 development environment. Either switch back to libxml v1 devel or
211
+ even better fix the code to compile with libxml2 (or both) by <a href="upgrade.html">following the instructions</a>.</p>
212
+ </li>
213
+ <li><em>I get compilation errors about non existing
214
+ <strong>xmlRootNode</strong> or <strong>xmlChildrenNode</strong>
215
+ fields.</em>
216
+ <p>The source code you are using has been <a href="upgrade.html">upgraded</a> to be able to compile with both libxml
217
+ and libxml2, but you need to install a more recent version:
218
+ libxml(-devel) &gt;= 1.8.8 or libxml2(-devel) &gt;= 2.1.0</p>
219
+ </li>
220
+ <li><em>Random crashes in threaded applications</em>
221
+ <p>Read and follow all advices on the <a href="threads.html">thread
222
+ safety</a> page, and make 100% sure you never call xmlCleanupParser()
223
+ while the library or an XML document might still be in use by another
224
+ thread.</p>
225
+ </li>
226
+ <li><em>The example provided in the web page does not compile.</em>
227
+ <p>It's hard to maintain the documentation in sync with the code
228
+ &lt;grin/&gt; ...</p>
229
+ <p>Check the previous points 1/ and 2/ raised before, and please send
230
+ patches.</p>
231
+ </li>
232
+ <li><em>Where can I get more examples and information than provided on the
233
+ web page?</em>
234
+ <p>Ideally a libxml2 book would be nice. I have no such plan ... But you
235
+ can:</p>
236
+ <ul><li>check more deeply the <a href="html/libxml-lib.html">existing
237
+ generated doc</a></li>
238
+ <li>have a look at <a href="examples/index.html">the set of
239
+ examples</a>.</li>
240
+ <li>look for examples of use for libxml2 function using the Gnome code
241
+ or by asking on Google.</li>
242
+ <li><a href="http://svn.gnome.org/viewvc/libxml2/trunk/">Browse
243
+ the libxml2 source</a> , I try to write code as clean and documented
244
+ as possible, so looking at it may be helpful. In particular the code
245
+ of <a href="http://svn.gnome.org/viewvc/libxml2/trunk/xmllint.c?view=markup">xmllint.c</a> and of the various testXXX.c test programs should
246
+ provide good examples of how to do things with the library.</li>
247
+ </ul></li>
248
+ <p></p>
249
+ <li><em>What about C++ ?</em>
250
+ <p>libxml2 is written in pure C in order to allow easy reuse on a number
251
+ of platforms, including embedded systems. I don't intend to convert to
252
+ C++.</p>
253
+ <p>There is however a C++ wrapper which may fulfill your needs:</p>
254
+ <ul><li>by Ari Johnson &lt;ari@btigate.com&gt;:
255
+ <p>Website: <a href="http://libxmlplusplus.sourceforge.net/">http://libxmlplusplus.sourceforge.net/</a></p>
256
+ <p>Download: <a href="http://sourceforge.net/project/showfiles.php?group_id=12999">http://sourceforge.net/project/showfiles.php?group_id=12999</a></p>
257
+ </li>
258
+ </ul></li>
259
+ <li><em>How to validate a document a posteriori ?</em>
260
+ <p>It is possible to validate documents which had not been validated at
261
+ initial parsing time or documents which have been built from scratch
262
+ using the API. Use the <a href="http://xmlsoft.org/html/libxml-valid.html#xmlValidateDtd">xmlValidateDtd()</a>
263
+ function. It is also possible to simply add a DTD to an existing
264
+ document:</p>
265
+ <pre>xmlDocPtr doc; /* your existing document */
266
+ xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
267
+
268
+ dtd-&gt;name = xmlStrDup((xmlChar*)"root_name"); /* use the given root */
269
+
270
+ doc-&gt;intSubset = dtd;
271
+ if (doc-&gt;children == NULL) xmlAddChild((xmlNodePtr)doc, (xmlNodePtr)dtd);
272
+ else xmlAddPrevSibling(doc-&gt;children, (xmlNodePtr)dtd);
273
+ </pre>
274
+ </li>
275
+ <li><em>So what is this funky "xmlChar" used all the time?</em>
276
+ <p>It is a null terminated sequence of utf-8 characters. And only utf-8!
277
+ You need to convert strings encoded in different ways to utf-8 before
278
+ passing them to the API. This can be accomplished with the iconv library
279
+ for instance.</p>
280
+ </li>
281
+ <li>etc ...</li>
282
+ </ol><p></p><p><a href="bugs.html">Daniel Veillard</a></p></td></tr></table></td></tr></table></td></tr></table></td></tr></table></td></tr></table></body></html>
@@ -0,0 +1,207 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3
+ <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><link rel="SHORTCUT ICON" href="/favicon.ico" /><style type="text/css">
4
+ TD {font-family: Verdana,Arial,Helvetica}
5
+ BODY {font-family: Verdana,Arial,Helvetica; margin-top: 2em; margin-left: 0em; margin-right: 0em}
6
+ H1 {font-family: Verdana,Arial,Helvetica}
7
+ H2 {font-family: Verdana,Arial,Helvetica}
8
+ H3 {font-family: Verdana,Arial,Helvetica}
9
+ A:link, A:visited, A:active { text-decoration: underline }
10
+ </style><title>Encodings support</title></head><body bgcolor="#8b7765" text="#000000" link="#a06060" vlink="#000000"><table border="0" width="100%" cellpadding="5" cellspacing="0" align="center"><tr><td width="120"><a href="http://swpat.ffii.org/"><img src="epatents.png" alt="Action against software patents" /></a></td><td width="180"><a href="http://www.gnome.org/"><img src="gnome2.png" alt="Gnome2 Logo" /></a><a href="http://www.w3.org/Status"><img src="w3c.png" alt="W3C Logo" /></a><a href="http://www.redhat.com/"><img src="redhat.gif" alt="Red Hat Logo" /></a><div align="left"><a href="http://xmlsoft.org/"><img src="Libxml2-Logo-180x168.gif" alt="Made with Libxml2 Logo" /></a></div></td><td><table border="0" width="90%" cellpadding="2" cellspacing="0" align="center" bgcolor="#000000"><tr><td><table width="100%" border="0" cellspacing="1" cellpadding="3" bgcolor="#fffacd"><tr><td align="center"><h1>The XML C parser and toolkit of Gnome</h1><h2>Encodings support</h2></td></tr></table></td></tr></table></td></tr></table><table border="0" cellpadding="4" cellspacing="0" width="100%" align="center"><tr><td bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td valign="top" width="200" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table width="100%" border="0" cellspacing="1" cellpadding="3"><tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Main Menu</b></center></td></tr><tr><td bgcolor="#fffacd"><form action="search.php" enctype="application/x-www-form-urlencoded" method="get"><input name="query" type="text" size="20" value="" /><input name="submit" type="submit" value="Search ..." /></form><ul><li><a href="index.html">Home</a></li><li><a href="html/index.html">Reference Manual</a></li><li><a href="intro.html">Introduction</a></li><li><a href="FAQ.html">FAQ</a></li><li><a href="docs.html" style="font-weight:bold">Developer Menu</a></li><li><a href="bugs.html">Reporting bugs and getting help</a></li><li><a href="help.html">How to help</a></li><li><a href="downloads.html">Downloads</a></li><li><a href="news.html">Releases</a></li><li><a href="XMLinfo.html">XML</a></li><li><a href="XSLT.html">XSLT</a></li><li><a href="xmldtd.html">Validation &amp; DTDs</a></li><li><a href="encoding.html">Encodings support</a></li><li><a href="catalog.html">Catalog support</a></li><li><a href="namespaces.html">Namespaces</a></li><li><a href="contribs.html">Contributions</a></li><li><a href="examples/index.html" style="font-weight:bold">Code Examples</a></li><li><a href="html/index.html" style="font-weight:bold">API Menu</a></li><li><a href="guidelines.html">XML Guidelines</a></li><li><a href="ChangeLog.html">Recent Changes</a></li></ul></td></tr></table><table width="100%" border="0" cellspacing="1" cellpadding="3"><tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Related links</b></center></td></tr><tr><td bgcolor="#fffacd"><ul><li><a href="http://mail.gnome.org/archives/xml/">Mail archive</a></li><li><a href="http://xmlsoft.org/XSLT/">XSLT libxslt</a></li><li><a href="http://phd.cs.unibo.it/gdome2/">DOM gdome2</a></li><li><a href="http://www.aleksey.com/xmlsec/">XML-DSig xmlsec</a></li><li><a href="ftp://xmlsoft.org/">FTP</a></li><li><a href="http://www.zlatkovic.com/projects/libxml/">Windows binaries</a></li><li><a href="http://opencsw.org/packages/libxml2">Solaris binaries</a></li><li><a href="http://www.explain.com.au/oss/libxml2xslt.html">MacOsX binaries</a></li><li><a href="http://lxml.de/">lxml Python bindings</a></li><li><a href="http://cpan.uwinnipeg.ca/dist/XML-LibXML">Perl bindings</a></li><li><a href="http://libxmlplusplus.sourceforge.net/">C++ bindings</a></li><li><a href="http://www.zend.com/php5/articles/php5-xmlphp.php#Heading4">PHP bindings</a></li><li><a href="http://sourceforge.net/projects/libxml2-pas/">Pascal bindings</a></li><li><a href="http://libxml.rubyforge.org/">Ruby bindings</a></li><li><a href="http://tclxml.sourceforge.net/">Tcl bindings</a></li><li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Bug Tracker</a></li></ul></td></tr></table></td></tr></table></td><td valign="top" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%"><tr><td><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table border="0" cellpadding="3" cellspacing="1" width="100%"><tr><td bgcolor="#fffacd"><p>If you are not really familiar with Internationalization (usual shortcut
11
+ is I18N) , Unicode, characters and glyphs, I suggest you read a <a href="http://www.tbray.org/ongoing/When/200x/2003/04/06/Unicode">presentation</a>
12
+ by Tim Bray on Unicode and why you should care about it.</p><p>If you don't understand why <b>it does not make sense to have a string
13
+ without knowing what encoding it uses</b>, then as Joel Spolsky said <a href="http://www.joelonsoftware.com/articles/Unicode.html">please do not
14
+ write another line of code until you finish reading that article.</a>. It is
15
+ a prerequisite to understand this page, and avoid a lot of problems with
16
+ libxml2, XML or text processing in general.</p><p>Table of Content:</p><ol><li><a href="encoding.html#What">What does internationalization support
17
+ mean ?</a></li>
18
+ <li><a href="encoding.html#internal">The internal encoding, how and
19
+ why</a></li>
20
+ <li><a href="encoding.html#implemente">How is it implemented ?</a></li>
21
+ <li><a href="encoding.html#Default">Default supported encodings</a></li>
22
+ <li><a href="encoding.html#extend">How to extend the existing
23
+ support</a></li>
24
+ </ol><h3><a name="What" id="What">What does internationalization support mean ?</a></h3><p>XML was designed from the start to allow the support of any character set
25
+ by using Unicode. Any conformant XML parser has to support the UTF-8 and
26
+ UTF-16 default encodings which can both express the full unicode ranges. UTF8
27
+ is a variable length encoding whose greatest points are to reuse the same
28
+ encoding for ASCII and to save space for Western encodings, but it is a bit
29
+ more complex to handle in practice. UTF-16 use 2 bytes per character (and
30
+ sometimes combines two pairs), it makes implementation easier, but looks a
31
+ bit overkill for Western languages encoding. Moreover the XML specification
32
+ allows the document to be encoded in other encodings at the condition that
33
+ they are clearly labeled as such. For example the following is a wellformed
34
+ XML document encoded in ISO-8859-1 and using accentuated letters that we
35
+ French like for both markup and content:</p><pre>&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
36
+ &lt;très&gt;là &lt;/très&gt;</pre><p>Having internationalization support in libxml2 means the following:</p><ul><li>the document is properly parsed</li>
37
+ <li>information about it's encoding is saved</li>
38
+ <li>it can be modified</li>
39
+ <li>it can be saved in its original encoding</li>
40
+ <li>it can also be saved in another encoding supported by libxml2 (for
41
+ example straight UTF8 or even an ASCII form)</li>
42
+ </ul><p>Another very important point is that the whole libxml2 API, with the
43
+ exception of a few routines to read with a specific encoding or save to a
44
+ specific encoding, is completely agnostic about the original encoding of the
45
+ document.</p><p>It should be noted too that the HTML parser embedded in libxml2 now obey
46
+ the same rules too, the following document will be (as of 2.2.2) handled in
47
+ an internationalized fashion by libxml2 too:</p><pre>&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
48
+ "http://www.w3.org/TR/REC-html40/loose.dtd"&gt;
49
+ &lt;html lang="fr"&gt;
50
+ &lt;head&gt;
51
+ &lt;META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"&gt;
52
+ &lt;/head&gt;
53
+ &lt;body&gt;
54
+ &lt;p&gt;W3C crée des standards pour le Web.&lt;/body&gt;
55
+ &lt;/html&gt;</pre><h3><a name="internal" id="internal">The internal encoding, how and why</a></h3><p>One of the core decisions was to force all documents to be converted to a
56
+ default internal encoding, and that encoding to be UTF-8, here are the
57
+ rationales for those choices:</p><ul><li>keeping the native encoding in the internal form would force the libxml
58
+ users (or the code associated) to be fully aware of the encoding of the
59
+ original document, for examples when adding a text node to a document,
60
+ the content would have to be provided in the document encoding, i.e. the
61
+ client code would have to check it before hand, make sure it's conformant
62
+ to the encoding, etc ... Very hard in practice, though in some specific
63
+ cases this may make sense.</li>
64
+ <li>the second decision was which encoding. From the XML spec only UTF8 and
65
+ UTF16 really makes sense as being the two only encodings for which there
66
+ is mandatory support. UCS-4 (32 bits fixed size encoding) could be
67
+ considered an intelligent choice too since it's a direct Unicode mapping
68
+ support. I selected UTF-8 on the basis of efficiency and compatibility
69
+ with surrounding software:
70
+ <ul><li>UTF-8 while a bit more complex to convert from/to (i.e. slightly
71
+ more costly to import and export CPU wise) is also far more compact
72
+ than UTF-16 (and UCS-4) for a majority of the documents I see it used
73
+ for right now (RPM RDF catalogs, advogato data, various configuration
74
+ file formats, etc.) and the key point for today's computer
75
+ architecture is efficient uses of caches. If one nearly double the
76
+ memory requirement to store the same amount of data, this will trash
77
+ caches (main memory/external caches/internal caches) and my take is
78
+ that this harms the system far more than the CPU requirements needed
79
+ for the conversion to UTF-8</li>
80
+ <li>Most of libxml2 version 1 users were using it with straight ASCII
81
+ most of the time, doing the conversion with an internal encoding
82
+ requiring all their code to be rewritten was a serious show-stopper
83
+ for using UTF-16 or UCS-4.</li>
84
+ <li>UTF-8 is being used as the de-facto internal encoding standard for
85
+ related code like the <a href="http://www.pango.org/">pango</a>
86
+ upcoming Gnome text widget, and a lot of Unix code (yet another place
87
+ where Unix programmer base takes a different approach from Microsoft
88
+ - they are using UTF-16)</li>
89
+ </ul></li>
90
+ </ul><p>What does this mean in practice for the libxml2 user:</p><ul><li>xmlChar, the libxml2 data type is a byte, those bytes must be assembled
91
+ as UTF-8 valid strings. The proper way to terminate an xmlChar * string
92
+ is simply to append 0 byte, as usual.</li>
93
+ <li>One just need to make sure that when using chars outside the ASCII set,
94
+ the values has been properly converted to UTF-8</li>
95
+ </ul><h3><a name="implemente" id="implemente">How is it implemented ?</a></h3><p>Let's describe how all this works within libxml, basically the I18N
96
+ (internationalization) support get triggered only during I/O operation, i.e.
97
+ when reading a document or saving one. Let's look first at the reading
98
+ sequence:</p><ol><li>when a document is processed, we usually don't know the encoding, a
99
+ simple heuristic allows to detect UTF-16 and UCS-4 from encodings where
100
+ the ASCII range (0-0x7F) maps with ASCII</li>
101
+ <li>the xml declaration if available is parsed, including the encoding
102
+ declaration. At that point, if the autodetected encoding is different
103
+ from the one declared a call to xmlSwitchEncoding() is issued.</li>
104
+ <li>If there is no encoding declaration, then the input has to be in either
105
+ UTF-8 or UTF-16, if it is not then at some point when processing the
106
+ input, the converter/checker of UTF-8 form will raise an encoding error.
107
+ You may end-up with a garbled document, or no document at all ! Example:
108
+ <pre>~/XML -&gt; ./xmllint err.xml
109
+ err.xml:1: error: Input is not proper UTF-8, indicate encoding !
110
+ &lt;très&gt;là &lt;/très&gt;
111
+ ^
112
+ err.xml:1: error: Bytes: 0xE8 0x73 0x3E 0x6C
113
+ &lt;très&gt;là &lt;/très&gt;
114
+ ^</pre>
115
+ </li>
116
+ <li>xmlSwitchEncoding() does an encoding name lookup, canonicalize it, and
117
+ then search the default registered encoding converters for that encoding.
118
+ If it's not within the default set and iconv() support has been compiled
119
+ it, it will ask iconv for such an encoder. If this fails then the parser
120
+ will report an error and stops processing:
121
+ <pre>~/XML -&gt; ./xmllint err2.xml
122
+ err2.xml:1: error: Unsupported encoding UnsupportedEnc
123
+ &lt;?xml version="1.0" encoding="UnsupportedEnc"?&gt;
124
+ ^</pre>
125
+ </li>
126
+ <li>From that point the encoder processes progressively the input (it is
127
+ plugged as a front-end to the I/O module) for that entity. It captures
128
+ and converts on-the-fly the document to be parsed to UTF-8. The parser
129
+ itself just does UTF-8 checking of this input and process it
130
+ transparently. The only difference is that the encoding information has
131
+ been added to the parsing context (more precisely to the input
132
+ corresponding to this entity).</li>
133
+ <li>The result (when using DOM) is an internal form completely in UTF-8
134
+ with just an encoding information on the document node.</li>
135
+ </ol><p>Ok then what happens when saving the document (assuming you
136
+ collected/built an xmlDoc DOM like structure) ? It depends on the function
137
+ called, xmlSaveFile() will just try to save in the original encoding, while
138
+ xmlSaveFileTo() and xmlSaveFileEnc() can optionally save to a given
139
+ encoding:</p><ol><li>if no encoding is given, libxml2 will look for an encoding value
140
+ associated to the document and if it exists will try to save to that
141
+ encoding,
142
+ <p>otherwise everything is written in the internal form, i.e. UTF-8</p>
143
+ </li>
144
+ <li>so if an encoding was specified, either at the API level or on the
145
+ document, libxml2 will again canonicalize the encoding name, lookup for a
146
+ converter in the registered set or through iconv. If not found the
147
+ function will return an error code</li>
148
+ <li>the converter is placed before the I/O buffer layer, as another kind of
149
+ buffer, then libxml2 will simply push the UTF-8 serialization to through
150
+ that buffer, which will then progressively be converted and pushed onto
151
+ the I/O layer.</li>
152
+ <li>It is possible that the converter code fails on some input, for example
153
+ trying to push an UTF-8 encoded Chinese character through the UTF-8 to
154
+ ISO-8859-1 converter won't work. Since the encoders are progressive they
155
+ will just report the error and the number of bytes converted, at that
156
+ point libxml2 will decode the offending character, remove it from the
157
+ buffer and replace it with the associated charRef encoding &amp;#123; and
158
+ resume the conversion. This guarantees that any document will be saved
159
+ without losses (except for markup names where this is not legal, this is
160
+ a problem in the current version, in practice avoid using non-ascii
161
+ characters for tag or attribute names). A special "ascii" encoding name
162
+ is used to save documents to a pure ascii form can be used when
163
+ portability is really crucial</li>
164
+ </ol><p>Here are a few examples based on the same test document and assumin a
165
+ terminal using ISO-8859-1 as the text encoding:</p><pre>~/XML -&gt; ./xmllint isolat1
166
+ &lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
167
+ &lt;très&gt;là&lt;/très&gt;
168
+ ~/XML -&gt; ./xmllint --encode UTF-8 isolat1
169
+ &lt;?xml version="1.0" encoding="UTF-8"?&gt;
170
+ &lt;très&gt;là  &lt;/très&gt;
171
+ ~/XML -&gt; </pre><p>The same processing is applied (and reuse most of the code) for HTML I18N
172
+ processing. Looking up and modifying the content encoding is a bit more
173
+ difficult since it is located in a &lt;meta&gt; tag under the &lt;head&gt;,
174
+ so a couple of functions htmlGetMetaEncoding() and htmlSetMetaEncoding() have
175
+ been provided. The parser also attempts to switch encoding on the fly when
176
+ detecting such a tag on input. Except for that the processing is the same
177
+ (and again reuses the same code).</p><h3><a name="Default" id="Default">Default supported encodings</a></h3><p>libxml2 has a set of default converters for the following encodings
178
+ (located in encoding.c):</p><ol><li>UTF-8 is supported by default (null handlers)</li>
179
+ <li>UTF-16, both little and big endian</li>
180
+ <li>ISO-Latin-1 (ISO-8859-1) covering most western languages</li>
181
+ <li>ASCII, useful mostly for saving</li>
182
+ <li>HTML, a specific handler for the conversion of UTF-8 to ASCII with HTML
183
+ predefined entities like &amp;copy; for the Copyright sign.</li>
184
+ </ol><p>More over when compiled on an Unix platform with iconv support the full
185
+ set of encodings supported by iconv can be instantly be used by libxml. On a
186
+ linux machine with glibc-2.1 the list of supported encodings and aliases fill
187
+ 3 full pages, and include UCS-4, the full set of ISO-Latin encodings, and the
188
+ various Japanese ones.</p><p>To convert from the UTF-8 values returned from the API to another encoding
189
+ then it is possible to use the function provided from <a href="html/libxml-encoding.html">the encoding module</a> like <a href="html/libxml-encoding.html#UTF8Toisolat1">UTF8Toisolat1</a>, or use the
190
+ POSIX <a href="http://www.opengroup.org/onlinepubs/009695399/functions/iconv.html">iconv()</a>
191
+ API directly.</p><h4>Encoding aliases</h4><p>From 2.2.3, libxml2 has support to register encoding names aliases. The
192
+ goal is to be able to parse document whose encoding is supported but where
193
+ the name differs (for example from the default set of names accepted by
194
+ iconv). The following functions allow to register and handle new aliases for
195
+ existing encodings. Once registered libxml2 will automatically lookup the
196
+ aliases when handling a document:</p><ul><li>int xmlAddEncodingAlias(const char *name, const char *alias);</li>
197
+ <li>int xmlDelEncodingAlias(const char *alias);</li>
198
+ <li>const char * xmlGetEncodingAlias(const char *alias);</li>
199
+ <li>void xmlCleanupEncodingAliases(void);</li>
200
+ </ul><h3><a name="extend" id="extend">How to extend the existing support</a></h3><p>Well adding support for new encoding, or overriding one of the encoders
201
+ (assuming it is buggy) should not be hard, just write input and output
202
+ conversion routines to/from UTF-8, and register them using
203
+ xmlNewCharEncodingHandler(name, xxxToUTF8, UTF8Toxxx), and they will be
204
+ called automatically if the parser(s) encounter such an encoding name
205
+ (register it uppercase, this will help). The description of the encoders,
206
+ their arguments and expected return values are described in the encoding.h
207
+ header.</p><p><a href="bugs.html">Daniel Veillard</a></p></td></tr></table></td></tr></table></td></tr></table></td></tr></table></td></tr></table></body></html>