[MPlayer-cvslog] r19258 - trunk/DOCS/tech/oggless-xiph-codecs.txt

[Alex Beregszaszi]

Hi,

> > > why on earth should i?!
> > 
> > uhm. Maybe an RFC document gives more technical background the
> > proposal? We want the way to be widespread. As an RFC it has a
> > reputation, its not just "a document on mplayerhq" or like that.
> > 
> > You dont want to have this as an RFC?
> 
> read what i wrote!

I read it. But you surely want to work on your own txt version, thus
having two similar versions lying around.

> furthermore, before this can become an RFC / be proposed to IETF or
> whatever the process is  ... it needs to be more mature and your way

Jesus! I didnt knew that! I wanted to send it today in this form!$@

Of course this is just a WORK IN PROGRESS document. Nothing final,
nothing mature, but a work in progress document conforming to a style
used by the RFCs. Thats all. Still, it uses some common layout and
formatting in opposition to your text only version.

> of droping random comments from posts on nut-devel into it is not
> making it more mature but less

I just copied Baptiste's note to it with a big FIXME notation. I think
you understand what a FIXME means.

Also dont forget that YOU asked me to commit the work in progress
version so WE can work on it in an EASIER way - effectively COOPERATING.

[..]

> containers, the result would not help anyone and would never be
> accepted as a RFC writing a specification is not a "dump random ideas
> into a text file" thing everything has to be carefully disscussed,
> thought through and checked against the relevant container specs

I never thought about this. As I said, I wanted to submit the document
as it is TODAY.

It was a start "dumping YOUR random ideas" into the style and format
required by the RFC editor. I added an Introduction, Theora and FLAC
support among others, and of course converted your textual format to
this style.

-- 
Alex Beregszaszi | alex at fsn.hu | +36 70 3144424