OggSRT: Difference between revisions
Jump to navigation
Jump to search
(add note about not customizing the srt format) |
(→SRT specification: note not supporting <b>, <font> etc., see http://lists.xiph.org/pipermail/accessibility/2008-December/000227.html) |
||
| Line 9: | Line 9: | ||
We adhere to existing SRT specifications without modification, for player compatibility. | We adhere to existing SRT specifications without modification, for player compatibility. | ||
* We base this on: http://en.wikipedia.org/wiki/Subrip#Sample_file | |||
http:// | * Accordingly, it would make sense to be lenient regarding the index number and the display position. | ||
With considerations of web interoperability, we do NOT require support for the additional markup tags | |||
such as <b> and <font> | |||
described at: http://forum.doom9.org/showthread.php?p=470941#post470941 | |||
== Encapsulation == | == Encapsulation == | ||
Revision as of 19:36, 7 December 2008
This is an unimplented discussion draft about encapsulating srt subtitles in OggText.
Discussion is on the accessibility@xiph.org list.
SRT specification
We adhere to existing SRT specifications without modification, for player compatibility.
- We base this on: http://en.wikipedia.org/wiki/Subrip#Sample_file
- Accordingly, it would make sense to be lenient regarding the index number and the display position.
With considerations of web interoperability, we do NOT require support for the additional markup tags such as <b> and <font> described at: http://forum.doom9.org/showthread.php?p=470941#post470941
Encapsulation
For details of Ogg BOS headers and granulepos etc, see OggText
It should be simple:
- It doesn't need an extra header.
- Each time span is mapped into a single packet.
- Silvia suggests to drop the index number upon mapping into Ogg -this will make it tolerant towards packet loss.
- The time span and the text will thus be the data inside the page.