Has anyone a working setup with openfts, aolserver 4 and a db encoded in unicode with some international (non-ascii) content?
I tried to index the same content with the same database with aolserver 3.3-oacs1 and it works, but 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
Versions used: Openfts:
Search-OpenFTS-tcl-0.3.2
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.
I sent this to openfts-general already but no answer yet, hopefully here it reaches more openfts with aolserver users.
