[django-modeltranslation] r175 committed - Edited wiki page InstallationAndUsage through web user interface.

[django-mode...@googlecode.com]

Revision: 175
Author: esc...@gmail.com
Date: Fri Oct 12 06:43:26 2012
Log: Edited wiki page InstallationAndUsage through web user interface.
http://code.google.com/p/django-modeltranslation/source/detail?r=175

Modified:
/wiki/InstallationAndUsage.wiki

=======================================
--- /wiki/InstallationAndUsage.wiki Wed Jul 11 15:42:37 2012
+++ /wiki/InstallationAndUsage.wiki Fri Oct 12 06:43:26 2012
@@ -19,7 +19,6 @@
* Installation
* Configure the project's `settings.py`
* Registering models and their fields for translation
- * Autoregister translation files
* Changes automatically applied to the model class
* Accessing translated and translation fields
* Rules for translated field access
@@ -120,7 +119,11 @@

`Modeltranslation` officially supports `CharField` and `TextField`.

-In most cases subclasses of these fields will work fine, too. Other fields
aren't supported and will throw an `ImproperlyConfigured` exception.
+*New in 0.4*
+
+Support for `FileField` and `ImageField`.
+
+In most cases subclasses of the supported fields will work fine, too.
Other fields aren't supported and will throw an `ImproperlyConfigured`
exception.

The list of supported fields can be extended. Just define a tuple of field
names in your settings.py like this:

@@ -171,7 +174,7 @@

== Changes automatically applied to the model class ==

-After registering the `News` model for transaltion an SQL dump of the News
app will look like this:
+After registering the `News` model for translation an SQL dump of the News
app will look like this:

{{{
$ ./manage.py sqlall news
@@ -437,7 +440,7 @@

= Caveats =

-Consider the following example (assuming the default lanuage is `de`):
+Consider the following example (assuming the default language is `de`):

{{{
>>> n = News.objects.create(title="foo")