Commit this while I'm in the middle of it because I'm really happy with it so far and I don't want to lose it. ;)

#330343, reported by fabio84 and also by epimeth in irc: Make script url valid again, I forgot that url() returns raw ampersands.

Let people pass map arrays to theme('gmap') without wrapping them in array('#settings' => ...). In theory.

* Remove references to mousewheel.js, clean up variable.
* Add support for Continuous Zoom, enabled by default.
* Add behavior flag for disabling Continuous Zoom.
* Remove workaround from may 2007 (rev 1.1.2.15) that was causing zooming problems.

* Add style keyword to the macro layer.
* Add code to merge styles in properly.
* Allow using references to styles in lines / polys.

* Delete marker associations properly.
* Join to {node_revisions} properly.
* Handle upgrading from a 5.x version after the changed I just made in that branch.

Add 'hl' parameter to allow the map to translate itself. (Part of #314777.)

Remove the markerdata hack.
Add a marker file generator and fix markers once and for all.
Add a button to the settings page to regenerate the marker cache.

#279049 reported by tormi: Use a valid variable for the author map marker. (You can now choose a marker by going to "configure" for the author map block.)

Fix minor issue with node type names. (This technically prevents XSS with content type names, but if you're giving out the ability to create / edit content types to people you don't trust, you have much bigger problems.)

Pamela Fox says to add overflow: hidden; to fix the "long copyright strings run out the left end of the map div" bug.
http://code.google.com/p/gmaps-api-issues/issues/detail?id=308

So, by popular demand, I'm adding a CSS rule for that.

Tested in Seamonkey and IE6.

Fixing align brokenness noted in comment 66 of #266595. I was treating a string as an array and accidentally stomping some css classes.

Make a slight change to how gmap element processing works. This should reduce warnings.
Add some tests.