[After trying openfts-general and openacs forums without success I
thought it might be worth trying the aolserver list, sorry if that is
a cross posting for you.]
openfts indexing of unicode encoded databases does not work anymore
with aolserver 4.
I get this error when the indexer encounters text with german umlauts
in it:
[05/Mar/2004:21:26:28][26498.1102388144][-sched:20-] Error: dbinit:
error(localhost:5432:rubi,ERROR: invalid byte sequence for encoding
"UNICODE": 0xc3
): '
insert into index4
(lexem,tid,pos)
values
('m�',21313,
'{31}')'
transaction error
Does anyone use openfts successfully with aolserver 4 on a unicode
encoded database with international content? If yes are there any
extra steps necessary to make it work? It used to work fine with
aolserver 3.3oacs1 - the items were indexed and searching for text
with umlauts in it returned the desired results.
I tried having a look how the nsfts module communicates with aolserver
and what change might have resulted in the error, but my C skills are
not sufficient.
Openfts:
Search-OpenFTS-tcl-0.3.2 / Search-OpenFTS-tcl-0.3.1 (same effect with
either version)
pg version:
PostgreSQL 7.4.1 on i386-pc-linux-gnu, compiled by GCC i386-linux-gcc
(GCC) 3.3.3 20040125 (prerelease) (Debian)
aolserver:
with aolserver3.3oacs1 it works, with aolserver 4.0.2 (local tcl
8.4.5-1 of debian unstable) it doesn't.
Any hints appreciated, til
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
