Skip to content

Check numeric rating value after splitting country code - #17273

Merged
Bond-009 merged 2 commits into
jellyfin:masterfrom
theguymadmax:ratigs-numerical-score
Jul 13, 2026
Merged

Bond-009 merged 2 commits into
jellyfin:masterfrom
theguymadmax:ratigs-numerical-score

Conversation

@theguymadmax

Copy link
Copy Markdown
Member

We were already converting plain numeric ratings straight to a score, e.g., a rating of 16 became a score of 16. But we only did that as a whole, not when a country code was present. So GR-16 would not match and would be treated as unrated.

Changes

  • After splitting a rating into country code & rating, if there is no match, try parsing it as a plain number before giving up and treating it as unrated.
  • Also handle a trailing "+" so JP-18+ will be be scored as 18

Code assistance
N/A

Issues
I've been seeing lots of log reports with parental rating being treated as unrated when there is a numerical value and a country code present.

[2026-07-08 02:51:46.466 +03:00] [WRN] [32] Emby.Server.Implementations.Localization.LocalizationManager: Rating '"GR-16"' not found in the '"GR"' rating system, treating as unrated

@jellyfin-bot

Copy link
Copy Markdown
Contributor

Jellyfin API (v 12.0.0)


Result


No differences. Specifications are equivalent

@Shadowghost
Shadowghost requested a review from a team July 9, 2026 06:56
Comment thread Emby.Server.Implementations/Localization/LocalizationManager.cs Outdated
@sonarqubecloud

Copy link
Copy Markdown

@theguymadmax theguymadmax moved this from Todo to Approved in Jellyfin v12 Jul 12, 2026
@Bond-009
Bond-009 merged commit ebab369 into jellyfin:master Jul 13, 2026
19 checks passed
@github-project-automation github-project-automation Bot moved this from Approved to Done in Jellyfin v12 Jul 13, 2026
@theguymadmax
theguymadmax deleted the ratigs-numerical-score branch July 20, 2026 23:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants