French accents not supported by Java client

[Torsten Kupke]

Hi,

if I use the native Windows client, I can enter french letters with an
accent (like e.g. 'é') as usual by typing the accent (e.g. '´') follwed
by the accent-less letter (e.g. 'e'). With the Java client this doesn't
work. And I found no other way to achieve this. I only can search some
text for that french letter (which can be quite difficult) and copy it
from there. Is this a known issue with the Java client, and is there any
shorter workaround, than my one?

Best regards

Torsten

[DRC]

I know I tested this with the Java viewer. I’ll retest and see what’s up. Are you using Windows 10?

> --
> You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/78c57080-d60a-8f47-ef4a-ea6d95fb49d3%40hacon.de.

[Torsten Kupke]

Hi DRC,

under Windows 10 I use the native client. The Java client I only use on
the Ubuntu 18.04 host to connect to the local open session.

It were great, if you could fix it, since I have some collegues with
accents in their name. Another case is retyping a french word or text
from a screenshot.

Best regards

Torsten

[DRC]

Unfortunately I think you're probably encountering this issue:

https://github.com/TurboVNC/turbovnc/issues/30

which is due to a bug in Java that is still unresolved
(https://bugs.openjdk.java.net/browse/JDK-8016255). Java 8 is
generating a key release event for certain dead keys but not a key press
event. I wasn't able to make the dead grave accent or dead acute accent
keys on a French keyboard layout work properly in Ubuntu 18.04 at all,
even without TurboVNC. However, I was able to reproduce the issue by
using the dead circumflex/dead diaeresis key.

As with other international keyboard issues, the long-term solution for
this will be to implement

https://github.com/TurboVNC/turbovnc/issues/108

which is currently in need of funding.

[DRC]

Here is a roll-up of the remaining known issues with dead keys:

https://github.com/TurboVNC/turbovnc/issues/194

Unfortunately, I'm not sure how to work around these issues, other than to take drastic measures, such as:

- implementing our own hotkeys for every possible dead key

- modifying the keyboard layout

I also looked into the feasibility of implementing QEMU extended key events (https://github.com/TurboVNC/turbovnc/issues/108), but whereas that is possible, it's not going to be as easy as I thought.  Unfortunately, Java/Swing gets in my way there as well, since it doesn't consistently generate layout-independent key codes for dead keys.  Thus, it may be necessary to drop into JNI to get information about which physical key was actually pressed.

Any ideas are appreciated.  I'm stumped.

DRC

 

On 9/1/19 8:53 AM, Torsten Kupke wrote:

[Torsten Kupke]

Hi DRC,

I think, you shouldn't spend time for a workaround for this, but wait
for a fix of https://bugs.openjdk.java.net/browse/JDK-8016255. Perhaps
you can post a comment there, that your users have trouble with it.

Best regards

Torsten

Am 10.09.19 um 20:09 schrieb DRC:

--
Torsten Kupke
Development Planning/Disposition Systems

HaCon Ingenieurgesellschaft mbH
Lister Str. 15, 30163 Hannover, Germany
Tel. +49 511 33699-464
Fax. +49 511 33699-99
Torste...@hacon.de
http://www.hacon.de

Office/Sitz: Hannover, Registry Court/Amtsgericht: Hannover HRB 1712
Managing Directors/Geschäftsführer:
Michael Frankenberg (CEO), Andreas Dittmann (CFO), Claus Müller-Haude

HaCon - A Siemens Company

[DRC]

Unfortunately, only the OpenJDK development team can post or comment on their bug tracker, but I did ping the OpenJDK AWT-Dev mailing list to ask about the status of the issue.

I found a way forward for the QEMU extended key event feature, so I am proceeding with that work, since it has other benefits besides just working around this.

[DRC]

The dev/3.1 evolving builds should now have a proper fix for all dead
key and other international key mapping issues.  (Key mapping is now
done on the server side rather than the client side.)

DRC