Peter Moogk

Wow, that was super fast. Thanks so much for the fix!

Hebrew translation issue when multiple characters

@pmattes Hi Paul, I was able to build a Windows version of your fix for the Hebrew issue. I see in the trace that the upper byte is no longer truncated. However, I'm getting a weird response when the next readbuffer is performed. In my test I sent the following string: "aaaaaa\u05e9bbbbb". Where \u05e9 is a Hebrew character. In the trace I see the following which is good: 20240207.150856.022 string -> Key(U+05e9) There is no warning about EBCIDIC conversion. However, later in the trace I see: 20240207.150856.023...

@pmattes Hi Paul, I was able to build a Windows version of your fix for the Hebrew issue. I see in the trace that the upper byte is not longer truncated. However, I'm getting a weird response when the next readbuffer is performed. In my test I sent the following string: "aaaaaa\u05e9bbbbb". Where \u05e9 is a Hebrew character. In the trace I see the following which is good: 20240207.150856.022 string -> Key(U+05e9) There is no warning about EBCIDIC conversion. However, later in the trace I see: 20240207.150856.023...

@pmattes Hi Paul, I was able to build a Windows version of fix for the Hebrew issue. I see in the trace that the upper byte is not longer truncated. However, I'm getting a weird response when the next readbuffer is performed. In my test I sent the following string: "aaaaaa\u05e9bbbbb". Where \u05e9 is a Hebrew character. In the trace I see the following which is good: 20240207.150856.022 string -> Key(U+05e9) There is no warning about EBCIDIC conversion. However, later in the trace I see: 20240207.150856.023...

Wow, that was fast! Thanks, Paul, for fixing this issue. Can you let me know when this fix will get into the next build? Thanks so much.

Unable to send Hebrew characters to the host

Wow, thanks so much, Paul, for the speedy turn around on this! I'll download the 4.3GA release today and try it out. Thanks!