Repository files navigation

The Dubbing and Audio description Profiles of TTML2,by theTimed Text Working Groupis a profile of TTML2 suitable for the scripting, voicing and audio mixingof dubbing tracks and audio description for video.This work was originally a combination ofTheAudio Description Profile of TTML2, which was originally made by theAudio Description Community Group,andTimed Text Authoring Lineage (TTAL).

It is intended to meet the requirements set out in theRequirements for Dubbing and Audio description.

The Editor's Draft can be viewed athttps://w3c.github.io/dapt/

The specification is built usingRespec and needs noadditional build steps for the main body. The figures are written inPlantUML and need to be exported in SVG formatafter any changes.

The PlantUML figures' source files are in/figures/sources.

The PlantUML figures can be exported as SVG via the command line,but IDE support in e.g. VSCode can make the editing experience simpler.

If using VSCode with thePlantUML Extension, the following workspace settings may be helpful:

{"plantuml.diagramsRoot":"figures/sources","plantuml.exportFormat":"svg","plantuml.exportOutDir":"figures","plantuml.exportSubFolder":false,}

Then while editing the source, running "PlantUML: Export Current Diagram"from the command palette will regenerate the SVG and write the output tothe correct location,/figures.

Unfortunately the SVG that PlantUML generates from our source files has some structural issues that cause it to fail the W3C's HTML validator.The following steps can be taken to fix them. It'd be neat to automate this somehow, one day...

1. deletecontentStyleType="text/css"
2. delete text matching the regexp title="[#a-zA-Z\-]+"
3. delete text matching the regexp = codeline="[#a-zA-Z0-9\-]+"
4. deduplicate id values, e.g. in more than one place - a specific problem with the two links from Text to Style in the class diagram. E.g. change the "other" link withid="link_Text_Style" toid="link_Text_Style_other"
5. Move wrappers from around boxes which contain other elements, which therefore get nested, so the link is not on the box but is on the top text.
   • Specifically, where there is/svg/a/g/text move the<a> wrappers to being around the<text> that includes the text that's relevant.
   • It then becomes/svg/g/a/text (where thea has is the second child of theg, the first being arect)
   • Atsushi also moved the<rect> at/svg/a/g/rect out of the<g> so there is/svg/rect followed by/svg/g/a/text but why? Seems okay without doing that.