![]() Uses "\N" for line breaks (though this is somewhat configurable). Uses "\n" for line breaks.Ĭurrently has pixel-based positioning. Appears to be text-based.Ĭouldn't find a specification for these formats. Appears to be XML-based.Ĭouldn't find a specification for this format. Appears to come in text and binary variants.Ĭouldn't find a specification for this format. Would be difficult to extend in a backwards-compatible way.Ĭouldn't find a specification for this format. Probably has complicated legacy parsing requirements. Could probably be used as the basis for a new similar format. ![]() Supports a number of features that aren't necessary. (Appears to be basically the MicroDVD format, but using seconds instead of frames.)Ĭouldn't find a specification for this format or it's later version PU2020. Has some weird rules relating to displaying multiple subtitles at once.Ĭurrently has low resolution timings. adding a new timing format).īinary format, nigh on impossible to hand-edit. Could be extended, though most useful extensions would not be backwards-compatible (e.g. Relative timings, which can be hard to hand-edit correctly. Uses frames for timings in the first version decaseconds in the second version. Uses strings delimited by apostrophes to mark line breaks. (Appears to be basically the PowerDivX format, but using frames instead of seconds.) Uses "\n" for line breaks.īinary format with text components, making it hard to hand-edit. Could be extended usefully.Ĭouldn't find any information on this format. Uses tabs as a deliminator in one version, spaces and commas in another. ![]() Unclear how easy it would be to extend usefully without effectively making a completely new format. Doesn't seem to support overlapping times. Couldn't find a specification for this format.Īpparently XML-based and/or binary based.
0 Comments
Leave a Reply. |