[ogg-dev] [PATCH] oggmerge, various

ogg.k.ogg.k at googlemail.com ogg.k.ogg.k at googlemail.com
Fri Mar 28 05:52:00 PDT 2008

> To provide you with a proper answer, I'd have to read what you do to
> the text data to encode it in binary. Haven't got the time for that
> right now, sorry. But if it is some binary encoding and not just a
> gzip-type compression, maybe application/x-kate may indeed be
> appropriate. This would however mean that some specialised application
> is required to decode the data.

In a nutshell, all data is stuffed into an oggpack_buffer. Text data often
ends up non byte aligned. A packet's data is unrecognizable as text
(and contains a fair amount of non-text data anyway).
A specialized program is indeed required (something linking against
the libkate API, which does the oggpack stuff).

Interesting point about gzip however, I'd have thought gzipped text would
use something like application/gzip rather than text/gzip, though I suppose
it does make sense to allow programs to auto apply gzip -dc filters and
get at the text.

> I might spend some time tomorrow to properly understand the
> situation... but have to get sleep now...

Sure, didn't mean to take up your time, sorry.


More information about the ogg-dev mailing list