[MPlayer-DOCS] CVS: main/DOCS/xml/en mencoder.xml,1.62,1.63

[Diego Biurrun]

On Sat, May 14, 2005 at 06:07:01AM -0400, The Wanderer wrote:
> Diego Biurrun wrote:
> 
> >On Sat, May 14, 2005 at 12:45:54AM -0400, The Wanderer wrote:
> >
> >>Guillaume Poirier CVS wrote:
> 
> >>>+  Television was designed to refresh these in alternation as a
> >>>+  cheap form of analog compression.
> >>>+  The human eye supposedly compensates for this, but once you
> >>>+  understand interlacing you will learn to see it on TV too and
> >>>+  never enjoy TV again.
> >>
> >>I'd say "as much" before "again" here.
> >
> >While I would normally agree here, this completely distorts what Rich
> >is saying, he'd never make such a balanced and non-controversial
> >statement, so I'll reject this change ;-)
> 
> I'd have no objection to this if the text in question were clearly
> ascribed to Richard; as things stand, unless I've missed something there
> is no indication of where the text came from much less exactly who's
> responsible for any given portion of it. As such, unless you want to
> attribute this directly to him in the text itself, I still think it
> should be changed.

Notice the ;-).  I completely agree with you, I was just poking
(well-deserved ;) fun at Rich :-)

> >>Also: elsewhere you have usages like "24fps", but here you have "25
> >>fps". Presumably this is because it would be awkward to say "24
> >>and 30fps", and at least nearly equally so to say "24fps and
> >>30fps"; still, it might be worth trying to keep things consistent.
> >
> >I've wondered myself what the best way to solve this would be.
> 
> In this particular instance, it occurs to me that we may be able to
> dodge the problem by simply expanding the acronym; "24 and 30 frames per
> second" followed by either "25 frames per second" or "25fps" doesn't
> look too bad to me, and it seems to fit the rule well enough.

Aren't workarounds great? :)

Diego