== What is Kate? ==
a codec for karaoke and text encapsulation for Ogg. Text and images can becarried by a Kate stream, and animated. Most of the time, this would be multiplexedwith audio/video to carry subtitles, song lyrics (with or without karaoke data), etc,but doesn't have to be . A possible use of a lone Kate stream would be an e-book. Moreover, the motion feature gives Kate a powerful means to describe arbitrary curves, so hand drawing of shapes can be achieved. This was originally meant for karaoke use, but can be used for any purpose. Motions can be attached to various semantics, like position, color, etc, so scrolling or fading text can be defined.
Simple uses of Kate streams are movie subtitles for Theora videos, either text based,
as may be created by [http://www.v2v.cc/~j/ffmpeg2theora ffmpeg2theora], or image
based, such as created by [http://thoggen.net Thoggen] (patching needed).
== Why a new codec? ==
*text data: text/image and optional motions, accompanied by optional overrides for style, region, language, etc
*keepalive: can be emitted at any time to help a demuxer know where we're at, but those packets are optional
*end data [EOS]: marks the end of the stream, it doesn't have any useful payload
::0x00 text data (including optional motions and overrides)
::0x7f end packet (EOS)
This format described here is for bitstream version 0.x.
For more detailed information, refer to the format documentation
I have patches for the following with Kate support:
(for multiplexed per-language subtitles - all region/style info is ignored)*xine (everything kate supports, as xine is my testbed)
These may be found in the libkate source distribution (see [[#Downloading|Downloading]]
Please remember the 15 character limit if proposing other categories.
* Note that the list of categories is subject to change, and will likelybe replaced by new, more "identifier like" ones. The three ones above,however, would be kept for backward compatibility as they're already used.
== Text to speech ==
== Reference encoder/decoder ==
A encoder and a decoder are included in the tools directory. The encoder
pulls its input from a customtext based file format (see [[#The Kate file format|The Kate file format]]),which is by no means meant to be part of the Kate bitstream specification itself , from an SubRip (.srt) format file (the most common subtitle format I found , and a very basic one) , or from a lyrics ( . lrc) format file.
The Kate bitstreams encoded and decoded by those tools are (supposed to be) correct for this
And after all, some people might prefer editing the XML version.
== Matroska mapping ==
A public git repository is available at [http://git.xiph.org/?p=users/oggk/tiger.git;a=summary http://git.xiph.org/?p=users/oggk/tiger.git;a=summary].
Things I need to get feedback on ==
* is it a good idea to avoid floating point usage altogether ?