[ jedit-Bugs-2093501 ] Norwegian/Danish characters ÆØà inconsistent in UTF-8

[SourceForge.net <no...@so...>]

Bugs item #2093501, was opened at 2008-09-04 19:02
Message generated for change (Comment added) made by rambosmurf
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=2093501&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: keyboard / mouse
Group: normal bug
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Martin Sommervold (rambosmurf)
Assigned to: Nobody/Anonymous (nobody)
Summary: Norwegian/Danish characters ÆØÅ inconsistent in UTF-8

Initial Comment:
When changing the default encoding in jEdit 4.3 PRE15 to UTF-8, the characters æøå/ÆØÅ are not registered by input from the keyboard. 

Restarting jEdit fixes this temporarily, however, when alt-tabbing back and forth into the application, the problem recurs.

Furthermore, the problem can once again (after alt-tabbing back and forth) be fixed by first typing something other than æøå/ÆØÅ, and the characters will then work.

This is on Windows Vista SP1 / Java 1.6.0 (build 1.6.0_01-b06).

The problem persists on several computers with equal setups.

----------------------------------------------------------------------

>Comment By: Martin Sommervold (rambosmurf)
Date: 2008-09-10 12:49

Message:
You are correct, this also happens when other default encodings are
selected. However, i did notice something weird with the keyboard tester;

When i tried to enter either æøå/ÆØÅ as the first character into the
keyboard tester dialouge, the jedit content area registered the input, but
the character itself was not displayed in the input box used by the
keyboard tester.

Similarly to the text area problem as described in my bug report, this
issue resolves itself if a different key is entered before æøå (the
special characters become visible in the input box after entering "k" for
instance).

Working case
Here is a log from the keyboard tester when i did NOT use æøå to begin
with:

Event KEY_PRESSED,keyCode=0x41,keyChar=0x61,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0x61,modifiers=0x0,consumed=0 passed
==> Translated to <0,61>
Event KEY_RELEASED,keyCode=0x41,keyChar=0x61,modifiers=0x0,consumed=0
passed
Event KEY_PRESSED,keyCode=0x42,keyChar=0x62,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0x62,modifiers=0x0,consumed=0 passed
==> Translated to <0,62>
Event KEY_PRESSED,keyCode=0x43,keyChar=0x63,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0x63,modifiers=0x0,consumed=0 passed
==> Translated to <0,63>
Event KEY_RELEASED,keyCode=0x42,keyChar=0x62,modifiers=0x0,consumed=0
passed
Event KEY_RELEASED,keyCode=0x43,keyChar=0x63,modifiers=0x0,consumed=0
passed
Event KEY_PRESSED,keyCode=0x44,keyChar=0x64,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0x64,modifiers=0x0,consumed=0 passed
==> Translated to <0,64>
Event KEY_RELEASED,keyCode=0x44,keyChar=0x64,modifiers=0x0,consumed=0
passed

------------------------

Not working case
Here is a log from the keyboard tester when i DID use æøå to begin
with, then folloed up with the letter "k", then followed up with æøå
afterwards (where "kæøå" is the only text displayed in the input box):

Event KEY_PRESSED,keyCode=0x0,keyChar=0xe6,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0xe6,modifiers=0x0,consumed=0
filtered
Event KEY_RELEASED,keyCode=0x0,keyChar=0xe6,modifiers=0x0,consumed=0
passed
Event KEY_PRESSED,keyCode=0x0,keyChar=0xf8,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0xf8,modifiers=0x0,consumed=0
filtered
Event KEY_RELEASED,keyCode=0x0,keyChar=0xf8,modifiers=0x0,consumed=0
passed
Event KEY_PRESSED,keyCode=0x0,keyChar=0xe5,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0xe5,modifiers=0x0,consumed=0
filtered
Event KEY_RELEASED,keyCode=0x0,keyChar=0xe5,modifiers=0x0,consumed=0
passed
Event KEY_PRESSED,keyCode=0x4b,keyChar=0x6b,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0x6b,modifiers=0x0,consumed=0 passed
==> Translated to <0,6b>
Event KEY_RELEASED,keyCode=0x4b,keyChar=0x6b,modifiers=0x0,consumed=0
passed
Event KEY_PRESSED,keyCode=0x0,keyChar=0xe6,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0xe6,modifiers=0x0,consumed=0 passed
==> Translated to <0,e6>
Event KEY_RELEASED,keyCode=0x0,keyChar=0xe6,modifiers=0x0,consumed=0
passed
Event KEY_PRESSED,keyCode=0x0,keyChar=0xf8,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0xf8,modifiers=0x0,consumed=0 passed
==> Translated to <0,f8>
Event KEY_RELEASED,keyCode=0x0,keyChar=0xf8,modifiers=0x0,consumed=0
passed
Event KEY_PRESSED,keyCode=0x0,keyChar=0xe5,modifiers=0x0,consumed=0
filtered
Event KEY_TYPED,keyCode=0x0,keyChar=0xe5,modifiers=0x0,consumed=0 passed
==> Translated to <0,e5>
Event KEY_RELEASED,keyCode=0x0,keyChar=0xe5,modifiers=0x0,consumed=0
passed

Hope this helps. Thank you for all your efforts!

----------------------------------------------------------------------

Comment By: Kazutoshi Satoda (k_satoda)
Date: 2008-09-07 06:31

Message:
Logged In: YES 
user_id=1483238
Originator: NO

Are you sure thant this doesn't happen with another default encoding
except UTF-8? I don't think the default encoding affects keyboard input.
It is used for file I/O.

Please use [Utilities] > [Troubleshooting] > [Keyboard Tester...], and
report logs for both working and not woking case.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=2093501&group_id=588