Ticket #4814: tutorial01.diff

tutorial01.txt

@@ -494 +494 @@
 
 .. admonition:: Why ``__unicode__()`` and not ``__str__()``?
 
-        If you're familiar with Python, you might be in the habit of adding
-        ``__str__()`` methods to your classes, not ``__unicode__()`` methods.
+    If you're familiar with Python, you might be in the habit of adding
+    ``__str__()`` methods to your classes, not ``__unicode__()`` methods.
     We use ``__unicode__()`` here because Django models deal with Unicode by
     default. All data stored in your database is converted to Unicode when it's
     returned.
 
-        Django models have a default ``__str__()`` method that calls ``__unicode__()``
-        and converts the result to a UTF-8 bytestring. This means that ``unicode(p)``
-        will return a Unicode string, and ``str(p)`` will return a normal string,
-        with characters encoded as UTF-8.
+    Django models have a default ``__str__()`` method that calls
+    ``__unicode__()`` and converts the result to a UTF-8 bytestring. This means
+    that ``unicode(p)`` will return a Unicode string, and ``str(p)`` will return
+    a normal string, with characters encoded as UTF-8.
 
-        If all of this is jibberish to you, just remember to add ``__unicode__()``
-        methods to your models. With any luck, things should Just Work for you.
+    If all of this is jibberish to you, just remember to add ``__unicode__()``
+    methods to your models. With any luck, things should Just Work for you.
 
 Note these are normal Python methods. Let's add a custom method, just for
 demonstration::