Comment 10 for bug 201291

(sorry for the break, need to attach two things)

The second patch is the naive solution that just
associates the .oga etc. extensions with application/ogg,
which is what .ogg was associated with before.

However I think this makes it difficult to move forward
in such a way that we can set one application to
handle .oga and another for .ogv.

On balance I think the first is the correct thing to
do, but we will need some way of working out what
else needs to be fixed. Can anyone produce a list
of what needs to be fixed, or tell me a way to
produce one?

Thanks,

James