[mythtv-commits] Ticket #12298: Sorting improperly assuming an Article

MythTV noreply at mythtv.org
Fri Dec 14 19:32:53 UTC 2018


#12298: Sorting improperly assuming an Article
----------------------------------+-------------------------------
 Reporter:  skd5aner@…            |          Owner:  David Hampton
     Type:  Bug Report - General  |         Status:  assigned
 Priority:  minor                 |      Milestone:  30.0
Component:  MythTV - General      |        Version:  0.27-fixes
 Severity:  medium                |     Resolution:
 Keywords:                        |  Ticket locked:  0
----------------------------------+-------------------------------

Comment (by David Hampton):

 The changes that I'm planning to commit take the list of prefixes to
 delete from the existing language translation of the string '(A |An |The
 )' that is used in the 'Watch Recordings' section of MythTV.

 My changes will extend the prefix manipulation into the rest of the user
 interface.  If the translation of the prefix strings is empty then no
 changes are made.  If the translation is not empty, there is a user
 settable flag indicating whether or not the user would like the prefixes
 deleted.  If prefixes are to be deleted, there is a user settable list of
 strings to be exempt from prefix deletion.  I think that covers all the
 cases.

 At one point I was storing the sortable versions of the strings into the
 database, per a suggestion from dekarl, but I backed out that code.
 Upgrading the database to populate the new sortable string columns takes
 quite a bit of time, which is ok, but then any change to the sort
 preferences would require another delay while repopulating the database
 with new sort strings.  That delay would not be part of an upgrade and
 probably not be welcome by the user.  Individual translation take on the
 order of 1 usec on my development system, and 11 usec on a rPi, which
 seems fast enough for now.

 I would like to see better musicbrainz support at some point in the
 future, including parsing the sort tags.  That would definitely require
 storing the sort strings in the database, but would also introduce the
 need to track which strings came from an external source like MB and which
 came from heuristics.

-- 
Ticket URL: <https://code.mythtv.org/trac/ticket/12298#comment:7>
MythTV <http://www.mythtv.org>
MythTV Media Center


More information about the mythtv-commits mailing list