Change Details

Translating video clips is currently done as plain text. This has all the disadvantages listed in T30021. The Translate extension can probably provide an easier interface for translators, but it will require some integration work.

**Type of activity:** unconference **Main topic:** Possibly slightly related to Handling wiki content beyond plaintext == The problem == Translating video clips is currently done as plain text. This has all the disadvantages listed in T30021. The Translate extension can probably provide an easier interface for translators, hopefully leading to increased number of translations, but it will require some integration work. Some open questions: # Do translators often tweak the timestamps? # Do translators often combine/split/add/delete units compared to the source language? # Do translators watch the video while or after translating? Which will influence the answers to: # Is it enough to create a message group from the strings and allow only translation of those? # Do we need to integrate video player to the translation tool? # Should we really be thinking of dedicated interface rather than extending Special:Translate... # ...but would starting with Special:Translate be better than waiting for that? # How would changes be handled? Like translatable pages, or like file based message groups? Or completely manually? # Would solution that treats them as translatable pages make sense? == Expected outcome == * Better understanding of how subtitles are translated (ideally before Summit, unless people who would use this attend the Summit) * Narrowing down implementation options based on above as well how to best interact with the video player, content handler etc. * Better understanding how this relates to any other work related to videos (if any) such as structured == Current status of the discussion == * Starting the exploration

**Type of activity:** unconference **Main topic:** Possibly slightly related to Handling wiki content beyond plaintext == The problem == Translating video clips is currently done as plain text. This has all the disadvantages listed in T30021. The Translate extension can probably provide an easier interface for translators, hopefully leading to increased number of translations, but it will require some integration work. Some open questions: # Do translators often tweak the timestamps? # Do translators often combine/split/add/delete units compared to the source language? # Do translators watch the video while or after translating? Which will influence the answers to: # Is it enough to create a message group from the strings and allow only translation of those? # Do we need to integrate video player to the translation tool? # Should we really be thinking of dedicated interface rather than extending Special:Translate... # ...but would starting with Special:Translate be better than waiting for that? # How would changes be handled? Like translatable pages, or like file based message groups? Or completely manually? # Would solution that treats them as translatable pages make sense? == Expected outcome == * Better understanding of how subtitles are translated (ideally before Summit, unless people who would use this attend the Summit) * Narrowing down implementation options based on above as well how to best interact with the video player, content handler etc. * Better understanding how this relates to any other work related to videos (if any) such as structured == Current status of the discussion == * Starting the exploration