We’re working on a site build for a client who publishes an enormous amount of text content in six different languages. Their collection of videos, however, is currently only available on the English version of the site. Since the videos are very useful to all of their audiences, we set out to find a way to make them more accessible.
We found the solution in JW FLV Media Player, a robust tool that has already proven itself in the Drupal community. Here is an example of what our main video play landing page looks like right now for the client.
The player’s subtitle feature parses an XML document based on the W3C Timed-Text specification, which allows you to specify the start time and end time of each line of text. Several applications capable of authoring these XML files are listed towards the bottom of JW’s Accessibility page.
Je trouve très inquiétant que le monde semble pas au courant de l'ampleur du problème de disparitions au Sri Lanka. Il n'existe pas de chiffres, mais le nombre de cas que nous avons documentés
Using this feature, the Internationalization module (i18n), and some CCK configurations we were a able to have our video player automatically display subtitles to users browsing the site in a non-English language.
We began with node type called video with two CCK filefields. One is used to upload and store an FLV video file. The i18n module works by cloning a master node for each translation. Since the video file is identical for each language, we’ve configured the field to be synchronized among all translated nodes. The second file field will hold the Timed-Text XML document. This field should not be synchronized because each translation will need to reference a different file.
drupal_add_js('so1.addVariable("captions", "/sites/default/files/subtitles/subtitles.xml");', 'inline', 'footer');
If you’re using Playlists (we were), you should look at the XPFS playlist module. We’ve put this to use by overriding themexspfplaylist_list() and adding our own meta field for the caption file.