I understand your point, but Django has the benefit of coming bundled with GAE, whereas Babel is an external lib that you need to import in your project, keep up to date, etc... I'll try to use what comes with GAE, and if it doesn't perform well, then maybe I'll start looking at other external libraries.
On 1 août, 10:16, Rodrigo Moraes <rodrigo.mor...@gmail.com> wrote: > On Sat, Aug 1, 2009 at 11:51 AM, Emilien Klein wrote: > > The problem I see with using Babel is that it IS an external library, > > which means that I need to integrate it with my project. What I'm > > looking for is a way to have a translated application WITHOUT having > > to install any external library... > > Without any other external library, you have 2 options: > > 1. use gettext -http://docs.python.org/library/gettext.html > 2. hack and patch django's i18n > > The problem with the 2nd option is that your app stays tied to > django's ecosystem - later you need i18n in a small project and you'll > have to add django just for it. Ok, it is a valid solution, I just > personally prefer to use a external library that is not coupled with a > bunch of unrelated things, and avoid all the monkeypatching mess. > > -- rodrigo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
