Arseny Kapoulkine

pugixml does provide basic encoding/decoding functions: `as_utf8` and `as _wide`. Not sure if they fit your usecase - if not, can you describe it more? (that is, what encodings do...

Let me make sure I understand this correctly... 1. You have an XML file with XML contents encoded using utf-8 2. You are loading this XML file with pugixml compiled...

Right, so I believe that in this case we're explicitly talking about a legacy Windows application - a modern Windows application would probably use UTF-16 and *W style APIs, or...

> Btw. I am quite sure that there are lost of applications out there, who even haven't figured out that they must convert the data in order to use your...

Well, there seems to be a disconnect in that pugixml currently *doesn't* have the functionality you are looking for - none of the encoding conversions implemented internally are adequate for...

Here's some previous discussion on the topic: https://code.google.com/p/pugixml/issues/detail?id=49 That thread also has different implementations of a possible solution.

I experimented a bit with string_arg approach (the link above appears to be dead, but basically one way to implement this is to replace all existing `const char_t*` arguments with...

> (BTW, I don't see how the namespace-uri() = X XPath predicate can be correct and efficient w/o the parse-tree knowing about the NS of all nodes, as described above)...

The canonical recommendation is to use `setlocale` at the beginning of `main`, which automatically makes both parsing and converting to strings locale-independent. Unfortunately std::to_chars specifically doesn't enjoy wide support, so...

This should not be done in pugixml.hpp - it should instead be done in CMakeLists.txt similarly to dllexport, when configuring pugixml-shared project. The reason for why it's wrong to do...