Reopening this ticket because browsershots.org shows that there still may be a
few issues with IE7 rendering.  Nothing big, but I'm reassigning this to Alex so
he can give this a once-over and close it when he's satisfied that things are
where they should be.

Regenerated Deeds for all jurisdictions.  NRY made some quick fixes to mkdeeds
so that it would exit cleanly after each run and I was able to do the Deed
generation iteratively.  Closing ticket.

It'd be nice if mkdeeds returned, but I'm loathe to spend time hacking on it at
the moment since Chris is working on it's successor.

I'll try rebuilding locally; somewhat lower risk if the process goes nuts.

Fail.  Because mkdeeds never returns (it's necessary to Ctrl-z then kill %1)
looping over the jurisdictions doesn't work.  It just hangs after Deeds are
generated for first jurisdiction in the list.  I had been hoping that the
following little script would work.  Nathan, any ideas on how to proceed?  It'd
be nice if mkdeeds actually returned:

#!/usr/bin/python

from xml.dom import minidom
import subprocess

dom = minidom.parse('./cc.license_/cc/license/license_xsl/licenses.xml')
elems = dom.getElementsByTagName('jurisdiction-info')
jurisdictions = [elem.attributes['id'].value for elem in elems]

for jurisdiction in jurisdictions[1:]:
	print "Generating Deeds for " + jurisdiction
	subprocess.call(['./bin/mkdeeds', '-j %s' % jurisdiction, '-o
../../../license.rdf/trunk/licenses/'])

I tried rebuilding all the Deeds late last week in a screen session on a6, but I
was rudely awakened in the middle of the night by an SMS from Nagios notifying
me that learn.creativecommons.org was down.  Turns out that mkdeeds was using
1.2G of memory and causing backups on a6.

I'm going to take a different tack on this, and setup some sort of for;do;done
that loops over the jurisdiction codes.  This should ensure that mkdeeds is
stopped and started fresh for each jurisdiction thereby preventing it from
running out of control.

Just assuming you were busy with other things before then.

Why should I wait until the campaign launch?

We just need to regenerate *all* the deeds.  This sort of sucks since we've been
doing it incrementally, but in a way I suppose it's good; brings them all to the
same state.

Nathan, can you plan to do this once we launch the campaign?  We'll probably
have new deeds for new-ish locales so we'll have to svn add those.

Flag displays correctly, above the section banner, on staging (e.g. http://staging.creativecommons.org/licenses/by-nc/3.0/no/) -- could be out of date 
CSS on production, or a deed html change that isn't live yet.

Flags don't seem to be displaying correctly on Deeds when using IE7.  Here's an
example link:

http://creativecommons.org/licenses/by-nc-nd/2.5/hu/

In that particular Deed IE7 seems to place the flag behind the section that it's
supposed to appear in, such that only the red strip on the flag is visible.