Hi,
Why don't you look at TextIndexNG3 where almost everything is pluggable and configurable?
Firstly because I wasn't aware of its existence... Secondly (now I've seen it) because it seems particularly heavy for my use: It proposes many features, of which I shall only need 2 I have a very tight deadline on this and I'm new to Zope, python and the likes... I can't see how easy it's going to be to use: how long will it take me to transition from ZCTextindexes to TextIndexNG3's? (I've already spent quite some time integrating the ZCTextIndex queries into my code) If these issues are unfounded, I would be happy to use TextIndexNG3, but so far I think I'm better off fixing the couple of bugs in my Lexicon (apart from these, it's finished) TIA for your input on this :) Jonathan -----Message d'origine----- De : Andreas Jung [mailto:lists@zopyx.com] Envoyé : mercredi 2 mai 2007 10:57 À : Winterflood, Jonathan; zope@zope.org Objet : Re: [Zope] custom Lexicon developpement problems --On 2. Mai 2007 10:50:41 +0200 "Winterflood, Jonathan" <jonathan.winterflood@capgemini.com> wrote:
Hi all,
With the goal of allowing the use of wildcards anywhere in a ZCTextIndex query, and also ignore accentuated characters, I am developping a custom Lexicon, Splitter and CaseNormalizer. These are packed into a Product
Why don't you look at TextIndexNG3 where almost everything is pluggable and configurable? -aj This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.