LocalString with null values in string originated from native are broken

Question

LocalString with null values in string originated from native are broken

jwhpryor opened this issue a year ago · comments

Additional context in CL description:
ff9c084

Jamieson · Answer 1 · Sat Jan 06 2024 07:16:35 GMT+0800 (China Standard Time)

Unfortunately, I think this is unsupportable. I experimented with this a bit, and I notice when I print a java String "A\0BC\0" originated from Java in native, it prints A�BC�.

This looks like a unicode specials character for "unrepresentable".

Furthermore, the NewStringUTF JNI call does not allow for providing a length.

Because of these two things, I'm unfortunately inclined to think this is just not possible from native JNI.

Jamieson · Answer 2 · Sat Jan 06 2024 07:22:05 GMT+0800 (China Standard Time)

I guess I missed #194 where it looks like maybe you actually do have a fix. I wish I'd noticed that earlier, as it would seem I clearly didn't understand the locale issues well enough.

Jamieson · Answer 3 · Mon Mar 18 2024 10:50:21 GMT+0800 (China Standard Time)

The referenced CL is actually WAII. I've added some context in #194. I think this can be marked as obsolete.