[SCM] libav/experimental: Clarify Visual Studio FAQ.

[siretart at users.alioth.debian.org]

The following commit has been merged in the experimental branch:
commit a9d5a4485ae53f263f67a3804d8edabe65c955c2
Author: Diego Biurrun <diego at biurrun.de>
Date:   Fri Nov 9 14:05:43 2007 +0000

    Clarify Visual Studio FAQ.
    
    Originally committed as revision 10970 to svn://svn.ffmpeg.org/ffmpeg/trunk

diff --git a/doc/faq.texi b/doc/faq.texi
index 8ace580..fcb58fe 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -360,10 +360,10 @@ 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
 with @code{#ifdef}s related to the compiler.
 
- at section Microsoft Visual C++ produces many errors.
+ at section Is Microsoft Visual C++ supported?
 
-Microsoft Visual C++ is not compliant to the C standard and does not support
-the inline assembly used in FFmpeg.
+No. Microsoft Visual C++ is not compliant to the C99 standard and does
+not - among other things - support the inline assembly used in FFmpeg.
 If you wish - for whatever weird reason - to use MSVC++ for your
 project then you can link the MSVC++ code with libav* as long as
 you compile the latter with a working C compiler. For more information, see
@@ -372,7 +372,7 @@ documentation.
 
 There have been efforts to make FFmpeg compatible with MSVC++ in the
 past. However, they have all been rejected as too intrusive, especially
-since MinGW does the job perfectly adequately. None of the core developers
+since MinGW does the job adequately. None of the core developers
 work with MSVC++ and thus this item is low priority. Should you find
 the silver bullet that solves this problem, feel free to shoot it at us.
 

-- 
Libav/FFmpeg packaging