"... the user is likely to see the untranslated version first" Yup - that's exactly what's happening in ie.
On Jun 5, 8:06 am, Christophe Porteneuve <[EMAIL PROTECTED]> wrote: > Adam Groves a écrit : > > > I was thinking of the benefits of using it with page caching: it would > > mean that you wouldn't need to cache for every language. > > I see very little point in that. Cache is expandable on the server > side. OTOH, translating client-side is putting way too much processing > there, and will result in detectable latencies both for loading (you're > trying to load all the languages there) and then applying the > translation (the user is likely to see the untranslated version first). > > -- > Christophe Porteneuve a.k.a. TDD > "[They] did not know it was impossible, so they did it." --Mark Twain > Email: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
