Opened 13 years ago

Closed 13 years ago

#2414 closed enhancement (invalid)

Use category names in non-case-sensitvie manner

Reported by: Cougar <cougar@…> Owned by: danielk
Priority: minor Milestone: unknown
Component: mythtv Version: head
Severity: medium Keywords: EPG category listing
Cc: Ticket locked: no

Description

Different EPG grabbers use different name for the same category. Often the difference is only in caps. One example: "Game Show", "Game show" and "GAME SHOW". Last one is not in categories.xml yet but indroduced by tv_grab_ee (don't know what is the reason but all category names are always in caps). To keep categories.xml under reasonable size and to use the same color for the same category, I propose to use non-case-sensitvie names internally.

Here is patch that converts all category names from categories.xml to lowercase and later uses lowercase form of category from guide data when drawing backgroung for listing. I think it works with all charsets. At least UTF-8 characters with punctation was ok.

I'm not 100% sure I changed it in right places but it works. After using this patch it is also possible to clean up a categories.xml file a little bit.

To speed up it a little bit it is not possible to use lower case in categories.xml file and not convert these on fly. I'd like to not touch EPG data to show users category names exactly the way they was in EPG data.

Any feedback is welcome.

Attachments (1)

mythtv-category-11238.patch (1.2 KB) - added by Cougar <cougar@…> 13 years ago.

Download all attachments as: .zip

Change History (3)

Changed 13 years ago by Cougar <cougar@…>

Attachment: mythtv-category-11238.patch added

comment:1 Changed 13 years ago by danielk

Owner: changed from Isaac Richards to danielk

comment:2 Changed 13 years ago by danielk

Resolution: invalid
Status: newclosed

Please rework the patch to not do the lower case conversion in XMLParse, we shouldn't be mucking with the data that much in the parser. If the UIGuideType changes are sufficient, this change should be ok.

Reopen the ticket when you have updated + tested a new patch.

Note: See TracTickets for help on using tickets.