3 ms·
I think the right approach would be to label content that is not in the source language you have set as your device locale. It’s not about filtering out the co
by sethd 3y ago
I think the right approach would be to label content that is not in the source language you have set as your device locale.
It’s not about filtering out the content, it’s about making it easy to tell whether or not it’s going to start playing with dubbed audio so the viewer can make a better choice.
- homarp 3y agoHollywood is not in the source language for most of the world. Netflix brand new English content is also not in the source language for most of the world.
- jltsiren 3y agoLocales are often compromises that don't reflect user preferences particularly well. People speak multiple languages, and they may have different preferences for content / UI languages, date/time formats etc. And the preferences may be situational, such as native X > native English > English translation/localization > X translation/localization. Just tag the content with the relevant languages and let the user create filters based on them. And assume that the user understands that languages don't form disjoint categories, because the content itself could be multilingual. Besides, original audio with subtitles is usually superior to dubbed audio.