[PR #7388] [MERGED] Hide ISO 639-2 special codes in display titles #11372

Closed
opened 2026-02-07 06:37:19 +03:00 by OVERLORD · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/7388
Author: @GermanCoding
Created: 3/1/2022
Status: Merged
Merged: 3/5/2022
Merged by: @crobibero

Base: masterHead: iso639-undefined


📝 Commits (2)

  • e09641b Hide ISO 639-2 special codes in display titles
  • 3f6a14e Use extension method for list search

📊 Changes

1 file changed (+15 additions, -1 deletions)

View changed files

📝 MediaBrowser.Model/Entities/MediaStream.cs (+15 -1)

📄 Description

This has bugged me for a while now.

Jellyfin shows the language for audio streams, if it is present in metadata. This is great and correct.

However, there are audio streams that make use of ISO 639-2 special codes. Those then look like this:

before

"und" is ISO-special for undetermined, which is confusing for users (especially as "und" is also a word in german). Generally I think some of these specials are rarely known, e.g who knows that "zxx" is "no linguistic content; not applicable".

Therefore I believe having these specials displayed prominently in display titles is wrong. I get that there is still value in displaying this information - it's technical data that may be of interest to more technical users. Hence I did not remove language codes displaying from metadata - just from the display title.

Not it looks like this, much cleaner IMHO:

after

Language codes are still shown in associated metadata:

metadata

There are also more language codes that Jellyfin currently can't expand (ISO 639-2 B codes for example), but here I think that there is still value in displaying them, hence they are not filtered. It's just the specials that cause more confusion than providing information to users.

Changes

Filters ISO639-2 special codes (except the reserved range - whoever uses that hopefully knows what they're doing) from display titles.

Testing

As shown in the screenshots above, manually verified that this works as intended.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/7388 **Author:** [@GermanCoding](https://github.com/GermanCoding) **Created:** 3/1/2022 **Status:** ✅ Merged **Merged:** 3/5/2022 **Merged by:** [@crobibero](https://github.com/crobibero) **Base:** `master` ← **Head:** `iso639-undefined` --- ### 📝 Commits (2) - [`e09641b`](https://github.com/jellyfin/jellyfin/commit/e09641b452fcdd76c08dc18abeefa089f92212f1) Hide ISO 639-2 special codes in display titles - [`3f6a14e`](https://github.com/jellyfin/jellyfin/commit/3f6a14e1fd458eb6455d2c07f516dc827fdf3239) Use extension method for list search ### 📊 Changes **1 file changed** (+15 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `MediaBrowser.Model/Entities/MediaStream.cs` (+15 -1) </details> ### 📄 Description This has bugged me for a while now. Jellyfin shows the language for audio streams, if it is present in metadata. This is great and correct. However, there are audio streams that make use of ISO 639-2 special codes. Those then look like this: ![before](https://user-images.githubusercontent.com/4279661/156206695-4d13bc11-d49e-492a-adba-6c4e7e8b1861.PNG) "und" is ISO-special for undetermined, which is confusing for users (especially as "und" is also a word in german). Generally I think some of these specials are rarely known, e.g who knows that "zxx" is "no linguistic content; not applicable". Therefore I believe having these specials displayed prominently in display titles is wrong. I get that there is still value in displaying this information - it's technical data that may be of interest to more technical users. Hence I did **not** remove language codes displaying from metadata - just from the display title. Not it looks like this, much cleaner IMHO: ![after](https://user-images.githubusercontent.com/4279661/156207278-8500f2dd-511c-4c9f-9365-a193d97abcab.PNG) Language codes are still shown in associated metadata: ![metadata](https://user-images.githubusercontent.com/4279661/156207392-6d3f7444-15e2-4419-8422-05e9f2612cda.PNG) There are also more language codes that Jellyfin currently can't expand (ISO 639-2 B codes for example), but here I think that there is still value in displaying them, hence they are not filtered. It's just the specials that cause more confusion than providing information to users. <!-- Ensure your title is short, descriptive, and in the imperative mood (Fix X, Change Y, instead of Fixed X, Changed Y). For a good inspiration of what to write in commit messages and PRs please review https://chris.beams.io/posts/git-commit/ and our documentation. --> **Changes** Filters ISO639-2 special codes (except the reserved range - whoever uses that hopefully knows what they're doing) from display titles. **Testing** As shown in the screenshots above, manually verified that this works as intended. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 06:37:19 +03:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#11372