Hello, I have the same probleme running french iso8859-1.
A quick work around that works for me is running the follwing SQL command on after indexation: update urlwords00 set charset = ''; update urlwords01 set charset = ''; update urlwords02 set charset = ''; update urlwords03 set charset = ''; update urlwords04 set charset = ''; update urlwords05 set charset = ''; update urlwords06 set charset = ''; update urlwords07 set charset = ''; update urlwords08 set charset = ''; update urlwords09 set charset = ''; update urlwords10 set charset = ''; update urlwords11 set charset = ''; update urlwords12 set charset = ''; update urlwords13 set charset = ''; update urlwords14 set charset = ''; update urlwords15 set charset = ''; After indexation "charset" field is filled with iso8859-1 and I have buggy char. With "charset" empty, char are ok. if anyone has a cleaner workaround I also be intereted in. xav Le mer 08/10/2003 � 15:13, Martin Sarsale a �crit : > Dear all: > > I've posted a message on the forums > (http://forum.aspseek.org/index.php?t=msg&th=972&rid=&S=350509258e89155abff94bbaf6d73294&pl_view=&start=0#msg_2740) > some time ago and I got no answer, so I'll ask my questions here: > > We're having problems with spanish accented letters. I've followed all the steps in > the faq, but the only see question marks instead of accented letters in the result > page. > > > Aspseek version: 1.2.10-1asp rpm (mysql backend) > > 2) ucharset.conf is included in both searchd.conf and aspseek.conf > 3) ucharset.conf has: > CharsetTableU1 iso-8859-1 es tables/iso8859-1.txt > CharsetAlias iso-8859-1 iso88591 iso8859-1 iso8859.1 iso-8859.1 iso_8859-1:1988 > iso_8859-1 iso_8859.1 > 4) Web server returns > Content-Type: text/html; charset=iso8859-1 > > Any ideas?
