Search Engine has an issue with international characters

[MRAMBERG@…]

Sat May 22 17:01:40 2004 MRAMBERG - Ticket created [Reply] [Comment]

Subject: Search Engine has an issue with international characters

Namely, it doesn't support them, so searches for things like grünerløkka and grønland are moot.

Download (untitled) 95b

Sat May 22 17:14:21 2004 IVORW - Correspondence added [Reply] [Comment]

From: IVORW

[MRAMBERG - Sat May 22 17:01:40 2004]:

Namely, it doesn't support them, so searches for things like grünerløkka and grønland are moot.

I will look at expanding the allowed character set for search strings to take into account internationalization. We need to see if there are issues with Search::InvertedIndex?, and make sure that it tokenizes in an i18n way.

Ivor.

Download (untitled) 379b

Mon Dec 13 19:19:56 2004 DOM - Severity Normal added Sun Jan 9 10:02:22 2005 DOM - Comments added [Reply] [Comment]

[IVORW - Sat May 22 17:14:21 2004]:

[MRAMBERG - Sat May 22 17:01:40 2004]:

Namely, it doesn't support them, so searches for things like grünerløkka and grønland are moot.

I will look at expanding the allowed character set for search strings to take into account internationalization. We need to see if there are issues with Search::InvertedIndex?, and make sure that it tokenizes in an i18n way.

Work on this should probably be concentrated on Plucene - see other utf8 bugs in OpenGuides though.

[klur]

Doing the search with accented characters: hotel/hôtel the keyword hôtel doesn't even appear in the search title, where hotel does. Otherwise accented characters are displayed properly using sqlite.