The old Kaltura mode seems to show subtitles in the site content language by default if present (except for English, maybe...?). Videojs mode does not; thus user must manually engage subtitles.
Need to check this logic and maybe adjust it on the videojs side.
Probably should mark one of the text tracks as 'default' for the content language, in which case video.js should pick it up.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Videojs: Enable texttrack in by default | mediawiki/extensions/TimedMediaHandler | master | +40 -0 |
What we really would want to know, is the language of the audio track... and compare that with wgUserLanguage...
Sounds like something that Commons Structured Data can help out with....
And maybe have settings in the preferences keeping track if people want to have subtitling enabled by default or not...
What would also be nice: an ability to pre-select (or opt out) the CC in [[File:...]].
Why is this lowest priority? Is accessibility of content not important? Is the work of subtitle writers not valuable?
https://www.mediawiki.org/wiki/Bug_management/Phabricator_etiquette
Report status and priority fields summarize and reflect reality and do not cause it. Read about the meaning of the Priority field values and, when in doubt, do not change them, but add a comment suggesting the change and convincing reasons for it.
As a general rule, the fastest way to see a bug resolved is to provide a patch; +2 is one policy for approving proposed code.
Convincing reasons for raising the priority of a bug include evidence that it affects normal, everyday work significantly. Contrived examples or problems that only appear under unlikely circumstances are generally evidence for treating the problem as "low" or "lowest" priority, since the limits of any non-trivial software can be exceeded if you try hard enough.
Translated. No one is working on this and unless the website is burning because of it, that means it has low priority. Because there is just too much stuff.
Because you (or someone else) have not written a patch yet. :) Longer version: https://www.mediawiki.org/wiki/Bug_management/Development_prioritization
Yes, I also started working with video from Commons, and noticed that it is very inconvenient to independently enable and select subtitles from a list of 50 languages.
Noticed this while testing on English Wikipedia as well. See https://en.wikipedia.org/wiki/Bangladesh for example where there is a national anthem with lyrics as subtitles. In the old player, those words appeared by default. This is quite essential, since the audio track is actually instrumental – without voice.
I think this would mostly close off discovery of lyrics and song text for such instrumental tracks. If a user happens to know these exist, they can still selected these through the settings, but I'm not sure a typical user would have enough confidence to understand that this is a pseudo-video, and that subtitles are a thing for these, and then to have the confidence and expectation that there both can be and actually are subtitles available.
Change 752233 had a related patch set uploaded (by TheDJ; author: TheDJ):
[mediawiki/extensions/TimedMediaHandler@master] Videojs: Enable texttrack in by default
Change 752233 merged by jenkins-bot:
[mediawiki/extensions/TimedMediaHandler@master] Videojs: Enable texttrack in by default