Customize Language Extensions

4 votes

Allow user to specify customized language extensions such as:
.en -> .English
.fr -> .French

Under consideration Suggested by: TerranHOS (01 Nov, '19) • Upvoted: 27 Feb • Comments: 4

Comments: 4

01 Nov, '19
morpheus65535 Admin
Why in hell would you want that? They probably won’t even be recognized by most media player...
01 Nov, '19
TerranHOS
Plex recognizes both ISO-639-1 (2-letter) and ISO-639-2/B (3-letter) extensions. I believe it simply truncates whatever proceeds the 3-character limit. In my particular use case, I would like to label subtitles along the lines of ".English.Forced.srt" and ".English.SDH.srt" for human readability. While this does not necessarily impact Bazarr, allowing Bazarr to see these as existing subtitles (or even cases as simple as .English.srt) would prevent the creation of duplicate subtitles.
01 Nov, '19
morpheus65535 Admin
Oh... ok. Bazarr already name forced subtitles file like subs.en.forced.srt. We don't use hearing-impaired extension as there is no "standard": some use SDH where en-HI.
25 Apr, '23
TokerX
Late to the party, but it hasn't been implemented yet, so a quick reminder as to "why the hell" would anyone want this feature (for different reasons than OP)?

Simply because the naming is terrible.

"LATIN AMERICAN SPANISH" gets named as es-MX. Which in turn also makes it show in Plex as "Spanish (Mexico)". Latin America is slightly bigger than Mexico. The proper code for it, would be es-419. It's like like pt-BR where there's only one country that side of the ocean that speaks it. And quite insulting to all my Latin American Plex users, of whom none are Mexican.

Same thing with Traditional Chinese. It gets named zh-TW, according to Plex as well Taiwan seems to be the only place where Traditional Chinese is used, but that's simply not the case. zh-CHT or my preferred zh-Hant is much more appropriate.

Nothing a simple script can't solve, but it would be nice to have it implemented.