Found it! Line 89, sfLuceneIndexer.class.php, change this: return Zend_Search_Lucene_Field::Text($name, $contents);
To this: return Zend_Search_Lucene_Field::Text($name, $contents, 'UTF-8'); And it works... If you check the Zend manual you can see that each Zend_Search_Lucene_Field type takes a third parameter for the encoding of the field. http://framework.zend.com/manual/en/zend.search.lucene.html#zend.search.lucene.overview "Each of these methods (excluding Zend_Search_Lucene_Field::Binary() method) has optional $encoding parameter. It specifies input data encoding." On Oct 9, 12:31 am, Carl Vondrick <[EMAIL PROTECTED]> wrote: > On Monday, October 08, 2007, Daniel Staver wrote: > > What's causing this to happen? I've configured everything to use UTF-8 > > Hi, > This is either a bug in Zend Search Lucene or sfLucene. The tricky part is > figuring out which. :) > > I just committed a change that will let you configure this some more. In your > search.yml file, you can now define the analyzer, case sensitivity, and > whether to use mb_* functions: > > index: > analyzer: utf8num > case_sensitive: off > mb_string: on > > (mb_* functions are ~100 times slower than other functions, so beware!) > > If you figure out a work around, do let me know and I'll try to include it in > the next release. > > Carl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
