Issue with PRFullTextSearch - WideString

[Reza RAZAVI]

At 18:56 15/04/2010, you wrote:
>Do you use WAKomEncoded in Seaside 2.8

I use WAKomEncoded in Seaside 3.0.

>or the UTF-8
>codex in Seaside 3?

Good point! Actually, I forgot (sorry for that) to mention that the 
bug has happened on a Debian server, where the VM has been launched 
with the following parm: "-encoding latin1".

However, I've saved the image on Debian, with the debugger already 
triggered. Then, I moved the image to Win/Vista, where I had the 
observations reported previously.

Otherwise I'm basically using default Pharo/Seaside/Pier configs.

Thanks again for your insight,
Regards,
Reza