StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>You're in luck, Java and Android both use the Unicode character set. However, Android (by default) use the UTF-8 encoding, which JNI doesn't intrisically support. Nonetheless, Java classes are fully capable of converting between character set encodings. The <code>lang.java.String</code> constructors allow you to specify a character set/encoding or use the OS-default, which on Android, of course, is coded as UTF-8.</p> <p>To make it easier (I prefer coding in Java, minimizing code that calls the JNI library), create an overload of your method and do some of the implementation in Java:</p> <pre><code>private static byte[] getLevelFile(byte[] levelName) { return getLevelFile(new String(levelName)).getBytes(); } </code></pre> <p>Now the JNI code only has to deal with jbytearray, both for the parameter and the return value:</p> <pre><code>JniMethodInfoJavaApi methodInfo; if (! getStaticMethodInfo(methodInfo, "getLevelFile", "([B)[B")) { return std::string(""); } LOGD("calling getLevelFile"); int nameLength = levelName.length(); jbyteArray nameBytes = methodInfo.env->NewByteArray(nameLength); methodInfo.env->SetByteArrayRegion(nameBytes, 0, nameLength, reinterpret_cast<const jbyte*>(levelName.c_str())); jbyteArray returnString = (jbyteArray) methodInfo.env->CallStaticObjectMethod(methodInfo.classID, methodInfo.methodID, nameBytes); LOGD("returned from getLevelFile"); methodInfo.env->DeleteLocalRef(methodInfo.classID); methodInfo.env->DeleteLocalRef(nameBytes); int returnLength = methodInfo.env->GetArrayLength(returnString); std::string data; data.reserve(returnLength); methodInfo.env->GetByteArrayRegion(returnString, 0, returnLength, reinterpret_cast<jbyte*>(&data[0])); methodInfo.env->DeleteLocalRef(returnString); LOGD("returning Level data"); return data; </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload