[FFmpeg-cvslog] doc: replace '=?UTF-8?Q?=C3=97?=' symbol with 'x'

[Stefano Sabatini]

ffmpeg | branch: master | Stefano Sabatini <stefasab at gmail.com> | Wed Feb  6 22:40:18 2013 +0100| [d11ac64ecf03f7896ebc5e776e078fdc1f0543a4] | committer: Stefano Sabatini

doc: replace '×' symbol with 'x'

Non-ascii chars are not correctly rendered in both MAN and HTML output or
may even cause compilation failure. Thus avoid to use them until we find
a satisfying way to deal with them.

Fix trac ticket #2243.

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

 doc/ffmpeg.texi  |    2 +-
 doc/filters.texi |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi
index 4761d39..8dc97b8 100644
--- a/doc/ffmpeg.texi
+++ b/doc/ffmpeg.texi
@@ -1024,7 +1024,7 @@ ffmpeg -filter_complex 'color=c=red' -t 5 out.mkv
 
 As a special exception, you can use a bitmap subtitle stream as input: it
 will be converted into a video with the same size as the largest video in
-the file, or 720×576 if no video is present. Note that this is an
+the file, or 720x576 if no video is present. Note that this is an
 experimental and temporary solution. It will be removed once libavfilter has
 proper support for subtitles.
 
diff --git a/doc/filters.texi b/doc/filters.texi
index 76a73e6..e047852 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -5996,7 +5996,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.