Thanks for the suggestions. > * Write messages in Turkish and provide an English translation for the > projects that need it, but not for this one (untested).
This would be an interesting hack but there already exists a Turkish translation. Reversing it would be a burden. Also, it wouldn't solve the case for preset messages like form validation error messages. > * Hack this specific django installation to always return LANGUAGE_CODE > in get_language_from_request. I've tested this, it works. A better way Maintenance nightmares > would be to use smth. like FORCE_LANGUAGE if set, otherwise fall back > to the stuff django does now. Then you can use the same django > installation for different projects. I agree. It would be great to have an option in the settings file. I posted thşs suggestion in the on-going discussion on the upcoming django release: http://groups.google.com/group/django-users/browse_thread/thread/287912177d469a64 Thanks, oMat > > With kind regards, > -- > Baurzhan Ismagulovhttp://www.kz-easy.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
