DeltaEscher / editra

Automatically exported from code.google.com/p/editra
Other
0 stars 0 forks source link

find&replace for unicode strings broken #502

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. create a new file with some unicode strings (öäü߀)
2. try to find and replace any of the strings with something else

What is the expected output? What do you see instead?
Since regular ASCII characters work fine, there is something broken here.

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

What version of the product are you using? On what operating system?
0.5.32, Linux i586 and x86_64

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

Original issue reported on code.google.com by danielst...@googlemail.com on 31 Mar 2010 at 4:59

GoogleCodeExporter commented 8 years ago
Hi,

Works fine for me. So some questions.

1) What version/build of wxPython are you using (screenshot of Editra's About 
Dialog)

2) There is no 'binaries' for Linux the source version is always run. How did 
you
install (package manager?/What Distro?).

Thanks,

Cody

Original comment by CodyPrec...@gmail.com on 31 Mar 2010 at 5:37

GoogleCodeExporter commented 8 years ago
1) Editra 0.5.32, Platform Info: (linux2, python 2.6.4,wxGTK 2.8.9.2, unicode, 
gtk2,
wx-assertions-off, SWIG-1.3.29)

2) sorry, I am using the tarball, of course. Just unpacked to ~/bin/

Thanks a lot,
Daniel

Original comment by danielst...@googlemail.com on 31 Mar 2010 at 5:48

GoogleCodeExporter commented 8 years ago
I will try on my Linux machine tonight to see if it behaves any different. It 
about
the same setup as yours.

If you have a test file with some characters in it that the searching fails for 
that
you can attach that would be helpful when I try to reproduce again.

Thanks,

Cody

Original comment by CodyPrec...@gmail.com on 31 Mar 2010 at 6:01

GoogleCodeExporter commented 8 years ago
I haven't been able to reproduce this, is anyone else still seeing this?

Original comment by CodyPrec...@gmail.com on 22 Dec 2010 at 3:43

GoogleCodeExporter commented 8 years ago
I still have this issue on Linux with the latest verstion. Not sure about 
Windows, will have to try tomorrow.

When I try to replace ä or the like, nothing happens. ASCII characters work as 
expected.

Thanks,
Daniel

Original comment by danielst...@googlemail.com on 22 Dec 2010 at 7:08

GoogleCodeExporter commented 8 years ago
Odd, I just tested again and found one way that reproduces it.

The find/replace functionality works fine but "Replace All" seems to be what 
doesn't work.

Thanks, will be able to investigate this now.

Original comment by CodyPrec...@gmail.com on 22 Dec 2010 at 7:35

GoogleCodeExporter commented 8 years ago
I think I have corrected the issue the new added test cases pass.

There was a flow where a unicode object was being used to search in a raw 
string pool. Needed to encode the unicode search query into a string before 
starting the search.

Fix is available in svn now or in the next release.

Original comment by CodyPrec...@gmail.com on 22 Dec 2010 at 8:42