On Oct 23, 3:30 pm, Jonas Obrist <ojiido...@gmail.com> wrote: > Oh... Well than consider this a 1.X suggestion. I've tried Rosetta > however it just doesn't seem to work.... Also I don't really like to use > 3rd Party apps for what I'd consider core functionality. I mean django > boasts with having excellent i18n capabilities, but when it comes to > actually translating stuff it just refers to a 3rd party app....
My understanding is that translation tools are actually quite a controversial issue within the translation community. Most translators work on more than just one piece of software - they might help out translating Django, Firefox, Emacs and a bunch of other stuff. As such, they generally have their own standard tool that they work within for managing all of their translation activity. A Django- specific tool wouldn't actually help them at all, since they wouldn't be able to use it for the other translation work that they do. As such, I don't think a single translation management tool should ever be shipped as part of Django. It's too sticky a problem, and hence is definitely best addressed by third party modules such as Rosetta. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
