Re: [greenstone-devel] greenstone preferences and history in Greek

From Katherine Don
DateTue, 26 Jul 2005 16:39:55 +1200
Subject Re: [greenstone-devel] greenstone preferences and history in Greek
In-Reply-To (1122039593-22003-5-camel-localhost-localdomain)
Hi Daniel

The search history bug affects most languages, but it has nothing to do
with typing characters into the search box.

Entering characters into the search box is more dependent on your
computer setup. If you can type non-US characters into a document
editor, then I would assume you can type them into the search box.
(Although I am not too sure about all this). Depending on the encoding
that your computer is using, you may need to change the encoding on the
preferences page.

The cut and past method is quite good because it means anyone can enter
these characters, regardless of their setup.

Regards,
Katherine Don

Daniel Paul O'Donnell wrote:
> Was this bug somehow specific to greek? What aspects of typing non-US
> keyboard characters in the search window did it affect? We were unable
> to enter characters like the ae-ligature into ours, and ended up with a
> cut-and-paste method.
>
> -d
>
> On Fri, 2005-22-07 at 15:30 +1200, Katherine Don wrote:
>
>>Hi Marios
>>
>>>Firstly, when I perform a search for something in Greek, the search history
>>>does not present the Greek characters correctly.
>>
>>This is a bug. I have fixed it for the next release. If you want to fix
>>your version and you have a C++ compiler, then here is the fix:
>>in src/recpt/queryaction.cpp, in method save_search_history
>>
>>change
>> text_t formattedquery =cgi_safe(qstring);
>> query += "&q="+formattedquery;
>>
>>to
>> query += "&q="+qstring;
>>
>>then recompile the code.
>>
>>>Secondly, when I go to the "Preferences" option and choose "ignore lower
>>>case/ upper case" this function does not appear to work or respond.
>>>
>>
>>Are you clicking the set preferences button? How are you leaving the
>>preferences page? You can't use the back button, you must use one of the
>>navigation bar buttons to go to the search page, otherwise preferences
>>will not be changed.
>>
>>Does case folding work for other languages, eg english?
>>
>>
>>>Thirdly, how can the choices I make in the "Preferences" option work by
>>>default, without having to choose them each time I want to perform a search?
>>>
>>
>>You can set the default values for preferences in etc/main.cfg:
>>eg
>># sets the default value for k (case folding) to 1 (casefolding on)
>>cgiarg shortname=k argdefault=1
>>
>>
>>>Finally, at the Librarian Interface when I choose the "Enable Advanced
>>>Searches" option and then "Form", whatever I try to search for in Greek will
>>>not produce any results.
>>
>>What encoding are you entering the query terms in? If it's not utf-8,
>>then try setting the encoding (on the preferences page) to greek. does
>>it work now?
>>
>>Regards,
>>Katherine Don
>>
>>>Thanks
>>>
>>>Marios
>>>
>>>
>>>Your immediate response to the above queries would be greatly appreciated.
>>>Thanking you in advance for your kind cooperation.
>>>
>>>
>>>
>>>_______________________________________________
>>>greenstone-devel mailing list
>>>greenstone-devel@list.scms.waikato.ac.nz
>>>https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel
>>>
>>
>>_______________________________________________
>>greenstone-devel mailing list
>>greenstone-devel@list.scms.waikato.ac.nz
>>https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel
>
>
>