@Olly, @Richard: Thanks for chiming in! Afaik we use use Xapian::TermGenerator and Xapian:QueryParser everywhere. So maybe we should aim for Richard's solution for Natty and then hope we get CJK support out of the box for Natty+1.
The complicating factor here is that the Software Center index is created from a Python program (and also consumed by that program), but also consumed from a C program (unity-place-applications). So we'll need the CJK support available for Python as well. If it's built into Xapian this is a non-issue of course, but using Richard's cjk-tokenizer for Natty may be too complex for this late point in the cycle (considering we need to add Python bindings for it) - i'll talk to Michael Vogt about this.
@Olly, @Richard: Thanks for chiming in! Afaik we use use Xapian: :TermGenerator and Xapian:QueryParser everywhere. So maybe we should aim for Richard's solution for Natty and then hope we get CJK support out of the box for Natty+1.
The complicating factor here is that the Software Center index is created from a Python program (and also consumed by that program), but also consumed from a C program (unity- place-applicati ons). So we'll need the CJK support available for Python as well. If it's built into Xapian this is a non-issue of course, but using Richard's cjk-tokenizer for Natty may be too complex for this late point in the cycle (considering we need to add Python bindings for it) - i'll talk to Michael Vogt about this.