preparing for release 2.03
diff --git a/README.html b/README.html
index 93969da..4830f4d 100644
--- a/README.html
+++ b/README.html
@@ -4,7 +4,7 @@
 <head>

 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

 <meta name="generator" content="Docutils 0.6: http://docutils.sourceforge.net/" />

-<title>pycparser v2.02</title>

+<title>pycparser v2.03</title>

 <meta name="author" content="Eli Bendersky" />

 <style type="text/css">

 

@@ -305,8 +305,8 @@
 </style>

 </head>

 <body>

-<div class="document" id="pycparser-v2-02">

-<h1 class="title">pycparser v2.02</h1>

+<div class="document" id="pycparser-v2-03">

+<h1 class="title">pycparser v2.03</h1>

 <table class="docinfo" frame="void" rules="none">

 <col class="docinfo-name" />

 <col class="docinfo-content" />

@@ -387,8 +387,8 @@
 <div class="section" id="prerequisites">

 <h2>2.1&nbsp;&nbsp;&nbsp;Prerequisites</h2>

 <ul class="simple">

-<li><tt class="docutils literal"><span class="pre">pycparser</span></tt> was tested on Python 2.5, 2.6 and 3.1, on both Linux and Windows</li>

-<li><tt class="docutils literal"><span class="pre">pycparser</span></tt> uses the PLY module for the actual lexer and parser construction. Install PLY version 3.3 (earlier versions work at least since 2.5) from <a class="reference external" href="http://www.dabeaz.com/ply/">its website</a>.</li>

+<li><tt class="docutils literal"><span class="pre">pycparser</span></tt> was tested on Python 2.6 and 3.2, on both Linux and Windows. It should work on any later version (in both the 2.x and 3.x lines) as well.</li>

+<li><tt class="docutils literal"><span class="pre">pycparser</span></tt> uses the PLY module for the actual lexer and parser construction. Install PLY from <a class="reference external" href="http://www.dabeaz.com/ply/">its website</a>.</li>

 </ul>

 </div>

 <div class="section" id="installation-process">

@@ -413,7 +413,7 @@
 </div>

 <div class="section" id="what-about-the-standard-c-library-headers">

 <h2>3.2&nbsp;&nbsp;&nbsp;What about the standard C library headers?</h2>

-<p>C code almost always includes various header files from the standard C library, like <tt class="docutils literal"><span class="pre">stdio.h</span></tt>. While, with some effort, <tt class="docutils literal"><span class="pre">pycparser</span></tt> can be made to parse the standard headers from any C compiler, it's much simpler to use the provided &quot;fake&quot; standard in includes in <tt class="docutils literal"><span class="pre">utils/fake_libc_include</span></tt>. These are standard C header files that contain only the bare necessities to allow valid parsing of the files that use them. As a bonus, since they're minimal, it can significantly improve the performance of parsing C files.</p>

+<p>C code almost always includes various header files from the standard C library, like <tt class="docutils literal"><span class="pre">stdio.h</span></tt>. While, with some effort, <tt class="docutils literal"><span class="pre">pycparser</span></tt> can be made to parse the standard headers from any C compiler, it's much simpler to use the provided &quot;fake&quot; standard  includes in <tt class="docutils literal"><span class="pre">utils/fake_libc_include</span></tt>. These are standard C header files that contain only the bare necessities to allow valid parsing of the files that use them. As a bonus, since they're minimal, it can significantly improve the performance of parsing C files.</p>

 <p>See the <tt class="docutils literal"><span class="pre">using_cpp_libc.py</span></tt> example for more details.</p>

 </div>

 <div class="section" id="basic-usage">

@@ -463,6 +463,20 @@
 <div class="section" id="changelog">

 <h1>7&nbsp;&nbsp;&nbsp;Changelog</h1>

 <ul class="simple">

+<li>Version 2.03 (06.03.2011)<ul>

+<li>Bug fixes:<ul>

+<li>Issue 17: empty file-level declarations</li>

+<li>Issue 18: empty statements and declarations in functions</li>

+<li>Issue 19: anonymous structs &amp; union fields</li>

+<li>Issue 23: fix coordinates of Cast nodes</li>

+</ul>

+</li>

+<li>New example added (<tt class="docutils literal"><span class="pre">examples/c-to-c.py</span></tt>) for translating ASTs generated by <tt class="docutils literal"><span class="pre">pycparser</span></tt> back into C code.</li>

+<li><tt class="docutils literal"><span class="pre">pycparser</span></tt> is now on PyPI (Python Package Index)</li>

+<li>Created <a class="reference external" href="http://code.google.com/p/pycparser/wiki/FAQ">FAQ</a> on the <tt class="docutils literal"><span class="pre">pycparser</span></tt> project page</li>

+<li>Removed support for Python 2.5. <tt class="docutils literal"><span class="pre">pycparser</span></tt> supports Python 2 from 2.6 and on, and Python 3.</li>

+</ul>

+</li>

 <li>Version 2.02 (10.12.2010)<ul>

 <li>The name of a <tt class="docutils literal"><span class="pre">NamedInitializer</span></tt> node was turned into a sequence of nodes

 instead of an attribute, to make it discoverable by the AST node visitor.</li>