> I'm testing this. Meanwhile, a brief question, do you really want > Kate's media type to be "application" as opposed to "text"?Thanks. About the media type, my understanding was that text was for actual text, not binary that could be decoded into text. If you think another would be more appropriate, please tell which. If it would be text/x-kate, I'd see that more for the textual representation, eg: kate { event { from 0:0:0 to 0:1:0 "Hello, world!" } } I quickly had a search and found: http://www.w3.org/Protocols/rfc1341/4_Content-Type.html which seems to corroborate the use of "text/foo" for actual text. However, I'm not very familiar with all of this, so I'm happy to be corrected and the content type to be changed.
If you look at http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions right at the bottom is a description of what the codecs without container format are called. CMML as a timed text codec has a mime type of text/cmml. Similarly, the textual representation of Kate should be text/x-kate. When you encode Kate in Ogg, it would not normally be expected to come without audio or video. Thus, if it's an audio file, it should be video/ogg - for a video file it should be video/ogg - and if it's a random other file (such as Kate encoded inside Ogg without anything else) it should be application/ogg with the mime type text/x-kate inside skeleton. Cheers, Silvia. On Fri, Mar 28, 2008 at 9:01 PM, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote:> > I'm testing this. Meanwhile, a brief question, do you really want > > Kate's media type to be "application" as opposed to "text"? > > Thanks. > > About the media type, my understanding was that text was for actual text, > not binary that could be decoded into text. If you think another would be > more appropriate, please tell which. If it would be text/x-kate, I'd see that > more for the textual representation, eg: > > kate { > event { > from 0:0:0 to 0:1:0 "Hello, world!" > } > } > > I quickly had a search and found: > http://www.w3.org/Protocols/rfc1341/4_Content-Type.html > which seems to corroborate the use of "text/foo" for actual text. However, > I'm not very familiar with all of this, so I'm happy to be corrected and the > content type to be changed. > > > _______________________________________________ > ogg-dev mailing list > ogg-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/ogg-dev >
> container format are called. CMML as a timed text codec has a mime > type of text/cmml. Similarly, the textual representation of Kate > should be text/x-kate.Agree, as both of these are text.> When you encode Kate in Ogg, it would not normally be expected to come > without audio or video. Thus, if it's an audio file, it should be > video/ogg - for a video file it should be video/ogg - and if it's a > random other file (such as Kate encoded inside Ogg without anything > else) it should be application/ogg with the mime type text/x-kate > inside skeleton.So, just to confirm, you reckon it'd be text/x-kate in skeleton for the embedded Kate stream in Ogg, though it is 8 bit binary data and not the text source representation ? If so, I'll post an updated patch soon, but I want to make sure we're on the same thing as, from he link I posted, text means "such [extra] software must not be required in order to get the general idea of the content", which is clearly not the case for kate, as text data is often not even byte aligned (something I've wondered about whether it'd be a good idea to autoalign actually, too late now though), and application is "some other kind of data, typically either uninterpreted binary data or information to be processed by a mail-based application." Of course, this is a layman's reading, so if you confirm text/x-kate would be correct for the binary bitstream, I'll change it so. Cheers