On Thu, May 30, 2019 at 3:35 AM Adrian Owen <[email protected]> wrote:

> Hi Mike,
>
>
>
> Screen Shot send by user is attached.
>
>
>
> User said they changed Input method to “Text Input”, and entered Chinese
> text. Rather than the Chinese they expected, they got ASCII..
>

The "Text Input" method will allow a local input method to be used to enter
Chinese text. You do not need to use "Text Input" if an input method is
being used remotely, as shown in your screenshot.

Note: I see these WARNINGS in catalina.out in my LAB. Could they be related
> to issue?
>

No, the below messages are unrelated.


>
> 11:18:25.406 [http-nio-8080-exec-6] INFO
> o.a.g.r.auth.AuthenticationService - User "" successfully authenticated
> from 192.168.242.53.
>
> 11:18:26.228 [http-nio-8080-exec-3] WARN  o.a.g.e.LanguageResourceService
> - Root-level "NAME" string missing or invalid in language "zh_TW"
>
> 11:18:26.229 [http-nio-8080-exec-3] WARN  o.a.g.e.LanguageResourceService
> - Root-level "NAME" string missing or invalid in language "zh"
>

Are you defining custom translations?

There is no "zh_TW" set of translation strings defined in the current
webapp, and the "zh" translation strings do have a proper "NAME":

https://github.com/apache/guacamole-client/blob/2362cfcabef3ea4f879e0538883cc95a031a790c/guacamole/src/main/webapp/translations/zh.json#L3

This has no bearing on whether a user will be able to type in Chinese, nor
on whether "Text Input" will work as intended, but these are valid warnings
regarding malformed translation files.

11:18:28.741 [http-nio-8080-exec-9] INFO  o.a.g.tunnel.TunnelRequestService
> - User "" connected to connection "RDP administrator@HUB12
> trialuser@SE16HUBDEV01 SE16HUBDEV01".
>
> Exception in thread "Thread-17" java.lang.IllegalStateException: Message
> will not be sent because the WebSocket session has been closed
>

This just indicates the connection was closed.

- Mike

Reply via email to