#14974: Contrib application for i18n functions
---------------------------------------------+------------------------------
          Reporter:  marinho                 |         Owner:  nobody
            Status:  new                     |     Milestone:        
         Component:  Internationalization    |       Version:  SVN   
        Resolution:                          |      Keywords:        
             Stage:  Design decision needed  |     Has_patch:  0     
        Needs_docs:  0                       |   Needs_tests:  0     
Needs_better_patch:  0                       |  
---------------------------------------------+------------------------------
Comment (by jezdez):

 Replying to [comment:2 marinho]:
 > Of course... so, '''because''' it is not for dynamic translations,
 '''it's a problem''' to do it if the only way that the framework offers to
 do is using gettext.

 You're basically trying to justify a new feature by saying the existing
 feature doesn't cover your use case, which is a moot point in my opinion.

 > This is why I believe a backend system would help a lot, because who
 want to work with non-static translations (and at the level of model
 objects) can avoid gettext and use database or cache to do it.

 Right, I don't quite understand what you mean by backend system though. An
 explanation (on the mailing list) might help to clarify what you mean. The
 big issue I see here (at least from what I understand) is that content
 translation and translation of UI elements are completely different
 stories because the way those content types differ in structure and
 storage. Adding a backend system implies having a common API, but I don't
 see any. Can you elaborate?

 > I know that gettext is mature and fast, yet a limited sollution.

 It's not limited but really just not supposed to be used like you use.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/14974#comment:3>
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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to