`render_to_kmz` can't handle non-ascii data

[jbronn]

So, say you are using the world application from the GeoDjango tutorial (​source here), and you set up the following view:

from django.contrib.gis.shortcuts import render_to_kmz
from world.models import WorldBorders

def kmz(request):
    # getting only the Åland Islands, non-ascii character in the name
    qs = WorldBorders.objects.filter(id=142).kml()
    return render_to_kmz('gis/kml/placemarks.kml',
                         { 'places' : qs})

When trying to visit this view, one gets a UnicodeEncodeError instead of a KMZ file.

Because ZipFile objects only accept byte strings, the unicode string from render_to_kml needs to be encoded properly. I assume this should be for what the users has in settings.DEFAULT_CHARSET, and the attached patch does that -- but I want to have additional eyes look this over to make sure I'm doing it right.

[jbronn]

Encode the KML as a bytestring using DEFAULT_CHARSET.

[jbronn]

(In [11527]) Fixed #11624: render_to_kmz no longer balks on non-ASCII data.

[jbronn]

(In [11575]) [1.1.X] Fixed #11624: render_to_kmz no longer balks on non-ASCII data.

Backport of r11527 from trunk.

[palewire]

Thanks for doing this. Just patched it on 1.1 and found the fix is already in the trunk. You guys rock!

[Jacob]

Milestone 1.2 deleted