This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | [65cat] 'ç' keyboard key don't recognized by IDE main window | ||
---|---|---|---|
Product: | editor | Reporter: | Michel Graciano <hmichel> |
Component: | -- Other -- | Assignee: | issues@editor <issues> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | CC: | mmetelka |
Priority: | P3 | Keywords: | I18N |
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
IDE log file
New log file More logs |
Description
Michel Graciano
2008-08-27 14:48:21 UTC
reassigning to editor. I can write Czech - šěščřžýáí - in editor without any problem hmichel, what means "any text field in toolbar"? I don't have textfields in toolbar :( And what editor? I used java. Hi, I have a plugin, the Sandip regex highlighter, which has a text field in the toolbar. BTW, I forgot to say, I can just write 'ç' when I press ' + c which are translated to ç. This is the workaround I use for a while. I will try to test in my Win XP workstation later, but AFAIR it works on it. Regards Are you sure that 'ç' can be handled by ISO-8859-1 encoding? Could you please try to run Netbeans with '-J-Dfile.encoding=UTF-8' added in <nb-inst>/etc/netbeans.conf and see if it fixes the problem? Also, could you try to do the same with java notepad (eg run 'java -jar $JAVA_HOME/demo/jfc/Notepad/Notepad.jar' or the equivalent for your OS and type the character to the notepad's text area). Thanks > Are you sure that 'ç' can be handled by ISO-8859-1 encoding? Yes, ISO-8859-1 is the default Windows encoding, where is works fine. Just my 'ç' key don't works, if I press ' + c the 'ç' char is inserted in nb editor, btw, if I try to use ç key for Options text field, as Ant path, it works. It just don't works for nb editor and main window text fields. > Could you please try to run Netbeans with '-J-Dfile.encoding=UTF-8' added in <nb-inst>/etc/netbeans.conf and see if > it fixes the problem? For: Product Version: NetBeans IDE Dev (Build 200808261401) Java: 1.6.0_07; Java HotSpot(TM) Client VM 10.0-b23 System: Linux version 2.6.24-21-generic running on i386; UTF-8; pt_BR (nb) Userdir: /home/hmichel/.netbeans/dev it doesn't work too. > Also, could you try to do the same with java notepad (eg run 'java -jar $JAVA_HOME/demo/jfc/Notepad/Notepad.jar' or the > equivalent for your OS and type the character to the notepad's text area) Yes, it works perfectly. BTW, I don't think it is a I18N problem. It is some problem about the keycode NetBeans is interpreting from my keyboard, just for editor, since this key can be used in another text IDE text components. If you need any test, just let me know. Thanks I added more logging to BaseKit.DefaultKeyTypedAction which should now show what commands it is processing. The change was pushed as http://hg.netbeans.org/main/rev/4c0b853bceba. Could you please download hudson build containing this changeset and run it with '-J-Dorg.netbeans.editor.BaseKit.level=FINE'. In the console window or log file you should see messages like 'Processing command char: XX' or 'Invalid command char: XX'. Please try to type the 'ç' char and attach the log file here. The log file is in <ide-userdir>/var/log/messages.log. Thanks Can you send me the jar for these? The last main builds are unstable or failing and I don't like to get it. Is it possible? Regards Integrated into 'main-golden', available in build *200808300201* on http://bits.netbeans.org/dev/nightly/ Changeset: http://hg.netbeans.org/main/rev/4c0b853bceba User: Vita Stejskal <vstejskal@netbeans.org> Log: #145306: diagnostic logs No, please download the build. You can use it just for this test. Thanks Created attachment 68798 [details]
IDE log file
Hi, I tested with several kind of editors as java, text and sql. No entries on log file for this, but if I use keys as A, B or C it is inserted on file. Just let me know if you need more help. Thanks for that. So, it seems that something is swallowing the keystroke even before it reaches our DefaultKeyTypedAction. I'm not sure how to find who without patching JDK/Swing classes. Milo, do you have any idea? Thanks Any news about it? Milo, any idea? The text might be inserted by an input method - the code in JTextComponent.replaceInputMethodText(). We could try to debug the running IDE to find out how the method executes. What is your keyboard layout and what key combination do you use for typing of the special char? I've seen "pt_br" in the report so it should stand for Brazilian Portuguese, right? You may also try run NB with -J-Dnetbeans.debug.editor.document=true -J-Dnetbeans.debug.editor.document.stack=true to see whether e.g. the text is not inserted and removed afterwards for some reason. I use IDE in English by default for now, so, now I am starting NB with the --locale en:US parameter. I will test following the instructions and post here more details soon. This is my current environment: Product Version: NetBeans IDE 6.5 (Build 200811100001) Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15 System: Linux version 2.6.27-8-generic running on i386; ISO-8859-1; en_US (nb) Userdir: /home/hmichel/.netbeans/6.5 Created attachment 73907 [details]
New log file
Created attachment 73908 [details]
More logs
I attached 2 log files, where the first one I just opened a class file and typed 'ç' key, and I just can see the 'Unknow keycode: 0x0' text at status bar. The second I typed 'a', 'b' and 'c' keys, and everything work fine (I can see exceptions on log file, but the class file was saved without any problem). Just let me know if you need more details or some specific use case. Regards (In reply to comment #16) > Created an attachment (id=73907) [details] > New log file In this log file there are no keystrokes logged. It shows only the initial loading of the document. This corresponds to what you described earlier and my suspicion that 'something' intercepts key-typed events and steals the one for 'ç'. Which is why the key-typed event does not arrive to the editor. We have to find out who is this thief. Hi Vita, I tested right now at 6.8 and everything is okey for now. Or it was fixed by another issue or some plugin was the thief. BTW, you can close this as you wish, I consider it resolved. Thanks for your great work. Ok, Michel. Thanks |