[ogg-dev] How Ogg mappings translate into the codecs parameter in Ogg media types
Silvia Pfeiffer
silviapfeiffer1 at gmail.com
Fri May 30 15:54:47 PDT 2008
I agree - we should use only hex or octal, but not mixed.
Cheers,
Silvia.
On Sat, May 31, 2008 at 2:20 AM, Ivo Emanuel Gonçalves
<justivo at gmail.com> wrote:
> I received the following comment regarding the table:
>
>> The table contains a mix of octal and hexadecimal 'escape sequences'
>> for non-printable / non-ASCII octets.
>> I strongly suggest to only use a single kind of numerical escapes.
>
> Is this feasible or even desired, or should we leave things as they are?
>
> For reference, this is how the table looks right now:
>
> Codec Identifier | Codecs Parameter
> -----------------------------------------------------------
> char[5]: 'BBCD\0' | dirac
> char[5]: '\177FLAC' | flac
> char[7]: '\x80theora' | theora
> char[7]: '\x01vorbis' | vorbis
> char[8]: 'Speex ' | speex
> char[8]: 'OggMIDI\0' | midi
> char[8]: 'CMML\0\0\0\0' | cmml
> char[8]: '\211PNG\r\n\032\n' | png
> char[8]: '\212MNG\r\n\032\n' | mng
> char[8]: '\213JNG\r\n\032\n' | jng
> char[8]: 'CELT ' | celt
> char[8]: 'PCM ' | pcm
> char[9]: '\x80kate\0\0\0\0' | kate
> char[9]: 'YUV4MPEG2' | yuv4mpeg
>
> (Don't expect it to look pretty without a monospaced font)
>
> -Ivo
> _______________________________________________
> ogg-dev mailing list
> ogg-dev at xiph.org
> http://lists.xiph.org/mailman/listinfo/ogg-dev
>
More information about the ogg-dev
mailing list