* Peter Alberer <[EMAIL PROTECTED]> [20040311 16:07]:
> I am not sure that has anything to do with your problem, but i had to
> readd the following line to /aolserver/modules/tcl/init.tcl that was in
> aolserver-33-ad13:
>
> encoding system [ns_config ns/server/[ns_info server] SystemEncoding
> utf-8]
>
> otherwise the system encoding was iso8859 and that caused problems when
> talking to a Unicode-database.

Thanks for the advice. The system encoding of aolserver was indeed
iso8859-1 before that change. Unfortunately changing it to utf-8 the
way you suggested did not change the indexing behaviour, so I reverted
it back because I don't know where else that interferes (propably when
writing files).

Another suggestion from Matthew Walker was to change fts_index.tcl
from

db_dml insert_idx_tbl "
    insert into $self(PREFIX)index$g
        (lexem,tid,pos)
         values
        ('$lexem',$tid,
        '\{[join $rs($lexem) ,]\}')"


to

set converted_lexem [encoding convertto utf-8 $lexem]
db_dml insert_idx_tbl "
    insert into $self(PREFIX)index$g
        (lexem,tid,pos)
         values
        ('$converted_lexem',$tid,
        '\{[join $rs($lexem) ,]\}')"


And that made the indexing work again! The content also seems to be
correctly retrievable in searches. Thanks a lot Matthew!

Is anyone with more insight in openfts following this discussion and
can suggest a general fix for this that works with both aolserver 3
and 4?


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.

Reply via email to