Guido van Rossum wrote:
I don't know where you would expect a patch to be found, but in this
particular case the Zope Collector is a good place to look:
http://collector.zope.org/Zope/597
Use the collector, Luke! ;-)
Um, that's not a patch. Can you attach a context or unified diff to
the col
> I don't know where you would expect a patch to be found, but in this
> particular case the Zope Collector is a good place to look:
>
> http://collector.zope.org/Zope/597
>
> Use the collector, Luke! ;-)
Um, that's not a patch. Can you attach a context or unified diff to
the collector item?
>
> I must've missed the start of this thread (I only just signed up for
> this list). I didn't see any patch -- I thought it was just a gripe
> about ZCTextIndex. Of course patches are welcome -- where can I find
> this particular patch?
Hi Guido!
I don't know where you would expect a patch to b
> >>The problem seems to be that ZCTextIndex indeed does not do the
> >>splitting "right" if German Umlauts are used. There is no option for
> >>"Unicode-aware splitter". Instead of a Vocabulary it uses a
> >>Lexicon, which just offers two options: "HTML aware splitter" and
> >>"Whitespace splitte
Guido van Rossum wrote:
The problem seems to be that ZCTextIndex indeed does not do the
splitting "right" if German Umlauts are used. There is no option for
"Unicode-aware splitter". Instead of a Vocabulary it uses a
Lexicon, which just offers two options: "HTML aware splitter" and
"Whitespace sp
> The problem seems to be that ZCTextIndex indeed does not do the
> splitting "right" if German Umlauts are used. There is no option for
> "Unicode-aware splitter". Instead of a Vocabulary it uses a
> Lexicon, which just offers two options: "HTML aware splitter" and
> "Whitespace splitter". I have
Hi!
> Please note that former Zope versions already include a dedicated
> unicode-aware
> splitter that is already usable with the old TextIndex and maybe with
> ZCTextIndex.
> TextIndexNG resolves all these issues by doing the complete internal
> processing by
> converting the data into unicode.
--On Freitag, 8. November 2002 19:49 +0100 Joachim Werner
<[EMAIL PROTECTED]> wrote:
Hi!
Some additional remarks: While making the splitting dependent on the
locale settings (as done in the old TextIndex) helps with most use cases,
I'm not sure if that is the right thing to do in the long run.
Hi!
Some additional remarks: While making the splitting dependent on the locale
settings (as done in the old TextIndex) helps with most use cases, I'm not
sure if that is the right thing to do in the long run. Locale settings are
good for client software, i.e. if you want to have a program behave
Casey Duncan wrote:
The main reason I have not merged this already is that I lack a sample to make
a new test with. If someone can provide me with some content samples that
break now, but work with the patch, I will make a new test and checkin the
fix for 2.7 perhaps 2.6.1 if desired.
-Casey
The main reason I have not merged this already is that I lack a sample to make
a new test with. If someone can provide me with some content samples that
break now, but work with the patch, I will make a new test and checkin the
fix for 2.7 perhaps 2.6.1 if desired.
-Casey
On Friday 08 November
Joachim Werner wrote:
Does it make sense to get ZCTextIndex fixed (there seems to be a patch in
the collector already) or should I go with TextIndexNG? If yes, is it ready
for production environments?
hi,
I've submitted a patch for locale-support for ZCTextIndex:
http://collector.zope.org/Zope
12 matches
Mail list logo
