#14910: I18N locale per app resolving - documentation incorrect and bug
-------------------------------------------+--------------------------------
Reporter: vanschelven | Owner: nobody
Status: new | Milestone: 1.3
Component: Internationalization | Version: 1.2
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by vanschelven):
Replying to [comment:6 ramiro]:
>
> I haven thought about the OP proposals yet, just wanted to get these
notes written down. IMHO this ticket should deal with what OP call item 1.
Item 2 should be reported and dealt in another ticket, one issue per
ticket/commit.
In that case I would suggest to adapt the documentation to reflect the
reality of the code:
1. This won't break any existing code
2. It makes more sense to have static translations than dynamic ones.
Behavior will be more reliable, debugging and testing will be easier.
--
Ticket URL: <http://code.djangoproject.com/ticket/14910#comment:7>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
