jelle napisał(a): > Has anyone has had a bit more luck with django.contrib.search than > what I've been getting so far? > The API seems quite nice, and its easy to set up, but it seems that > the lucene back end that I've been using so far is pretty useless > since it can't deal with Unicode text. Which for me is a showstopper > for sure. > Which is a pity in my mind: django.contrib.search could be a wonderful > addition!
PyLucene on its own has no problems with unicode. The PyLucene API accepts either unicode objects or utf-8 encoded strings. I suppose the problem is in the django.contrib.search (I don't use it so I cann't be sure). -- Jarek Zgoda Skype: jzgoda | GTalk: [EMAIL PROTECTED] | voice: +48228430101 "We read Knuth so you don't have to." (Tim Peters) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
