[FFmpeg-cvslog] Slight bug building ffmpeg-1.1.3 on OSX + patch to fix

[David Favor]

ffmpeg | branch: release/1.1 | David Favor <david at davidfavor.com> | Wed Feb 27 08:19:14 2013 -0600| [d4d1f32e48d92edc69c69b14f8e642e519f7c9af] | committer: Michael Niedermayer

Slight bug building ffmpeg-1.1.3 on OSX + patch to fix

Two instances of non-ascii characters have crept into file
doc/filters.texi which causes pod2man to error out and
break the build.

Signed-off-by: Michael Niedermayer <michaelni at gmx.at>

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=d4d1f32e48d92edc69c69b14f8e642e519f7c9af
---

 doc/filters.texi |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/filters.texi b/doc/filters.texi
index 937addf..9d6c2b8 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -4149,7 +4149,7 @@ Alternatively, the options can be specified as a flat string:
 
 @var{layout}[:@var{nb_frames}[:@var{margin}[:@var{padding}]]]
 
-For example, produce 8×8 PNG tiles of all keyframes (@option{-skip_frame
+For example, produce 8x8 PNG tiles of all keyframes (@option{-skip_frame
 nokey}) in a movie:
 @example
 ffmpeg -skip_frame nokey -i file.avi -vf 'scale=128:72,tile=8x8' -an -vsync 0 keyframes%03d.png
@@ -5543,7 +5543,7 @@ Activate unsafe mode: do not fail if segments have a different format.
 The filter has @var{v}+ at var{a} outputs: first @var{v} video outputs, then
 @var{a} audio outputs.
 
-There are @var{n}×(@var{v}+ at var{a}) inputs: first the inputs for the first
+There are @var{n}x(@var{v}+ at var{a}) inputs: first the inputs for the first
 segment, in the same order as the outputs, then the inputs for the second
 segment, etc.