Hi James. James Gardner wrote: > The translation should occur at run time so this shouldn't be a problem. > How are you doing the translation? > On closer inspection it doesn't seem to be a problem. I was thinking that the pre-compiled templates were what was being sent to the browser. My mistake. > If you are using the Pylons _() function in the template everything > should be fine surely? > All is translating fine using _() although it would be nice if there was some quick way to get all the strings from a template.
Another question however: Is request.environ['HTTP_ACCEPT_LANGUAGE'] the best way to get access to the languages acceptable to the browser? This is what I get when I execute the above:- en-GB,en;q=0.9,en-us;q=0.8,en-US;q=0.6,ar-AE;q=0.5,ar;q=0.4,en-gb;q=0.3,en;q=0.1 Is there a further breakdown or list or should I parse the line manually? request.environ.languages returing a list would be cool. The list for the above might look like ['en-GB','en',en-us','en-US','ar-AE','ar','en-gb'] leaving off the duplicate 'en' off the end. Uwe --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
