|
The reason is that charset is not set for page: http://melior.univ-montp3.fr/ and
ASPseek indexer treats word P�rez as two words: P and rez.
I don't know which value of iso88591 do you use in
CharsetTableU1 directive, but if you use value iso-8859-1 then this value must
be first in the CharsetAlias directive.
If cs parameter is set to iso88591 which is
different from specified in CharsetTableU1, then searcher also treats word P�rez as two words and finds the page.
If cs parameter is set to the value specified in
CharsetTableU1 then searcher can't find word P�rez because
it is not in the index due to absent charset.
Alexander.
|
Title: Re: [aseek-users] Problems with charsets/unicode
- SV: [aseek-users] Problems with charsets/unicode Claus Jul Larsen
- SV: [aseek-users] Problems with charsets/unicode Claus Jul Larsen
- Re: [aseek-users] Problems with charsets/unicode Alexander F. Avdonkin
- SV: [aseek-users] Problems with charsets/unicode Claus Jul Larsen
- Re: [aseek-users] Problems with charsets/unicode Alexander F. Avdonkin
- SV: [aseek-users] Problems with charsets/unicode Claus Jul Larsen
- Re: [aseek-users] Problems with charsets/unicode Alexander F. Avdonkin
- SV: [aseek-users] Problems with charsets/unicode Claus Jul Larsen
- Re: [aseek-users] Problems with charsets/unicode Alexander F. Avdonkin
- Re: [aseek-users] Problems with charsets/unicode Gilles Perez-Lambert
- Re: [aseek-users] Problems with charsets/unicode Alexander F. Avdonkin
- Re: [aseek-users] Problems with charsets/unicode Gilles Perez-Lambert
- Re[2]: [aseek-users] Problems with charsets/unicode Alexei Sh.
- Re: [aseek-users] Problems with charsets/unicode Jan Karabina
- Re: [aseek-users] Problems with charsets/unicode Alexander F. Avdonkin
