Characters [ and { does not work with Spanish keyboards

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
No ouput. ] and } work fine.

IMPORTANT!!! Please answer these questions for any and ALL bug reports

What version of the product are you using? On what operating system?
Editra v0.5.70. Mac OSX 10.6.4. It did not work in previous versions either.

What method of install was your version installed with (Binary/Source)?
Binary

If from source: What version of python and wxPython are you using?
2.6.1

Please provide any additional information below.

Original issue reported on code.google.com by jprietop...@gmail.com on 17 Jun 2010 at 10:48

[GoogleCodeExporter]

Hello,

This is a known issue and unfortunately without hardware I can't really debug 
this. Others that have reported it on the forum (http://editra.org/forum) did 
some debugging and the last I remember it appeared to be a problem in wxPython 
and not Editra. 

If you can try to reproduce the problem in the wxPython Demo applications 
StyledTextCtrl sample that would show whether the problem is in Editra or the 
text control widget.

Thanks,

Cody

Original comment by CodyPrec...@gmail.com on 17 Jun 2010 at 12:55

• Changed state: Investigate

[GoogleCodeExporter]

Issue 554 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 1 Nov 2010 at 12:37

[GoogleCodeExporter]

Issue 566 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 1 Dec 2010 at 1:56

[GoogleCodeExporter]

I have made some minor changes in 0.5.99 that I hope may help with this issue.

Please test version 0.5.99 and let me know if it is fixed or not.

Original comment by CodyPrec...@gmail.com on 6 Dec 2010 at 6:17

[GoogleCodeExporter]

No. It does not work yet :((

Editra 0.5.99 checked on Mac OSX 10.6.5.

Thanks.

Original comment by jprietop...@gmail.com on 9 Dec 2010 at 5:34

[GoogleCodeExporter]

Darn, that was about my last idea.

I guess I really need someone who has the hardware to download the source code 
and try somethings out with the key handling to see if it can be fixed. If 
anyone knows a little about Python it shouldnt be very hard to test some things 
out.

Cody

Original comment by CodyPrec...@gmail.com on 9 Dec 2010 at 5:46

[GoogleCodeExporter]

I'tried to check it on wxWidgets demos, but theres no demo for StyledTextCtrl. 
An other text input works just fine (also in editra... as the search input, or 
so).

Original comment by nanof...@gmail.com on 20 Jan 2011 at 3:17

[GoogleCodeExporter]

also happens with Editra 6.0

Original comment by nanof...@gmail.com on 20 Jan 2011 at 3:18

[GoogleCodeExporter]

New data:
the problem is not the keyboard itself, it´s the language of the input source.
you could reproduce the bug by enabling Spanish ISO in the input sources list 
of the system preferences. 
Tip: Check "Show input Menu un menu bar" to quickly change the languague of the 
input. Also in System preferenes, Keyboard, check "Show Keyboard & Character 
Viewer in menu bar", so you can use the virtual keyboard to find the keys "[" 
"{". (you must press alt in order to see the alternates chars of the keys)
Hope this help you to reproduce the bug

seeya

Original comment by nanof...@gmail.com on 20 Jan 2011 at 3:47

[GoogleCodeExporter]

If this is the case then thats great. I will try this out as soon as I get a 
chance. Being able to reproduce and debug it will make it much easier to 
resolve.

Thanks

Original comment by CodyPrec...@gmail.com on 20 Jan 2011 at 2:18

[GoogleCodeExporter]

Issue 620 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 11 Feb 2011 at 11:17

[GoogleCodeExporter]

First of all, sorry about my English.

I have the same problem, it's very difficult to code in any programming 
language without these two characters, so please, fix it soon.

I don't know how, but I think that may be accents in the same key can be the 
cause of the problem. The two keys that doesn't work are accents keys when you 
press them "normally", without the alt key needed for those chars. And I think 
that are the only two keys like that, so I think maybe it's relationated in any 
manner.

I hope this deduction can help. I'm at your entire disposition if you need help 
to debug it.

Thanks

Original comment by hq063...@gmail.com on 7 Oct 2011 at 12:34

[GoogleCodeExporter]

Hi,

The bug is in wxWidgets StyledTextCtrl somewhere, not in Editra. The issue 
needs to be found in the upstream library and fixed there. There is no way to 
control or fix this from within Editra itself.

I can try to see if I can figure out the problem and report it up stream but as 
mentioned I unfortunately wont be able to fix it here. 

Original comment by CodyPrec...@gmail.com on 8 Oct 2011 at 7:59

[GoogleCodeExporter]

Think I found it this time and have submitted a possible patch upstream that 
fixes the issue in my testing.

http://trac.wxwidgets.org/ticket/9663

Original comment by CodyPrec...@gmail.com on 8 Oct 2011 at 9:37

[GoogleCodeExporter]

Hi! sorry Cody, I downt understand, so we need to wait until a new release of 
wxWidgets and after taht, a new release of Editra, right? Thanks a lot! 

Original comment by nanof...@gmail.com on 8 Oct 2011 at 11:54

[GoogleCodeExporter]

Well assuming the fix is correct and gets into the ex trunk then yes would 
first need a release of ex widgets with the fix 2.9.3 would be the darkest hope 
then assuming the mac build is finally stable enough then I could build new 
editra binaries based on them.

Original comment by CodyPrec...@gmail.com on 9 Oct 2011 at 1:07

[GoogleCodeExporter]

Or, if we don't want to wait, we cant test downloading the sources, applying 
the fix, and building both apps, right?

Original comment by hq063...@gmail.com on 9 Oct 2011 at 8:17

[GoogleCodeExporter]

Hi,

Yes of course that is always an option as well and you could do this today if 
you wanted as my patch to wx is only a couple lines of code it should be easy 
to apply.

Need to:

1) Get a copy of wxWidgets 2.8 or 2.9(svn) (2.8 suggested for OSX / Linux users)
2) Build it using the python build script in build/tools with the option for 
wxPython.
3) Build a matching version of wxPython against your build wxWidgets 
(instructions for this can be readily found on the wxpython.org)
4) Run editra using the newly built version of wxPython (or use editra's 
setup.py script to build a binary version using the new libraries).

Original comment by CodyPrec...@gmail.com on 11 Oct 2011 at 7:50

[GoogleCodeExporter]

Issue 712 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 27 Nov 2011 at 4:04

[GoogleCodeExporter]

Issue 722 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 26 Jan 2012 at 3:45

[GoogleCodeExporter]

Issue 739 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 11 May 2012 at 2:34

[GoogleCodeExporter]

Issue 620 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 15 Jul 2012 at 2:10

[GoogleCodeExporter]

Issue 769 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 16 Oct 2012 at 5:39

[GoogleCodeExporter]

Hi, there's no fix yet for this issue in any DMG built development version? Is 
very difficult to build the sources anytime that I want to install Editra on a 
new Mac.

Thanks! 

Original comment by jbezequ...@gmail.com on 2 Feb 2013 at 12:41

[GoogleCodeExporter]

Hi,

Have you tested with using Editra against wxPython 2.9?

If it works there then I can look at providing a DMG build using 2.9 in the 
next release possibly. If its not fixed there then I don't think they ever 
applied my patch to fix the issue....

Original comment by CodyPrec...@gmail.com on 6 Feb 2013 at 8:05

[GoogleCodeExporter]

Issue 813 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 5 Nov 2013 at 9:10

[GoogleCodeExporter]

Issue 816 has been merged into this issue.

Original comment by CodyPrec...@gmail.com on 17 Jan 2014 at 4:51