Update Changelog adn docs.

CHANGELOG.txt

@@ -10,8 +10,9 @@
   ADDED: Convenient admin classes which already contain proper Media
          definitions.
          (resolves issue #171)
-  ADDED: Only/defer methods to MultilingualManager.
-         (resolves issue #166)
+  ADDED: Only, defer, values, values_list, dates, raw_values methods to
+         MultilingualManager.
+         (resolves issue #166 adn #173)
   ADDED: Support for ForeignKey and OneToOneField.
          (thanks to Braden MacDonald and Jacek Tomaszewski,
           resolves issue #161)
@@ -35,6 +36,8 @@
           resolves issue #181 and #190)
   FIXED: Form saving when translated field is excluded (e.g. in admin)
          (resolves issue #183)
+  FIXED: Multilingual clones are Multilingual too.
+         (resolved issue #189)
 
 CHANGED: Every model's manager is patched as MultiLingual, not only objects.
          (resolved issue #198)

docs/modeltranslation/usage.rst

@@ -122,6 +122,9 @@ These manager methods perform rewriting:
 - ``filter()``, ``exclude()``, ``get()``
 - ``order_by()``
 - ``update()``
+- ``only()``, ``defer()``
+- ``values()``, ``values_list()``
+- ``dates()``
 - ``create()``, with optional auto-population_ feature
 
 In order not to introduce differences between ``X.objects.create(...)`` and ``X(...)``, model
@@ -131,6 +134,9 @@ If one wants to turn rewriting of field names off, this can be easily achieved w
 ``rewrite(mode)`` method. ``mode`` is a boolean specifying whether rewriting should be applied.
 It can be changed several times inside a query. So ``X.objects.rewrite(False)`` turns rewriting off.
 
+``MultilingualManager`` offers one additional method: ``raw_values``. It returns actual values from
+the database, without field names rewriting. Useful for checking translated field database value.
+
 Auto-population
 ***************