Re: Need for an internationalization/translation system not request-based

On Thu, 2009-08-13 at 10:11 +0200, Jarek Zgoda wrote: > Wiadomość napisana w dniu 2009-08-13, o godz. 09:38, przez Enrico > Sartorello: > > > Nice information, so we can go ahead working with activate() :-) > > > > Let me ask you one more question: in your code, i see you're using > > django.

Re: Need for an internationalization/translation system not request-based

Wiadomość napisana w dniu 2009-08-13, o godz. 09:38, przez Enrico Sartorello: > Nice information, so we can go ahead working with activate() :-) > > Let me ask you one more question: in your code, i see you're using > django.util.translation.get_language(), it's not a documented > function

Re: Need for an internationalization/translation system not request-based

Nice information, so we can go ahead working with activate() :-) Let me ask you one more question: in your code, i see you're using django.util.translation.get_language(), it's not a documented function and according to django policies it can be changed or removed in any new release. Perhaps it's

Re: Need for an internationalization/translation system not request-based

Wiadomość napisana w dniu 2009-08-12, o godz. 17:11, przez Andrea Zilio: > I'm sorry, can you explain a little bit this problem? Or where I can > get info about it? > > On Aug 12, 3:48 pm, Jarek Zgoda wrote: >> Wiadomość napisana w dniu 2009-08-12, o godz. 13:00, przez Enrico >> Sartorello: >> >

Re: Need for an internationalization/translation system not request-based

Wiadomość napisana w dniu 2009-08-13, o godz. 04:31, przez Malcolm Tredinnick: >> As translation.activate() is process-wide, this approach is not >> safe in multithreaded environment if using static translation (not >> request-based). > > This is not correct. The translation.activate() call is

Re: Need for an internationalization/translation system not request-based

On Wed, 2009-08-12 at 15:48 +0200, Jarek Zgoda wrote: [...] > As translation.activate() is process-wide, this approach is not > safe in multithreaded environment if using static translation (not > request-based). This is not correct. The translation.activate() call is thread-specific and defi

Re: Need for an internationalization/translation system not request-based

I'm sorry, can you explain a little bit this problem? Or where I can get info about it? On Aug 12, 3:48 pm, Jarek Zgoda wrote: > Wiadomość napisana w dniu 2009-08-12, o godz. 13:00, przez Enrico   > Sartorello: > > > i'm facing a problem developing with Django a Web Application: in > > response

Re: Need for an internationalization/translation system not request-based

Wiadomość napisana w dniu 2009-08-12, o godz. 13:00, przez Enrico Sartorello: > i'm facing a problem developing with Django a Web Application: in > response to some events (for example, after an admin action) i need to > send emails to some users of my site. > > The problem arises when i want t

Re: Need for an internationalization/translation system not request-based

Hallöchen! Enrico Sartorello writes: > [...] > > Roughly speaking i need (at least) a way to manually decide which > is the language to apply for translations. I had the same problem. My solution (not in Django) can be seen at

Need for an internationalization/translation system not request-based

Hi all, i'm facing a problem developing with Django a Web Application: in response to some events (for example, after an admin action) i need to send emails to some users of my site. The problem arises when i want these emails to be translated in any user-specific language: the Request object i h