Now Fixed: Bug with Geocoder Output

[pamela (Google employee)]

We have now fixed the bug with the HTTP Geocoder's XML output that was
described in the last post. The Geocoder now produces valid XML.

We are adding additional tests to ensure this does not happen in the
future. We apologize profusely for this error.

Note: If your website is using the HTTP Geocoder for user-entered
addresses, you should consider switching to GClientGeocoder in JS API
v2 or ClientGeocoder in the Flash API. We designed the APIs and quota
system so that it is better to use the provided classes for user-
entered addresses than the HTTP Geocoder. It is best to use the HTTP
Geocoder for geocoding a cache of known addresses on the server.
Please post in the forum for more details on the distinction.