[theora-dev] libtheora API documentation

Silvia.Pfeiffer at csiro.au Silvia.Pfeiffer at csiro.au
Tue Jun 27 03:26:32 PDT 2006

I suggest giving Shane cvs access. He has been involved with gstreamer coding before and has proven to be a great developer (as well as documentation writer :).


-----Original Message-----
From:	theora-dev-bounces at xiph.org on behalf of Michael Smith
Sent:	Tue 6/27/2006 8:15 PM
To:	Shane Stephens
Cc:	theora-dev at xiph.org
Subject:	Re: [theora-dev] libtheora API documentation

On 6/27/06, Shane Stephens <shane.stephens at gmail.com> wrote:
> Hi,
> The documentation for the libtheora API is a little bit sparse - for
> example, information about whether yuv_buffer structs should be
> managed by the user or the library is missing.  From talking to derf,
> and from what I can see in the example files, the user allocates the
> struct but not the luma/chroma buffers on decode; and the user
> allocates both the struct and the luma/chroma buffers on encode.
> I've made some small additions to the documentation explaining this.
> Should I send these changes?  If so, do you have any guidelines for
> patch format?

Patches are always welcome. Documentation patches are _particularly_
welcome - we know that our documentation is often insufficient, so
help here is great. Thanks!

Generally, unified diffs are the preferred way to provide patches.

It's probably best to send what you have now, then updates when you've
got substantial improvements - no need to make people wait even longer
for this!

theora-dev mailing list
theora-dev at xiph.org

More information about the theora-dev mailing list