#24739: Undocumented i18n behavior change in 1.8 (or a regression)
--------------------------------------+------------------------------------
     Reporter:  drakkan               |                    Owner:  nobody
         Type:  Bug                   |                   Status:  new
    Component:  Internationalization  |                  Version:  1.8
     Severity:  Release blocker       |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------

Comment (by claudep):

 #24503 was partially related.

 What about:
 {{{
 #!diff
 diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt
 index fb0438a..c5f3e72 100644
 --- a/docs/releases/1.8.txt
 +++ b/docs/releases/1.8.txt
 @@ -1159,6 +1159,10 @@ Miscellaneous
  * :func:`django.utils.translation.get_language()` now returns ``None``
 instead
    of :setting:`LANGUAGE_CODE` when translations are temporarily
 deactivated.

 +* When a translation doesn't exist for a specific literal, the fallback
 is now
 +  taken from the :setting:`LANGUAGE_CODE` language (instead of the
 untranslated
 +  ``msgid`` message).
 +
  * The ``name`` field of
 :class:`django.contrib.contenttypes.models.ContentType`
    has been removed by a migration and replaced by a property. That means
 it's
    not possible to query or filter a ``ContentType`` by this field any
 longer.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/24739#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a888167c25f761e8ab90ece70824fe2b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to