Remove space before question marks.

Originally committed as revision 9378 to svn://svn.ffmpeg.org/ffmpeg/trunk

doc/faq.texi

@@ -16,7 +16,7 @@ Even if ffmpeg can read the file format, it may not support all its
 codecs. Please consult the supported codec list in the ffmpeg
 documentation.
 
-@section How do I encode single pictures to movies ?
+@section How do I encode single pictures to movies?
 
 First, rename your pictures to follow a numerical sequence.
 For example, img1.jpg, img2.jpg, img3.jpg,...
@@ -32,7 +32,7 @@ Notice that @samp{%d} is replaced by the image number.
 
 The same logic is used for any image format that ffmpeg reads.
 
-@section How do I encode movie to single pictures ?
+@section How do I encode movie to single pictures?
 
 Use:
 
@@ -58,26 +58,26 @@ Applying that to the previous example:
 
 Beware that there is no "jpeg" codec. Use "mjpeg" instead.
 
-@section FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it ?
+@section FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it?
 
 No. FFmpeg only supports open source codecs. Windows DLLs are not
 portable, bloated and often slow.
 
-@section I get "Unsupported codec (id=86043) for input stream #0.1". What is the problem ?
+@section I get "Unsupported codec (id=86043) for input stream #0.1". What is the problem?
 
 This is the Qcelp codec, FFmpeg has no support for that codec currently. Try mencoder/mplayer it might work.
 
-@section Why do I see a slight quality degradation with multithreaded MPEG* encoding ?
+@section Why do I see a slight quality degradation with multithreaded MPEG* encoding?
 
 For multithreaded MPEG* encoding, the encoded slices must be independent,
 otherwise thread n would practically have to wait for n-1 to finish, so it's
 quite logical that there is a small reduction of quality. This is not a bug.
 
-@section How can I read from the standard input or write to the standard output ?
+@section How can I read from the standard input or write to the standard output?
 
 Use @file{-} as filename.
 
-@section Why does ffmpeg not decode audio in VOB files ?
+@section Why does ffmpeg not decode audio in VOB files?
 
 The audio is AC3 (a.k.a. A/52). AC3 decoding is an optional component in ffmpeg
 as the component that handles AC3 decoding (liba52) is currently released under
@@ -86,7 +86,7 @@ with @code{./configure --enable-liba52 --enable-gpl}. Take care: by
 enabling AC3, you automatically change the license of libavcodec from
 LGPL to GPL.
 
-@section Which codecs are supported by Windows ?
+@section Which codecs are supported by Windows?
 
 Windows does not support standard formats like MPEG very well, unless you
 install some additional codecs
@@ -326,13 +326,13 @@ If there is a feature that is important to you, the best way to get
 it implemented is to undertake the task yourself.
 
 
-@section Are there examples illustrating how to use the FFmpeg libraries, particularly libavcodec and libavformat ?
+@section Are there examples illustrating how to use the FFmpeg libraries, particularly libavcodec and libavformat?
 
 Yes. Read the Developers Guide of the FFmpeg documentation. Alternatively,
 examine the source code for one of the many open source projects that
 already incorporate ffmpeg at (@url{projects.php}).
 
-@section Can you support my C compiler XXX ?
+@section Can you support my C compiler XXX?
 
 It depends. If your compiler is C99-compliant, then patches to support
 it are likely to be welcome if they do not pollute the source code
@@ -353,7 +353,7 @@ since MinGW does the job perfectly adequately. None of the core developers
 work with Visual C++ and thus this item is low priority. Should you find
 the silver bullet that solves this problem, feel free to shoot it at us.
 
-@section Can I use FFmpeg or libavcodec under Windows ?
+@section Can I use FFmpeg or libavcodec under Windows?
 
 Yes, but the MinGW tools @emph{must} be used to compile FFmpeg. You
 can link the resulting DLLs with any other Windows program. Read the
@@ -364,24 +364,24 @@ To get help and instructions for using FFmpeg under Windows, check out
 the FFmpeg Windows Help Forum at
 @url{http://arrozcru.no-ip.org/ffmpeg/}.
 
-@section Can you add automake, libtool or autoconf support ?
+@section Can you add automake, libtool or autoconf support?
 
 No. These tools are too bloated and they complicate the build.
 
-@section Why not rewrite ffmpeg in object-oriented C++ ?
+@section Why not rewrite ffmpeg in object-oriented C++?
 
 ffmpeg is already organized in a highly modular manner and does not need to
 be rewritten in a formal object language. Further, many of the developers
 favor straight C; it works for them. For more arguments on this matter,
 read "Programming Religion" at (@url{http://www.tux.org/lkml/#s15}).
 
-@section Why are the ffmpeg programs devoid of debugging symbols ?
+@section Why are the ffmpeg programs devoid of debugging symbols?
 
 The build process creates ffmpeg_g, ffplay_g, etc. which contain full debug
 information. Those binaries are strip'd to create ffmpeg, ffplay, etc. If
 you need the debug information, used the *_g versions.
 
-@section I do not like the LGPL, can I contribute code under the GPL instead ?
+@section I do not like the LGPL, can I contribute code under the GPL instead?
 
 Yes, as long as the code is optional and can easily and cleanly be placed
 under #ifdef CONFIG_GPL without breaking anything. So for example a new codec
@@ -395,7 +395,7 @@ the whole libav*. If you wish, disable some parts with configure switches.
 You can also try to hack it and remove more, but if you had problems fixing
 the compilation failure then you are probably not qualified for this.
 
-@section I have a file in memory / a API different from *open/*read/ libc how do i use it with libavformat ?
+@section I have a file in memory / a API different from *open/*read/ libc how do i use it with libavformat?
 
 You have to implement a URLProtocol, see libavformat/file.c in FFmpeg
 and libmpdemux/demux_lavf.c in MPlayer sources.