Search with Swedish national characters...

[miniGranis]

I have this problem as well.
I tried to copy the patch above to the web dir. and make a search though Search2 but I still dont get any hits.
I cant try to search from the GBPVR UI since my graphics card wont support VMR9 renderer.
I am a real newbie to GB-PVR but I am very familiar with PVR's a such having used BeyondTV for several years.

My intent is to use GB-PVR as a recording server, all interactions will be through EWA. Playback is done on XBOX running XBMC.

[forzaKGB]

Actually I have also noticed the patch did not fix all errors. I still get some searches that miss out. But have not been able to nail down the problem. I will try to get some time to create logs and upload. But as christmas is coming up there are more pressing duties at hand...

[miniGranis]

I understand fully, I am currently just trying GB-PCR out so there is no rush.
Let me know if I can help.

[UncleJohnsBand]

I have this problem as well.
I tried to copy the patch above to the web dir. and make a search though Search2 but I still dont get any hits.
I cant try to search from the GBPVR UI since my graphics card wont support VMR9 renderer.
I am a real newbie to GB-PVR but I am very familiar with PVR's a such having used BeyondTV for several years.

My intent is to use GB-PVR as a recording server, all interactions will be through EWA. Playback is done on XBOX running XBMC.

Are you searching a different language as well?

[miniGranis]

Yes I am, Swedish as well.
Let me know if you need my xmltv file, screen shots or anything else.
BTW I also noted two other issues:
1 - To search the Description field both description ansd Subtitle needs to be checked, this applies for both search and search2.
2 - For guide2 size of the channel logos in Config screen does not work.

Do you want me to start new threads on those issues ?

[UncleJohnsBand]

Yes I am, Swedish as well.
Let me know if you need my xmltv file, screen shots or anything else.

See my PM.....need you to upload your gbpvr.db3 file to my FTP site and give me an example search phrase that is not working and I can look into what might be going on.

BTW I also noted two other issues:
1 - To search the Description field both description ansd Subtitle needs to be checked, this applies for both search and search2.

This is fixed for the next release.

2 - For guide2 size of the channel logos in Config screen does not work.

This is by design.....in CSS mode the channel icon dynamically changes based on the browser window size.

Do you want me to start new threads on those issues ?

No need to re-post somewhere....I took care of it out of this thread.

[miniGranis]

Will do, it might take a day or two since my GBPVR HW is giving me trouble right now.
Thanks for the other answers.

[miniGranis]

OK, after my motherboard gave up I am on track again...
Here is a snapshot from my EPG and one from the search page.






This search comes up empty.

Please look into all swedish characters, namely åäö ÅÄÖ
The same problems occurs for both search and search2
(Also responded to PM)

Thanks and Merry Christmas.

[UncleJohnsBand]

OK, after my motherboard gave up I am on track again...
Here is a snapshot from my EPG and one from the search page.

This search comes up empty.

Please look into all swedish characters, namely åäö ÅÄÖ
The same problems occurs for both search and search2
(Also responded to PM)

Thanks and Merry Christmas.

Ok.....I think this may be a SQLite limitation......I found the below info on the FAQ's for SQLite:

I searched for Där without checking the Case Sensitive box next to the search phrase and came up empty.....however, when I selected the Case Sensitive option I got results.

Try searching and checking the Case Sensitive box and see if that makes a difference for you.

(18) Case-insensitive matching of Unicode characters does not work.[INDENT]The default configuration of SQLite only supports case-insensitive comparisons of ASCII characters. The reason for this is that doing full Unicode case-insensitive comparisons and case conversions requires tables and logic that would nearly double the size of the SQLite library. The SQLite developers reason that any application that needs full Unicode case support probably already has the necessary tables and functions and so SQLite should not take up space to duplicate this ability. Instead of providing full Unicode case support by default, SQLite provides the ability to link against external Unicode comparison and conversion routines. The application can overload the built-in NOCASE collating sequence (using sqlite3_create_collation()) and the built-in like(), upper(), and lower() functions (using sqlite3_create_function()). The SQLite source code includes an "ICU" extension that does these overloads. Or, developers can write their own overloads based on their own Unicode-aware comparison routines already contained within their project.
[/INDENT]

[miniGranis]

Ok.....I think this may be a SQLite limitation......I found the below info on the FAQ's for SQLite:

I searched for Där without checking the Case Sensitive box next to the search phrase and came up empty.....however, when I selected the Case Sensitive option I got results.

Try searching and checking the Case Sensitive box and see if that makes a difference for you.

(18) Case-insensitive matching of Unicode characters does not work.[INDENT]The default configuration of SQLite only supports case-insensitive comparisons of ASCII characters. The reason for this is that doing full Unicode case-insensitive comparisons and case conversions requires tables and logic that would nearly double the size of the SQLite library. The SQLite developers reason that any application that needs full Unicode case support probably already has the necessary tables and functions and so SQLite should not take up space to duplicate this ability. Instead of providing full Unicode case support by default, SQLite provides the ability to link against external Unicode comparison and conversion routines. The application can overload the built-in NOCASE collating sequence (using sqlite3_create_collation()) and the built-in like(), upper(), and lower() functions (using sqlite3_create_function()). The SQLite source code includes an "ICU" extension that does these overloads. Or, developers can write their own overloads based on their own Unicode-aware comparison routines already contained within their project.
[/INDENT]

Thanks this ineed seems to be the case.
I guess I have to live with it, not a biggie if you know it.
Thanks for the investigation.