OggSRT: Difference between revisions

From XiphWiki
Jump to navigation Jump to search
(init draft of page, from a11y discussion)
 
(cat)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{draft}}
{{draft}}


This is an unimplented discussion draft about encapsulating srt subtitles in [[OggText]]
This is an unimplented discussion draft about encapsulating srt subtitles in [[OggText]].
 
Discussion is on the [http://lists.xiph.org/mailman/listinfo/accessibility accessibility@xiph.org] list.


== SRT specification ==
== SRT specification ==


The following describes the SRT format:
We adhere to existing SRT specifications without modification, for player compatibility.
http://forum.doom9.org/showthread.php?p=470941#post470941


According to: http://en.wikipedia.org/wiki/Subrip#Sample_file
* We base this on: http://en.wikipedia.org/wiki/Subrip#Sample_file
it would make sense to be lenient regarding the index number and the
* Accordingly, it would make sense to be lenient regarding the index number and the display position.
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 ==
Line 21: Line 25:
* Silvia suggests to drop the index number upon mapping into Ogg -this will make it tolerant towards packet loss.
* 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.
* The time span and the text will thus be the data inside the page.
[[Category:Ogg Mappings]]

Latest revision as of 05:42, 8 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.

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.