What is happening here is that we are working around the issue that C++ won't let you initialize a `std::string` that does have an embedded NUL character in the sequence, since it effectively uses `strlen` functions to initialize the internal storage with the given c-string. The result is that we have one NUL and some other unicode characters that cause Java Modified UTF-8 to produce bytes that are not really UTF-8 compatible (by design).
[ Full content available at: https://github.com/apache/geode-native/pull/424 ] This message was relayed via gitbox.apache.org for [email protected]
