> 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).
True, I've seen that as well.
--~--~-~--~~~---
> 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).
True, I've seen that as well.
--~--~-~--~~~---
> 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).
True, I've seen that as well.
--~--~-~--~~~---
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
4 matches
Mail list logo
