X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fdrawing;h=987301236d4f8c8470a9a79437bc24ba7716ef2e;hb=a17adea98d0e3b4b130ba2d3c65521c26e7f32a7;hp=b8867f63d438b4d26a6e7d66f63722ff8aaf37db;hpb=79b9bc16839fca8f1436223bcb5fcd55ad098798;p=mono.git

diff --git a/web/drawing b/web/drawing
index b8867f63d43..987301236d4 100644
--- a/web/drawing
+++ b/web/drawing
@@ -11,19 +11,27 @@
 	similar to the PDF 1.4 composition-based imaging model.
 
 	Our implementation is a C# wrapper around the GDI+ C API (also
-	called the "GDI+ Flat API").  
+	called the <a
+	href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdicpp/GDIPlus/GDIPlusReference.asp">"GDI+
+	Flat API"</a>).
+
+	This means that the C# code is the same for Windows and Unix
+	systems.  The following graph explains the situation:
 
 	<center>
 	<img src="images/system-drawing.png">
 	</center>
 
-	In Windows Mono uses the GDI+ library that is included
-	with the operating system, while in Unix we provide an
-	implementation of this API which uses Cairo to do the heavy
-	lifting. 
+	In Windows Mono uses the GDI+ library that is included with
+	the operating system (<tt>GDIPLUS.DLL</tt>, while in Unix we
+	provide an implementation of this API in the
+	<tt>libgdiplus.so</tt> shared library.  Our
+	<tt>libgdiplus.so</tt> has the same C Flat API as the
+	<tt>GDIPLUS.DLL</tt>.  Our implementation uses Cairo to do
+	the heavy lifting.
 
-	The implementation of GDI+ lives in mcs/class/System.Drawing
-	in the gdiplus directory and requires <a
+	The implementation of GDI+ lives in the libgdiplus cvs module
+	and requires <a
 	href="http://www.cairographics.org">Cairo</a> to be installed
 	to get the package built.