[MPlayer-DOCS] CVS: main/DOCS/man/en mplayer.1,1.648,1.649

[Diego Biurrun]

The Wanderer writes:
> Diego Biurrun wrote:
> 
> > The Wanderer writes:
> > 
> >> Diego Biurrun CVS wrote:
> >> 
> >>> -switch to fixed quantizer mode and specify the quantizer to be used
> >>> +Switch to fixed quantizer mode and specify the quantizer to be used.
> >> 
> >> Possibly "fixed-quantizer"; this is perhaps arguable.
> > 
> > I tend to disagree, we would have to write "constant-bitrate" then as
> > well, wouldn't we?
> 
> Probably, since that is AFAICT the technically correct form. The fact
> that it is the expansion of a well-known acronym helps with grouping in
> that respect, however, and might qualify it for an exception.
> 
> In any case, I did note that this was arguable; I leave the decision to
> you.

Let's keep "fixed quantizer" then.

> > Yes, this is clumsy, but I think more radical surgery is needed.
> > 
> > How about
> > 
> >   .B interlacing
> >   Encode the fields of interlaced video material.
> >   Turn this option on for interlaced content.
> > 
> > instead of
> > 
> >   .B interlacing
> >   For interlaced video material, turn this option on.
> >   .I Note:
> >   This option does not deinterlace video, it encodes it field-based.
> > 
> > ?
> 
> That works, and has the advantage of being more clear; now I actually
> understand what it's talking about. <grin>

:-)

> >>> -use 4 motion vectors per macro-block, might give better compression at the
> >>> -cost of a slower encoding (default: off).
> >>> +Use 4 motion vectors per macro-block, might give better compression at the
> >>> +cost of a slower encoding.
> >>
> >> As I understand it, that's "macroblock". I'm also not happy with
> >> the phrasing of the rest, in terms of the pauses; I'd suggest
> >> either "macroblock, which might give" or "macroblock; this might
> >> give", and "but results in a slower encoding process" or similar.
> > 
> > I settled for
> > 
> >   Use 4 motion vectors per macroblock.
> >   This might give better compression but slows down encoding.
> 
> I still think you need a comma before the "but", but this is otherwise
> good.

OK.

> >>> -Enable Global Motion Compensation, which makes XviD generate Sprite
> >>> -Frames which best describe Pan/Zoom/Rotating images.
> >>> +Enable Global Motion Compensation, which makes XviD generate special
> >>> +frames (GMC-frames) which best describe Pan/Zoom/Rotating images.
> >>>  The decision whether to activate this option or not to save bits
> >>>  depends highly on the video material.
> >>
> >> This still feels fairly awkward, but I don't have suggestions to
> >> fix it offhand.
> > 
> > How about
> > 
> >   Enable Global Motion Compensation, which makes XviD generate special
> >   frames (GMC-frames) which are well suited for Pan/Zoom/Rotating images.
> > 
> > ?
> 
> That's fine for the first sentence, but IIRC I included the second
> because it is also not quite right, and this doesn't change that.
> 
> How about something like "Whether or not the use of this option will
> save bits is highly dependent on the source material."? That's still not
> perfect, but I think it's better.

OK.

> >> (It probably doesn't help that I leave for a job interview in an
> >> hour.)
> > 
> > How did it go?
> 
> As far as I could tell... the first part I couldn't tell, the
> interviewer was the type of Hispanic whom I find almost unreadable. The
> second part, however, seemed to go fairly well, and they tell me I'll
> know one way or another by early in the week (possibly even Monday).
> 
> I used my activity, such as it is, on these lists as part of my
> credentials... I was pleased to note that one of the people, at least,
> did appear to have heard of MPlayer. <grin>

:-)

Hmm, what kind of job did you apply for, btw?

Diego