PassMark Logo
Home » Forum

utf-8 problem V6 asp

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • kdoucette
    Junior Member
    • Jan 2010
    • 2

    #1

    utf-8 problem V6 asp

    I am using Zoom V6, platform is ASP, pages being indexed have charset = utf-8 and I have configured Zoom to use unicode/utf-8 as the charset. Several pages use – for an en-dash character. The search results are garbling this character and displaying –.

    The site is at http://204.14.165.177/ - use CALSTART as the keyword and you'll see the issue.

    Any help you could give would be appreciated!
  • David
    Administrator
    • Dec 2004
    • 4714

    #2
    We'll have a look at it.
    As a quick work around you could use the normal ASCII hyphen.

    Comment

    • Ray
      Administrator
      • Dec 2004
      • 4357

      #3
      Your search page is here with the CALSTART query submitted:
      http://204.14.165.177/searchewd.asp?zoom_query=CALSTART&submit.x=20&subm it.y=16

      "searchewd.asp" appears to be your own script. It seems to be wrapping our script, "search.asp", which is here:
      http://204.14.165.177/search.asp?zoom_query=CALSTART&submit.x=20&submit. y=16

      Now if you go to the latter URL, you'll see that the search results provided by Zoom did not have a problem with the dash character. The cause is most likely because your script is re-encoding the (already correct) UTF-8 output from Zoom, and treating it as if it was not encoded, thus corrupting the character. You'll need to fix this in your "searchewd.asp" script.
      --Ray
      Wrensoft Web Software
      Sydney, Australia
      Zoom Search Engine

      Comment

      • kdoucette
        Junior Member
        • Jan 2010
        • 2

        #4
        server charset was interferring - thanks for helping

        Hi Ray,

        Thank you for looking at this issue. The server was set for iso-8859-1, so I had to regenerate the Zoom output with that charset and also set my asp program's charset to iso-8859-1 rather than utf-8. It is now working.

        Again, thanks for your help and your explanation.

        Kathy

        Comment

        Working...