Using CString and clarification about UTF

[ajtruckle]

Hi
With the tinyxml2 library we use utf8 strings. With your exstention for the paths does it still need to be utf8? I ask because I have to convert from CString to std::string so want to be sure.
Thanks.

[ajtruckle]

This is OK to me:

CString strWeekPath = L"AssignmentHistory/" + strDateKey;
std::string stdWeekPath(CW2A(strWeekPath.GetString(), CP_UTF8));

[ajtruckle]

Turns out that the text helper returns corrupted elements when they have accents etc. Atleast when I assign a c_str result to a CString it corrupts. So I had to convert using old approach with the UTF8 code page.

[ajtruckle]

See https://stackoverflow.com/q/72859063/2287576 for more info.

[stanthomas]

I would not recommend using the XPath implementation with characters outside the ASCII 127 range. It's a very simple, non-conforming, XPath-like functionality that does straight single character equality tests for the escape characters. It could be enhanced but would have to only use standard C++ and might add an unacceptable overhead to what is a very small code base.

[stanthomas]

It's because tixml2ex::text (see line 465 in tixml2ex.h) does this:

			if (auto value = element -> GetText())
				return std::string (value);

which will corrupt any string containing characters outside ASCII 127.

[ajtruckle]

Ok. But as you can see, I was not using non ASCII with XPath, but using it with the Text values. And by design the tinyxml2 library returns text values as UTF8 encoded.

But thanks for explaining. It may be an idea to clarify in the notes about UTF8.

I am happy to get the text values like I used to do.

As for the original purpose of this actual question, it was building an XPath with a simple ASCII attribute. I was going from CString to std::string for passing to your API.