Removed last vestiges of references to technical messages from documentation.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16224 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/ref/utils.txt

@@ -492,12 +492,6 @@ For a complete discussion on the usage of the following see the
      * ``False`` = left-to-right layout
      * ``True`` = right-to-left layout
 
-.. function:: get_date_formats()
-
-    Checks whether translation files provide a translation for some technical
-    message ID to store date and time formats. If it doesn't contain one, the
-    formats provided in the settings will be used.
-
 .. function:: get_language_from_request(request)
 
     Analyzes the request to find what language the user wants the system to show.

docs/topics/i18n/index.txt

@@ -88,26 +88,3 @@ way Django does translation:
       that those are as small as possible.
     * Django doesn't use ``xgettext`` alone. It uses Python wrappers around
       ``xgettext`` and ``msgfmt``. This is mostly for convenience.
-
-.. _technical-messages:
-
-Django technical message IDs
-----------------------------
-
-.. versionchanged:: 1.2
-    Starting with Django 1.2, technical message IDs are being replaced by :ref:`format-localization`
-
-Django uses technical message IDs to translate date formats and time formats.
-Technical message IDs are :term:`translation strings <translation string>` and
-can be easily recognized; they're all upper case. You don't translate the
-message ID as with other translation strings, you provide the correct local
-variant on the provided English value. The format is identical to the format
-strings used by the ``now`` template tag.
-
-For example, with ``DATETIME_FORMAT`` (or ``DATE_FORMAT`` or ``TIME_FORMAT``),
-this would be the format string that you want to use in your language. A Django
-contributor localizing it to Spanish probably would provide a ``"j N Y P"``
-"translation" for it in the relevant ``django.po`` file::
-
-    msgid "DATETIME_FORMAT"
-    msgstr "j N Y P"