Most of (newer) scrapers (such as default tmdb) supports wraping item Title in user’s choice language. And they are able to store also original name into originaltitle variable (infolabel).
It could be displayed by skin in lists, etc. User can choose, which title he wants in lists, dynamically, even both of them for example.
The problem is, that Kodi lacks function to sort list according that title. It supports only Title, and Sorttitle parameters. Sorttitle is written to DB during scraping, so its not dynamic parameter at all.
I added this SortbyOriginalTitle function to Kodi (using 18 at this time, due to GXBB platform). I know, that this should go to the Kodi, and I will try create PR there eventually, but looking on Issues they have quite a full hands with Matrix, I would guess this will take significant amount of time to pull out.
My question is: would you be willing include this to the CE’s xbmc, if I create PR against CE’s xbmc? Or could be added like temporary patch, but this would be more suitable for 18 branch, since 19 is very active and patch would be possible needed to correct in future.
So far it works fine for me on Win32/Amlogic/Amlogic-ng… The 18 branch PR was closed, it will be maybe backported or not (they dont backport features usually). 19 branch is now in pending room
I added also sortmetod into JSON call, after 19434 was closed, so there is missing one commit, if you would decide to pick that one for Leia at some point. PR against master should be complete I believe.
If anyone would like to have this, or wants to take a quick peek, here is patch for Leia branch.
Ah, I didnt didnt noticed that (I am on 9.2 due to C2 hardware), I didnt noticed it on 9.2 branch so I assumed it wasnt included at all
The formatting should be already solved, I think that second automated Jenkins response was caused due build, which was automatically planned before I appled/commited requested changes and finishes after submit.
@JimmyS what about the JSON API version?
Every time I rebase XBMC and the JSONRPC_VERSION is changed the patch fails.
Is it really needed to bump the JSONRPC_VERSION or can it be excluded from the patch?
well, to be honest I dont have that deep understanding of project, but if I remember corectly, Kodi team requested JSON coverage in original PR, as I didnt include it in first draft.
For the patch purposes, I dont think that version number is needed to track, and when they include this PR, the patch wouldnt be needed at all (at least for the next Kodi version) ? However, the working code for JSON call could be usefull for someone.