Frequently Asked Questions (FAQs)

Why XiMoL is not really a DOM parser ?

There is no data object model defined by the library.
When you load your XML file, you use only your data structure and not your data structure and the DOM structure.

Why XiMoL is not really a SAX parser ?

There is nothing like event handler.

Why XiMoL is close to a DOM parser?

XiMoL is close to the Object model.

Why XiMoL is close to a SAX parser ?

For a huge file, you could only choose an element.

Which character encoding are managed by XiMoL ?

We use the standard wchar and libiconv for the conversion. This library is wrapped in the class codecvt_ximol derived from the ::std::codecvt<wchar_t, char, mbstate_t>. Here is the list of all supported encoding (from the libiconv manual):

  • European languages ASCII, ISO-8859-{1,2,3,4,5,7,9,10,13,14,15,16}, KOI8-R, KOI8-U, KOI8-RU, CP{1250,1251,1252,1253,1254,1257}, CP{850,866}, Mac{Roman,CentralEurope,Iceland,Croatian,Romania}, Mac{Cyrillic,Ukraine,Greek,Turkish}, Macintosh
  • Semitic languages ISO-8859-{6,8}, CP{1255,1256}, CP862, Mac{Hebrew,Arabic}
  • Japanese EUC-JP, SHIFT_JIS, CP932, ISO-2022-JP, ISO-2022-JP-2, ISO-2022-JP-1
  • Chinese EUC-CN, HZ, GBK, GB18030, EUC-TW, BIG5, CP950, BIG5-HKSCS, ISO-2022-CN, ISO-2022-CN-EXT
  • Korean EUC-KR, CP949, ISO-2022-KR, JOHAB
  • Armenian ARMSCII-8
  • Georgian Georgian-Academy, Georgian-PS
  • Tajik KOI8-T
  • Thai TIS-620, CP874, MacThai
  • Laotian MuleLao-1, CP1133
  • Vietnamese VISCII, TCVN, CP1258
  • Platform specifics HP-ROMAN8, NEXTSTEP
  • Full Unicode UTF-8 UCS-2, UCS-2BE, UCS-2LE UCS-4, UCS-4BE, UCS-4LE UTF-16, UTF-16BE, UTF-16LE UTF-32, UTF-32BE, UTF-32LE UTF-7 C99, JAVA
  • European languages CP{437,737,775,852,853,855,857,858,860,861,863,865,869,1125}
  • Semitic languages CP864
  • Japanese EUC-JISX0213, Shift_JISX0213, ISO-2022-JP-3
  • Turkmen TDS565
  • Platform specifics RISCOS-LATIN1

Donate to the XiMoL project Logo If you have any questions about XiMoL, you could write to