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

[Michael Niedermayer]

Hi

On Tue, Aug 01, 2006 at 04:21:22PM +0200, Alex Beregszaszi wrote:
[...]
> > B. do you agree on disscussing every non trivial change before
> > commiting it?
> 
> It was the same all the time.
> 
> > C. do you agree to keep functional changes and cosmetics seperate?
> 
> I did it so anyway.

iam sorry but iam not exactly sure what your awnsers mean, iam not a
native english speaker though i normally do understand what people mean
pretty well, here though iam unsure
and the online dictionaries ive tried also fail to translate this to
anything which would come close to an awnser, i could of course guess
what you mean but i feel that for an policy related issue that would
be inappropriate
so please elaborate on how you intend to decide on what you will commit
to the rfc draft?

can we agree on a seperation of seperate changes?
i still havent had enough time to review your xml file to look at all the
changes, as the complete txt->xml reformating makes that hard

just a few random changes i noticed:
"ther" vs. "theo" fourcc for theora
"Examples and Disscussions about specific containers" vs. "Example use in common containers"

 <section title="ASF">
     <t>ASF supports a single global header per stream and has timestamps so
     storing Vorbis in it should be possible.</t>
 </section>
vs.
Example and Disscussion of the asf container
asf supports a single global header per stream and has timestamps so
storing xiph codecs in it should be possible but asf is patented and 
microsoft has already threatened individuals so we strongly urge you to 
avoid this container

here the patent warning dissapeared, thats something which should be
disscussed not something which should happen during a format conversation


<t><xref target="NUT">NUT</xref> supports a single global header per
stream so the 3->1 merge and and the 1->3 split procedure above must be used.</t>
<t>In addition to that, there is nothing special with storing Vorbis
in NUT.</t>
vs.
Example and Disscussion of the nut container
nut supports a single global header per stream so the 1<->3 merge/split
procedure above must be used, except that theres nothing special with 
storing xiph codecs in nut

note the xiph vs vorbis change, and there are many other spots where
"vorbis" is used where my text used "xiph codecs"

these changes just dont belong in a txt->xml change, not to mention that many
are wrong my vote is to drop the xml as it is currently and either work with
the txt file or do a clean conversaion without any non formatting changes

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In the past you could go to a library and read, borrow or copy any book
Today you'd get arrested for mere telling someone where the library is