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

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

Revision: 151
Author: esc...@gmail.com
Date: Wed Jul 11 15:42:37 2012
Log: Edited wiki page InstallationAndUsage through web user interface.
http://code.google.com/p/django-modeltranslation/source/detail?r=151

Modified:
/wiki/InstallationAndUsage.wiki

=======================================
--- /wiki/InstallationAndUsage.wiki Tue Jul 10 08:34:13 2012
+++ /wiki/InstallationAndUsage.wiki Wed Jul 11 15:42:37 2012
@@ -58,7 +58,6 @@
# Configure your `LANGUAGES` in `settings.py`.
# Create a `translation.py` in your app directory and register
`TranslationOptions` for every model you want to translate.
# Configure the `MODELTRANSLATION_TRANSLATION_FILES` variable in your
`settings.py`.
- # Add `translator.autoregister()` to your project's `urls.py`.
# Sync the database using `manage.py syncdb` (note that this only
applies if the models registered in the `translations.py` did not have been
synced to the database before. If they did - read further down what to do
in that case.


@@ -170,23 +169,6 @@

At this point you are mostly done and the model classes registered for
translation will have been added some auto-magical fields. The next section
explains how things are working under the hood.

-=== Autoregister translation files ===
-
-Similiar to Django's admin, modeltranslation provides a mechanism to
automatically register your translation files. It has to be hooked into
your project's urls.py.
-
-{{{
-from modeltranslation import translator
-translator.autodiscover()
-
-# ...
-# Must be in in front of:
-
-from django.contrib import admin
-admin.autodiscover()
-}}}
-
-*Note*: This step is basically optional if you prefer to register your
models programmatically.
-
== 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: